Re: [VOTE] Move Chukwa to incubator
On Thu, Jun 24, 2010 at 8:21 PM, William A. Rowe Jr. wrote: > On 6/23/2010 8:12 AM, Bernd Fondermann wrote: >> On Wed, Jun 23, 2010 at 14:45, ant elder wrote: >> >>> IMHO we should insist on using the incubator naming for the Chukwa >>> website/svn/MLs because I think Chukwa should just go directly to a >>> TLP and if they have to use the incubator naming it may help them >>> decide that the direct to TLP route really is better ;-) >> >> I see you blinking here, so I guess this is not just for putting up a >> strawman ;-) > > Well folks, it's a fun debate and all, but it isn't helping bring this > vote to a conclusion :) > > Is anyone in agreement with ant? Otherwise we should just move ahead > and can hold a separate vote on allowing tlp resource creation at this > time. > > If the proposers want (Eric?) a three choice vote, 1. recommend TLP with > guides to help the initial pmc, 2. accept incubating with tlp resource > naming, but -incubating release naming, or 3. accept incubating requiring > all incubator naming conventions, that might help the incubator simplify > this decision. > > At this point, I personally guess that 1. might be the most sensible in > terms of resource creation and management; Option 1. sounds most sensible to me too. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
{[RESULT][VOTE] Nuvem Project
On Sat, Jun 19, 2010 at 8:07 AM, Luciano Resende wrote: > After initial discussion [1], please vote on the acceptance of Nuvem > Project for incubation at the Apache Incubator. The full proposal is > available at the end of this message and on the wiki at > > http://wiki.apache.org/incubator/Nuvem > > We ask the Incubator PMC to sponsor the project with Luciano Resende > as the Champion and Jean-Frederic Clere, Paul Fremantle, Ant Elder and > Donald Woods volunteering to be mentors. > > Please cast your votes: > > [ ] +1, bring Nuvem into Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring Nuvem into Incubator, because... > > The vote is open for the next 72 hours and only votes from the > Incubator PMC are binding. > > [1] http://www.mail-archive.com/general@incubator.apache.org/msg24841.html > [2] http://wiki.apache.org/incubator/Nuvem > > > = > Apache Nuvem, a cross-cloud application programming interface > = > > Abstract > --- > > Nuvem will define an open application programming interface for common > cloud application services, allowing applications to be easily ported > across the most popular cloud platforms. > > Proposal > --- > > * Define an open API that abstracts common cloud platform services to > help decouple the application logic from the particulars of a specific > proprietary cloud. > * Implement the Nuvem API for popular clouds such as Google > AppEngine, Amazon EC2 and Microsoft Azure. > * Initially focus on User Authentication and Authorization, > Distributed Cache, Data Store, Queuing; then extend to other services > such as Chat, Logging, and Debugging. > > Background > > > An important issue for application developers is to avoid lock-in to a > specific cloud application platform. By providing a cross-cloud > application programming interface that abstracts common cloud platform > services, Nuvem addresses this concern and strives to help make > applications easily portable across multiple clouds. > > In mixed cloud deployments, applications need to access platform > services across cloud boundaries. Nuvem will make this possible by > providing a remote API for these cloud application platform services. > > Rationale > - > > There are currently no efforts to define a truly open-source API to > abstract common cloud platform services. Nuvem strives to create a > community around building an open-source cloud application programming > interface in a manner that fully allows for tried-and-true open source > mechanisms such as user-driven innovation. > > Initial Goals > > > A Nuvem prototype is currently being developed in an Apache Tuscany > sandbox, providing initial support for some cloud platform services > from Google AppEngine and Amazon EC2. We look at moving this prototype > to the Apache Incubator as the next step to broaden the community, > expand the API to support more services and cloud platforms. > > Current Status > > > The initial code has been developed under the Apache Software License > 2.0 by current Apache committers. > > Meritocracy > --- > > We recognize the importance of running the project as a meritocracy. > We are eager to engage other members of the community and operate to > the standard of meritocracy that Apache emphasizes; we believe this is > the most effective method of growing our community and enabling > widespread adoption. > > Community > --- > > The initial committer list consists of a couple of independent > developers. We expect that the project will greatly increase in > contribution base, and this is one aspect the project will monitor in > becoming ready for graduation. > > Alignment > -- > > Currently, there are no other Apache projects concerned with building > a cross-cloud API for application platform services. We feel that it > would be a good complement to the set of Apache projects and could > provide them with an API for interacting with cloud application > platforms. > > Nuvem complements Apache libCloud and Deltacloud projects (which both > cover provisioning and elasticity in the cloud), providing portability > of applications and application services across heterogeneous cloud > environments. > > Orphaned Products > -- > > The Nuvem developers have a long-term interest in use and maintenance > of the code and there is also hope that different cloud providers will > be interested in providing support for the Nuvem API and will join the > project. We feel that it is important to put formal governance in > place both for the project and the contributors as the project > expands. We feel the ASF is the best location for this. > > Inexperience with Open Source > -- > > Luciano Resende have been involved with Open Source Software for > s
Re: [VOTE] Move Chukwa to incubator
Hrm. I think my preference is for 1 or 2. Given that Chukwa already has a fair bit of infrastructure up and running, seems like fewer renames is better and would reduce user confusion. --Ari On Thu, Jun 24, 2010 at 3:21 PM, William A. Rowe Jr. wrote: > On 6/23/2010 8:12 AM, Bernd Fondermann wrote: >> On Wed, Jun 23, 2010 at 14:45, ant elder wrote: >> >>> IMHO we should insist on using the incubator naming for the Chukwa >>> website/svn/MLs because I think Chukwa should just go directly to a >>> TLP and if they have to use the incubator naming it may help them >>> decide that the direct to TLP route really is better ;-) >> >> I see you blinking here, so I guess this is not just for putting up a >> strawman ;-) > > Well folks, it's a fun debate and all, but it isn't helping bring this > vote to a conclusion :) > > Is anyone in agreement with ant? Otherwise we should just move ahead > and can hold a separate vote on allowing tlp resource creation at this > time. > > If the proposers want (Eric?) a three choice vote, 1. recommend TLP with > guides to help the initial pmc, 2. accept incubating with tlp resource > naming, but -incubating release naming, or 3. accept incubating requiring > all incubator naming conventions, that might help the incubator simplify > this decision. > > At this point, I personally guess that 1. might be the most sensible in > terms of resource creation and management; it would simply require the > group to vote for an initial chair/VP. If they are unsure of their group > yet, perhaps one of the other mentors would offer to serve as their chair > for the first six months, if they rather would do that? > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Ari Rabkin asrab...@gmail.com UC Berkeley Computer Science Department - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Move Chukwa to incubator
On 6/23/2010 8:12 AM, Bernd Fondermann wrote: > On Wed, Jun 23, 2010 at 14:45, ant elder wrote: > >> IMHO we should insist on using the incubator naming for the Chukwa >> website/svn/MLs because I think Chukwa should just go directly to a >> TLP and if they have to use the incubator naming it may help them >> decide that the direct to TLP route really is better ;-) > > I see you blinking here, so I guess this is not just for putting up a > strawman ;-) Well folks, it's a fun debate and all, but it isn't helping bring this vote to a conclusion :) Is anyone in agreement with ant? Otherwise we should just move ahead and can hold a separate vote on allowing tlp resource creation at this time. If the proposers want (Eric?) a three choice vote, 1. recommend TLP with guides to help the initial pmc, 2. accept incubating with tlp resource naming, but -incubating release naming, or 3. accept incubating requiring all incubator naming conventions, that might help the incubator simplify this decision. At this point, I personally guess that 1. might be the most sensible in terms of resource creation and management; it would simply require the group to vote for an initial chair/VP. If they are unsure of their group yet, perhaps one of the other mentors would offer to serve as their chair for the first six months, if they rather would do that? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
