Countersignature Copyright Assignment Agreement Made Easy

Countersignature copyright assignment agreement

hi it's mark Collier with the OpenStack foundation and today we're gonna talk a little bit about OpenStack and the trademark and the logo and the various marketing assets and some of the marketing programs that are available to commercial companies as well as some of the rules of the road if you want to use the OpenStack trademark in a non-commercial setting and if you want to follow me on Twitter I'm Sparky Collier and with that I will give you my very short disclaimer which is that this presentation is intended to really kind of address some of the frequently asked questions about the trademark the policy some of the licensing programs if you really want to get into every detail of course you need to go to the website and read the policies and the license agreements that are posted there you can also contact logo at OpenStack org so this is not a substitute for reading every word of the agreements but hopefully it's a pretty good start so why are people interested in the OpenStack trademark and in talking about OpenStack well first of all there's a ton of interest in OpenStack if you see over time it's been growing this is using Google Trends so lots and lots of people are interested in learning about OpenStack and deploying OpenStack using it potentially you know buying different types of OpenStack products and services and that interest is very global so we see all over the world lots of user groups popping up there's over 40 user groups now all over the world so very exciting to see all this interest and there's a large ecosystem of companies here just a few of them that have started to build products and services and actually deliver those to the market that are based on OpenStack or compatible OpenStack and so with all this interest and all this activity we do have the potential for there to be confusion in the market and so when we design the trademark policy the idea here is to really first of all make it easy efore people in the community to understand and use you know understand how to use the OpenStack trademark or the OpenStack marks the right way and have policies there for the occasional bad actors and then when it comes to the products that are based on OpenStack or compatible with OpenStack we want to really try to be clear and communicate clearly and help people identify these OpenStack products or OpenStack powered products in the market sort of know what to expect when they when they purchase those and install them deploy them you know face a cloud on products that have the OpenStack name and so with so many different people involved it is important to have some clear communication around it so the primary logo is the one you've probably seen the most often here on the screen and you know this is really widely available for non-commercial use and so if you're organizing a user group meetup you're talking about OpenStack on your blog and your contribution about a meet-up that you attend it or some code that you contributed it's not really connected to a specific product so it's really just evangelizing OpenStack or your participation in it as a member of the community then it's absolutely okay to use the logo and we encourage you to do that and we've tried because we do get questions on this quite a bit in the policy itself to give a few examples of things that are allowed so that people don't feel like they're gonna get caught up inadvertently you know by violating that policy but again OpenStack dot org slash brand is really always the best place to start if you're looking for those resources to kind of check or you can email us logo at OpenStack org so a lot of what I want to talk about today is really geared towards people that have OpenStack related products and so for those commercial situations we've created some Co marketing programs that include licenses to if ik logos that are designed to be easily identifiable and really also provide guidelines for how the word OpenStack can be used when it comes to the name of name of your product and so before I dive into those in detail let me just give you a quick example of some do's and don'ts when you're thinking about you know both the commercial and non-commercial use you're basically just looking for some examples perhaps of what you what isn't is not allowed under these policies so certainly we want companies to talk about OpenStack and there are appropriate ways to do that depending on if you're marketing your product as product marketing or if you're actually just talking about your community involvement so that would be an example of a do so two thumbs up there an example of a don't would be registering domain names that have OpenStack or social media handles that have the word OpenStack in it another example would be when you're talking about your product and you're doing you know outbound marketing or product marketing we ask that you use the official OpenStack names if you're talking about the components or projects if you will within OpenStack such as OpenStack object storage or OpenStack networking as opposed to the project code names that is also something to keep in mind other things to to do and don't do again open email us or check the website if you're not sure you know just taking a random guess probably not the best way to get the right answer buying keywords is also something that if you look at the policy is not allowed under the trademark policy on the website for example Google keywords so you know these are some frequently asked questions we see we again just want you to contact us check out the assets on the site and I'll show you in a bit a little bit exactly you know how easy it is to find the different information that you may find but getting back to the family of logos for product marketing so these are for commercial use and you'll see that there's a number of different programs here they all have a similar look to them you know certainly similar to the primary logo but we tried to make it distinct enough so that as a customer out there user who's looking at to you know purchase your product perhaps they they know you know what they're they can recognize these logos as being part of these commercially licensed programs and so within these five programs that I've shown you the logos for here they kind of fall into two major buckets or two camps one on the left side you have the programs that are specific to your product if it incorporates the OpenStack software so if your software ships with OpenStack or it's a cloud that's powered by OpenStack to your you're actually using the the software then you know those would fall on this examples on the left and those are products that incorporate the software both compute and object storage and we do ask that they be part of a recent releases so one of the two most recent releases or you know associated milestones for people that are on the cutting edge and doing the continuous deployment thing and then of course exposing the OpenStack API is is important and this is all part of that setting expectations for customers when they see this incredible number of choices out there for OpenStack power products from this diverse ecosystem they can know what to expect when they see these logos and then on the right side this is the built for OpenStack logo and that's really for everything else that doesn't use the software in in the product so maybe a management tool we've also used this to date to kind of cover service businesses of professional services training and you know in the future there may be some other programs that that we can develop that are more specific to these these other types of businesses in the eCos like training but for right now this is the the set of programs we have and kind of what they're targeted for so hopefully if you have one of these products or you're playing to launch one you can identify which of these is the right one for you and it's probably fairly self-evident as to what these different logos are for but the OpenStack distribution is for a software distribution so you know it's roughly analogous to a Linux distribution that people are familiar with and in fact many of the major Linux distributions are also distributing OpenStack so that we're very excited about that a OpenStack cloud you know that particular license program or marketing program is for infrastructure as a service cloud that's powered by OpenStack and then the other two are really more for converged type products so the powered by OpenStack is for something that combines hardware and software as an appliance or a converged model and then the storage power by OpenStack is really for products that are just using the object storage component of OpenStack because that is a a piece of OpenStack that is very useful on its own we do see a number of products out there that are just purely targeted at object storage to address that particular use case and so we created a separate logo for that just to be clear that when you buy that OpenStack product it's really a storage oriented product so there's no confusion and then I mentioned before the built for OpenStack is for management tools and maybe you have a piece of hardware that you've tested with OpenStack it's designed to work with it but you're not actually shipping OpenStack with your product but that's tested to work with it so it's kind of a catch-all for a lot of other different types of products and services including again professional services and training so in this slide I just talk about a few of the other requirements that I think are important to know and again it kind of goes back to the the frequently asked questions I'd like to try to address here so that you know before you pour over the various legal agreements kind of you know what some of the highlights are so again on the products that are incorporating OpenStack software these particular license programs or marketing programs are available to any of the companies that are corporate sponsors or gold or platinum members of the foundation and so if you're not one of those companies you want to participate in this you can certainly sign up OpenStack org slash join there is a one-year agreement that goes with these these different products a licensing agreement there's product naming guidelines and other details and it's all we also ask that you clearly state which components and versions you're using so that when a customer is comparing different OpenStack products they're not confused and what you'll see here in the middle is another really just kind of a mock-up for illustrative purposes what we lovingly called the nutrition label and this is really just an example of how you might clearly state which component versions you're using with your product this again is just a mock up here for to kind of show you what we're thinking in terms of you know one way you could make that clear to users and we use of course grizzly is an example which is which is still in development but that gives you some idea of what we mean by you know letting customers know what to expect and then on the built for OpenStack logo on the far right this one also has you know naming guidelines and the license agreement associated with it however in this particular case you're not required to be a corporate sponsor or gold or platinum member and the reason for that was that this is such a broad category and such a huge ecosystem of really anything in IT world it might be targeted at the data center we wanted to make that really accessible for just a whole variety of products that might want to interface or plugin to OpenStack and and not make that too hard to get into and this slide here is really just a summary of all the information that we've reviewed kind of shows you all the different commercial use programs side by side a little bit of an eye chart but you know we want to make this deck available and if you're ever wanting to sort of have a one page cheat sheet it does help because you know they're all quite similar looking but there are some you know subtle differences in in the way the product naming rights work and so forth to have it all kind of side by side is helpful and in terms of how you would participate so first of all you know understanding which program is right for you if there is a program you're wanting to participate in that requires you know being a corporate sponsor or a gold or platinum member of the foundation then you can again see this URL here make a note of it open stack that org slash join you'll want to go in to the website and actually assignment the agreement and then as you work to incorporate the the logos associated with it in into your product marketing following the various guidelines we would love for you to actually contact us at the foundation to help with any marketing launch you may have or other product marketing type activities we think we can we can help a lot of companies we've done this quite effectively in the past and if you are leading up to a launch and you want to you know not just you know get the logos to be part of the program but actually have our help in promoting your launch we're happy to do that and and then last but not least I will leave you with these these URLs again as well as letting you know that logo at OpenStack org is a great place to just send your general questions and then before I let you go I'm actually going to show you the website I was just talking about OpenStack org slash brand so as you can see there's a lot of content here that sort of describes the different program so you can see that there's information about the non-commercial use logo the guidelines on the left-hand nav we have the trademark policy itself the event policy so if you're wanting to throw an event if you're one of the people that post to the OpenStack blog we've got a code of conduct there and really again getting into more detail about these commercial use programs I'll show you a little quickly how it works to actually sign the agreement right here online so when you click through you'll see the restricted use of guidelines so it's important to look at the trademark policy the restricted use guidelines and of course you're gonna read all of this before you click agree and continue and then when you get to this point you will see the agreement and we're using echo sign many of you are probably familiar with echo sign we actually have recently been using it for the summit sponsorship so if you're if you have been a sponsor of our recent upcoming summit then you've probably seen this and it's this very common electronic document signing service and in this case we've actually embedded it right here on the page and so you'll go through and in this case we ask that you complete your product name or names associated with this license of course there's lots of detail you want to read and then you'll sign it and it's great for us to be able have that all online electronic so with that I will just note a couple of things once you've signed this agreement it will need to be countersigned by the foundation you will also get an email from echo sign that you need to confirm your email address if you're not if you've never used echo sign before sometimes that trips people up and then of course once the logo agreements are signed and countersigned will be in touch to actually give you access to the logos that you're looking for and to help you with your product launch if that's something you're looking for help with so again I'm mark Collier I am the CEO of the OpenStack foundation and you can follow me on twitter at Sparky Collier hope this was helpful and when in doubt check out our website thanks