Per the [DISCUSS] thread from last week, here's the formal vote. I'm proposing that (1) the project take on the responsibility to manage our trademark usage approvals, and (2) that the proposed patch to the trademark guidelines should be applied in support of 1.
There is one minor edit to the patch in the DISCUSS thread: adding press@ to the intro paragraph about how to contact the project for approval. [ ] +1 - Take on this responsibility as a project and apply the proposed patch. [ ] +/-0 - No strong opinion either way [ ] -1 - Don't take on tm approval and / or don't apply the proposed patch. -chip
Index: trademark-guidelines.mdtext =================================================================== --- trademark-guidelines.mdtext (revision 1609716) +++ trademark-guidelines.mdtext (working copy) @@ -29,13 +29,26 @@ The Apache Software Foundation has an established trademark policy ([http://www.apache.org/foundation/marks](http://www.apache.org/foundation/marks)) -that when in conflict should be considered the canonical standard. +that when in conflict should be considered the canonical standard (with one +exception noted below). + However, the Apache Software Foundation has given the responsibility for brand management to the project's Project Management Committee. Thus this document should be taken as additive to the Apache Software Foundation's trademark guideline. Nothing contained herein provides an -exception to those guidelines. +exception to those guidelines (again, with one exception below). +*Exception:* The Apache CloudStack PMC is the contact point for all requests +related to the use of the CloudStack Trademarks. In places where the Apache +Software Foundation's formal trademark usage documentation and policies specify [email protected], requesters should use [email protected] or [email protected]. In places where the Apache Software +Foundation's policies specify that explicit approval must come from the VP +Brand Management, requesters will be given authoritative approval from a +representative of the Apache CloudStack PMC instead. The Apache Software +Foundation has delegated approval authority to the Apache CloudStack PMC, +specifically related to the CloudStack Trademarks. + ## Mark usage ### Wordmark @@ -80,21 +93,17 @@ The following is required: -* Sponsorship discussed and approved on the [[email protected]](mailto:[email protected]) list. -* Requests for approval will be acknowledged by a member of the PMC, forwarded to [[email protected]]([email protected]), and approved automatically if no issues are raised 72 hours after acknowledgement. +* Sponsorship discussed and approved on the [[email protected]](mailto:[email protected]) mailing list. +* Requests for approval will be acknowledged by a member of the PMC and approved automatically if no issues are raised 72 hours after acknowledgement. * Sponsorship must be provided with no additional affiliation - and only project provided marks used. * At least one committer must be planning to represent the project. -If desired by the funding organization, the sponsorship may be -discussed on the [[email protected]](mailto:[email protected]) -list, which will follow the same process listed above. - ### CloudStack Specific Conferences: The following is required: -* Project approval from the PMC is needed. -* Requests for approval will be acknowledged by a member of the PMC, forwarded to [[email protected]]([email protected]), and approved automatically if no issues are raised 72 hours after acknowledgement. +* Project approval from the PMC is needed via the [[email protected]](mailto:[email protected]) mailing list. +* Requests for approval will be acknowledged by a member of the PMC and approved automatically if no issues are raised 72 hours after acknowledgement. * Membership on committees deciding content should be open to any Committer. * At least one committer must be planning to attend the event. @@ -108,9 +117,20 @@ ## Non-software goods -* Without explicit written permission, goods bearing any of the CloudStack marks may not be sold. -* Designs for non-software goods require both PMC approval and approval from [[email protected]](mailto:[email protected]). +Creating non-software goods (e.g.: stickers, event give-aways, etc...) to help +promote the Apache CloudStack project is encouraged. However, there are some +requirements that must be met prior to producing the goods. Additionally, +goods bearing any of the CloudStack marks may not be sold without explicit +written permission. +The following is required: + +* The design (mock-up) must be shared with the CloudStack PMC via [[email protected]](mailto:[email protected]). +* Requests for approval will be acknowledged by a member of the PMC and approved automatically if no issues are raised 72 hours after acknowledgement. +* Permission may be granted for requests that are intended to promote the Apache CloudStack project. +* Permission will likely *not* be granted for requests that are indented to, or percieved to by the PMC, reflect negatively on Apache CloudStack. +* Approval may be contingent on specific requested changed in how the mark(s) are applied. + ## Websites No additional guidelines are required above and beyond the
