I've applied these changes (with a few tweaks after our discussion here), and moved the trademark guidelines to: http://cloudstack.apache.org/trademark-guidelines.html
On Wed, May 22, 2013 at 11:25:41AM -0400, Chip Childers wrote: > Hi all, > > The last ASF board meeting dissolved the ConCom PMC, and has split out > responsibilities to other parts of the foundation. This impacts us > specifically, in that approvals for the use of our Brand (including > events) are primarily the responsibility of the PMC. > > That being said, we are now being asked to switch from concom approval > to a trademarks@ lazy consensus. Guidance from the board was to change > our trademark guidelines to require trademarks@ lazy concensus, and that > the PMC was actually accountable for all of these approvals. > > I am proposing the following changes to our current guidelines [1] > (provided in diff format for easily understanding what I'm proposing to > change). Please provide any comments, but hearing none, I'll make the > changes to the guidelines early next week. > > > diff --git a/trademarkguidelines.wiki b/trademarkguidelines.wiki > index f3fcb8e..81f583a 100644 > --- a/trademarkguidelines.wiki > +++ b/trademarkguidelines.wiki > @@ -35,16 +35,21 @@ h2. Sponsoring Events: > > Sponsoring events can provide good visibility for the project, however it > frequently requires funds that the project does not have access to. Many > outside organizations wish to provide this type of visibility. > > -In addition to gaining the approval of ConCom the following is required: > +The following is required: > > -* Sponsorship discussed and approved on the cloudstack-marketing list. > Approval is given by the PMC. > +* Sponsorship discussed and approved on the [email protected] > list. Approval is given by the PMC. > +* After approval from the PMC, the sponsorship approval will be forwarded to > [email protected] by the PMC, followed by a 72 hour waiting period in > case of objections from that ASF committee. > * 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] list. > + > h2. CloudStack Specific Conferences: > > -In addition to seeking permission from ConCom and other general ASF > guidelines the additional guidelines for Apache CloudStack > -* Project approval from the PMC is needed. > +The following is required: > + > +* Discussed and approved on the [email protected] list. > Approval is given by the PMC. > +* After approval from the PMC, the event approval will be forwarded to > [email protected] by the PMC, followed by a 72 hour waiting period in > case of objections from that ASF committee. > * Membership on committees deciding content should be open to any Committer. > > h2. Meetup groups, hackfests, barcamps, Birds of a Feather, and other small > events. > > > > > -chip > > [1] > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Trademark+Guidelines >
