Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Date: Fri, 22 Feb 2013 16:02:31 -0500
From: Chip Childers <chip.childers@sungard.com>
To: cloudstack-dev@incubator.apache.org
Subject: Re: [DRAFT] Graduation resolution / IPMC vote email draft for
 discussion
Message-ID: <20130222210231.GJ58000@USLT-205755.sungardas.corp>
References: <20130221172151.GC90611@USLT-205755.sungardas.corp>
 <61F61BE4-34B6-4B16-BF46-D9003F8CAC99@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <61F61BE4-34B6-4B16-BF46-D9003F8CAC99@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

I can always count on Sebastien to review things like this (thanks!)...

On Fri, Feb 22, 2013 at 09:53:30PM +0100, Sebastien Goasguen wrote:
> inline
> On Feb 21, 2013, at 6:21 PM, Chip Childers <chip.childers@sungard.com> wrote:
> 
> > Hi all,
> > 
> > I feel like we have reached a consensus around the idea of graduating [1].  
> > If this is incorrect, or anyone feels that their perspective or concerns 
> > were not addressed, please say so.
> > 
> > Continuing down the path towards an eventual graduation, I took the
> > liberty of drafting the vote email that we would send to the IPMC,
> > including the draft graduation resolution that would be sent to the
> > board if the IPMC approves of our graduation.
> > 
> > I'd like to get your comments and suggested changes...
> > 
> > Keep in mind that there are several places where we have placeholders in
> > this draft.  That includes committer and PMC numbers, the PMC chair
> > name, and several reference links that need to be added as we finalize
> > things.
> > 
> > The pre-amble to the IPMC vote is totally up to us, although I modeled
> > it after another project's graduation vote thread.  Comments welcome on
> > how we express our readiness to the IPMC!
> > 
> > The graduation resolution is based on a template, but the relevant
> > portion to review is how I chose to scope the project.  Namely this
> > text:
> > 
> >> related to the development of software to deploy and manage large
> >> networks of virtual machines, as a highly available, highly scalable
> >> Infrastructure as a Service (IaaS) cloud computing platform.
> > 
> > I stole this from our project's home page ;)
> > 
> > Information from the incubator on how to best describe the project
> > within a charter is at [2].
> > 
> > [1] http://markmail.org/message/3nluchj5q5waguws
> > [2] http://incubator.apache.org/guides/graduation.html#tlp-resolution
> > 
> > Here's the draft vote email and resolution:
> > 
> > *************************************************
> > 
> > Apache CloudStack entered the Incubator in April of 2012. We have made
> > significant progress with the project since moving over to Apache. We have
> > XX committers and XX PPMC members listed on our status page at [1], not including 
> > the 8 mentors that helped guide our community through incubation.  XX of the 
> > committers and XX of the PPMC members were added after the podling was
> > formed. Additionally, XX of our mentors will be remaining with the
> > project as it transitions into a TLP, with XX transitioning into the PMC
> > and XX deciding to only remain as committers on the project.
> > 
> > We have verified that Apache CloudStack is a suitable name [2], and the
> > CloudStack marks have been donated from Citrix to the ASF.
> > 
> 
> marks or brands ?

It's technically a "word mark" to the USPTO:

http://tess2.uspto.gov/bin/showfield?f=toc&state=4006%3Ax29ohx.1.1&p_search=searchss&p_L=50&BackReference=&p_plural=yes&p_s_PARA1=&p_tagrepl~%3A=PARA1%24LD&expr=PARA1+AND+PARA2&p_s_PARA2=cloudstack&p_tagrepl~%3A=PARA2%24COMB&p_op_ALL=AND&a_default=search&a_search=Submit+Query&a_search=Submit+Query

And the above statement is in anticipation of that transfer, which has
not yet happened.

