[VOTE] Accept Cassandra into the Incubator (Summary)
After 5 days, the following is the vote summary of the binding votes (apologies if I missed your vote in advance). +1: (5) Brian, Ian, Otis, Dims, Emmanuel +0: (2) Bertrand, Torsten -1: (1) Niclas ?: Jason, Martijn, Matthieu (commented but no vote) The only concern on the voting process was that it was started on the 23rd (GMT) and that people were not given enough time. I extended the vote for 2 more days to help alleviate that. I'll leave it up to the PMC/board if they consider this sufficient, as they can invalidate the vote on those grounds (possibly others that i'm not aware of too). I would like to say In defense of the vote, that of the people who discussed the Cassandra proposal since it was proposed on the 2nd, only two (Paul & Roland) have not voted/commented. According to my notes, only Paul has a binding vote and has been active on other apache threads during the period that the vote was being held. Regards Ian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator (Summary)
+1 Brian's response clarified the situation for me. On 28-Dec-08, at 7:29 PM, Ian Holsman wrote: After 5 days, the following is the vote summary of the binding votes (apologies if I missed your vote in advance). +1: (5) Brian, Ian, Otis, Dims, Emmanuel +0: (2) Bertrand, Torsten -1: (1) Niclas ?: Jason, Martijn, Matthieu (commented but no vote) The only concern on the voting process was that it was started on the 23rd (GMT) and that people were not given enough time. I extended the vote for 2 more days to help alleviate that. I'll leave it up to the PMC/board if they consider this sufficient, as they can invalidate the vote on those grounds (possibly others that i'm not aware of too). I would like to say In defense of the vote, that of the people who discussed the Cassandra proposal since it was proposed on the 2nd, only two (Paul & Roland) have not voted/commented. According to my notes, only Paul has a binding vote and has been active on other apache threads during the period that the vote was being held. Regards Ian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- We know what we are, but know not what we may be. -- Shakespeare - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
My concern is that though the original FB devs told that they wanted to move to apache, they are (according to what I've read here) silent again. The discussions on the original list did not show a trust in a community without the Facebook devs. Futhermore, from what I've read on the original lists is that the original FB devs are accustomed to a code dump style of development. I'd like to hear from them how they are going to open up their development, or in the proposal how to mitigate such practices. Martijn On Sat, Dec 27, 2008 at 9:18 PM, Brian McCallister wrote: > On Sat, Dec 27, 2008 at 11:26 AM, Martijn Dashorst > wrote: >> I'd like to see some plan on dealing with the fork/community stuff. We >> *know* it is a problem, and I'd like to see how this is being >> addressed in the proposal. In my opinion that is the crux to this >> proposal. Just going Apache is not going to solve problems. The >> feather is not a magic wand you can wave around and make problems >> disappear. >> >> What will happen when the original coders won't come with the project? >> What when they do and then disappear *again*? How will you get the >> folks on board that don't want to come over? > > The "fork" was something proposed by Ian because there was no clear > path for folks to become involved with Cassandra. The folks working on > it at Facebook didn't want to see a fork, and proposed entering > incubation in order to structure opening up development. Avinash and > the others on the proposal *are* the core contributors, there is no > fork, and hopefully there will be no need to. > > No one expects to wave a feather over the code and have a vibrant > developer community appear, but you *can* wave a wand and have a set > of expectations appear, which is what Cassandra is trying to do. > > The plan: follow the normal apache process. Folks contribute good > stuff, the folks involved recognize this and make the contributor a > committer, useful code continues to come into existence, rinse-repeat. > > The "plan" is no different than any apache project. > > -Brian > >> >> Martijn >> >> On Sat, Dec 27, 2008 at 6:13 PM, Brian McCallister wrote: >>> I consider this to be a high-risk project, and agree with Martjin's >>> concerns, but do not consider this a bar to entering incubation. The >>> *reason* Cassandra wants to enter incubation is to address these >>> weaknesses. >>> >>> +1 >>> >>> -Brian >>> >>> On Tue, Dec 23, 2008 at 2:01 PM, Ian Holsman wrote: Dear Incubator PMC, There has been some discussion around the Cassandra proposal, and we would now like to officially propose Cassandra to the Incubator for consideration.. Please vote on accepting Cassandra project for incubation. The full Cassandra proposal is available at the end of this message and as a wiki page at http://wiki.apache.org/incubator/Cassandra. We ask the Incubator PMC to sponsor the Cassandra podling, with Brian as the Champion, and Torsten, Matthieu, and Ian volunteering to mentor as well. The vote is open for the next 72 hours and only votes from the Incubator PMC are binding. [ ] +1 Accept Cassandra as a new podling [ ] -1 Do not accept the new podling (provide reason, please) = Abstract = Cassandra is a distributed storage system for managing structured/unstructured data while providing reliability at a massive scale. = Background = Development of Cassandra started in Facebook in June 2007. It started of a system to solve the Inbox Search problem and since then has matured to solve various storage problems associated with structured/unstructured data. = Rationale = Cassandra is a distributed storage system for managing structured data that is designed to scale to a very large size across many commodity servers, with no single point of failure. The philosophy behind the design of the storage portion of Cassandra is that it be able to satisfy the requirements of applications that demand storage of large amounts of structured data. Reliability at massive scale is a very big challenge. Outages in the service can have significant negative impact. Hence Cassandra aims to run on top of an infrastructure of hundreds of nodes (possibly spread across different datacenters). At this scale, small and large components fail continuously; the way Cassandra manages the persistent state in the face of these failures drives the reliability and scalability of the software systems relying on this service. = Initial Source = Intial Source can be obtained from the following site - http://the-cassandra-project.googlecode.com/svn/branches/development/. The mailing list is currently maintained at the same site. We will move it over to Apache once this proposal has been accepted. >>
Re: [VOTE] Accept Cassandra into the Incubator
Hi Martijn. The major bottleneck with the FB devs in the repository is that they are using a separate one internally for their development and then refactoring it for public use. Prashant has committed to using the public repository in the future. (see thread "get a cold and miss all the fun"). As Brian mentioned, one of the primary focuses for the incubation will be getting non-FB contributors to contribute. Regards Ian Martijn Dashorst wrote: My concern is that though the original FB devs told that they wanted to move to apache, they are (according to what I've read here) silent again. The discussions on the original list did not show a trust in a community without the Facebook devs. Futhermore, from what I've read on the original lists is that the original FB devs are accustomed to a code dump style of development. I'd like to hear from them how they are going to open up their development, or in the proposal how to mitigate such practices. Martijn On Sat, Dec 27, 2008 at 9:18 PM, Brian McCallister wrote: On Sat, Dec 27, 2008 at 11:26 AM, Martijn Dashorst wrote: I'd like to see some plan on dealing with the fork/community stuff. We *know* it is a problem, and I'd like to see how this is being addressed in the proposal. In my opinion that is the crux to this proposal. Just going Apache is not going to solve problems. The feather is not a magic wand you can wave around and make problems disappear. What will happen when the original coders won't come with the project? What when they do and then disappear *again*? How will you get the folks on board that don't want to come over? The "fork" was something proposed by Ian because there was no clear path for folks to become involved with Cassandra. The folks working on it at Facebook didn't want to see a fork, and proposed entering incubation in order to structure opening up development. Avinash and the others on the proposal *are* the core contributors, there is no fork, and hopefully there will be no need to. No one expects to wave a feather over the code and have a vibrant developer community appear, but you *can* wave a wand and have a set of expectations appear, which is what Cassandra is trying to do. The plan: follow the normal apache process. Folks contribute good stuff, the folks involved recognize this and make the contributor a committer, useful code continues to come into existence, rinse-repeat. The "plan" is no different than any apache project. -Brian Martijn On Sat, Dec 27, 2008 at 6:13 PM, Brian McCallister wrote: I consider this to be a high-risk project, and agree with Martjin's concerns, but do not consider this a bar to entering incubation. The *reason* Cassandra wants to enter incubation is to address these weaknesses. +1 -Brian On Tue, Dec 23, 2008 at 2:01 PM, Ian Holsman wrote: Dear Incubator PMC, There has been some discussion around the Cassandra proposal, and we would now like to officially propose Cassandra to the Incubator for consideration.. Please vote on accepting Cassandra project for incubation. The full Cassandra proposal is available at the end of this message and as a wiki page at http://wiki.apache.org/incubator/Cassandra. We ask the Incubator PMC to sponsor the Cassandra podling, with Brian as the Champion, and Torsten, Matthieu, and Ian volunteering to mentor as well. The vote is open for the next 72 hours and only votes from the Incubator PMC are binding. [ ] +1 Accept Cassandra as a new podling [ ] -1 Do not accept the new podling (provide reason, please) = Abstract = Cassandra is a distributed storage system for managing structured/unstructured data while providing reliability at a massive scale. = Background = Development of Cassandra started in Facebook in June 2007. It started of a system to solve the Inbox Search problem and since then has matured to solve various storage problems associated with structured/unstructured data. = Rationale = Cassandra is a distributed storage system for managing structured data that is designed to scale to a very large size across many commodity servers, with no single point of failure. The philosophy behind the design of the storage portion of Cassandra is that it be able to satisfy the requirements of applications that demand storage of large amounts of structured data. Reliability at massive scale is a very big challenge. Outages in the service can have significant negative impact. Hence Cassandra aims to run on top of an infrastructure of hundreds of nodes (possibly spread across different datacenters). At this scale, small and large components fail continuously; the way Cassandra manages the persistent state in the face of these failures drives the reliability and scalability of the software systems relying on this service. = Initial Source = Intial Source can be obtained from the following site - http://the-cassandra-project.googlecode.com/svn/branches/development/. The mailing list is curr
Re: [VOTE] Accept Cassandra into the Incubator
On Mon, Dec 29, 2008 at 9:48 AM, Ian Holsman wrote: > getting non-FB contributors to contribute. Isn't this an oxymoron? Cheers Niclas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Niclas Hedhman wrote: On Mon, Dec 29, 2008 at 9:48 AM, Ian Holsman wrote: getting non-FB contributors to contribute. Isn't this an oxymoron? c/contribute/re-contribute/ Cheers Niclas - 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
