[RESULT] [IP CLEARANCE] CloudStack Terraform Provider project contribution

[paul_a]

 

There were no -1 votes, therefore this IP clearance vote passes by lazy

consensus. Thank you!

 

 

 

Kind regards

 

Paul Angus

 

From: pau...@apache.org <mailto:pau...@apache.org>  mailto:pau...@apache.org> > 
Sent: Tuesday, July 20, 2021 9:51 AM
To: general@incubator.apache.org <mailto:general@incubator.apache.org> 
Cc: Rohit Yadav mailto:rohit.ya...@shapeblue.com> >
Subject: [IP CLEARANCE] CloudStack Terraform Provider project contribution

 

Hi Incubator PMC,

 

The Apache CloudStack PMC has voted to accept the donation of " CloudStack
Terraform Provider", which

is a Terraform provider for CloudStack [1].

 

Please vote to accept this contribution.

 

This is a lazy consensus majority vote, per the IP clearance process [2],

open for at least 72 hours.

 

Apache CloudStack PMC

 

[1] https://incubator.apache.org/ip-clearance/cloudstack-terraform.html

 

[2] http://incubator.apache.org/ip-clearance/

 

 

Many Thanks

 

Paul Angus

 

[RESULT] [IP CLEARANCE] CloudStack Go SDK project contribution

[paul_a]

 

There were no -1 votes, therefore this IP clearance vote passes by lazy

consensus. Thank you!

 

 

Kind regards

 

Paul Angus

 

From: pau...@apache.org <mailto:pau...@apache.org>  mailto:pau...@apache.org> > 
Sent: Tuesday, July 20, 2021 9:51 AM
To: general@incubator.apache.org <mailto:general@incubator.apache.org> 
Cc: Rohit Yadav mailto:rohit.ya...@shapeblue.com> >
Subject: [IP CLEARANCE] CloudStack Go SDK project contribution

 

Hi Incubator PMC,

 

The Apache CloudStack PMC has voted to accept the donation of " CloudStack
Go SDK", which

is a web based API for CloudStack [1].

 

Please vote to accept this contribution.

 

This is a lazy consensus majority vote, per the IP clearance process [2],

open for at least 72 hours.

 

 

Apache CloudStack PMC

 

[1] https://incubator.apache.org/ip-clearance/cloudstack-go-sdk.html

 

[2] http://incubator.apache.org/ip-clearance/

 

 

 

Many Thanks

 

Paul Angus

 

RE: [IP CLEARANCE] CloudStack Terraform Provider project contribution

[paul_a]

There were no -1 votes, therefore this IP clearance vote passes by lazy

consensus. Thank you!

 

 

 

Kind regards

 

Paul Angus

 

From: pau...@apache.org  
Sent: Tuesday, July 20, 2021 9:51 AM
To: general@incubator.apache.org
Cc: Rohit Yadav 
Subject: [IP CLEARANCE] CloudStack Terraform Provider project contribution

 

Hi Incubator PMC,

 

The Apache CloudStack PMC has voted to accept the donation of " CloudStack
Terraform Provider", which

is a Terraform provider for CloudStack [1].

 

Please vote to accept this contribution.

 

This is a lazy consensus majority vote, per the IP clearance process [2],

open for at least 72 hours.

 

Apache CloudStack PMC

 

[1] https://incubator.apache.org/ip-clearance/cloudstack-terraform.html

 

[2] http://incubator.apache.org/ip-clearance/

 

 

Many Thanks

 

Paul Angus

 

RE: [IP CLEARANCE] CloudStack Go SDK project contribution

[paul_a]

There were no -1 votes, therefore this IP clearance vote passes by lazy

consensus. Thank you!

 

 

Kind regards

 

Paul Angus

 

From: pau...@apache.org  
Sent: Tuesday, July 20, 2021 9:51 AM
To: general@incubator.apache.org
Cc: Rohit Yadav 
Subject: [IP CLEARANCE] CloudStack Go SDK project contribution

 

Hi Incubator PMC,

 

The Apache CloudStack PMC has voted to accept the donation of " CloudStack
Go SDK", which

is a web based API for CloudStack [1].

 

Please vote to accept this contribution.

 

This is a lazy consensus majority vote, per the IP clearance process [2],

open for at least 72 hours.

 

 

Apache CloudStack PMC

 

[1] https://incubator.apache.org/ip-clearance/cloudstack-go-sdk.html

 

[2] http://incubator.apache.org/ip-clearance/

 

 

 

Many Thanks

 

Paul Angus

 

[IP CLEARANCE] CloudStack Go SDK project contribution

[paul_a]

Hi Incubator PMC,

 

The Apache CloudStack PMC has voted to accept the donation of " CloudStack
Go SDK", which

is a web based API for CloudStack [1].

 

Please vote to accept this contribution.

 

This is a lazy consensus majority vote, per the IP clearance process [2],

open for at least 72 hours.

 

 

Apache CloudStack PMC

 

[1] https://incubator.apache.org/ip-clearance/cloudstack-go-sdk.html

 

[2] http://incubator.apache.org/ip-clearance/

 

 

 

Many Thanks

 

Paul Angus

 

[IP CLEARANCE] CloudStack Terraform Provider project contribution

[paul_a]

Hi Incubator PMC,

 

The Apache CloudStack PMC has voted to accept the donation of " CloudStack
Terraform Provider", which

is a Terraform provider for CloudStack [1].

 

Please vote to accept this contribution.

 

This is a lazy consensus majority vote, per the IP clearance process [2],

open for at least 72 hours.

 

Apache CloudStack PMC

 

[1] https://incubator.apache.org/ip-clearance/cloudstack-terraform.html

 

[2] http://incubator.apache.org/ip-clearance/

 

 

Many Thanks

 

Paul Angus

 

Re: [IP CLEARANCE] gstack donation to Apache CloudStack

[David Nalley]

Looks sane to me, +1

On Tue, Apr 28, 2015 at 11:03 AM, sebgoa run...@gmail.com wrote:
 Apache CloudStack is receiving code for a Google GCE interface to the 
 CloudStack API.

 http://incubator.apache.org/ip-clearance/cloudstack-gstack.html

 Please vote to approve this contribution.

 Lazy consensus applies.

 If no -1 votes are cast within the next 72 hours, the vote passes.

 Thanks,
 -Sebastien
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IP CLEARANCE] ec2stack donated to Apache CloudStack

[David Nalley]

Looks sane to me, +1

On Tue, Apr 28, 2015 at 11:03 AM, sebgoa run...@gmail.com wrote:
 Apache CloudStack is receiving code for an EC2 interface to the CloudStack 
 API.

 http://incubator.apache.org/ip-clearance/cloudstack-ec2stack.html

 Please vote to approve this contribution.

 Lazy consensus applies.

 If no -1 votes are cast within the next 72 hours, the vote passes.

 Thanks,
 -Sebastien
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULTS] [IP CLEARANCE] ec2stack donated to Apache CloudStack

[Sebastien Goasguen]

Vote passes by lazy consensus

 On Apr 28, 2015, at 5:03 PM, sebgoa run...@gmail.com wrote:
 
 Apache CloudStack is receiving code for an EC2 interface to the CloudStack 
 API.
 
 http://incubator.apache.org/ip-clearance/cloudstack-ec2stack.html
 
 Please vote to approve this contribution.
 
 Lazy consensus applies.
 
 If no -1 votes are cast within the next 72 hours, the vote passes.
 
 Thanks,
 -Sebastien


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULTS] [IP CLEARANCE] gstack donation to Apache CloudStack

[Sebastien Goasguen]

vote passes by lazy consensus

 On May 1, 2015, at 10:20 AM, sebgoa run...@gmail.com wrote:
 
 ping on this, would be nice to get at least another pair of eyes on it
 
 On Apr 28, 2015, at 5:03 PM, sebgoa run...@gmail.com wrote:
 
 Apache CloudStack is receiving code for a Google GCE interface to the 
 CloudStack API.
 
 http://incubator.apache.org/ip-clearance/cloudstack-gstack.html
 
 Please vote to approve this contribution.
 
 Lazy consensus applies.
 
 If no -1 votes are cast within the next 72 hours, the vote passes.
 
 Thanks,
 -Sebastien
 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IP CLEARANCE] gstack donation to Apache CloudStack

[sebgoa]

ping on this, would be nice to get at least another pair of eyes on it

On Apr 28, 2015, at 5:03 PM, sebgoa run...@gmail.com wrote:

 Apache CloudStack is receiving code for a Google GCE interface to the 
 CloudStack API.
 
 http://incubator.apache.org/ip-clearance/cloudstack-gstack.html
 
 Please vote to approve this contribution.
 
 Lazy consensus applies.
 
 If no -1 votes are cast within the next 72 hours, the vote passes.
 
 Thanks,
 -Sebastien


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IP CLEARANCE] ec2stack donated to Apache CloudStack

[sebgoa]

ping on this, would be nice to get at least another pair of eyes on it

On Apr 28, 2015, at 5:03 PM, sebgoa run...@gmail.com wrote:

 Apache CloudStack is receiving code for an EC2 interface to the CloudStack 
 API.
 
 http://incubator.apache.org/ip-clearance/cloudstack-ec2stack.html
 
 Please vote to approve this contribution.
 
 Lazy consensus applies.
 
 If no -1 votes are cast within the next 72 hours, the vote passes.
 
 Thanks,
 -Sebastien


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[IP CLEARANCE] ec2stack donated to Apache CloudStack

[sebgoa]

Apache CloudStack is receiving code for an EC2 interface to the CloudStack API.

http://incubator.apache.org/ip-clearance/cloudstack-ec2stack.html

Please vote to approve this contribution.

Lazy consensus applies.

If no -1 votes are cast within the next 72 hours, the vote passes.

Thanks,
-Sebastien
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[IP CLEARANCE] gstack donation to Apache CloudStack

[sebgoa]

Apache CloudStack is receiving code for a Google GCE interface to the 
CloudStack API.

http://incubator.apache.org/ip-clearance/cloudstack-gstack.html

Please vote to approve this contribution.

Lazy consensus applies.

If no -1 votes are cast within the next 72 hours, the vote passes.

Thanks,
-Sebastien
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[Pre - IP Clearance] ec2stack and gstack donation to CloudStack

[Sebastien Goasguen]

Hi,

This is a heads up and request for help to prepare for a IP clearance request 
for two code base to be donated to Apache CloudStack:

ec2stack: https://github.com/BroganD1993/ec2stack

and,

gstack: https://github.com/NOPping/gstack

Its two software there were developed on github by myself and two other folks 
(mostly them :) ). One of them is on the cloudstack PMC and the other one has 
an ICLA on file.
The code is already ASF licensed.

I am a member and will do the work for the IP clearance forms and requests but 
I have never done it, so I want to make sure I do this properly.

I am following instructions in [1].
I submitted a software grant for each code base to secretary@ today.
I committed a draft of the forms [2] and [3]
I edited [4] but do not know how to generate the html.

Do I need to drop a tarball somewhere or is pointing to the github releases 
enough ?

Having a second pair of eyes to check everything would be nice,

Once everything is in order I will call a vote.

thanks for your time,

[1] http://incubator.apache.org/ip-clearance/
[2] 
https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/cloudstack-ec2stack.xml
[3] 
https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/cloudstack-gstack.xml
[4] 
https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/index.xml

-Sebastien
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IP CLEARANCE] RDP client for CloudStack

[Chip Childers]

On Mon, Nov 04, 2013 at 02:05:06AM -0500, Chip Childers wrote:
 Citrix has donated a plugin for Apache CloudStack to support RDP
 connectivity for virtual machines running within Hyper-V hypervisors.
 
 IP Clearance Document:
 
 http://incubator.apache.org/ip-clearance/cloudstack-rdp-client.html
 
 Please vote to approve this contribution.  Lazy consensus applies: if no
 -1 votes are cast within the next 72 hours, the vote passes.
 
 Thanks.

With no comments, we'll proceed with the import. Thanks.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[IP CLEARANCE] RDP client for CloudStack

[Chip Childers]

Citrix has donated a plugin for Apache CloudStack to support RDP
connectivity for virtual machines running within Hyper-V hypervisors.

IP Clearance Document:

http://incubator.apache.org/ip-clearance/cloudstack-rdp-client.html

Please vote to approve this contribution.  Lazy consensus applies: if no
-1 votes are cast within the next 72 hours, the vote passes.

Thanks.


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IP CLEARANCE] Contrail Plugin for CloudStack

[Chip Childers]

With no comments, I'll proceed to accept this donation.  Thanks.


On Fri, Oct 04, 2013 at 01:50:47PM -0400, Chip Childers wrote:
 Juniper Networks, Inc has dontated a plugin for Apache CloudStack to
 work with their Contrail networking software.
 
 IP Clearance Document:
 
 http://incubator.apache.org/ip-clearance/cloudstack-contrail-plugin.html
 
 Please vote to approve this contribution.  Lazy consensus applies: if no
 -1 votes are cast within the next 72 hours, the vote passes.
 
 Thanks.
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[IP CLEARANCE] Contrail Plugin for CloudStack

[Chip Childers]

Juniper Networks, Inc has dontated a plugin for Apache CloudStack to
work with their Contrail networking software.

IP Clearance Document:

http://incubator.apache.org/ip-clearance/cloudstack-contrail-plugin.html

Please vote to approve this contribution.  Lazy consensus applies: if no
-1 votes are cast within the next 72 hours, the vote passes.

Thanks.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IP CLEARANCE] CloudStack Marvin Test Suite

[Chip Childers]

On Monday, May 6, 2013, Chip Childers wrote:

 Citrix has donated the source code artifact detailed at [1] to the ASF.
 This email is to request lazy consensus from the IPMC for the IP
 clearance of this donation.

 Please reply with questions or concerns if there are any.

 -chip

 [1]
 http://incubator.apache.org/ip-clearance/cloudstack-marvin-test-suite.html


 72 hours have passed with no objections. We will proceed with the import.
Thanks!

[IP CLEARANCE] CloudStack Marvin Test Suite

[Chip Childers]

Citrix has donated the source code artifact detailed at [1] to the ASF.
This email is to request lazy consensus from the IPMC for the IP
clearance of this donation.

Please reply with questions or concerns if there are any.

-chip

[1] http://incubator.apache.org/ip-clearance/cloudstack-marvin-test-suite.html

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

CloudStack in the incubator report page for April

[Chip Childers]

Hi all,

It looks like I hadn't updated CloudStack's status to graduated soon
enough to have the incubator report generation process skip it on the
wiki.

Anyone mind if I simply remove CloudStack's section from the report
page?  We'll be reporting directly to the board this month.

http://wiki.apache.org/incubator/April2013

-chip

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: CloudStack in the incubator report page for April

[Chip Childers]

On Tue, Apr 02, 2013 at 09:55:51AM -0400, Benson Margulies wrote:
 Please do it.

Done - thx.

 
 On Tue, Apr 2, 2013 at 9:35 AM, Chip Childers chip.child...@sungard.com 
 wrote:
  Hi all,
 
  It looks like I hadn't updated CloudStack's status to graduated soon
  enough to have the incubator report generation process skip it on the
  wiki.
 
  Anyone mind if I simply remove CloudStack's section from the report
  page?  We'll be reporting directly to the board this month.
 
  http://wiki.apache.org/incubator/April2013
 
  -chip
 
  -
  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
  For additional commands, e-mail: general-h...@incubator.apache.org
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate CloudStack from Incubator

[Marcel Offermans]

+1 (binding)

Greetings, Marcel


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate CloudStack from Incubator

[Brett Porter]

+1 !

