Mailing-List: contact marketing-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: marketing@cloudstack.apache.org
Received-SPF: error (athena.apache.org: local policy)
Date: Fri, 31 May 2013 13:47:53 -0400
From: Chip Childers <chip.childers@sungard.com>
To: marketing@cloudstack.apache.org
Subject: Re: Event approval process changes
Message-ID: <20130531174753.GU25016@USLT-205755.sungardas.corp>
References: <20130522152541.GV56667@USLT-205755.sungardas.corp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130522152541.GV56667@USLT-205755.sungardas.corp>
User-Agent: Mutt/1.5.21 (2010-09-15)

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 marketing@cloudstack.apache.org list. Approval is given by the PMC.
> +* After approval from the PMC, the sponsorship approval will be forwarded to trademarks@apache.org 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 private@cloudstack.apache.org 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 marketing@cloudstack.apache.org list. Approval is given by the PMC.
> +* After approval from the PMC, the event approval will be forwarded to trademarks@apache.org 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
>