cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chipchild...@apache.org
Subject svn commit: r1650901 - in /cloudstack/site/trunk/content: bylaws.mdtext trademark-guidelines.mdtext
Date Sun, 11 Jan 2015 14:30:45 GMT
Author: chipchilders
Date: Sun Jan 11 14:30:44 2015
New Revision: 1650901

URL: http://svn.apache.org/r1650901
Log:
Very belated commit of TM Usage and project bylaw changes voted on back in July 2014.

TM Guideline changes VOTE:
Message-ID: <20140714164546.GU72090@Chips-MacBook-Air.local>

Bylaw changes VOTE:
Message-ID: <20140714163911.GT72090@Chips-MacBook-Air.local>


Modified:
    cloudstack/site/trunk/content/bylaws.mdtext
    cloudstack/site/trunk/content/trademark-guidelines.mdtext

Modified: cloudstack/site/trunk/content/bylaws.mdtext
URL: http://svn.apache.org/viewvc/cloudstack/site/trunk/content/bylaws.mdtext?rev=1650901&r1=1650900&r2=1650901&view=diff
==============================================================================
--- cloudstack/site/trunk/content/bylaws.mdtext (original)
+++ cloudstack/site/trunk/content/bylaws.mdtext Sun Jan 11 14:30:44 2015
@@ -100,6 +100,8 @@ repository, mailing lists, websites.
 
 2.4.1.7. Maintaining these bylaws and other guidelines of the project.
 
+2.4.1.8. Managing and protecting the project's trademarks and brand.
+
 2.4.2. Membership of the PMC is by invitation only and must be approved by a
 lazy consensus of active PMC members.
 
@@ -232,7 +234,8 @@ decision making process.
 3.4.2. Non-Technical Decisions
 
 A non-technical decisions is any decision that does not involve changes to the
-source code that we distribute in our official releases.
+source code that we distribute in our official releases (excluding questions of 
+trademark usage).
 
 Non-technical decisions should normally be made by the entire community using
 discussion-lead consensus-building, and not through formal voting.
@@ -330,6 +333,50 @@ Lazy majority of active PMC members
 Any active committer or PMC member may call a vote. The vote must occur on the
 project development mailing list.
 
+3.4.11. Trademark Usage Approvals
+
+Our project maintains a formal Trademark Usage Guidelines document, which
+serves as a additive reference to the Apache Software Foundation's trademark
+policies. The Apache CloudStack PMC has had approval authority delegated to it
+for requests from third parties to use our trademarks. It is the PMC's
+responsibility to provide these approvals, and to ensure that any requests
+are in compliance with both the project and the foundation's trademark
+usage policies.
+
+The CloudStack Trademark Guidelines specify how a requestor is expected to
+request permission for usage of the trademarks.
+
+The process of approval will typically be as follows:
+
+* A request is made that includes the required information for the PMC to make 
+a decision.
+* A PMC member reviews the request and provides an initial acknowledgement 
+response to the requester.
+* If no PMC member raises a concern after 72 hours, the requester can assume 
+approval.
+
+In situations where a concern is raised, the PMC member is expected inform the
+requster that there is some discussion that needs to be had prior to approval
+from the PMC.  This notice serves to end the assumed approval after 72 hours.  
+
+After raising a concern, the PMC member in question is required to forward the
+concern to private@cloudstack.apache.org, explaining the issue that they have
+with the request.  The use of private@cloudstack.apache.org for discussing the
+request is to allow the PMC to deliberate without confusing the requester, and
+to ensure that a formal approval or denial is clear at the end of the
+discusion.
+
+The PMC will then attempt to achieve consensus on how the request for approval
+will be answered.  The requester may be asked for more information to help the
+PMC make a decision, may be asked to make a change to the proposal in order to
+gain approval, or may have their request be denied.
+
+If consensus is not achieved within the PMC by discussion, then a formal VOTE
+can be called as a Lazy 2/3 majority of voting PMC members.
+
+Votes related to trademark usage approvals may be performed on the
+private@cloudstack.apache.org mailing list.
+
 3.5. Voting Timeframes
 
 Formal votes are open for a period of at least 72 hours to allow all active

Modified: cloudstack/site/trunk/content/trademark-guidelines.mdtext
URL: http://svn.apache.org/viewvc/cloudstack/site/trunk/content/trademark-guidelines.mdtext?rev=1650901&r1=1650900&r2=1650901&view=diff
==============================================================================
--- cloudstack/site/trunk/content/trademark-guidelines.mdtext (original)
+++ cloudstack/site/trunk/content/trademark-guidelines.mdtext Sun Jan 11 14:30:44 2015
@@ -29,12 +29,25 @@ loss of the marks.
 
 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
+trademarks@apache.org, requesters should use press@cloudstack.apache.org or
+private@cloudstack.apache.org.  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
 
@@ -80,21 +93,17 @@ Many outside organizations wish to provi
 
 The following is required:
 
-* Sponsorship discussed and approved on the [marketing@cloudstack.apache.org](mailto:marketing@cloudstack.apache.org)
list.
-* Requests for approval will be acknowledged by a member of the PMC, forwarded to [trademarks@apache.org](trademarks@apache.org),
and approved automatically if no issues are raised 72 hours after acknowledgement.
+* Sponsorship discussed and approved on the [press@cloudstack.apache.org](mailto:press@cloudstack.apache.org)
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 [private@cloudstack.apache.org](mailto:private@cloudstack.apache.org) 
-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 [trademarks@apache.org](trademarks@apache.org),
and approved automatically if no issues are raised 72 hours after acknowledgement.
+* Project approval from the PMC is needed via the [press@cloudstack.apache.org](mailto:press@cloudstack.apache.org)
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,8 +117,19 @@ Local area user events are encouraged.
 
 ## 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 [trademarks@apache.org](mailto:trademarks@apache.org).
+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 [press@cloudstack.apache.org](mailto:press@cloudstack.apache.org).
+* 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
 



Mime
View raw message