On 14/03/2013, at 12:47 PM, Chip Childers chip.child...@sungard.com wrote:

 Apache CloudStack entered the Incubator in April of 2012. We have made
 significant progress with the project since moving over to Apache. 
 
 We have 31 committers and 13 PPMC members listed on our status page at [1], 
 not including the 8 mentors that helped guide our community through 
 incubation.  
 16 of the committers and 7 of the PPMC members were added after the podling 
 was
 formed. One mentor joined the project after the podling started.  3 of the 
 initial
 committers that were not in the initial PPMC have now joined the PPMC. 7 of 
 our 
 mentors will be remaining with the project as it transitions into a TLP.
 
 We have verified that Apache CloudStack is a suitable name [2], and the
 CloudStack marks are being donated from Citrix to the ASF.
 
 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).
 
 Our community has created a set of bylaws for the project [3].
 
 The community of Apache CloudStack is active, healthy, and growing and has
 demonstrated the ability to self-govern using accepted Apache practices.
 
 After holding a discussion [4][5], the Apache CloudStack community 
 subsequently 
 voted overwhelmingly to graduate [6], collecting 55 +1 votes (including 
 4 from IPMC members), and no +0 or -1 votes.
 
 IPMC members voting +1 in the project-level thread are:
 * Mohammad Nour El-Din (IPMC/mentor) [7]
 * Noah Slater (IPMC/mentor) [8]
 * Alex Karasulu (IPMC/mentor) [9]
 * Brett Porter (IPMC/mentor) [10]
 
 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...
 
 -chip
 
 
 [1] http://incubator.apache.org/projects/cloudstack.html
 [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
 [3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
 [4] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E
 [5] http://markmail.org/message/3nluchj5q5waguws
 [6] http://markmail.org/message/ntf777ctbhdytijp
 [7] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E
 [8] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E
 [9] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E
 [10] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E
 
 
 Proposed Resolution:
 
 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 providing and supporting Infrastructure-as-a-Service (IaaS)
 cloud computing platforms.
 
 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 CloudStack Project be and hereby is responsible
 for the creation and maintenance of software related to providing and 
 supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms.
 
 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:
 
 * Joe Brockmeier j...@apache.org
 * Will Chan willc...@apache.org
 * Chip Childers chipchild...@apache.org
 * Mohammad Nour El-Din mn...@apache.org
 * Sebastien Goasguen seb...@apache.org
 * Matt Richard Hogstrom hogst...@apache.org
 * Wido den Hollander wid...@apache.org
 * Alex Huang ahu...@apache.org
 * Jim Jagielski j...@apache.org
 * Alex Karasulu akaras...@apache.org
 * John Kinsella j...@apache.org
 * Kevin Kluge kl...@apache.org
 * Olivier Lamy ol...@apache.org
 * David Nalley ke4...@apache.org
 * Brett Porter br...@apache.org
 * Noah Slater nsla...@apache.org
 * Marcus Sorensen mlsoren...@apache.org

Re: [VOTE] Graduate CloudStack from Incubator

[Suresh Marru]

+ 1 (binding)

Great going in a short time (given the size of the project), All the best as a 
TLP,
Suresh

On Mar 14, 2013, at 12:47 PM, Chip Childers chip.child...@sungard.com wrote:

 Apache CloudStack entered the Incubator in April of 2012. We have made
 significant progress with the project since moving over to Apache. 
 
 We have 31 committers and 13 PPMC members listed on our status page at [1], 
 not including the 8 mentors that helped guide our community through 
 incubation.  
 16 of the committers and 7 of the PPMC members were added after the podling 
 was
 formed. One mentor joined the project after the podling started.  3 of the 
 initial
 committers that were not in the initial PPMC have now joined the PPMC. 7 of 
 our 
 mentors will be remaining with the project as it transitions into a TLP.
 
 We have verified that Apache CloudStack is a suitable name [2], and the
 CloudStack marks are being donated from Citrix to the ASF.
 
 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).
 
 Our community has created a set of bylaws for the project [3].
 
 The community of Apache CloudStack is active, healthy, and growing and has
 demonstrated the ability to self-govern using accepted Apache practices.
 
 After holding a discussion [4][5], the Apache CloudStack community 
 subsequently 
 voted overwhelmingly to graduate [6], collecting 55 +1 votes (including 
 4 from IPMC members), and no +0 or -1 votes.
 
 IPMC members voting +1 in the project-level thread are:
 * Mohammad Nour El-Din (IPMC/mentor) [7]
 * Noah Slater (IPMC/mentor) [8]
 * Alex Karasulu (IPMC/mentor) [9]
 * Brett Porter (IPMC/mentor) [10]
 
 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...
 
 -chip
 
 
 [1] http://incubator.apache.org/projects/cloudstack.html
 [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
 [3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
 [4] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E
 [5] http://markmail.org/message/3nluchj5q5waguws
 [6] http://markmail.org/message/ntf777ctbhdytijp
 [7] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E
 [8] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E
 [9] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E
 [10] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E
 
 
 Proposed Resolution:
 
 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 providing and supporting Infrastructure-as-a-Service (IaaS)
 cloud computing platforms.
 
 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 CloudStack Project be and hereby is responsible
 for the creation and maintenance of software related to providing and 
 supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms.
 
 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:
 
 * Joe Brockmeier j...@apache.org
 * Will Chan willc...@apache.org
 * Chip Childers chipchild...@apache.org
 * Mohammad Nour El-Din mn...@apache.org
 * Sebastien Goasguen seb...@apache.org
 * Matt Richard Hogstrom hogst...@apache.org
 * Wido den Hollander wid...@apache.org
 * Alex Huang ahu...@apache.org
 * Jim Jagielski j...@apache.org
 * Alex Karasulu akaras...@apache.org
 * John Kinsella j...@apache.org
 * Kevin Kluge kl...@apache.org
 * Olivier Lamy ol...@apache.org
 * David Nalley ke4...@apache.org

Re: [VOTE] Graduate CloudStack from Incubator

[Mohammad Nour El-Din]

+1 (binding)


On Sun, Mar 17, 2013 at 3:38 PM, Suresh Marru sma...@apache.org wrote:

 + 1 (binding)

 Great going in a short time (given the size of the project), All the best
 as a TLP,
 Suresh

 On Mar 14, 2013, at 12:47 PM, Chip Childers chip.child...@sungard.com
 wrote:

  Apache CloudStack entered the Incubator in April of 2012. We have made
  significant progress with the project since moving over to Apache.
 
  We have 31 committers and 13 PPMC members listed on our status page at
 [1],
  not including the 8 mentors that helped guide our community through
 incubation.
  16 of the committers and 7 of the PPMC members were added after the
 podling was
  formed. One mentor joined the project after the podling started.  3 of
 the initial
  committers that were not in the initial PPMC have now joined the PPMC. 7
 of our
  mentors will be remaining with the project as it transitions into a TLP.
 
  We have verified that Apache CloudStack is a suitable name [2], and the
  CloudStack marks are being donated from Citrix to the ASF.
 
  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).
 
  Our community has created a set of bylaws for the project [3].
 
  The community of Apache CloudStack is active, healthy, and growing and
 has
  demonstrated the ability to self-govern using accepted Apache practices.
 
  After holding a discussion [4][5], the Apache CloudStack community
 subsequently
  voted overwhelmingly to graduate [6], collecting 55 +1 votes (including
  4 from IPMC members), and no +0 or -1 votes.
 
  IPMC members voting +1 in the project-level thread are:
  * Mohammad Nour El-Din (IPMC/mentor) [7]
  * Noah Slater (IPMC/mentor) [8]
  * Alex Karasulu (IPMC/mentor) [9]
  * Brett Porter (IPMC/mentor) [10]
 
  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...
 
  -chip
 
 
  [1] http://incubator.apache.org/projects/cloudstack.html
  [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
  [3]
 https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
  [4]
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E
  [5] http://markmail.org/message/3nluchj5q5waguws
  [6] http://markmail.org/message/ntf777ctbhdytijp
  [7]
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E
  [8]
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E
  [9]
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E
  [10]
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E
 
 
  Proposed Resolution:
 
  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 providing and supporting Infrastructure-as-a-Service (IaaS)
  cloud computing platforms.
 
  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 CloudStack Project be and hereby is responsible
  for the creation and maintenance of software related to providing and
  supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms.
 
  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:
 
  * Joe Brockmeier j...@apache.org
  * Will Chan willc...@apache.org
  * Chip Childers chipchild...@apache.org
  * Mohammad Nour El-Din mn...@apache.org
  * Sebastien Goasguen seb...@apache.org
  * Matt Richard Hogstrom hogst...@apache.org
  * Wido den Hollander wid...@apache.org
  * Alex Huang ahu...@apache.org
  * Jim Jagielski j...@apache.org
  * Alex Karasulu akaras

[VOTE][RESULT] Graduate CloudStack from Incubator

[Chip Childers]

After 72 hours, the vote to graduate CloudStack from the incubator has
*passed*.  Thank you everyone!

I'll forward a request to be on the agenda of the next board meeting to
board@ momentarily.

+1: 12 binding, 4 non-binding
+0: none
-1: none

Binding votes:
* Noah Slater
* Alex Karasulu
* Daniel Kulp
* Roman Shaposhnik
* Alan Cabrera
* Jim Jagielski
* Niall Pemberton
* Danese Cooper
* Marcel Offermans
* Brett Porter
* Suresh Marru
* Mohammad Nour El-Din

Non-Binding:
* Daniel Gruno
* Ioan Eugen Stan
* Andrei Savu
* Bruno Mahé

-chip

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE][RESULT] Graduate CloudStack from Incubator

[Shane Curcuru]

Uh, +1 also!  Drat, missed the window.

I wanted to mention that the Apache CloudStack PPMC has done a great job 
on ensuring their branding comes over cleanly from Citrix, and has 
really put work into building an independent community, so kudos are 
definitely deserved.


- Shane

On 3/17/2013 12:52 PM, Chip Childers wrote:

After 72 hours, the vote to graduate CloudStack from the incubator has
*passed*.  Thank you everyone!

I'll forward a request to be on the agenda of the next board meeting to
board@ momentarily.

+1: 12 binding, 4 non-binding
+0: none
-1: none

Binding votes:
* Noah Slater
* Alex Karasulu
* Daniel Kulp
* Roman Shaposhnik
* Alan Cabrera
* Jim Jagielski
* Niall Pemberton
* Danese Cooper
* Marcel Offermans
* Brett Porter
* Suresh Marru
* Mohammad Nour El-Din

Non-Binding:
* Daniel Gruno
* Ioan Eugen Stan
* Andrei Savu
* Bruno Mahé

-chip

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate CloudStack from Incubator

[Bruno Mahé]

+1 (non binding)

On 03/14/2013 09:47 AM, Chip Childers wrote:

Apache CloudStack entered the Incubator in April of 2012. We have made
significant progress with the project since moving over to Apache.

We have 31 committers and 13 PPMC members listed on our status page at [1],
not including the 8 mentors that helped guide our community through incubation.
16 of the committers and 7 of the PPMC members were added after the podling was
formed. One mentor joined the project after the podling started.  3 of the 
initial
committers that were not in the initial PPMC have now joined the PPMC. 7 of our
mentors will be remaining with the project as it transitions into a TLP.

We have verified that Apache CloudStack is a suitable name [2], and the
CloudStack marks are being donated from Citrix to the ASF.

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).

Our community has created a set of bylaws for the project [3].

The community of Apache CloudStack is active, healthy, and growing and has
demonstrated the ability to self-govern using accepted Apache practices.

After holding a discussion [4][5], the Apache CloudStack community subsequently
voted overwhelmingly to graduate [6], collecting 55 +1 votes (including
4 from IPMC members), and no +0 or -1 votes.

IPMC members voting +1 in the project-level thread are:
  * Mohammad Nour El-Din (IPMC/mentor) [7]
  * Noah Slater (IPMC/mentor) [8]
  * Alex Karasulu (IPMC/mentor) [9]
  * Brett Porter (IPMC/mentor) [10]

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...

-chip


[1] http://incubator.apache.org/projects/cloudstack.html
[2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
[3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
[4] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E
[5] http://markmail.org/message/3nluchj5q5waguws
[6] http://markmail.org/message/ntf777ctbhdytijp
[7] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E
[8] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E
[9] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E
[10] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E


Proposed Resolution:

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 providing and supporting Infrastructure-as-a-Service (IaaS)
cloud computing platforms.

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 CloudStack Project be and hereby is responsible
for the creation and maintenance of software related to providing and
supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms.

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:

* Joe Brockmeier j...@apache.org
* Will Chan willc...@apache.org
* Chip Childers chipchild...@apache.org
* Mohammad Nour El-Din mn...@apache.org
* Sebastien Goasguen seb...@apache.org
* Matt Richard Hogstrom hogst...@apache.org
* Wido den Hollander wid...@apache.org
* Alex Huang ahu...@apache.org
* Jim Jagielski j...@apache.org
* Alex Karasulu akaras...@apache.org
* John Kinsella j...@apache.org
* Kevin Kluge kl...@apache.org
* Olivier Lamy ol...@apache.org
* David Nalley ke4...@apache.org
* Brett Porter br...@apache.org
* Noah Slater nsla...@apache.org
* Marcus Sorensen mlsoren...@apache.org
* Edison Su edi...@apache.org
* Hugo Trippaers h...@apache.org
* Chiradeep Vittal chirad...@apache.org

NOW, THEREFORE, BE IT FURTHER

Re: [VOTE] Graduate CloudStack from Incubator

[Ioan Eugen Stan]

+1 non-binding
-- 
Ioan Eugen Stan

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate CloudStack from Incubator

[Andrei Savu]

+1 non-binding

-- Andrei Savu

On Fri, Mar 15, 2013 at 8:15 AM, Ioan Eugen Stan stan.ieu...@gmail.comwrote:

 +1 non-binding
 --
 Ioan Eugen Stan

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate CloudStack from Incubator

[Alan Cabrera]

+1 binding


Regards,
Alan

On Mar 14, 2013, at 9:47 AM, Chip Childers chip.child...@sungard.com wrote:

 Apache CloudStack entered the Incubator in April of 2012. We have made
 significant progress with the project since moving over to Apache. 
 
 We have 31 committers and 13 PPMC members listed on our status page at [1], 
 not including the 8 mentors that helped guide our community through 
 incubation.  
 16 of the committers and 7 of the PPMC members were added after the podling 
 was
 formed. One mentor joined the project after the podling started.  3 of the 
 initial
 committers that were not in the initial PPMC have now joined the PPMC. 7 of 
 our 
 mentors will be remaining with the project as it transitions into a TLP.
 
 We have verified that Apache CloudStack is a suitable name [2], and the
 CloudStack marks are being donated from Citrix to the ASF.
 
 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).
 
 Our community has created a set of bylaws for the project [3].
 
 The community of Apache CloudStack is active, healthy, and growing and has
 demonstrated the ability to self-govern using accepted Apache practices.
 
 After holding a discussion [4][5], the Apache CloudStack community 
 subsequently 
 voted overwhelmingly to graduate [6], collecting 55 +1 votes (including 
 4 from IPMC members), and no +0 or -1 votes.
 
 IPMC members voting +1 in the project-level thread are:
 * Mohammad Nour El-Din (IPMC/mentor) [7]
 * Noah Slater (IPMC/mentor) [8]
 * Alex Karasulu (IPMC/mentor) [9]
 * Brett Porter (IPMC/mentor) [10]
 
 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...
 
 -chip
 
 
 [1] http://incubator.apache.org/projects/cloudstack.html
 [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
 [3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
 [4] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E
 [5] http://markmail.org/message/3nluchj5q5waguws
 [6] http://markmail.org/message/ntf777ctbhdytijp
 [7] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E
 [8] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E
 [9] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E
 [10] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E
 
 
 Proposed Resolution:
 
 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 providing and supporting Infrastructure-as-a-Service (IaaS)
 cloud computing platforms.
 
 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 CloudStack Project be and hereby is responsible
 for the creation and maintenance of software related to providing and 
 supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms.
 
 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:
 
 * Joe Brockmeier j...@apache.org
 * Will Chan willc...@apache.org
 * Chip Childers chipchild...@apache.org
 * Mohammad Nour El-Din mn...@apache.org
 * Sebastien Goasguen seb...@apache.org
 * Matt Richard Hogstrom hogst...@apache.org
 * Wido den Hollander wid...@apache.org
 * Alex Huang ahu...@apache.org
 * Jim Jagielski j...@apache.org
 * Alex Karasulu akaras...@apache.org
 * John Kinsella j...@apache.org
 * Kevin Kluge kl...@apache.org
 * Olivier Lamy ol...@apache.org
 * David Nalley ke4...@apache.org
 * Brett Porter br...@apache.org
 * Noah Slater nsla...@apache.org
 * Marcus Sorensen

Re: [VOTE] Graduate CloudStack from Incubator

[Jim Jagielski]

+1!
On Mar 14, 2013, at 12:47 PM, Chip Childers chip.child...@sungard.com wrote:

 Apache CloudStack entered the Incubator in April of 2012. We have made
 significant progress with the project since moving over to Apache. 
 
 We have 31 committers and 13 PPMC members listed on our status page at [1], 
 not including the 8 mentors that helped guide our community through 
 incubation.  
 16 of the committers and 7 of the PPMC members were added after the podling 
 was
 formed. One mentor joined the project after the podling started.  3 of the 
 initial
 committers that were not in the initial PPMC have now joined the PPMC. 7 of 
 our 
 mentors will be remaining with the project as it transitions into a TLP.
 
 We have verified that Apache CloudStack is a suitable name [2], and the
 CloudStack marks are being donated from Citrix to the ASF.
 
 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).
 
 Our community has created a set of bylaws for the project [3].
 
 The community of Apache CloudStack is active, healthy, and growing and has
 demonstrated the ability to self-govern using accepted Apache practices.
 
 After holding a discussion [4][5], the Apache CloudStack community 
 subsequently 
 voted overwhelmingly to graduate [6], collecting 55 +1 votes (including 
 4 from IPMC members), and no +0 or -1 votes.
 
 IPMC members voting +1 in the project-level thread are:
 * Mohammad Nour El-Din (IPMC/mentor) [7]
 * Noah Slater (IPMC/mentor) [8]
 * Alex Karasulu (IPMC/mentor) [9]
 * Brett Porter (IPMC/mentor) [10]
 
 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...
 
 -chip
 
 
 [1] http://incubator.apache.org/projects/cloudstack.html
 [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
 [3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
 [4] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E
 [5] http://markmail.org/message/3nluchj5q5waguws
 [6] http://markmail.org/message/ntf777ctbhdytijp
 [7] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E
 [8] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E
 [9] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E
 [10] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E
 
 
 Proposed Resolution:
 
 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 providing and supporting Infrastructure-as-a-Service (IaaS)
 cloud computing platforms.
 
 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 CloudStack Project be and hereby is responsible
 for the creation and maintenance of software related to providing and 
 supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms.
 
 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:
 
 * Joe Brockmeier j...@apache.org
 * Will Chan willc...@apache.org
 * Chip Childers chipchild...@apache.org
 * Mohammad Nour El-Din mn...@apache.org
 * Sebastien Goasguen seb...@apache.org
 * Matt Richard Hogstrom hogst...@apache.org
 * Wido den Hollander wid...@apache.org
 * Alex Huang ahu...@apache.org
 * Jim Jagielski j...@apache.org
 * Alex Karasulu akaras...@apache.org
 * John Kinsella j...@apache.org
 * Kevin Kluge kl...@apache.org
 * Olivier Lamy ol...@apache.org
 * David Nalley ke4...@apache.org
 * Brett Porter br...@apache.org
 * Noah Slater nsla...@apache.org
 * Marcus Sorensen mlsoren...@apache.org

Re: [VOTE] Graduate CloudStack from Incubator

[Niall Pemberton]

Thanks for laying out all the evidence for graduation - this was a
good vote email.

+1 from me.

Niall

On Thu, Mar 14, 2013 at 4:47 PM, Chip Childers
chip.child...@sungard.com wrote:
 Apache CloudStack entered the Incubator in April of 2012. We have made
 significant progress with the project since moving over to Apache.

 We have 31 committers and 13 PPMC members listed on our status page at [1],
 not including the 8 mentors that helped guide our community through 
 incubation.
 16 of the committers and 7 of the PPMC members were added after the podling 
 was
 formed. One mentor joined the project after the podling started.  3 of the 
 initial
 committers that were not in the initial PPMC have now joined the PPMC. 7 of 
 our
 mentors will be remaining with the project as it transitions into a TLP.

 We have verified that Apache CloudStack is a suitable name [2], and the
 CloudStack marks are being donated from Citrix to the ASF.

 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).

 Our community has created a set of bylaws for the project [3].

 The community of Apache CloudStack is active, healthy, and growing and has
 demonstrated the ability to self-govern using accepted Apache practices.

 After holding a discussion [4][5], the Apache CloudStack community 
 subsequently
 voted overwhelmingly to graduate [6], collecting 55 +1 votes (including
 4 from IPMC members), and no +0 or -1 votes.

 IPMC members voting +1 in the project-level thread are:
  * Mohammad Nour El-Din (IPMC/mentor) [7]
  * Noah Slater (IPMC/mentor) [8]
  * Alex Karasulu (IPMC/mentor) [9]
  * Brett Porter (IPMC/mentor) [10]

 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...

 -chip


 [1] http://incubator.apache.org/projects/cloudstack.html
 [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
 [3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
 [4] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E
 [5] http://markmail.org/message/3nluchj5q5waguws
 [6] http://markmail.org/message/ntf777ctbhdytijp
 [7] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E
 [8] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E
 [9] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E
 [10] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E


 Proposed Resolution:

 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 providing and supporting Infrastructure-as-a-Service (IaaS)
 cloud computing platforms.

 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 CloudStack Project be and hereby is responsible
 for the creation and maintenance of software related to providing and
 supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms.

 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:

 * Joe Brockmeier j...@apache.org
 * Will Chan willc...@apache.org
 * Chip Childers chipchild...@apache.org
 * Mohammad Nour El-Din mn...@apache.org
 * Sebastien Goasguen seb...@apache.org
 * Matt Richard Hogstrom hogst...@apache.org
 * Wido den Hollander wid...@apache.org
 * Alex Huang ahu...@apache.org
 * Jim Jagielski j...@apache.org
 * Alex Karasulu akaras...@apache.org
 * John Kinsella j...@apache.org
 * Kevin Kluge kl...@apache.org
 * Olivier Lamy ol...@apache.org
 * David Nalley ke4...@apache.org
 * Brett Porter br...@apache.org

Re: [VOTE] Graduate CloudStack from Incubator

[Danese Cooper]

What Niall said. +1 and congrats.

Danese

On Mar 15, 2013, at 7:08 PM, Niall Pemberton niall.pember...@gmail.com wrote:

 Thanks for laying out all the evidence for graduation - this was a
 good vote email.
 
 +1 from me.
 
 Niall
 
 On Thu, Mar 14, 2013 at 4:47 PM, Chip Childers
 chip.child...@sungard.com wrote:
 Apache CloudStack entered the Incubator in April of 2012. We have made
 significant progress with the project since moving over to Apache.
 
 We have 31 committers and 13 PPMC members listed on our status page at [1],
 not including the 8 mentors that helped guide our community through 
 incubation.
 16 of the committers and 7 of the PPMC members were added after the podling 
 was
 formed. One mentor joined the project after the podling started.  3 of the 
 initial
 committers that were not in the initial PPMC have now joined the PPMC. 7 of 
 our
 mentors will be remaining with the project as it transitions into a TLP.
 
 We have verified that Apache CloudStack is a suitable name [2], and the
 CloudStack marks are being donated from Citrix to the ASF.
 
 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).
 
 Our community has created a set of bylaws for the project [3].
 
 The community of Apache CloudStack is active, healthy, and growing and has
 demonstrated the ability to self-govern using accepted Apache practices.
 
 After holding a discussion [4][5], the Apache CloudStack community 
 subsequently
 voted overwhelmingly to graduate [6], collecting 55 +1 votes (including
 4 from IPMC members), and no +0 or -1 votes.
 
 IPMC members voting +1 in the project-level thread are:
 * Mohammad Nour El-Din (IPMC/mentor) [7]
 * Noah Slater (IPMC/mentor) [8]
 * Alex Karasulu (IPMC/mentor) [9]
 * Brett Porter (IPMC/mentor) [10]
 
 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...
 
 -chip
 
 
 [1] http://incubator.apache.org/projects/cloudstack.html
 [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
 [3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
 [4] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E
 [5] http://markmail.org/message/3nluchj5q5waguws
 [6] http://markmail.org/message/ntf777ctbhdytijp
 [7] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E
 [8] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E
 [9] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E
 [10] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E
 
 
 Proposed Resolution:
 
 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 providing and supporting Infrastructure-as-a-Service (IaaS)
 cloud computing platforms.
 
 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 CloudStack Project be and hereby is responsible
 for the creation and maintenance of software related to providing and
 supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms.
 
 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:
 
 * Joe Brockmeier j...@apache.org
 * Will Chan willc...@apache.org
 * Chip Childers chipchild...@apache.org
 * Mohammad Nour El-Din mn...@apache.org
 * Sebastien Goasguen seb...@apache.org
 * Matt Richard Hogstrom hogst...@apache.org
 * Wido den Hollander wid...@apache.org
 * Alex Huang ahu...@apache.org
 * Jim Jagielski j...@apache.org
 * Alex Karasulu akaras...@apache.org
 * John

[VOTE] Graduate CloudStack from Incubator

[Chip Childers]

Apache CloudStack entered the Incubator in April of 2012. We have made
significant progress with the project since moving over to Apache. 

We have 31 committers and 13 PPMC members listed on our status page at [1], 
not including the 8 mentors that helped guide our community through incubation. 
 
16 of the committers and 7 of the PPMC members were added after the podling was
formed. One mentor joined the project after the podling started.  3 of the 
initial
committers that were not in the initial PPMC have now joined the PPMC. 7 of our 
mentors will be remaining with the project as it transitions into a TLP.

We have verified that Apache CloudStack is a suitable name [2], and the
CloudStack marks are being donated from Citrix to the ASF.

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).

Our community has created a set of bylaws for the project [3].

The community of Apache CloudStack is active, healthy, and growing and has
demonstrated the ability to self-govern using accepted Apache practices.

After holding a discussion [4][5], the Apache CloudStack community subsequently 
voted overwhelmingly to graduate [6], collecting 55 +1 votes (including 
4 from IPMC members), and no +0 or -1 votes.

IPMC members voting +1 in the project-level thread are:
 * Mohammad Nour El-Din (IPMC/mentor) [7]
 * Noah Slater (IPMC/mentor) [8]
 * Alex Karasulu (IPMC/mentor) [9]
 * Brett Porter (IPMC/mentor) [10]

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...

-chip


[1] http://incubator.apache.org/projects/cloudstack.html
[2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
[3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
[4] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E
[5] http://markmail.org/message/3nluchj5q5waguws
[6] http://markmail.org/message/ntf777ctbhdytijp
[7] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E
[8] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E
[9] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E
[10] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E


Proposed Resolution:

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 providing and supporting Infrastructure-as-a-Service (IaaS)
cloud computing platforms.

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 CloudStack Project be and hereby is responsible
for the creation and maintenance of software related to providing and 
supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms.

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:

* Joe Brockmeier j...@apache.org
* Will Chan willc...@apache.org
* Chip Childers chipchild...@apache.org
* Mohammad Nour El-Din mn...@apache.org
* Sebastien Goasguen seb...@apache.org
* Matt Richard Hogstrom hogst...@apache.org
* Wido den Hollander wid...@apache.org
* Alex Huang ahu...@apache.org
* Jim Jagielski j...@apache.org
* Alex Karasulu akaras...@apache.org
* John Kinsella j...@apache.org
* Kevin Kluge kl...@apache.org
* Olivier Lamy ol...@apache.org
* David Nalley ke4...@apache.org
* Brett Porter br...@apache.org
* Noah Slater nsla...@apache.org
* Marcus Sorensen mlsoren...@apache.org
* Edison Su edi...@apache.org
* Hugo Trippaers h...@apache.org
* Chiradeep Vittal chirad...@apache.org

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Chip Childers be appointed to the
office

Re: [VOTE] Graduate CloudStack from Incubator

[Noah Slater]

+1

(I figure a second vote from me can't hurt...)


On 14 March 2013 16:47, Chip Childers chip.child...@sungard.com wrote:

 Apache CloudStack entered the Incubator in April of 2012. We have made
 significant progress with the project since moving over to Apache.

 We have 31 committers and 13 PPMC members listed on our status page at [1],
 not including the 8 mentors that helped guide our community through
 incubation.
 16 of the committers and 7 of the PPMC members were added after the
 podling was
 formed. One mentor joined the project after the podling started.  3 of the
 initial
 committers that were not in the initial PPMC have now joined the PPMC. 7
 of our
 mentors will be remaining with the project as it transitions into a TLP.

 We have verified that Apache CloudStack is a suitable name [2], and the
 CloudStack marks are being donated from Citrix to the ASF.

 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).

 Our community has created a set of bylaws for the project [3].

 The community of Apache CloudStack is active, healthy, and growing and has
 demonstrated the ability to self-govern using accepted Apache practices.

 After holding a discussion [4][5], the Apache CloudStack community
 subsequently
 voted overwhelmingly to graduate [6], collecting 55 +1 votes (including
 4 from IPMC members), and no +0 or -1 votes.

 IPMC members voting +1 in the project-level thread are:
  * Mohammad Nour El-Din (IPMC/mentor) [7]
  * Noah Slater (IPMC/mentor) [8]
  * Alex Karasulu (IPMC/mentor) [9]
  * Brett Porter (IPMC/mentor) [10]

 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...

 -chip


 [1] http://incubator.apache.org/projects/cloudstack.html
 [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
 [3]
 https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
 [4]
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E
 [5] http://markmail.org/message/3nluchj5q5waguws
 [6] http://markmail.org/message/ntf777ctbhdytijp
 [7]
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E
 [8]
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E
 [9]
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E
 [10]
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E


 Proposed Resolution:

 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 providing and supporting Infrastructure-as-a-Service (IaaS)
 cloud computing platforms.

 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 CloudStack Project be and hereby is responsible
 for the creation and maintenance of software related to providing and
 supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms.

 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:

 * Joe Brockmeier j...@apache.org
 * Will Chan willc...@apache.org
 * Chip Childers chipchild...@apache.org
 * Mohammad Nour El-Din mn...@apache.org
 * Sebastien Goasguen seb...@apache.org
 * Matt Richard Hogstrom hogst...@apache.org
 * Wido den Hollander wid...@apache.org
 * Alex Huang ahu...@apache.org
 * Jim Jagielski j...@apache.org
 * Alex Karasulu akaras...@apache.org
 * John Kinsella j...@apache.org
 * Kevin Kluge kl...@apache.org
 * Olivier Lamy ol...@apache.org
 * David Nalley ke4...@apache.org
 * Brett Porter br...@apache.org
 * Noah Slater nsla...@apache.org
 * Marcus Sorensen mlsoren

Re: [VOTE] Graduate CloudStack from Incubator

[Daniel Gruno]

Top-posting since this is a long letter and you just need to see whether
it's +1 or -1 ;)

So here: +1 (non-binding).

I've seen your work flow from an infra perspective, and it seems vibrant
and well oiled, and I'm pleased to see this vote. You're an easy team to
work with (that is my opinion at least), always give feedback, and
aren't afraid of using bleeding edge tools (even those written by me),
which speaks warmly of your ability to adjust to new surroundings.

With regards,
Daniel.

On 03/14/2013 05:47 PM, Chip Childers wrote:
 Apache CloudStack entered the Incubator in April of 2012. We have made
 significant progress with the project since moving over to Apache. 
 
 We have 31 committers and 13 PPMC members listed on our status page at [1], 
 not including the 8 mentors that helped guide our community through 
 incubation.  
 16 of the committers and 7 of the PPMC members were added after the podling 
 was
 formed. One mentor joined the project after the podling started.  3 of the 
 initial
 committers that were not in the initial PPMC have now joined the PPMC. 7 of 
 our 
 mentors will be remaining with the project as it transitions into a TLP.
 
 We have verified that Apache CloudStack is a suitable name [2], and the
 CloudStack marks are being donated from Citrix to the ASF.
 
 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).
 
 Our community has created a set of bylaws for the project [3].
 
 The community of Apache CloudStack is active, healthy, and growing and has
 demonstrated the ability to self-govern using accepted Apache practices.
 
 After holding a discussion [4][5], the Apache CloudStack community 
 subsequently 
 voted overwhelmingly to graduate [6], collecting 55 +1 votes (including 
 4 from IPMC members), and no +0 or -1 votes.
 
 IPMC members voting +1 in the project-level thread are:
  * Mohammad Nour El-Din (IPMC/mentor) [7]
  * Noah Slater (IPMC/mentor) [8]
  * Alex Karasulu (IPMC/mentor) [9]
  * Brett Porter (IPMC/mentor) [10]
 
 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...
 
 -chip
 
 
 [1] http://incubator.apache.org/projects/cloudstack.html
 [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
 [3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
 [4] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E
 [5] http://markmail.org/message/3nluchj5q5waguws
 [6] http://markmail.org/message/ntf777ctbhdytijp
 [7] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E
 [8] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E
 [9] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E
 [10] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E
 
 
 Proposed Resolution:
 
 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 providing and supporting Infrastructure-as-a-Service (IaaS)
 cloud computing platforms.
 
 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 CloudStack Project be and hereby is responsible
 for the creation and maintenance of software related to providing and 
 supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms.
 
 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:
 
 * Joe Brockmeier j...@apache.org
 * Will Chan willc...@apache.org
 * Chip Childers chipchild...@apache.org
 * Mohammad Nour El-Din mn...@apache.org

Re: [VOTE] Graduate CloudStack from Incubator

[Daniel Kulp]

+1

Dan



On Mar 14, 2013, at 12:47 PM, Chip Childers chip.child...@sungard.com wrote:

 Apache CloudStack entered the Incubator in April of 2012. We have made
 significant progress with the project since moving over to Apache. 
 
 We have 31 committers and 13 PPMC members listed on our status page at [1], 
 not including the 8 mentors that helped guide our community through 
 incubation.  
 16 of the committers and 7 of the PPMC members were added after the podling 
 was
 formed. One mentor joined the project after the podling started.  3 of the 
 initial
 committers that were not in the initial PPMC have now joined the PPMC. 7 of 
 our 
 mentors will be remaining with the project as it transitions into a TLP.
 
 We have verified that Apache CloudStack is a suitable name [2], and the
 CloudStack marks are being donated from Citrix to the ASF.
 
 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).
 
 Our community has created a set of bylaws for the project [3].
 
 The community of Apache CloudStack is active, healthy, and growing and has
 demonstrated the ability to self-govern using accepted Apache practices.
 
 After holding a discussion [4][5], the Apache CloudStack community 
 subsequently 
 voted overwhelmingly to graduate [6], collecting 55 +1 votes (including 
 4 from IPMC members), and no +0 or -1 votes.
 
 IPMC members voting +1 in the project-level thread are:
 * Mohammad Nour El-Din (IPMC/mentor) [7]
 * Noah Slater (IPMC/mentor) [8]
 * Alex Karasulu (IPMC/mentor) [9]
 * Brett Porter (IPMC/mentor) [10]
 
 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...
 
 -chip
 
 
 [1] http://incubator.apache.org/projects/cloudstack.html
 [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
 [3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
 [4] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E
 [5] http://markmail.org/message/3nluchj5q5waguws
 [6] http://markmail.org/message/ntf777ctbhdytijp
 [7] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E
 [8] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E
 [9] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E
 [10] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E
 
 
 Proposed Resolution:
 
 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 providing and supporting Infrastructure-as-a-Service (IaaS)
 cloud computing platforms.
 
 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 CloudStack Project be and hereby is responsible
 for the creation and maintenance of software related to providing and 
 supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms.
 
 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:
 
 * Joe Brockmeier j...@apache.org
 * Will Chan willc...@apache.org
 * Chip Childers chipchild...@apache.org
 * Mohammad Nour El-Din mn...@apache.org
 * Sebastien Goasguen seb...@apache.org
 * Matt Richard Hogstrom hogst...@apache.org
 * Wido den Hollander wid...@apache.org
 * Alex Huang ahu...@apache.org
 * Jim Jagielski j...@apache.org
 * Alex Karasulu akaras...@apache.org
 * John Kinsella j...@apache.org
 * Kevin Kluge kl...@apache.org
 * Olivier Lamy ol...@apache.org
 * David Nalley ke4...@apache.org
 * Brett Porter br...@apache.org
 * Noah Slater nsla...@apache.org
 * Marcus Sorensen mlsoren

Re: [VOTE] Graduate CloudStack from Incubator

[Roman Shaposhnik]

+1 (binding)

I've been keeping a bit of an eye on that community and FWIW
I think they are in a reasonable shape.

Thanks,
Roman.

On Thu, Mar 14, 2013 at 9:47 AM, Chip Childers
chip.child...@sungard.com wrote:
 Apache CloudStack entered the Incubator in April of 2012. We have made
 significant progress with the project since moving over to Apache.

 We have 31 committers and 13 PPMC members listed on our status page at [1],
 not including the 8 mentors that helped guide our community through 
 incubation.
 16 of the committers and 7 of the PPMC members were added after the podling 
 was
 formed. One mentor joined the project after the podling started.  3 of the 
 initial
 committers that were not in the initial PPMC have now joined the PPMC. 7 of 
 our
 mentors will be remaining with the project as it transitions into a TLP.

 We have verified that Apache CloudStack is a suitable name [2], and the
 CloudStack marks are being donated from Citrix to the ASF.

 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).

 Our community has created a set of bylaws for the project [3].

 The community of Apache CloudStack is active, healthy, and growing and has
 demonstrated the ability to self-govern using accepted Apache practices.

 After holding a discussion [4][5], the Apache CloudStack community 
 subsequently
 voted overwhelmingly to graduate [6], collecting 55 +1 votes (including
 4 from IPMC members), and no +0 or -1 votes.

 IPMC members voting +1 in the project-level thread are:
  * Mohammad Nour El-Din (IPMC/mentor) [7]
  * Noah Slater (IPMC/mentor) [8]
  * Alex Karasulu (IPMC/mentor) [9]
  * Brett Porter (IPMC/mentor) [10]

 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...

 -chip


 [1] http://incubator.apache.org/projects/cloudstack.html
 [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
 [3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
 [4] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E
 [5] http://markmail.org/message/3nluchj5q5waguws
 [6] http://markmail.org/message/ntf777ctbhdytijp
 [7] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E
 [8] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E
 [9] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E
 [10] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E


 Proposed Resolution:

 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 providing and supporting Infrastructure-as-a-Service (IaaS)
 cloud computing platforms.

 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 CloudStack Project be and hereby is responsible
 for the creation and maintenance of software related to providing and
 supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms.

 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:

 * Joe Brockmeier j...@apache.org
 * Will Chan willc...@apache.org
 * Chip Childers chipchild...@apache.org
 * Mohammad Nour El-Din mn...@apache.org
 * Sebastien Goasguen seb...@apache.org
 * Matt Richard Hogstrom hogst...@apache.org
 * Wido den Hollander wid...@apache.org
 * Alex Huang ahu...@apache.org
 * Jim Jagielski j...@apache.org
 * Alex Karasulu akaras...@apache.org
 * John Kinsella j...@apache.org
 * Kevin Kluge kl...@apache.org
 * Olivier Lamy ol...@apache.org
 * David Nalley ke4...@apache.org

[jira] [Commented] (PODLINGNAMESEARCH-23) Establish whether Apache CloudStack is a suitable name

[Shane Curcuru (JIRA)]

[ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13586164#comment-13586164
 ] 

Shane Curcuru commented on PODLINGNAMESEARCH-23:


Approved.

Note that this really points out a hole in the podling name search policy.  We 
need to update it to say (something like): If the podling has a 
well-established name over a period of several years, and the donor of the 
podling's IP is explicitly granting the trademark rights to the name to the ASF 
as part of the incubation/graduation, then the podling name search step is 
simply informing trademarks@ of this fact.

If there's a well-established name (or especially a registered one, although 
that's not required) being donated, that in of itself is a very strong 
indicator that the name will continue to be suitable, especially when we 
include it within the Apache Foo branding.  Obviously, if there are any 
previous or current complaints or issues with the pre-existing name, then 
trademarks@ and the PPMC need to evaluate those to ensure they can be dealt 
with as an Apache project.

Thanks to CloudStack PPMC for being diligent as always!

 Establish whether Apache CloudStack is a suitable name
 

 Key: PODLINGNAMESEARCH-23
 URL: 
 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: David Nalley



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Closed] (PODLINGNAMESEARCH-23) Establish whether Apache CloudStack is a suitable name

[David Nalley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Nalley closed PODLINGNAMESEARCH-23.
-

Resolution: Fixed

Thanks for the approval Shane. 

Closing this issue. 

 Establish whether Apache CloudStack is a suitable name
 

 Key: PODLINGNAMESEARCH-23
 URL: 
 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: David Nalley



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Created] (PODLINGNAMESEARCH-23) Establish whether Apache CloudStack is a suitable name

[David Nalley (JIRA)]

David Nalley created PODLINGNAMESEARCH-23:
-

 Summary: Establish whether Apache CloudStack is a suitable name
 Key: PODLINGNAMESEARCH-23
 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: David Nalley




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT][VOTE] Apache CloudStack 4.0.1-incubating

[Joe Brockmeier]

After 72 hours, the vote for CloudStack 4.0.1-incubating *passes* with 3
IPMC +1 vote:

+1 (binding)
* Jim Jagielski
* Olivier Lamy 
* Alex Karasulu

There were no -1 or +0 votes cast. 

Jim, Olivier, and Alex voted on the cloudstack-...@incubator.apache.org
vote thread [1]. 

I will be publishing the release today, and the project's community will
put out its release announcement next week (after the mirrors have
caught up). 

Thanks to everyone for participating!

Best,

jzb
-- 
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Apache CloudStack 4.0.1-incubating

[Joe Brockmeier]

Hi all,

I'd like to call a vote for Apache CloudStack (Incubating) release,
4.0.1-incubating. 

This has been voted through on the cloudstack-...@incubator.apache.org
mailing list (vote thread [1], and results [2]), and now requires a vote
on general@incubator.apache.org.

3 IPMC votes have already been cast on the vote held on cloudstack-dev:

+1 (PPMC / binding) 
* Jim Jagielski (mentor)
* Olivier Lamy (mentor)
* Alex Karasulu (mentor) 

There were no -1 or +0 votes cast. 

Instructions for validating and testing the artifacts can be found here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure

If you have any trouble setting up a test environment using the
procedure on the CloudStack wiki, please ask on the
cloudstack-...@incubator.apache.org list. Someone will be sure to help,
and we'll be sure to improve the test procedure documentation as well.

The following artifacts are up for vote:

Git Branch and Commit SH:

https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=shortlog;h=refs/heads/4.0
Commit: cd83b49ee5107f11a754679b376b8631e3535878

List of changes:
https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0

Source release (checksums and signatures are available here as well):
https://dist.apache.org/repos/dist/dev/incubator/cloudstack/candidates/4.0.1-incubating/

PGP release keys (signed using A0207CD4)
https://dist.apache.org/repos/dist/release/incubator/cloudstack/KEYS

The vote will be open for 72 hours.

For sanity in tallying the vote, can PPMC and IPMC members please be
sure to indicate (binding) with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Thanks!


[1]
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3C20130128212642.GA3954@localhost.localdomain%3E
[2]
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C1359976565.32074.140661186536781.17F27A4D%40webmail.messagingengine.com%3E

Best,

jzb
-- 
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IP Clearance] L4-L7 Network Services in shared networks using VLAN isolation in CloudStack

[David Nalley]

Our 72 hour window has passed. So, I'm calling this IP CLEARANCE complete.

--David

On Sun, Jan 27, 2013 at 3:48 PM, David Nalley da...@gnsa.us wrote:
 Citrix has offered a donation of code to enable L4-L7 Network Services
 in shared networks using VLAN isolation in CloudStack.

 - Code is available on people.a.o [1]
 - Author (Murali Reddy) has submitted a ICLA to secretary@, and it's
 noted on the committer index as having been received.
 - IP Clearance page is up on the incubator site [2]
 - Vote has passed on cloudstack-dev@i.a.o list. [3]

 If you have concerns about this donation, please don't hesitate to
 raise those questions.

 --David

 [1] 
 http://people.apache.org/~muralireddy/0001-CLOUDSTACK-312-enable-L4-L7-network-services-in-the-.patch
 [2] 
 http://incubator.apache.org/ip-clearance/cloudstack-network-services-in-shared-networks.html
 [3] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IP Clearance] CloudStack - Public IP assignment for EIP in Basic zone

[David Nalley]

Our 72 hour window has passed. So, I'm calling this IP CLEARANCE complete.

--David

On Sun, Jan 27, 2013 at 4:31 PM, David Nalley da...@gnsa.us wrote:
 Citrix wishes to donate a feature around providing the option to
 assign a public IP as an Elastic IP in Basic Zones in CloudStack.

 - The patch is available on people.a.o [1]
 - The author (Murali Reddy) has signed an ICLA which has been recorded
 as received by secretary@
 - The IP Clearance form has been uploaded to the incubator website [2]
 - The vote has passed on the cloudstack-dev@i.a.o mailing list [3]

 If there are any concerns around this donation, please don't hesitate
 to raise them.

 --David


 [1] 
 http://people.apache.org/~muralireddy/0001-CLOUDSTACK-265-provide-option-to-turn-off-automatic-.patch
 [2] 
 http://incubator.staging.apache.org/ip-clearance/cloudstack-optional-public-ip-assignment-for-EIP-with-basic-zone.html
 [3] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IP Clearance] CloudStack automated SSH key reset

[David Nalley]

Our 72 hour window has passed. So, I'm calling this IP CLEARANCE complete.

--David

On Sun, Jan 27, 2013 at 4:52 PM, David Nalley da...@gnsa.us wrote:
 Citrix wishes to donate code that permits users of CloudStack to reset
 the SSH key of a VM in an automated fashion.

 - The code in question is on review board [1]
 - The author (Harikrishna Patnala) has submitted an ICLA to secretary@
 which has been received.
 - The IP clearance form is on the incubator website [2]
 - The vote on cloudstack-dev@i.a.o has passed [3]

 If there are any concerns with this donation, please don't hesitate to
 raise them.

 --David

 [1] https://reviews.apache.org/r/8905/diff/2/
 [2] http://incubator.apache.org/ip-clearance/cloudstack-reset-ssh-key.html
 [3] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IP Clearance] CloudStack - enabling Juniper SRX/F5 BigIP inline mode functionality

[David Nalley]

Our 72 hour window has passed. So, I'm calling this IP CLEARANCE complete.

--David

On Sun, Jan 27, 2013 at 5:06 PM, David Nalley da...@gnsa.us wrote:
 Citrix wishes to donate to code that enables Juniper SRX and F5 Big IP
 to work in inline mode within CloudStack.

 - Code is on people.a.o [1]
 - Author (Kelven Yang) has signed an ICLA which has been acknowledged
 by secretary@
 - IP clearance  form is up on the incubator website.
 - Vote has passed on cloudstack-dev@i.a.o

 If there are any concerns about this donation, please don't hesitate
 to raise them.

 --David

 [1] 
 http://people.apache.org/~yasker/SRX_F5_inline_mode/0001-CLOUDSTACK-306-Implement-SRX-firewall.patch
 [2] 
 http://incubator.apache.org/ip-clearance/cloudstack-srx-f5-inline-mode.html
 [3] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] [IP CLEARANCE] Citrix donation of documentation for Apache CloudStack

[David Nalley]

Our 72 hour window has passed. So, I'm calling this IP CLEARANCE complete.

On Sat, Jan 26, 2013 at 12:30 AM, David Nalley da...@gnsa.us wrote:
 Citrix has documentation it wishes to donate to Apache CloudStack

 - The ASF Secretary has recorded an ICLA from the author (Jessica Tomechak).
 - The source code for this documentation was uploaded to people.a.o [1]
 - The IP Clearance form has been added to the incubator site [2]
 - The CloudStack vote to accept the contribution passed [3]

 If there are any concerns, please don't hesitate to raise them.

 --David

 [1] http://people.apache.org/~jtomechak/Jessica_docs.tar
 [2] 
 http://incubator.apache.org/ip-clearance/cloudstack-documentation-for-various-features.html
 [3] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] [IP Clearance] Citrix donation of egress firewall manipulation for guest network to Apache CloudStack

[David Nalley]

Our 72 hour window has passed. So, I'm calling this IP CLEARANCE complete.

--David

On Sat, Jan 26, 2013 at 12:43 AM, David Nalley da...@gnsa.us wrote:
 Citrix has offered donation of egress firewall manipulation for guest
 networks to Apache CloudStack.

 - The code was uploaded to ReviewBoard by the author (Jayapal Reddy) [1]
 - The ASF secretary has received an ICLA from Jayapal.
 - The IP clearance form has been submitted to the incubator site[2]
 - The CloudStack vote to accept the contribution passed [3]

 If there are any concerns, please don't hesitate to raise them.

 --David

 [1] https://reviews.apache.org/r/9010/
 [2] 
 http://incubator.apache.org/ip-clearance/cloudstack-egress-firewall-rules.html
 [3] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] [IP Clearance] Enhanced baremetal support for Apache CloudStack

[David Nalley]

Our 72 hour window has passed. So, I'm calling this IP CLEARANCE complete.

--David

On Sat, Jan 26, 2013 at 12:58 AM, David Nalley da...@gnsa.us wrote:
 - Donation uploaded to people.a.o [1]
 - ICLA from the author (Frank Zhang) has been received by the ASF Secretary.
 - IP Clearance form has been submitted to the incubator site. [2]
 - The CloudStack vote to accept the contribution passed [3]

 One thing to note on this particular submission is that the copyright
 headers aren't currently in compliance with the ASF guidelines, and
 will need to be cleaned up prior to being committed. This was noted in
 the original [VOTE] thread linked to below.

 If you have any concerns about this contribution, please don't
 hesitate to raise them.

 --David

 [1] http://people.apache.org/~frankzhang/CLOUDSTACK-774-baremetal-support.zip
 [2] 
 http://incubator.apache.org/ip-clearance/cloudstack-enahnced-baremetal-provisioning.html
 [3] 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[IP Clearance] L4-L7 Network Services in shared networks using VLAN isolation in CloudStack

[David Nalley]

Citrix has offered a donation of code to enable L4-L7 Network Services
in shared networks using VLAN isolation in CloudStack.

- Code is available on people.a.o [1]
- Author (Murali Reddy) has submitted a ICLA to secretary@, and it's
noted on the committer index as having been received.
- IP Clearance page is up on the incubator site [2]
- Vote has passed on cloudstack-dev@i.a.o list. [3]

If you have concerns about this donation, please don't hesitate to
raise those questions.

--David

[1] 
http://people.apache.org/~muralireddy/0001-CLOUDSTACK-312-enable-L4-L7-network-services-in-the-.patch
[2] 
http://incubator.apache.org/ip-clearance/cloudstack-network-services-in-shared-networks.html
[3] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[IP Clearance] CloudStack - Public IP assignment for EIP in Basic zone

[David Nalley]

Citrix wishes to donate a feature around providing the option to
assign a public IP as an Elastic IP in Basic Zones in CloudStack.

- The patch is available on people.a.o [1]
- The author (Murali Reddy) has signed an ICLA which has been recorded
as received by secretary@
- The IP Clearance form has been uploaded to the incubator website [2]
- The vote has passed on the cloudstack-dev@i.a.o mailing list [3]

If there are any concerns around this donation, please don't hesitate
to raise them.

--David


[1] 
http://people.apache.org/~muralireddy/0001-CLOUDSTACK-265-provide-option-to-turn-off-automatic-.patch
[2] 
http://incubator.staging.apache.org/ip-clearance/cloudstack-optional-public-ip-assignment-for-EIP-with-basic-zone.html
[3] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[IP Clearance] CloudStack automated SSH key reset

[David Nalley]

Citrix wishes to donate code that permits users of CloudStack to reset
the SSH key of a VM in an automated fashion.

- The code in question is on review board [1]
- The author (Harikrishna Patnala) has submitted an ICLA to secretary@
which has been received.
- The IP clearance form is on the incubator website [2]
- The vote on cloudstack-dev@i.a.o has passed [3]

If there are any concerns with this donation, please don't hesitate to
raise them.

--David

[1] https://reviews.apache.org/r/8905/diff/2/
[2] http://incubator.apache.org/ip-clearance/cloudstack-reset-ssh-key.html
[3] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[IP Clearance] CloudStack - enabling Juniper SRX/F5 BigIP inline mode functionality

[David Nalley]

Citrix wishes to donate to code that enables Juniper SRX and F5 Big IP
to work in inline mode within CloudStack.

- Code is on people.a.o [1]
- Author (Kelven Yang) has signed an ICLA which has been acknowledged
by secretary@
- IP clearance  form is up on the incubator website.
- Vote has passed on cloudstack-dev@i.a.o

If there are any concerns about this donation, please don't hesitate
to raise them.

--David

[1] 
http://people.apache.org/~yasker/SRX_F5_inline_mode/0001-CLOUDSTACK-306-Implement-SRX-firewall.patch
[2] http://incubator.apache.org/ip-clearance/cloudstack-srx-f5-inline-mode.html
[3] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[IP CLEARANCE] Citrix donation of documentation for Apache CloudStack

[David Nalley]

Citrix has documentation it wishes to donate to Apache CloudStack

- The ASF Secretary has recorded an ICLA from the author (Jessica Tomechak).
- The source code for this documentation was uploaded to people.a.o [1]
- The IP Clearance form has been added to the incubator site [2]
- The CloudStack vote to accept the contribution passed [3]

If there are any concerns, please don't hesitate to raise them.

--David

[1] http://people.apache.org/~jtomechak/Jessica_docs.tar
[2] 
http://incubator.apache.org/ip-clearance/cloudstack-documentation-for-various-features.html
[3] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[IP Clearance] Citrix donation of egress firewall manipulation for guest network to Apache CloudStack

[David Nalley]

Citrix has offered donation of egress firewall manipulation for guest
networks to Apache CloudStack.

- The code was uploaded to ReviewBoard by the author (Jayapal Reddy) [1]
- The ASF secretary has received an ICLA from Jayapal.
- The IP clearance form has been submitted to the incubator site[2]
- The CloudStack vote to accept the contribution passed [3]

If there are any concerns, please don't hesitate to raise them.

--David

[1] https://reviews.apache.org/r/9010/
[2] 
http://incubator.apache.org/ip-clearance/cloudstack-egress-firewall-rules.html
[3] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[IP Clearance] Enhanced baremetal support for Apache CloudStack

[David Nalley]

- Donation uploaded to people.a.o [1]
- ICLA from the author (Frank Zhang) has been received by the ASF Secretary.
- IP Clearance form has been submitted to the incubator site. [2]
- The CloudStack vote to accept the contribution passed [3]

One thing to note on this particular submission is that the copyright
headers aren't currently in compliance with the ASF guidelines, and
will need to be cleaned up prior to being committed. This was noted in
the original [VOTE] thread linked to below.

If you have any concerns about this contribution, please don't
hesitate to raise them.

--David

[1] http://people.apache.org/~frankzhang/CLOUDSTACK-774-baremetal-support.zip
[2] 
http://incubator.apache.org/ip-clearance/cloudstack-enahnced-baremetal-provisioning.html
[3] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Cloudstack report signoffs

[Joe Schaefer]

May have simply been to indicate that
there's new content in the report that
needs to be processed by mentors.  I'm
not worried about it personally.






 From: Benson Margulies bimargul...@gmail.com
To: cloudstack-...@incubator.apache.org; general@incubator.apache.org 
general@incubator.apache.org 
Sent: Thursday, January 10, 2013 3:58 PM
Subject: Cloudstack report signoffs
 
If I read the diffs correctly, Joe just posted an update to the report
which removed all the mentor signoffs.

Was this on purpose?

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Cloudstack report signoffs

[David Nalley]

On Thu, Jan 10, 2013 at 3:58 PM, Benson Margulies bimargul...@gmail.com wrote:
 If I read the diffs correctly, Joe just posted an update to the report
 which removed all the mentor signoffs.

 Was this on purpose?


This was on purpose.

See: http://markmail.org/message/w5mjdw3yfuxgrv3v

--David

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Cloudstack report signoffs

[Mohammad Nour El-Din]

Hi

   Re-reviewed the report and re-signed it


On Thu, Jan 10, 2013 at 10:31 PM, David Nalley da...@gnsa.us wrote:

 On Thu, Jan 10, 2013 at 3:58 PM, Benson Margulies bimargul...@gmail.com
 wrote:
  If I read the diffs correctly, Joe just posted an update to the report
  which removed all the mentor signoffs.
 
  Was this on purpose?
 

 This was on purpose.

 See: http://markmail.org/message/w5mjdw3yfuxgrv3v

 --David

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org




-- 
Thanks
- Mohammad Nour

Life is like riding a bicycle. To keep your balance you must keep moving
- Albert Einstein

[RESULT][VOTE] Apache CloudStack 4.0.0-incubating

[Chip Childers]

After 72 hours, the vote for CloudStack 4.0.0-incubating *passes* with
5 IPMC +1 votes.

+1 (binding)
* Jim Jagielski
* Olivier Lamy
* Brett Porter
* Daniel Kulp
* Noah Slater

There were no -1 or +0 votes cast.

Jim, Oliver, Brett, Daniel and Noah voted on the
cloudstack-...@incubator.apache.org list's vote thread [1].  Noah also
voted on the general@incubator.apache.org thread [2].

I will now publish the release, and the project's community will
commence with it's release announcement activities (after the mirrors
catch up).

Thanks to everyone participating, and especially to our mentors for
the guidance and support for this first release of CloudStack from
within ASF.  It's been both enlightening and fun!

-chip


[1] 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201210.mbox/%3CCA%2B96GG4KytVOCW%3Ddr7G%3DWg_Nu_zeC%2B3-hiH29wuEjSaisn53Fw%40mail.gmail.com%3E

[2] 
http://mail-archives.apache.org/mod_mbox/incubator-general/201210.mbox/%3CCA%2B96GG7-JycEZmpZhtLxkvOmH0yXaa33n9AdQfvkmZBexQHP9w%40mail.gmail.com%3E

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Shipping binary file in CloudStack release

[Noah Slater]

Thanks for the clarification Roy.

On 31 October 2012 05:29, Roy T. Fielding field...@gbiv.com wrote:

 [generic incubator comments -- nothing specific to CloudStack] ...

 On Oct 29, 2012, at 8:01 AM, Noah Slater wrote:
  On 29 October 2012 14:48, Chip Childers chip.child...@sungard.com
 wrote:
  On Mon, Oct 29, 2012 at 10:39 AM, Noah Slater nsla...@apache.org
 wrote:
  But regardless, you couldn't. A single -1 vote would be
  enough to block the release. Binding or not binding. It doesn't
 matter. If
  somebody expresses a real, and justified, concern about the artefact,
 then
  you don't release until you've addressed that concern.
 
  If that's true, then should the release policy [1] be updated?
 
  [1] http://www.apache.org/dev/release.html#approving-a-release
 
 
  Perhaps.
 
  I know I started out RMing with the idea that I just needed to collect
 more
  +1 votes than -1 votes. But I think that's broken in practice. I think if
  you have a valid, justified, -1 vote, and you release without addressing
  it, then there is something SERIOUSLY wrong.

 It entirely depends on why the -1 is cast.

 Release votes are lazy majority decisions.  They are not at all like
 design decisions or adding a new committer.  A person could -1 a release
 simply because they are working on a new feature and want the group
 to wait until it can be included.  These are matters of opinion.

 If someone casts a -1 because something is seriously wrong, then
 we expect the rest of the PMC to wake up and say -1 as well.
 If they don't, then it isn't seriously wrong even if one or a
 few people think so.  IOW, if it is a serious issue then we can
 expect the majority to agree that it is a serious issue.  There
 is no need to change the rules to accomplish that.

 An RM can choose to stop working on a release at any time.
 We are all volunteers. However, the release decision is made
 by the PMC; if a vote has completed on an artifact, then
 that artifact can be copied to dist by anyone in the PMC.
 If something really bad is found in a voted-on-but-not-yet-announced
 release, then we expect the PMC to work together to ditch the old
 artifacts, fix the problem(s), and start again with a new
 version number.  If they don't, the project has a much larger
 problem than anything we might find in a release.

 Note that there has never been a case where a real problem is
 found and the rest of the group hasn't immediately shut down
 the release.  However, there have been cases where individuals
 have poisoned an entire project simply by dragging their feet on
 the release process for the sake of their own work or world-view.

 A release vote is required to be a majority decision, rather than
 a consensus decision, because Apache understands group dynamics.
 That cork is meant to be popped.  It is better for the group
 that it be popped on a regular basis, where regular is
 defined by the majority of the group.  The more, the merrier.
 Adding glue around the cork to make sure it doesn't pop, unless
 we really really mean it, is not a good plan.  We are far more
 likely to be hurt by a project that can't release than a project
 that occasionally releases too soon.  Folks often lose sight of
 that when focused on fixing a specific issue.

 Roy


 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org




-- 
NS

[VOTE] Apache CloudStack 4.0.0-incubating

[Chip Childers]

Hi All,

I would like to call a vote for Apache CloudStack (Incubating) Release
4.0.0-incubating.

This has been voted through on the cloudstack-...@incubator.apache.org
mailing list (vote thread at [1], results at [2]), and now requires a
vote on general@incubator.apache.org

5 IPMC votes have already been cast (on cloudstack-dev):

+1 (PPMC / binding)
* Jim Jagielski (mentor)
* Olivier Lamy (mentor)
* Brett Porter (mentor)
* Daniel Kulp (mentor)
* Noah Slater (mentor)

There were no -1 or +0 votes cast.

Instructions for Validating and Testing the artifacts can be found here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure

If you have any trouble setting up a test environment using the
procedure above, please ask on the cloudstack-dev@i.a.o list. Someone
will be sure to help, and we'll improve our test procedure
documentation at the same time!

Now, on to the specifics of what we are voting on...

The following artifacts are up for the vote:
http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/

PGP release keys (signed using A99A5D58):
https://dist.apache.org/repos/dist/release/incubator/cloudstack/KEYS

Branch: 4.0
Commit: 6355965dcd956811dd471a9d03c73dadcf68f480 (tagged as 4.0.0-incubating)

List of changes:
https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0

The vote will be open for at least 72 hours.

For sanity in tallying the vote, can PPMC and IPMC members please be
sure to indicate (binding) with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Thanks!

-chip

[1] http://markmail.org/message/otomwu2pt75n6qbn
[2] http://markmail.org/thread/dg6mquboi65t2nho

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache CloudStack 4.0.0-incubating

[Noah Slater]

Sig: OK
Hashes: OK
RAT: OK
Source: OK
Build: OK
Tests: OK

(Based on my voting from yesterday during the project vote.)

(See my post to this list yesterday about the about the waf file, which
I believe to be resolved now.)

On 30 October 2012 18:51, Chip Childers chip.child...@sungard.com wrote:

 Hi All,

 I would like to call a vote for Apache CloudStack (Incubating) Release
 4.0.0-incubating.

 This has been voted through on the cloudstack-...@incubator.apache.org
 mailing list (vote thread at [1], results at [2]), and now requires a
 vote on general@incubator.apache.org

 5 IPMC votes have already been cast (on cloudstack-dev):

 +1 (PPMC / binding)
 * Jim Jagielski (mentor)
 * Olivier Lamy (mentor)
 * Brett Porter (mentor)
 * Daniel Kulp (mentor)
 * Noah Slater (mentor)

 There were no -1 or +0 votes cast.

 Instructions for Validating and Testing the artifacts can be found here:

 https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure

 If you have any trouble setting up a test environment using the
 procedure above, please ask on the cloudstack-dev@i.a.o list. Someone
 will be sure to help, and we'll improve our test procedure
 documentation at the same time!

 Now, on to the specifics of what we are voting on...

 The following artifacts are up for the vote:

 http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/

 PGP release keys (signed using A99A5D58):
 https://dist.apache.org/repos/dist/release/incubator/cloudstack/KEYS

 Branch: 4.0
 Commit: 6355965dcd956811dd471a9d03c73dadcf68f480 (tagged as
 4.0.0-incubating)

 List of changes:

 https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0

 The vote will be open for at least 72 hours.

 For sanity in tallying the vote, can PPMC and IPMC members please be
 sure to indicate (binding) with their vote?

 [ ] +1  approve
 [ ] +0  no opinion
 [ ] -1  disapprove (and reason why)

 Thanks!

 -chip

 [1] http://markmail.org/message/otomwu2pt75n6qbn
 [2] http://markmail.org/thread/dg6mquboi65t2nho

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org




-- 
NS

Re: [VOTE] Apache CloudStack 4.0.0-incubating

[Noah Slater]

Uh, would be handy if I included my vote. ;)

An emphatic +1

On 30 October 2012 19:51, Noah Slater nsla...@apache.org wrote:

 Sig: OK
 Hashes: OK
 RAT: OK
 Source: OK
 Build: OK
 Tests: OK

 (Based on my voting from yesterday during the project vote.)

 (See my post to this list yesterday about the about the waf file, which
 I believe to be resolved now.)


 On 30 October 2012 18:51, Chip Childers chip.child...@sungard.com wrote:

 Hi All,

 I would like to call a vote for Apache CloudStack (Incubating) Release
 4.0.0-incubating.

 This has been voted through on the cloudstack-...@incubator.apache.org
 mailing list (vote thread at [1], results at [2]), and now requires a
 vote on general@incubator.apache.org

 5 IPMC votes have already been cast (on cloudstack-dev):

 +1 (PPMC / binding)
 * Jim Jagielski (mentor)
 * Olivier Lamy (mentor)
 * Brett Porter (mentor)
 * Daniel Kulp (mentor)
 * Noah Slater (mentor)

 There were no -1 or +0 votes cast.

 Instructions for Validating and Testing the artifacts can be found here:

 https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure

 If you have any trouble setting up a test environment using the
 procedure above, please ask on the cloudstack-dev@i.a.o list. Someone
 will be sure to help, and we'll improve our test procedure
 documentation at the same time!

 Now, on to the specifics of what we are voting on...

 The following artifacts are up for the vote:

 http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/

 PGP release keys (signed using A99A5D58):
 https://dist.apache.org/repos/dist/release/incubator/cloudstack/KEYS

 Branch: 4.0
 Commit: 6355965dcd956811dd471a9d03c73dadcf68f480 (tagged as
 4.0.0-incubating)

 List of changes:

 https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0

 The vote will be open for at least 72 hours.

 For sanity in tallying the vote, can PPMC and IPMC members please be
 sure to indicate (binding) with their vote?

 [ ] +1  approve
 [ ] +0  no opinion
 [ ] -1  disapprove (and reason why)

 Thanks!

 -chip

 [1] http://markmail.org/message/otomwu2pt75n6qbn
 [2] http://markmail.org/thread/dg6mquboi65t2nho

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org




 --
 NS




-- 
NS

Re: Shipping binary file in CloudStack release

[Roy T. Fielding]

[generic incubator comments -- nothing specific to CloudStack] ...

On Oct 29, 2012, at 8:01 AM, Noah Slater wrote:
 On 29 October 2012 14:48, Chip Childers chip.child...@sungard.com wrote:
 On Mon, Oct 29, 2012 at 10:39 AM, Noah Slater nsla...@apache.org wrote:
 But regardless, you couldn't. A single -1 vote would be
 enough to block the release. Binding or not binding. It doesn't matter. If
 somebody expresses a real, and justified, concern about the artefact, then
 you don't release until you've addressed that concern.
 
 If that's true, then should the release policy [1] be updated?
 
 [1] http://www.apache.org/dev/release.html#approving-a-release
 
 
 Perhaps.
 
 I know I started out RMing with the idea that I just needed to collect more
 +1 votes than -1 votes. But I think that's broken in practice. I think if
 you have a valid, justified, -1 vote, and you release without addressing
 it, then there is something SERIOUSLY wrong.

It entirely depends on why the -1 is cast.

Release votes are lazy majority decisions.  They are not at all like
design decisions or adding a new committer.  A person could -1 a release
simply because they are working on a new feature and want the group
to wait until it can be included.  These are matters of opinion.

If someone casts a -1 because something is seriously wrong, then
we expect the rest of the PMC to wake up and say -1 as well.
If they don't, then it isn't seriously wrong even if one or a
few people think so.  IOW, if it is a serious issue then we can
expect the majority to agree that it is a serious issue.  There
is no need to change the rules to accomplish that.

An RM can choose to stop working on a release at any time.
We are all volunteers. However, the release decision is made
by the PMC; if a vote has completed on an artifact, then
that artifact can be copied to dist by anyone in the PMC.
If something really bad is found in a voted-on-but-not-yet-announced
release, then we expect the PMC to work together to ditch the old
artifacts, fix the problem(s), and start again with a new
version number.  If they don't, the project has a much larger
problem than anything we might find in a release.

Note that there has never been a case where a real problem is
found and the rest of the group hasn't immediately shut down
the release.  However, there have been cases where individuals
have poisoned an entire project simply by dragging their feet on
the release process for the sake of their own work or world-view.

A release vote is required to be a majority decision, rather than
a consensus decision, because Apache understands group dynamics.
That cork is meant to be popped.  It is better for the group
that it be popped on a regular basis, where regular is
defined by the majority of the group.  The more, the merrier.
Adding glue around the cork to make sure it doesn't pop, unless
we really really mean it, is not a good plan.  We are far more
likely to be hurt by a project that can't release than a project
that occasionally releases too soon.  Folks often lose sight of
that when focused on fixing a specific issue.

Roy


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Shipping binary file in CloudStack release

[Bertrand Delacretaz]

On Sun, Oct 28, 2012 at 7:01 PM, Noah Slater nsla...@apache.org wrote:
 ...We're just voting on our first release, and I spotted this file in the root
 of the source:

 https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=waf;hb=HEAD

 It seems to be a sort of hybrid source/binary file. Very strange.

 Can we ship this?...

I wouldn't define that file as source code, so IMO you cannot release
it as such.
Sounds like something for a separate -deps package.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Shipping binary file in CloudStack release

[Florian Holeczek]

Hi Noah,

 We're just voting on our first release, and I spotted this file in the root
 of the source:
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=waf;hb=HEAD
 
 It seems to be a sort of hybrid source/binary file. Very strange.
 
 Can we ship this?

it's this one: http://code.google.com/p/waf/
The website says it's licensed under the New BSD License.

Regards
 Florian

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Shipping binary file in CloudStack release

[Chip Childers]

Hi all,

I'm the RM for the release, so I wanted to provide some context to
Noah's question.  Some of this has already been mentioned on the
project's vote thread, but I'll bring it up again here to see if there
are any thoughts to help us decide if this is a blocker or not.  At
this point, I'm holding the vote thread open after 7 days of voting
(with a current +1 count of 5 PPMC votes, 4 mentors, and another 16
community votes - with no -1's or 0's), until I get a better feel for
the level of concern on this issue.

Here's the background:

Waf is a packaging utility, used to create RPMs and DEBs.  Work is
currently ongoing to remove it (and it's use) from the project
entirely, so we're not doing something that isn't already targeted for
being undone as fast as possible.   The challenge we have as a
community is that the removal of Waf will require a pretty heavy
amount of development time and another full round of functional /
regression testing.  That will be several weeks of work (not days),
which is significantly longer than the community's desire to get a
first podling release out the door (our original goal was for the end
of the summer).

And here's my current thinking:

It's one line of bytecode within a file that is not core to the
project itself (it's only a build utility), that has a clearly marked
license for file itself (so distribution is OK from a licensing
standpoint), that is only used as a quick way to create packages for
Linux distros (not to do the actual project builds), and that will be
ignored by any distro packagers that want to create proper RPMs / DEBs
anyway.

IMO, this does not represent a serious enough issue to block a
release.  As far as I understand the point of the incubation process,
this is the place where minor issues can be addressed over time.  (I'm
new to ASF,  so please do correct me if I'm wrong about that.)

I actually have more than enough votes right now to close the thread
out on the project's dev list, and open up a vote for the IPMC.  That
being said, I'm new to ASF and want us to get things right.  I
certainly don't want to use formalities like the voting rules process
to push past something that actually is a major problem, but I really
don't want to abort the vote due to what I personally view as a minor
issue.  It will potentially cause harm to the community, which has
been developing very nicely over the last several months.

Anyway, that's what we're struggling with.  Looking forward to your opinions...

-chip

On Sun, Oct 28, 2012 at 2:01 PM, Noah Slater nsla...@apache.org wrote:
 Hey,

 We're just voting on our first release, and I spotted this file in the root
 of the source:

 https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=waf;hb=HEAD

 It seems to be a sort of hybrid source/binary file. Very strange.

 Can we ship this?

 Thanks,

 --
 NS

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Shipping binary file in CloudStack release

[Chip Childers]

On Mon, Oct 29, 2012 at 8:57 AM, Benson Margulies bimargul...@gmail.com wrote:
 On Mon, Oct 29, 2012 at 4:26 AM, Florian Holeczek flor...@holeczek.de wrote:
 Hi Noah,

 We're just voting on our first release, and I spotted this file in the root
 of the source:

 https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=waf;hb=HEAD

 It seems to be a sort of hybrid source/binary file. Very strange.

 Can we ship this?

 it's this one: http://code.google.com/p/waf/
 The website says it's licensed under the New BSD License.

 This file is a an installer for an entire subsystem of python stuff,
 encoded with python pickle, built by their build script. If I
 understand what's going on, running it unpacks a tree of python
 *source*. So, it's no more good (or bad) than shipping a .tar.bz2 of
 some category A open source code (given the license).

 It would be more better, I suppose, to grab the corresponding source
 tree and run their build script as part of your build script, but I'm
 a bit puzzled as to whether this, as is, is actually a problem.

Benson,

I absolutely agree that it would be better to pull from the Waf
project source, and build prior to a user using it.  That being said,
your point about being puzzled as to whether it's a blocker or not is
exactly our issue (hence raising it on this list).


 Regards
  Florian

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org


 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Shipping binary file in CloudStack release

[Noah Slater]

On 29 October 2012 14:48, Chip Childers chip.child...@sungard.com wrote:

 On Mon, Oct 29, 2012 at 10:39 AM, Noah Slater nsla...@apache.org wrote:
  Thanks for following up Chip. Though I do just want to clarify one
  misconception.
 
  On 29 October 2012 13:21, Chip Childers chip.child...@sungard.com
 wrote:
 
 
  I actually have more than enough votes right now to close the thread
  out on the project's dev list, and open up a vote for the IPMC.
 
 
  No you don't.
 
  To me, this sounds like you're saying to be honest, I could just close
 the
  vote and ship this right now if I wanted to. I'm not sure if that was
 the
  intended message.

 Nope, that's not what I was saying.  That's taking a single comment
 out of the context of the larger email.


Well, in fairness, that is how I understood it *within* the context of your
entire email. I hope you don't think I was just looking for something to
take out of context to disagree with you on? I think we know each other
better than that by now! ;)



  But regardless, you couldn't. A single -1 vote would be
  enough to block the release. Binding or not binding. It doesn't matter.
 If
  somebody expresses a real, and justified, concern about the artefact,
 then
  you don't release until you've addressed that concern.

 If that's true, then should the release policy [1] be updated?

 [1] http://www.apache.org/dev/release.html#approving-a-release


Perhaps.

I know I started out RMing with the idea that I just needed to collect more
+1 votes than -1 votes. But I think that's broken in practice. I think if
you have a valid, justified, -1 vote, and you release without addressing
it, then there is something SERIOUSLY wrong.

-- 
NS

Re: Shipping binary file in CloudStack release

[Emmanuel Lécharny]

Le 10/29/12 3:39 PM, Noah Slater a écrit :

Thanks for following up Chip. Though I do just want to clarify one
misconception.

On 29 October 2012 13:21, Chip Childers chip.child...@sungard.com wrote:


I actually have more than enough votes right now to close the thread
out on the project's dev list, and open up a vote for the IPMC.


No you don't.

To me, this sounds like you're saying to be honest, I could just close the
vote and ship this right now if I wanted to. I'm not sure if that was the
intended message. But regardless, you couldn't. A single -1 vote would be
enough to block the release.



Binding or not binding. It doesn't matter. If
somebody expresses a real, and justified, concern about the artefact, then
you don't release until you've addressed that concern.

Technically speaking, for releases, a -1 is not a veto :

http://www.apache.org/foundation/voting.html
 Votes on Package Releases

Votes on whether a package is ready to be released use majority approval 
http://www.apache.org/foundation/glossary.html#MajorityApproval -- 
i.e. at least three PMC members must vote affirmatively for release, and 
there must be more positive than negative votes. *Releases may not be 
vetoed.* Generally the community will cancel the release vote if anyone 
identifies serious problems, but in most cases the ultimate decision, 
lies with the individual serving as release manager. The specifics of 
the process may vary from project to project, but the 'minimum quorum of 
three +1 votes' rule is universal.


However, having -1 would be a sign that something goes wrong. Either on 
the community side, or on the voter side ;) Better try to see why a -1 
(or many) have been casted before going for the release in such a case.


--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Shipping binary file in CloudStack release

[Chip Childers]

On Mon, Oct 29, 2012 at 11:01 AM, Noah Slater nsla...@apache.org wrote:
 On 29 October 2012 14:48, Chip Childers chip.child...@sungard.com wrote:

 On Mon, Oct 29, 2012 at 10:39 AM, Noah Slater nsla...@apache.org wrote:
  Thanks for following up Chip. Though I do just want to clarify one
  misconception.
 
  On 29 October 2012 13:21, Chip Childers chip.child...@sungard.com
 wrote:
 
 
  I actually have more than enough votes right now to close the thread
  out on the project's dev list, and open up a vote for the IPMC.
 
 
  No you don't.
 
  To me, this sounds like you're saying to be honest, I could just close
 the
  vote and ship this right now if I wanted to. I'm not sure if that was
 the
  intended message.

 Nope, that's not what I was saying.  That's taking a single comment
 out of the context of the larger email.


 Well, in fairness, that is how I understood it *within* the context of your
 entire email. I hope you don't think I was just looking for something to
 take out of context to disagree with you on? I think we know each other
 better than that by now! ;)


I'll try to be more clear next time.  I'm holding the vote open
specifically because of this outstanding question, *regardless* of the
current tally.  That's what I was expressing.


  But regardless, you couldn't. A single -1 vote would be
  enough to block the release. Binding or not binding. It doesn't matter.
 If
  somebody expresses a real, and justified, concern about the artefact,
 then
  you don't release until you've addressed that concern.

 If that's true, then should the release policy [1] be updated?

 [1] http://www.apache.org/dev/release.html#approving-a-release


 Perhaps.

 I know I started out RMing with the idea that I just needed to collect more
 +1 votes than -1 votes. But I think that's broken in practice. I think if
 you have a valid, justified, -1 vote, and you release without addressing
 it, then there is something SERIOUSLY wrong.

 --
 NS

No disagreement.  Again, that's why I'm holding the vote open until we
get enough clarity on the topic being discussed here.

IMO, fixing this in the policy would include a statement about the RM
having the right (but not the obligation) to abort the vote based on
any individual issue raised by a voter.  But perhaps this is a topic
for another list...

Using this thread a specific example, I'll abort if the advice here is
that waf needs to be removed in it's current form.

-chip

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Shipping binary file in CloudStack release

[Noah Slater]

On 29 October 2012 15:13, Chip Childers chip.child...@sungard.com wrote:


 I'll try to be more clear next time.  I'm holding the vote open
 specifically because of this outstanding question, *regardless* of the
 current tally.  That's what I was expressing.


Understood. I suspected we were on the same page, but I wanted to make sure.


 No disagreement.  Again, that's why I'm holding the vote open until we
 get enough clarity on the topic being discussed here.


Yep, and thank you. Especially considering the considerable delay in me
being able to find time to test.


 IMO, fixing this in the policy would include a statement about the RM
 having the right (but not the obligation) to abort the vote based on
 any individual issue raised by a voter.  But perhaps this is a topic
 for another list...

 Using this thread a specific example, I'll abort if the advice here is
 that waf needs to be removed in it's current form.


This may be an area for project bylaws.

On CouchDB, as the release manager, I added this to our release process:

The release manager has the power to abort a vote at any point and for any
reason.

I advise we do the same for CloudStack.

Basically, as RM, as long as you're operating within the Apache framework
and principals, and there is a documented release policy that the community
(even tacitly) agrees with, then you are empowered to do whatever you want
within the limits of that.


-- 
NS

Re: Shipping binary file in CloudStack release

[Chip Childers]

On Mon, Oct 29, 2012 at 9:38 AM, Chip Childers
chip.child...@sungard.com wrote:
 On Mon, Oct 29, 2012 at 8:57 AM, Benson Margulies bimargul...@gmail.com 
 wrote:
 On Mon, Oct 29, 2012 at 4:26 AM, Florian Holeczek flor...@holeczek.de 
 wrote:
 Hi Noah,

 We're just voting on our first release, and I spotted this file in the root
 of the source:

 https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=waf;hb=HEAD

 It seems to be a sort of hybrid source/binary file. Very strange.

 Can we ship this?

 it's this one: http://code.google.com/p/waf/
 The website says it's licensed under the New BSD License.

 This file is a an installer for an entire subsystem of python stuff,
 encoded with python pickle, built by their build script. If I
 understand what's going on, running it unpacks a tree of python
 *source*. So, it's no more good (or bad) than shipping a .tar.bz2 of
 some category A open source code (given the license).

 It would be more better, I suppose, to grab the corresponding source
 tree and run their build script as part of your build script, but I'm
 a bit puzzled as to whether this, as is, is actually a problem.

 Benson,

 I absolutely agree that it would be better to pull from the Waf
 project source, and build prior to a user using it.  That being said,
 your point about being puzzled as to whether it's a blocker or not is
 exactly our issue (hence raising it on this list).

Bringing this thread back to the topic at hand, any further opinions
about the severity of this file being include in the release artifact?

Looking forward to your inputs.



 Regards
  Florian

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org


 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Shipping binary file in CloudStack release

[Bertrand Delacretaz]

Hi,

On Mon, Oct 29, 2012 at 2:21 PM, Chip Childers
chip.child...@sungard.com wrote:
 ...Waf is a packaging utility, used to create RPMs and DEBs.  Work is
 currently ongoing to remove it (and it's use) from the project
 entirely...
 ...That will be several weeks of work (not days),
 which is significantly longer than the community's desire to get a
 first podling release out the door...

I don't think any Incubator PMC member is asking you to remove that
dependency, as I see it the only issue is that you are currently
aiming to release in in binary form.

 ...It's one line of bytecode within a file that is not core to the
 project itself ...

I don't think the issue is how big or how small that thing is: we do
not release binaries, see http://www.apache.org/dev/release.html

So IMO your options now are:

a) Fix the problem and recut your release without that binary. Make it
a separate -deps convenience package.

b) Come up with a documented plan (issue in your tracker for example)
for how you're going to remove it from future releases, and still try
to get this release through.