> 
> > We completed two releases (Apache CloudStack 4.0.0-incubating and Apache 
> > CloudStack 4.0.1-incubating) and are currently preparing for two more (4.0.2 
> > and 4.1.0).
> > 
> > The community of Apache CloudStack is active, healthy, and growing and has
> > demonstrated the ability to self-govern using accepted Apache practices.
> > 
> We have created bylaws and posted them on our wiki [5].
> 
> > The Apache CloudStack community voted overwhelmingly to graduate [3],
> > collecting XXXXX binding votes from our mentors and IPMC members XXXX. You 
> > can view the discussion at [4].
> > 
> Regarding [3], I just want to check that we have not yet voted on graduation, correct ?
> Therefore the "overwhelming" is in anticipation of the vote result ?
> 

I'm a "glass half full" kind of guy!

Yes, that's just anticipation.  I'd change it when we actually vote and
have results.

> > 
> > 
> > Please cast your votes:
> > 
> > [ ] +1 Graduate Apache CloudStack from Apache Incubator
> > [ ] +0 Indifferent to graduation status of Apache CloudStack
> > [ ] -1 Reject graduation of Apache CloudStack from Apache Incubator because...
> > 
> > We'll run the vote for at least 72 hours (closing at the earliest at
> > XXXX.)
> > 
> > [1] http://incubator.apache.org/projects/cloudstack.html
> > [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
> > [3] *insert graduation vote thread link*
> > [4] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E
> > [5] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
> > 
> > X. Establish the Apache CloudStack Project
> > 
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to the development of software to deploy and manage large
> > networks of virtual machines, as a highly available, highly scalable
> > Infrastructure as a Service (IaaS) cloud computing platform.
> 
> What happens if CloudStack starts to do more than manage large networks of VMs ?
> Pure theoretical speculation on my part.

Very good point.  We do bare-metal already.

How about:

"software to deploy and manage compute, storage and network services, as
a highly available, highly scalable Infrastructure as a Service (IaaS)
cloud computing platform"

Thoughts?

> 
> > 
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache CloudStack Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> > 
> > RESOLVED, that the Apache CloudStaack Project be and hereby is responsible
> 
> CloudStack

Ack

> 
> > for the creation and maintenance of software related to development of
> > software to deploy and manage large networks of virtual machines, as
> > a highly available, highly scalable Infrastructure as a Service (IaaS)
> > cloud computing platform.
> > 
> > RESOLVED, that the office of "Vice President, Apache CloudStack" be and
> > hereby is created, the person holding such office to serve at the direction
> > of the Board of Directors as the chair of the Apache CloudStack Project, and to
> > have primary responsibility for management of the projects within the scope
> > of responsibility of the Apache CloudStack Project; and be it further
> > 
> > RESOLVED, that the persons listed immediately below be and hereby
> > are appointed to serve as the initial members of the Apache CloudStack Project:
> > 
> > * *insert PMC list*
> > 
> 
> Committers won't be considered members of the "Project" ?
> 

For the purpose of the board resolution, only the PMC is listed.  This
is a standard practice for these resolutions.

> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that XXXXXXXXX be appointed to the
> > office of Vice President, Apache CloudStack, to serve in accordance with and
> > subject to the direction of the Board of Directors and the Bylaws of the
> > Foundation until death, resignation, retirement, removal
> > or disqualification, or until a successor is appointed; and be it further
> > 
> > RESOLVED, that the initial Apache CloudStack PMC be and hereby is tasked
> > with the creation of a set of bylaws intended to encourage open development
> > and increased participation in the Apache CloudStack Project; and be it further
> > 
> We will have new bylaws after graduation ?

I hope not.  My understanding is that we have already created them, and
therefore we can take them with us.

> 
> > RESOLVED, that the Apache CloudStack Project be and hereby is tasked with
> > the migration and rationalization of the Apache Incubator CloudStack podling;
> > and be it further
> > 
> > RESOLVED, that all responsibilities pertaining to the Apache
> > Incubator CloudStack podling encumbered upon the Apache Incubator Project are
> > hereafter discharged.
> > 
> 
>