c) Try to convince us that such things are not really important, which
does not seem successful so far.

IMO, doing a) will get you immediate +1s. It's not uncommon for
podling releases to go through a few iterations before being accepted,
so I'm not sure what the problem with creating a separate -deps
package is.

Choosing b) or c) lowers your chances for mentors and Incubator PMC to
give their +1s to the release.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Shipping binary file in CloudStack release

[Noah Slater]

Nice summary Bertrand.


On 29 October 2012 15:22, Bertrand Delacretaz bdelacre...@apache.orgwrote:

 Hi,

 On Mon, Oct 29, 2012 at 2:21 PM, Chip Childers
 chip.child...@sungard.com wrote:
  ...Waf is a packaging utility, used to create RPMs and DEBs.  Work is
  currently ongoing to remove it (and it's use) from the project
  entirely...
  ...That will be several weeks of work (not days),
  which is significantly longer than the community's desire to get a
  first podling release out the door...

 I don't think any Incubator PMC member is asking you to remove that
 dependency, as I see it the only issue is that you are currently
 aiming to release in in binary form.

  ...It's one line of bytecode within a file that is not core to the
  project itself ...

 I don't think the issue is how big or how small that thing is: we do
 not release binaries, see http://www.apache.org/dev/release.html

 So IMO your options now are:

 a) Fix the problem and recut your release without that binary. Make it
 a separate -deps convenience package.


I concur with Chip that this would come with a non-negligible cost to
community spirit at this point. We've already been through a few rounds. I
would +0 this is the community wanted to do it, but I would also
be disappointed that we had to stop the release for something so minor.


 b) Come up with a documented plan (issue in your tracker for example)
 for how you're going to remove it from future releases, and still try
 to get this release through.


Given the relative unimportance, and size, of the file in question, I would
be willing to cast a binding +1 vote (as mentor and very new member of the
Incubator PMC) on this, if we would say for definite that we remove this
problem for the next release. But I was looking for some confirmation from
this list that this is OK.


 c) Try to convince us that such things are not really important, which
 does not seem successful so far.


Yes, I don't think that's going to happen.


 IMO, doing a) will get you immediate +1s. It's not uncommon for
 podling releases to go through a few iterations before being accepted,
 so I'm not sure what the problem with creating a separate -deps
 package is.

 Choosing b) or c) lowers your chances for mentors and Incubator PMC to
 give their +1s to the release.

 -Bertrand

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org




-- 
NS

Re: Shipping binary file in CloudStack release

[Benson Margulies]

Bertrand, is a compressed archive of source a source or a binary?

On Oct 29, 2012, at 11:28 AM, Noah Slater nsla...@apache.org wrote:

 Nice summary Bertrand.


 On 29 October 2012 15:22, Bertrand Delacretaz bdelacre...@apache.orgwrote:

 Hi,

 On Mon, Oct 29, 2012 at 2:21 PM, Chip Childers
 chip.child...@sungard.com wrote:
 ...Waf is a packaging utility, used to create RPMs and DEBs.  Work is
 currently ongoing to remove it (and it's use) from the project
 entirely...
 ...That will be several weeks of work (not days),
 which is significantly longer than the community's desire to get a
 first podling release out the door...

 I don't think any Incubator PMC member is asking you to remove that
 dependency, as I see it the only issue is that you are currently
 aiming to release in in binary form.

 ...It's one line of bytecode within a file that is not core to the
 project itself ...

 I don't think the issue is how big or how small that thing is: we do
 not release binaries, see http://www.apache.org/dev/release.html

 So IMO your options now are:

 a) Fix the problem and recut your release without that binary. Make it
 a separate -deps convenience package.
 I concur with Chip that this would come with a non-negligible cost to
 community spirit at this point. We've already been through a few rounds. I
 would +0 this is the community wanted to do it, but I would also
 be disappointed that we had to stop the release for something so minor.


 b) Come up with a documented plan (issue in your tracker for example)
 for how you're going to remove it from future releases, and still try
 to get this release through.

 Given the relative unimportance, and size, of the file in question, I would
 be willing to cast a binding +1 vote (as mentor and very new member of the
 Incubator PMC) on this, if we would say for definite that we remove this
 problem for the next release. But I was looking for some confirmation from
 this list that this is OK.


 c) Try to convince us that such things are not really important, which
 does not seem successful so far.

 Yes, I don't think that's going to happen.


 IMO, doing a) will get you immediate +1s. It's not uncommon for
 podling releases to go through a few iterations before being accepted,
 so I'm not sure what the problem with creating a separate -deps
 package is.

 Choosing b) or c) lowers your chances for mentors and Incubator PMC to
 give their +1s to the release.

 -Bertrand

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org


 --
 NS

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Shipping binary file in CloudStack release

[Bertrand Delacretaz]

On Mon, Oct 29, 2012 at 4:32 PM, Benson Margulies bimargul...@gmail.com wrote:
 Bertrand, is a compressed archive of source a source or a binary?

hehe...right, you said earlier in this thread that the file in
question is actually just compressed source code, is that correct?

If yes, it's just weird to include it in that form but I agree that
the no binaries problem is not that important then, if one can
decompress and verify the actual source code. The reason we don't
release binaries is that it's usually impossible to verify them as
being harmless.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Shipping binary file in CloudStack release

[Marvin Humphrey]

On Mon, Oct 29, 2012 at 5:57 AM, Benson Margulies bimargul...@gmail.com wrote:

 So, it's no more good (or bad) than shipping a .tar.bz2 of
 some category A open source code (given the license).

+1

From your description, this is different from a compiled object file, it's
compressed source.  No information is lost, it's just obfuscated and can be
restored.  It's a little annoying as would be releasing source transformed via
rot-13, but it's still source IMO.

 It would be more better, I suppose, to grab the corresponding source
 tree and run their build script as part of your build script, but I'm
 a bit puzzled as to whether this, as is, is actually a problem.

Doesn't seem like a blocker to me, so long as people have expanded the archive
and are happy with what's inside.

Marvin Humphrey

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Shipping binary file in CloudStack release

[Chip Childers]

On Mon, Oct 29, 2012 at 11:41 AM, Marvin Humphrey
mar...@rectangular.com wrote:
 On Mon, Oct 29, 2012 at 5:57 AM, Benson Margulies bimargul...@gmail.com 
 wrote:

 So, it's no more good (or bad) than shipping a .tar.bz2 of
 some category A open source code (given the license).

 +1

 From your description, this is different from a compiled object file, it's
 compressed source.  No information is lost, it's just obfuscated and can be
 restored.  It's a little annoying as would be releasing source transformed via
 rot-13, but it's still source IMO.

 It would be more better, I suppose, to grab the corresponding source
 tree and run their build script as part of your build script, but I'm
 a bit puzzled as to whether this, as is, is actually a problem.

 Doesn't seem like a blocker to me, so long as people have expanded the archive
 and are happy with what's inside.

Thanks all.

I've just expanded the archive, and reviewed the contents.  It indeed
appears to be the source code for version 1.5.18 of waf.  I can't find
any issues with including this source code (excluding the obvious
weirdness about how it's included in our release package).

Any other concerns?

 Marvin Humphrey

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Shipping binary file in CloudStack release

[Chip Childers]

On Mon, Oct 29, 2012 at 11:37 AM, Bertrand Delacretaz
bdelacre...@apache.org wrote:
 On Mon, Oct 29, 2012 at 4:32 PM, Benson Margulies bimargul...@gmail.com 
 wrote:
 Bertrand, is a compressed archive of source a source or a binary?

 hehe...right, you said earlier in this thread that the file in
 question is actually just compressed source code, is that correct?

That's correct.  We ( the project ) were actually concerned that it
was compiled python code.  Benson is right.  In reality, it's just
compressed source.  I have extracted it and reviewed the contents.
It's the waf source.

 If yes, it's just weird to include it in that form but I agree that
 the no binaries problem is not that important then, if one can
 decompress and verify the actual source code. The reason we don't
 release binaries is that it's usually impossible to verify them as
 being harmless.

 -Bertrand

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Shipping binary file in CloudStack release

[Noah Slater]

Thanks for investigating this, Chip.

I am happy with us proceeding, but would caution us to think about
addressing or documenting this in a later release.

I'd say wait until tomorrow to see if anyone else objects then wrap up the
vote.

Let's ship this thing!

On 29 October 2012 16:21, Chip Childers chip.child...@sungard.com wrote:

 On Mon, Oct 29, 2012 at 11:37 AM, Bertrand Delacretaz
 bdelacre...@apache.org wrote:
  On Mon, Oct 29, 2012 at 4:32 PM, Benson Margulies bimargul...@gmail.com
 wrote:
  Bertrand, is a compressed archive of source a source or a binary?
 
  hehe...right, you said earlier in this thread that the file in
  question is actually just compressed source code, is that correct?

 That's correct.  We ( the project ) were actually concerned that it
 was compiled python code.  Benson is right.  In reality, it's just
 compressed source.  I have extracted it and reviewed the contents.
 It's the waf source.

  If yes, it's just weird to include it in that form but I agree that
  the no binaries problem is not that important then, if one can
  decompress and verify the actual source code. The reason we don't
  release binaries is that it's usually impossible to verify them as
  being harmless.
 
  -Bertrand
 
  -
  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
  For additional commands, e-mail: general-h...@incubator.apache.org
 
 

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org




-- 
NS

Shipping binary file in CloudStack release

[Noah Slater]

Hey,

We're just voting on our first release, and I spotted this file in the root
of the source:

https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=waf;hb=HEAD

It seems to be a sort of hybrid source/binary file. Very strange.

Can we ship this?

Thanks,

-- 
NS

Re: [VOTE] CloudStack for Apache Incubator

[Matt Hogstrom]

+1 (binding)

Matt Hogstrom
m...@hogstrom.org

A Day Without Nuclear Fusion Is a Day Without Sunshine

On Apr 9, 2012, at 9:32 PM, Kevin Kluge wrote:

 Hi All.  I'd like to call for a VOTE for CloudStack to enter the Incubator.  
 The proposal is available at [1] and I have also included it below.   Please 
 vote with:
 +1: accept CloudStack into Incubator
 +0: don't care
 -1: do not accept CloudStack into Incubator (please explain the objection)
 
 The vote is open for at least 72 hours from now (until at least 19:00 US-PST 
 on April 12, 2012).
 
 Thanks for the consideration.
 
 -kevin
 
 [1] http://wiki.apache.org/incubator/CloudStackProposal
 
 
 
 
 Abstract
 
 CloudStack is an IaaS (Infrastracture as a Service) cloud orchestration 
 platform.
 
 Proposal
 
 CloudStack provides control plane software that can be used to create an IaaS 
 cloud. It includes an HTTP-based API for user and administrator functions and 
 a web UI for user and administrator access. Administrators can provision 
 physical infrastructure (e.g., servers, network elements, storage) into an 
 instance of CloudStack, while end users can use the CloudStack self-service 
 API and UI for the provisioning and management of virtual machines, virtual 
 disks, and virtual networks.
 
 Citrix Systems, Inc. submits this proposal to donate the CloudStack source 
 code, documentation, websites, and trademarks to the Apache Software 
 Foundation (ASF).
 
 Background
 
 Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds 
 provide virtual machines to end users. CloudStack additionally provides 
 baremetal OS installation to end users via a self-service interface. The 
 management of physical resources to provide the larger goal of cloud service 
 delivery is known as orchestration. IaaS clouds are usually described as 
 elastic -- an elastic service is one that allows its user to rapidly scale 
 up or down their need for resources.
 
 A number of open source projects and companies have been created to implement 
 IaaS clouds. Cloud.com started CloudStack in 2008 and released the source 
 under GNU General Public License version 3 (GPL v3) in 2010. Citrix 
 acquired Cloud.com, including CloudStack, in 2011. Citrix re-licensed the 
 CloudStack source under Apache License v2 in April, 2012.
 
 Rationale
 
 IaaS clouds provide the ability to implement datacenter operations in a 
 programmable fashion. This functionality is tremendously powerful and 
 benefits the community by providing:
 
 - More efficient use of datacenter personnel
 - More efficient use of datacenter hardware
 - Better responsiveness to user requests
 - Better uptime/availability through automation
 
 While there are several open source IaaS efforts today, none are governed by 
 an independent foundation such as ASF. Vendor influence and/or proprietary 
 implementations may limit the community's ability to choose the hardware and 
 software for use in the datacenter. The community at large will benefit from 
 the ability to enhance the orchestration layer as needed for particular 
 hardware or software support, and to implement algorithms and features that 
 may reduce cost or increase user satisfaction for specific use cases. In this 
 respect the independent nature of the ASF is key to the long term health and 
 success of the project.
 
 Initial Goals
 
 The CloudStack project has two initial goals after the proposal is accepted 
 and the incubation has begun.
 
 The Cloudstack Project's first goal is to ensure that the CloudStack source 
 includes only third party code that is licensed under the Apache License or 
 open source licenses that are approved by the ASF for use in ASF projects. 
 The CloudStack Project has begun the process of removing third party code 
 that is not licensed under an ASF approved license. This is an ongoing 
 process that will continue into the incubation period. Third party code 
 contributed to CloudStack under the CloudStack contribution agreement was 
 assigned to Cloud.com in exchange for distributing CloudStack under GPLv3. 
 The CloudStack project has begun the process of amending the previous 
 CloudStack contribution agreements to obtain consent from existing 
 contributors to change the CloudStack project's license. In the event that an 
 existing contributor does not consent to this change, the project is prepared 
 to remove that contributor's code. Additionally, there are binary 
 dependencies on redistributed libraries that are not provided with an 
 ASF-approved license. Finally, the CloudStack has source files incorporated 
 from third parties that were not provided with an ASF-approved license. We 
 have begun the process of re-writing this software. This is an ongoing 
 process that will extend into the incubation period. These issues are 
 discussed in more detail later in the proposal.
 
 Although CloudStack is open source, many design documents and discussions 
 that should have been publicly

[RESULT][VOTE] CloudStack for Apache Incubator

[Kevin Kluge]

More than 72 hours have passed and the vote totals are:

21 Binding +1 votes
13 Non-binding +1 votes
0 +0 votes
0 -1 votes


Binding +1 votes from:
Raymond Feng
Olivier Lamy
Jean-Baptiste Onofré
Emmanuel Lécharny
Mohammad Nour El-Din
Alex Karasulu
Ate Douma
Matthew Franklin
Daniel Kulp
Davanum Srinivas 
Alan D. Cabrera
Ralph Goers
Dave Fisher
Chris Mattmann
Hadrian Zbarcea
Marcel Offermans
Gianugo Rabellino 
Tom White
Arun C Murthy
Jim Jagielski
Matt Hogstrom


Based on this I understand that the vote has passed.   We've reached out to the 
infrastructure team to begin setting up the CloudStack project with ASF.   
Looking forward to it, and thanks all!

-kevin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] CloudStack for Apache Incubator

[Mohammad Nour El-Din]

I believe this [VOTE] is ready to be wrapped up Kevin ;)

On Fri, Apr 13, 2012 at 3:46 PM, Jim Jagielski j...@jagunet.com wrote:


 On Apr 9, 2012, at 9:32 PM, Kevin Kluge wrote:

  Hi All.  I'd like to call for a VOTE for CloudStack to enter the
 Incubator.  The proposal is available at [1] and I have also included it
 below.   Please vote with:
  +1: accept CloudStack into Incubator
  +0: don't care
  -1: do not accept CloudStack into Incubator (please explain the
 objection)
 
  The vote is open for at least 72 hours from now (until at least 19:00
 US-PST on April 12, 2012).
 
  Thanks for the consideration.
 
  -kevin
 
  [1] http://wiki.apache.org/incubator/CloudStackProposal


 +1 (binding)
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org




-- 
Thanks
- Mohammad Nour

Life is like riding a bicycle. To keep your balance you must keep moving
- Albert Einstein

Re: [VOTE] CloudStack for Apache Incubator

[Jim Jagielski]

On Apr 9, 2012, at 9:32 PM, Kevin Kluge wrote:

 Hi All.  I'd like to call for a VOTE for CloudStack to enter the Incubator.  
 The proposal is available at [1] and I have also included it below.   Please 
 vote with:
 +1: accept CloudStack into Incubator
 +0: don't care
 -1: do not accept CloudStack into Incubator (please explain the objection)
 
 The vote is open for at least 72 hours from now (until at least 19:00 US-PST 
 on April 12, 2012).
 
 Thanks for the consideration.
 
 -kevin
 
 [1] http://wiki.apache.org/incubator/CloudStackProposal


+1 (binding)
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] CloudStack for Apache Incubator

[Jukka Zitting]

Hi,

On Tue, Apr 10, 2012 at 3:32 AM, Kevin Kluge kevin.kl...@citrix.com wrote:
 I'd like to call for a VOTE for CloudStack to enter the Incubator.

+1: accept CloudStack into Incubator

PS. Unless you've already done so, please get in touch with the ASF
infra team as soon as possible on the various infrastructure topics
mentioned. Experience from other complex podlings suggests that the
infrastructure migration may take months and be somewhat painful
unless properly planned and managed.

BR,

Jukka Zitting

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] CloudStack for Apache Incubator

[Brett Porter]

On 10/04/2012, at 11:32 AM, Kevin Kluge wrote:

 Hi All.  I'd like to call for a VOTE for CloudStack to enter the Incubator.  
 The proposal is available at [1] and I have also included it below.   Please 
 vote with:
 +1: accept CloudStack into Incubator
 +0: don't care
 -1: do not accept CloudStack into Incubator (please explain the objection)
 
 The vote is open for at least 72 hours from now (until at least 19:00 US-PST 
 on April 12, 2012).


+1

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter






-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] CloudStack for Apache Incubator

[Olivier Lamy]

+1 ( binding)

2012/4/10 Kevin Kluge kevin.kl...@citrix.com:
 Hi All.  I'd like to call for a VOTE for CloudStack to enter the Incubator.  
 The proposal is available at [1] and I have also included it below.   Please 
 vote with:
 +1: accept CloudStack into Incubator
 +0: don't care
 -1: do not accept CloudStack into Incubator (please explain the objection)

 The vote is open for at least 72 hours from now (until at least 19:00 US-PST 
 on April 12, 2012).

 Thanks for the consideration.

 -kevin

 [1] http://wiki.apache.org/incubator/CloudStackProposal




 Abstract

 CloudStack is an IaaS (Infrastracture as a Service) cloud orchestration 
 platform.

 Proposal

 CloudStack provides control plane software that can be used to create an IaaS 
 cloud. It includes an HTTP-based API for user and administrator functions and 
 a web UI for user and administrator access. Administrators can provision 
 physical infrastructure (e.g., servers, network elements, storage) into an 
 instance of CloudStack, while end users can use the CloudStack self-service 
 API and UI for the provisioning and management of virtual machines, virtual 
 disks, and virtual networks.

 Citrix Systems, Inc. submits this proposal to donate the CloudStack source 
 code, documentation, websites, and trademarks to the Apache Software 
 Foundation (ASF).

 Background

 Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds 
 provide virtual machines to end users. CloudStack additionally provides 
 baremetal OS installation to end users via a self-service interface. The 
 management of physical resources to provide the larger goal of cloud service 
 delivery is known as orchestration. IaaS clouds are usually described as 
 elastic -- an elastic service is one that allows its user to rapidly scale 
 up or down their need for resources.

 A number of open source projects and companies have been created to implement 
 IaaS clouds. Cloud.com started CloudStack in 2008 and released the source 
 under GNU General Public License version 3 (GPL v3) in 2010. Citrix 
 acquired Cloud.com, including CloudStack, in 2011. Citrix re-licensed the 
 CloudStack source under Apache License v2 in April, 2012.

 Rationale

 IaaS clouds provide the ability to implement datacenter operations in a 
 programmable fashion. This functionality is tremendously powerful and 
 benefits the community by providing:

 - More efficient use of datacenter personnel
 - More efficient use of datacenter hardware
 - Better responsiveness to user requests
 - Better uptime/availability through automation

 While there are several open source IaaS efforts today, none are governed by 
 an independent foundation such as ASF. Vendor influence and/or proprietary 
 implementations may limit the community's ability to choose the hardware and 
 software for use in the datacenter. The community at large will benefit from 
 the ability to enhance the orchestration layer as needed for particular 
 hardware or software support, and to implement algorithms and features that 
 may reduce cost or increase user satisfaction for specific use cases. In this 
 respect the independent nature of the ASF is key to the long term health and 
 success of the project.

 Initial Goals

 The CloudStack project has two initial goals after the proposal is accepted 
 and the incubation has begun.

 The Cloudstack Project's first goal is to ensure that the CloudStack source 
 includes only third party code that is licensed under the Apache License or 
 open source licenses that are approved by the ASF for use in ASF projects. 
 The CloudStack Project has begun the process of removing third party code 
 that is not licensed under an ASF approved license. This is an ongoing 
 process that will continue into the incubation period. Third party code 
 contributed to CloudStack under the CloudStack contribution agreement was 
 assigned to Cloud.com in exchange for distributing CloudStack under GPLv3. 
 The CloudStack project has begun the process of amending the previous 
 CloudStack contribution agreements to obtain consent from existing 
 contributors to change the CloudStack project's license. In the event that an 
 existing contributor does not consent to this change, the project is prepared 
 to remove that contributor's code. Additionally, there are binary 
 dependencies on redistributed libraries that are not provided with an 
 ASF-approved license. Finally, the CloudStack has source files incorporated 
 from third parties that were not provided with an ASF-approved license. We 
 have begun the process of re-writing this software. This is an ongoing 
 process that will extend into the incubation period. These issues are 
 discussed in more detail later in the proposal.

 Although CloudStack is open source, many design documents and discussions 
 that should have been publicly available and accessible were not publicized. 
 The Project's second goal will be to fix this lack of transparency

Re: [VOTE] CloudStack for Apache Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On 04/10/2012 08:45 AM, Olivier Lamy wrote:

+1 ( binding)

2012/4/10 Kevin Klugekevin.kl...@citrix.com:

Hi All.  I'd like to call for a VOTE for CloudStack to enter the Incubator.  
The proposal is available at [1] and I have also included it below.   Please 
vote with:
+1: accept CloudStack into Incubator
+0: don't care
-1: do not accept CloudStack into Incubator (please explain the objection)

The vote is open for at least 72 hours from now (until at least 19:00 US-PST on 
April 12, 2012).

Thanks for the consideration.

-kevin

[1] http://wiki.apache.org/incubator/CloudStackProposal




Abstract

CloudStack is an IaaS (Infrastracture as a Service) cloud orchestration 
platform.

Proposal

CloudStack provides control plane software that can be used to create an IaaS 
cloud. It includes an HTTP-based API for user and administrator functions and a 
web UI for user and administrator access. Administrators can provision physical 
infrastructure (e.g., servers, network elements, storage) into an instance of 
CloudStack, while end users can use the CloudStack self-service API and UI for 
the provisioning and management of virtual machines, virtual disks, and virtual 
networks.

Citrix Systems, Inc. submits this proposal to donate the CloudStack source code, 
documentation, websites, and trademarks to the Apache Software Foundation 
(ASF).

Background

Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds provide virtual 
machines to end users. CloudStack additionally provides baremetal OS installation to end users via 
a self-service interface. The management of physical resources to provide the larger goal of cloud 
service delivery is known as orchestration. IaaS clouds are usually described as 
elastic -- an elastic service is one that allows its user to rapidly scale up or down 
their need for resources.

A number of open source projects and companies have been created to implement IaaS 
clouds. Cloud.com started CloudStack in 2008 and released the source under GNU General 
Public License version 3 (GPL v3) in 2010. Citrix acquired Cloud.com, 
including CloudStack, in 2011. Citrix re-licensed the CloudStack source under Apache 
License v2 in April, 2012.

Rationale

IaaS clouds provide the ability to implement datacenter operations in a 
programmable fashion. This functionality is tremendously powerful and benefits 
the community by providing:

- More efficient use of datacenter personnel
- More efficient use of datacenter hardware
- Better responsiveness to user requests
- Better uptime/availability through automation

While there are several open source IaaS efforts today, none are governed by an 
independent foundation such as ASF. Vendor influence and/or proprietary 
implementations may limit the community's ability to choose the hardware and 
software for use in the datacenter. The community at large will benefit from 
the ability to enhance the orchestration layer as needed for particular 
hardware or software support, and to implement algorithms and features that may 
reduce cost or increase user satisfaction for specific use cases. In this 
respect the independent nature of the ASF is key to the long term health and 
success of the project.

Initial Goals

The CloudStack project has two initial goals after the proposal is accepted and 
the incubation has begun.

The Cloudstack Project's first goal is to ensure that the CloudStack source 
includes only third party code that is licensed under the Apache License or 
open source licenses that are approved by the ASF for use in ASF projects. The 
CloudStack Project has begun the process of removing third party code that is 
not licensed under an ASF approved license. This is an ongoing process that 
will continue into the incubation period. Third party code contributed to 
CloudStack under the CloudStack contribution agreement was assigned to 
Cloud.com in exchange for distributing CloudStack under GPLv3. The CloudStack 
project has begun the process of amending the previous CloudStack contribution 
agreements to obtain consent from existing contributors to change the 
CloudStack project's license. In the event that an existing contributor does 
not consent to this change, the project is prepared to remove that 
contributor's code. Additionally, there are binary dependencies on 
redistributed libraries that

are not provided with an ASF-approved license. Finally, the CloudStack has 
source files incorporated from third parties that were not provided with an 
ASF-approved license. We have begun the process of re-writing this software. 
This is an ongoing process that will extend into the incubation period. These 
issues are discussed in more detail later in the proposal.


Although CloudStack is open source, many design documents and discussions that 
should have been publicly available and accessible were not publicized. The 
Project's second goal will be to fix this lack of transparency

Re: [VOTE] CloudStack for Apache Incubator

[Ashish]

+1 (non-binding)


 2012/4/10 Kevin Klugekevin.kl...@citrix.com:

 Hi All.  I'd like to call for a VOTE for CloudStack to enter the
 Incubator.  The proposal is available at [1] and I have also included it
 below.   Please vote with:
 +1: accept CloudStack into Incubator
 +0: don't care
 -1: do not accept CloudStack into Incubator (please explain the
 objection)

 The vote is open for at least 72 hours from now (until at least 19:00
 US-PST on April 12, 2012).

 Thanks for the consideration.

 -kevin

 [1] http://wiki.apache.org/incubator/CloudStackProposal




 Abstract

 CloudStack is an IaaS (Infrastracture as a Service) cloud orchestration
 platform.

 Proposal

 CloudStack provides control plane software that can be used to create an
 IaaS cloud. It includes an HTTP-based API for user and administrator
 functions and a web UI for user and administrator access. Administrators can
 provision physical infrastructure (e.g., servers, network elements, storage)
 into an instance of CloudStack, while end users can use the CloudStack
 self-service API and UI for the provisioning and management of virtual
 machines, virtual disks, and virtual networks.

 Citrix Systems, Inc. submits this proposal to donate the CloudStack
 source code, documentation, websites, and trademarks to the Apache Software
 Foundation (ASF).

 Background

 Amazon and other cloud pioneers invented IaaS clouds. Typically these
 clouds provide virtual machines to end users. CloudStack additionally
 provides baremetal OS installation to end users via a self-service
 interface. The management of physical resources to provide the larger goal
 of cloud service delivery is known as orchestration. IaaS clouds are
 usually described as elastic -- an elastic service is one that allows its
 user to rapidly scale up or down their need for resources.

 A number of open source projects and companies have been created to
 implement IaaS clouds. Cloud.com started CloudStack in 2008 and released the
 source under GNU General Public License version 3 (GPL v3) in 2010. Citrix
 acquired Cloud.com, including CloudStack, in 2011. Citrix re-licensed the
 CloudStack source under Apache License v2 in April, 2012.

 Rationale

 IaaS clouds provide the ability to implement datacenter operations in a
 programmable fashion. This functionality is tremendously powerful and
 benefits the community by providing:

 - More efficient use of datacenter personnel
 - More efficient use of datacenter hardware
 - Better responsiveness to user requests
 - Better uptime/availability through automation

 While there are several open source IaaS efforts today, none are governed
 by an independent foundation such as ASF. Vendor influence and/or
 proprietary implementations may limit the community's ability to choose the
 hardware and software for use in the datacenter. The community at large will
 benefit from the ability to enhance the orchestration layer as needed for
 particular hardware or software support, and to implement algorithms and
 features that may reduce cost or increase user satisfaction for specific use
 cases. In this respect the independent nature of the ASF is key to the long
 term health and success of the project.

 Initial Goals

 The CloudStack project has two initial goals after the proposal is
 accepted and the incubation has begun.

 The Cloudstack Project's first goal is to ensure that the CloudStack
 source includes only third party code that is licensed under the Apache
 License or open source licenses that are approved by the ASF for use in ASF
 projects. The CloudStack Project has begun the process of removing third
 party code that is not licensed under an ASF approved license. This is an
 ongoing process that will continue into the incubation period. Third party
 code contributed to CloudStack under the CloudStack contribution agreement
 was assigned to Cloud.com in exchange for distributing CloudStack under
 GPLv3. The CloudStack project has begun the process of amending the previous
 CloudStack contribution agreements to obtain consent from existing
 contributors to change the CloudStack project's license. In the event that
 an existing contributor does not consent to this change, the project is
 prepared to remove that contributor's code. Additionally, there are binary
 dependencies on redistributed libraries that

 are not provided with an ASF-approved license. Finally, the CloudStack has
 source files incorporated from third parties that were not provided with an
 ASF-approved license. We have begun the process of re-writing this software.
 This is an ongoing process that will extend into the incubation period.
 These issues are discussed in more detail later in the proposal.


 Although CloudStack is open source, many design documents and discussions
 that should have been publicly available and accessible were not publicized.
 The Project's second goal will be to fix this lack of transparency by
 encouraging the initial committers

Re: [VOTE] CloudStack for Apache Incubator

[Emmanuel Lécharny]

+1: accept CloudStack into Incubator
(binding)


--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] CloudStack for Apache Incubator

[Mohammad Nour El-Din]

+1 (binding)

On Tue, Apr 10, 2012 at 8:55 AM, Emmanuel Lécharny elecha...@gmail.comwrote:

 +1: accept CloudStack into Incubator
 (binding)


 --
 Regards,
 Cordialement,
 Emmanuel Lécharny
 www.iktek.com



 --**--**-
 To unsubscribe, e-mail: 
 general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org
 For additional commands, e-mail: 
 general-help@incubator.apache.**orggeneral-h...@incubator.apache.org




-- 
Thanks
- Mohammad Nour

Life is like riding a bicycle. To keep your balance you must keep moving
- Albert Einstein

Re: [VOTE] CloudStack for Apache Incubator

[Alex Karasulu]

+1 (binding)

-- 
Best Regards,
-- Alex

Re: [VOTE] CloudStack for Apache Incubator

[dsh]

[X] +1: accept CloudStack into Incubator (non-binding)
[] +0: don't care
[] -1: do not accept CloudStack into Incubator (please explain the objection)

Cheers
Daniel

On Tue, Apr 10, 2012 at 3:32 AM, Kevin Kluge kevin.kl...@citrix.com wrote:
 Hi All.  I'd like to call for a VOTE for CloudStack to enter the Incubator.  
 The proposal is available at [1] and I have also included it below.   Please 
 vote with:
 +1: accept CloudStack into Incubator
 +0: don't care
 -1: do not accept CloudStack into Incubator (please explain the objection)

 The vote is open for at least 72 hours from now (until at least 19:00 US-PST 
 on April 12, 2012).

 Thanks for the consideration.

 -kevin

 [1] http://wiki.apache.org/incubator/CloudStackProposal




 Abstract

 CloudStack is an IaaS (Infrastracture as a Service) cloud orchestration 
 platform.

 Proposal

 CloudStack provides control plane software that can be used to create an IaaS 
 cloud. It includes an HTTP-based API for user and administrator functions and 
 a web UI for user and administrator access. Administrators can provision 
 physical infrastructure (e.g., servers, network elements, storage) into an 
 instance of CloudStack, while end users can use the CloudStack self-service 
 API and UI for the provisioning and management of virtual machines, virtual 
 disks, and virtual networks.

 Citrix Systems, Inc. submits this proposal to donate the CloudStack source 
 code, documentation, websites, and trademarks to the Apache Software 
 Foundation (ASF).

 Background

 Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds 
 provide virtual machines to end users. CloudStack additionally provides 
 baremetal OS installation to end users via a self-service interface. The 
 management of physical resources to provide the larger goal of cloud service 
 delivery is known as orchestration. IaaS clouds are usually described as 
 elastic -- an elastic service is one that allows its user to rapidly scale 
 up or down their need for resources.

 A number of open source projects and companies have been created to implement 
 IaaS clouds. Cloud.com started CloudStack in 2008 and released the source 
 under GNU General Public License version 3 (GPL v3) in 2010. Citrix 
 acquired Cloud.com, including CloudStack, in 2011. Citrix re-licensed the 
 CloudStack source under Apache License v2 in April, 2012.

 Rationale

 IaaS clouds provide the ability to implement datacenter operations in a 
 programmable fashion. This functionality is tremendously powerful and 
 benefits the community by providing:

 - More efficient use of datacenter personnel
 - More efficient use of datacenter hardware
 - Better responsiveness to user requests
 - Better uptime/availability through automation

 While there are several open source IaaS efforts today, none are governed by 
 an independent foundation such as ASF. Vendor influence and/or proprietary 
 implementations may limit the community's ability to choose the hardware and 
 software for use in the datacenter. The community at large will benefit from 
 the ability to enhance the orchestration layer as needed for particular 
 hardware or software support, and to implement algorithms and features that 
 may reduce cost or increase user satisfaction for specific use cases. In this 
 respect the independent nature of the ASF is key to the long term health and 
 success of the project.

 Initial Goals

 The CloudStack project has two initial goals after the proposal is accepted 
 and the incubation has begun.

 The Cloudstack Project's first goal is to ensure that the CloudStack source 
 includes only third party code that is licensed under the Apache License or 
 open source licenses that are approved by the ASF for use in ASF projects. 
 The CloudStack Project has begun the process of removing third party code 
 that is not licensed under an ASF approved license. This is an ongoing 
 process that will continue into the incubation period. Third party code 
 contributed to CloudStack under the CloudStack contribution agreement was 
 assigned to Cloud.com in exchange for distributing CloudStack under GPLv3. 
 The CloudStack project has begun the process of amending the previous 
 CloudStack contribution agreements to obtain consent from existing 
 contributors to change the CloudStack project's license. In the event that an 
 existing contributor does not consent to this change, the project is prepared 
 to remove that contributor's code. Additionally, there are binary 
 dependencies on redistributed libraries that are not provided with an 
 ASF-approved license. Finally, the CloudStack has source files incorporated 
 from third parties that were not provided with an ASF-approved license. We 
 have begun the process of re-writing this software. This is an ongoing 
 process that will extend into the incubation period. These issues are 
 discussed in more detail later in the proposal.

 Although CloudStack is open source, many