You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Ian Holsman <li...@holsman.net> on 2008/12/23 23:01:37 UTC
[VOTE] Accept Cassandra into the Incubator
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.
= Source and Intellectual Property Submission Plan =
= External Dependencies =
* All dependencies have Apache compatible licenses. Dependencies are
log4j, Thrift, Apache Commons.
= Cryptography =
* None
= Committers =
* Avinash Lakshman
* Prashant Malik
* Kannan Muthukkaruppan
* Jiansheng Huang
* Dan Dumitriu
= Current Status =
== Meritocracy ==
* Though initial development was done at Facebook, Cassandra was
intended to be released as an open source project from its inception.
Environment will lend itself to support meritocracy at all times.
== Community ==
* Folks who are actively considering deploying/prototyping Cassandra in
their respective organizations.
== Core Developers ==
* Avinash Lakshman
* Prashant Malik
* Kannan Muthukkaruppan
== License ==
* The Cassandra codebase is Apache 2.0 licensed, and currently hosted at
Google Code.
= Known Risks/Avoiding the Warning Signs =
== Orphaned Products ==
* Cassandra is already deployed within Facebook and many other
organizations are actively moving to deploy this in production. Original
developers
are and will actively stay involved and hence there is no realistic
chance of it getting orphaned.
== Homogenous Developers ==
* The current list of committers includes developers from different
companies. The committers are geographically distributed across the U.S.
== Reliance on Salaried Developers ==
* Yes. But don't expect this to be a risk of any nature.
== Relationships with Other Apache Products ==
* The Cassandra project is 'similar' to hbase/HDFS in concept, but
Cassandra is more geared for Online web site usage than batch. It also
doesn't have a single point of failure, which makes it interesting as well.
* Cassandra makes use of the Thrift project.
== An excessive fascination with the Apache brand ==
* Cassandra has already attracted a stable base of users. There are at
least 3 companies who are planning to use Cassandra in production as far
as we know. The reasons for joining Apache are not to advertise the
project, but rather to demonstrate the commitment to open source by
divorcing the trunk from any one corporation and pursuing further
integration with other Apache projects.
= Required Resources =
== Mailing lists ==
Once the project is approved, the following mailing lists will be used
for discussion.
* cassandra-user@incubator.apache.org
<ma...@incubator.apache.org>
== Subversion Directory ==
*[WWW] https://svn.apache.org/repos/asf/incubator/cassandra
== Issue Tracking ==
* JIRA Cassandra
= Sponsors =
== Champion ==
* Brian McCallister
== Mentors ==
* Torsten Curdt
* Brian McCallister
* Matthieu Riou
* Ian Holsman
== Sponsoring Entity ==
* Incubator
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Shalin Shekhar Mangar <sh...@gmail.com>.
On Wed, Dec 24, 2008 at 3:31 AM, Ian Holsman <li...@holsman.net> 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..
>
>
+1 (non-binding)
--
Regards,
Shalin Shekhar Mangar.
RE: [VOTE] Accept Cassandra into the Incubator
Posted by "Noel J. Bergman" <no...@devtech.com>.
> on a point of order, do mentors/champions need to formally '+1' the vote?
Yes. There are no implied votes.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Ian Holsman <li...@holsman.net>.
Matthieu Riou wrote:
> On Wed, Dec 24, 2008 at 2:54 AM, Niclas Hedhman <ni...@hedhman.org> wrote:
>
>
>> On Wed, Dec 24, 2008 at 6:01 AM, Ian Holsman <li...@holsman.net> wrote:
>>
>>
>>> There has been some discussion around the Cassandra proposal,
>>> and we would now like to officially propose Cassandra to the Incubator
>>> for consideration..
>>>
>>> [ ] +1 Accept Cassandra as a new podling
>>> [ ] -1 Do not accept the new podling (provide reason, please)
>>>
>> -1 (binding).
>>
>> I will even give reasons because it is Christmas;
>> a. See Martijn's concern.
>> b. Running vote over Christmas when *many* people are busy with other
>> things.
>> c. I would like to see a proposal with more "meat" in it. Some
>> history, more elaboration on the various topics that the template
>> provides...
>>
>>
>
> Just a different perspective:
>
>
> b) +1 on this one, it could just be balanced by setting a longer than usual
> voting time frame.
>
fair enough, lets wait an additional 48 hours (total 5 days)..
on a point of order, do mentors/champions need to formally '+1' the vote?
Regards
Ian
> c) I agree although some feedback has been provided on the ML, it could be
> nice to bring back some of that in the proposal.
>
> Merry Christmas,
> Matthieu
>
>
>
>> Cheers
>> Niclas
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Fri, Dec 26, 2008 at 9:31 PM, Torsten Curdt <tc...@apache.org> wrote:
> ...I also have the feeling that the proposal could benefit from some more
> "meat". The timing around Christmas indeed was not very helpful
> either. But what really concerns me a bit is the question whether
> people really want to/can work together. It seems like the fork /
> non-fork debate already left some scars and I am not eager to invest
> time when people can't get along even to begin with. Maybe my "Avalon"
> alarm is set a little too sensitive but for now I only vote +0....
Considering that Torsten is listed as a mentor on the proposal I
change my vote to +0 as well.
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Emmanuel Lecharny <el...@gmail.com>.
Ian Holsman wrote:
>>
>> Ian, since you are the one driving this... would you mind working with
>> the project team on improving the proposal? ...and then consider a
>> re-submit?
>>
> at the moment we have 4 '+1's (including mine) and one -1, and another
> ~45 hours to go.
You have my +1.
Even if I understand the concerns about the fork, we will have months to
see if it's a viable project. This is what the incubator is for, isn't
it ? (among other things, of course ...)
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Ian Holsman <li...@holsman.net>.
>
> Ian, since you are the one driving this... would you mind working with
> the project team on improving the proposal? ...and then consider a
> re-submit?
>
at the moment we have 4 '+1's (including mine) and one -1, and another
~45 hours to go.
We have had the project in 'discussion' for about a month, so I'm
reluctant to withdraw the vote and re-submit in a couple of months as It
might be detrimental to the project. It was my fault we waited until the
23rd to submit, we should have submitted it on the Monday (mea culpa).
Remember.. this is a vote to enter incubation, not to exit. The project
(and community) behind it isn't perfect and in it's current state would
never graduate. But we're not even thinking of exiting yet, and the
possibility of failing should not stop the project from entering in the
first place. (IMHO).
Ian
> --
> Torsten
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Jason van Zyl <jv...@sonatype.com>.
On 26-Dec-08, at 3:31 PM, Torsten Curdt wrote:
>>>> [ ] +1 Accept Cassandra as a new podling
>>>> [ ] -1 Do not accept the new podling (provide reason, please)
>>>
>>> -1 (binding).
>>>
>>> I will even give reasons because it is Christmas;
>>> a. See Martijn's concern.
>>> b. Running vote over Christmas when *many* people are busy with
>>> other
>>> things.
>>> c. I would like to see a proposal with more "meat" in it. Some
>>> history, more elaboration on the various topics that the template
>>> provides...
>>>
>>
>> Just a different perspective:
>>
>> a) I agree with the concern but as Martijn expressed, I'm not sure it
>> should be a real concern for the vote. If the project dies, so be
>> it. But
>> clearly a few individuals seem to care so why not giving them a
>> chance?
>> b) +1 on this one, it could just be balanced by setting a longer
>> than usual
>> voting time frame.
>> c) I agree although some feedback has been provided on the ML, it
>> could be
>> nice to bring back some of that in the proposal.
>
> Some thoughts from this end:
>
> I also have the feeling that the proposal could benefit from some more
> "meat". The timing around Christmas indeed was not very helpful
> either. But what really concerns me a bit is the question whether
> people really want to/can work together. It seems like the fork /
The word fork does not appear in the proposal, but at the very top of
the proposal it says it started at Facebook. I just read the proposal
and a few emails today so I don't know anything about the project but
that immediately says to me there is some disparity. If it's a fork
that's fine, but that's something pretty important to leave out of the
proposal.
>
> non-fork debate already left some scars and I am not eager to invest
> time when people can't get along even to begin with. Maybe my "Avalon"
> alarm is set a little too sensitive but for now I only vote +0.
>
> Ian, since you are the one driving this... would you mind working with
> the project team on improving the proposal? ...and then consider a
> re-submit?
>
> cheers ...and Merry Christmas
> --
> Torsten
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
We all have problems. How we deal with them is a measure of our worth.
-- Unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Torsten Curdt <tc...@apache.org>.
>> > [ ] +1 Accept Cassandra as a new podling
>> > [ ] -1 Do not accept the new podling (provide reason, please)
>>
>> -1 (binding).
>>
>> I will even give reasons because it is Christmas;
>> a. See Martijn's concern.
>> b. Running vote over Christmas when *many* people are busy with other
>> things.
>> c. I would like to see a proposal with more "meat" in it. Some
>> history, more elaboration on the various topics that the template
>> provides...
>>
>
> Just a different perspective:
>
> a) I agree with the concern but as Martijn expressed, I'm not sure it
> should be a real concern for the vote. If the project dies, so be it. But
> clearly a few individuals seem to care so why not giving them a chance?
> b) +1 on this one, it could just be balanced by setting a longer than usual
> voting time frame.
> c) I agree although some feedback has been provided on the ML, it could be
> nice to bring back some of that in the proposal.
Some thoughts from this end:
I also have the feeling that the proposal could benefit from some more
"meat". The timing around Christmas indeed was not very helpful
either. But what really concerns me a bit is the question whether
people really want to/can work together. It seems like the fork /
non-fork debate already left some scars and I am not eager to invest
time when people can't get along even to begin with. Maybe my "Avalon"
alarm is set a little too sensitive but for now I only vote +0.
Ian, since you are the one driving this... would you mind working with
the project team on improving the proposal? ...and then consider a
re-submit?
cheers ...and Merry Christmas
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Matthieu Riou <ma...@gmail.com>.
On Wed, Dec 24, 2008 at 2:54 AM, Niclas Hedhman <ni...@hedhman.org> wrote:
> On Wed, Dec 24, 2008 at 6:01 AM, Ian Holsman <li...@holsman.net> wrote:
>
> > There has been some discussion around the Cassandra proposal,
> > and we would now like to officially propose Cassandra to the Incubator
> > for consideration..
>
> > [ ] +1 Accept Cassandra as a new podling
> > [ ] -1 Do not accept the new podling (provide reason, please)
>
> -1 (binding).
>
> I will even give reasons because it is Christmas;
> a. See Martijn's concern.
> b. Running vote over Christmas when *many* people are busy with other
> things.
> c. I would like to see a proposal with more "meat" in it. Some
> history, more elaboration on the various topics that the template
> provides...
>
Just a different perspective:
a) I agree with the concern but as Martijn expressed, I'm not sure it
should be a real concern for the vote. If the project dies, so be it. But
clearly a few individuals seem to care so why not giving them a chance?
b) +1 on this one, it could just be balanced by setting a longer than usual
voting time frame.
c) I agree although some feedback has been provided on the ML, it could be
nice to bring back some of that in the proposal.
Merry Christmas,
Matthieu
>
> Cheers
> Niclas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Wed, Dec 24, 2008 at 6:01 AM, Ian Holsman <li...@holsman.net> wrote:
> There has been some discussion around the Cassandra proposal,
> and we would now like to officially propose Cassandra to the Incubator
> for consideration..
> [ ] +1 Accept Cassandra as a new podling
> [ ] -1 Do not accept the new podling (provide reason, please)
-1 (binding).
I will even give reasons because it is Christmas;
a. See Martijn's concern.
b. Running vote over Christmas when *many* people are busy with other things.
c. I would like to see a proposal with more "meat" in it. Some
history, more elaboration on the various topics that the template
provides...
Cheers
Niclas
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Brian McCallister <br...@skife.org>.
On Sat, Dec 27, 2008 at 11:26 AM, Martijn Dashorst
<ma...@gmail.com> 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.
Actually, it is a huge first step. Right now there is no path for
non-FB employees to contribute.
Second step is to encourage non-FB (or other FB folks) folks to contribute.
Third step is to make them committers.
Fourth step is to have the whole crowd get beers together at the next apachecon.
Fifth step is GOTO 2.
:-)
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Ian Holsman <li...@holsman.net>.
Niclas Hedhman wrote:
> On Mon, Dec 29, 2008 at 9:48 AM, Ian Holsman <li...@holsman.net> wrote:
>
>
>> getting non-FB contributors to contribute.
>>
>
> Isn't this an oxymoron?
>
c/contribute/re-contribute/
>
> Cheers
> Niclas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Mon, Dec 29, 2008 at 9:48 AM, Ian Holsman <li...@holsman.net> wrote:
> getting non-FB contributors to contribute.
Isn't this an oxymoron?
Cheers
Niclas
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Ian Holsman <li...@holsman.net>.
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 <br...@skife.org> wrote:
>
>> On Sat, Dec 27, 2008 at 11:26 AM, Martijn Dashorst
>> <ma...@gmail.com> 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 <br...@skife.org> 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 <li...@holsman.net> 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.
>>>>>
>>>>> = Source and Intellectual Property Submission Plan =
>>>>>
>>>>> = External Dependencies =
>>>>> * All dependencies have Apache compatible licenses. Dependencies are log4j,
>>>>> Thrift, Apache Commons.
>>>>>
>>>>> = Cryptography =
>>>>> * None
>>>>> = Committers =
>>>>>
>>>>> * Avinash Lakshman
>>>>> * Prashant Malik
>>>>> * Kannan Muthukkaruppan
>>>>> * Jiansheng Huang
>>>>> * Dan Dumitriu
>>>>>
>>>>> = Current Status =
>>>>> == Meritocracy ==
>>>>>
>>>>> * Though initial development was done at Facebook, Cassandra was intended to
>>>>> be released as an open source project from its inception. Environment will
>>>>> lend itself to support meritocracy at all times.
>>>>>
>>>>> == Community ==
>>>>> * Folks who are actively considering deploying/prototyping Cassandra in
>>>>> their respective organizations.
>>>>>
>>>>> == Core Developers ==
>>>>> * Avinash Lakshman
>>>>> * Prashant Malik
>>>>> * Kannan Muthukkaruppan
>>>>>
>>>>> == License ==
>>>>> * The Cassandra codebase is Apache 2.0 licensed, and currently hosted at
>>>>> Google Code.
>>>>> = Known Risks/Avoiding the Warning Signs =
>>>>>
>>>>> == Orphaned Products ==
>>>>> * Cassandra is already deployed within Facebook and many other organizations
>>>>> are actively moving to deploy this in production. Original developers
>>>>> are and will actively stay involved and hence there is no realistic chance
>>>>> of it getting orphaned.
>>>>>
>>>>> == Homogenous Developers ==
>>>>> * The current list of committers includes developers from different
>>>>> companies. The committers are geographically distributed across the U.S.
>>>>>
>>>>> == Reliance on Salaried Developers ==
>>>>> * Yes. But don't expect this to be a risk of any nature.
>>>>>
>>>>> == Relationships with Other Apache Products ==
>>>>> * The Cassandra project is 'similar' to hbase/HDFS in concept, but Cassandra
>>>>> is more geared for Online web site usage than batch. It also doesn't have a
>>>>> single point of failure, which makes it interesting as well.
>>>>>
>>>>> * Cassandra makes use of the Thrift project.
>>>>>
>>>>> == An excessive fascination with the Apache brand ==
>>>>> * Cassandra has already attracted a stable base of users. There are at least
>>>>> 3 companies who are planning to use Cassandra in production as far as we
>>>>> know. The reasons for joining Apache are not to advertise the project, but
>>>>> rather to demonstrate the commitment to open source by divorcing the trunk
>>>>> from any one corporation and pursuing further integration with other Apache
>>>>> projects.
>>>>>
>>>>> = Required Resources =
>>>>> == Mailing lists ==
>>>>>
>>>>> Once the project is approved, the following mailing lists will be used for
>>>>> discussion.
>>>>> * cassandra-user@incubator.apache.org
>>>>> <ma...@incubator.apache.org>
>>>>>
>>>>> == Subversion Directory ==
>>>>>
>>>>> *[WWW] https://svn.apache.org/repos/asf/incubator/cassandra == Issue
>>>>> Tracking ==
>>>>>
>>>>> * JIRA Cassandra
>>>>>
>>>>> = Sponsors =
>>>>>
>>>>> == Champion ==
>>>>> * Brian McCallister == Mentors ==
>>>>> * Torsten Curdt * Brian McCallister
>>>>> * Matthieu Riou
>>>>> * Ian Holsman
>>>>>
>>>>> == Sponsoring Entity ==
>>>>> * Incubator
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>>>
>>>
>>> --
>>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>>> Apache Wicket 1.3.4 is released
>>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Martijn Dashorst <ma...@gmail.com>.
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 <br...@skife.org> wrote:
> On Sat, Dec 27, 2008 at 11:26 AM, Martijn Dashorst
> <ma...@gmail.com> 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 <br...@skife.org> 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 <li...@holsman.net> 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.
>>>>
>>>> = Source and Intellectual Property Submission Plan =
>>>>
>>>> = External Dependencies =
>>>> * All dependencies have Apache compatible licenses. Dependencies are log4j,
>>>> Thrift, Apache Commons.
>>>>
>>>> = Cryptography =
>>>> * None
>>>> = Committers =
>>>>
>>>> * Avinash Lakshman
>>>> * Prashant Malik
>>>> * Kannan Muthukkaruppan
>>>> * Jiansheng Huang
>>>> * Dan Dumitriu
>>>>
>>>> = Current Status =
>>>> == Meritocracy ==
>>>>
>>>> * Though initial development was done at Facebook, Cassandra was intended to
>>>> be released as an open source project from its inception. Environment will
>>>> lend itself to support meritocracy at all times.
>>>>
>>>> == Community ==
>>>> * Folks who are actively considering deploying/prototyping Cassandra in
>>>> their respective organizations.
>>>>
>>>> == Core Developers ==
>>>> * Avinash Lakshman
>>>> * Prashant Malik
>>>> * Kannan Muthukkaruppan
>>>>
>>>> == License ==
>>>> * The Cassandra codebase is Apache 2.0 licensed, and currently hosted at
>>>> Google Code.
>>>> = Known Risks/Avoiding the Warning Signs =
>>>>
>>>> == Orphaned Products ==
>>>> * Cassandra is already deployed within Facebook and many other organizations
>>>> are actively moving to deploy this in production. Original developers
>>>> are and will actively stay involved and hence there is no realistic chance
>>>> of it getting orphaned.
>>>>
>>>> == Homogenous Developers ==
>>>> * The current list of committers includes developers from different
>>>> companies. The committers are geographically distributed across the U.S.
>>>>
>>>> == Reliance on Salaried Developers ==
>>>> * Yes. But don't expect this to be a risk of any nature.
>>>>
>>>> == Relationships with Other Apache Products ==
>>>> * The Cassandra project is 'similar' to hbase/HDFS in concept, but Cassandra
>>>> is more geared for Online web site usage than batch. It also doesn't have a
>>>> single point of failure, which makes it interesting as well.
>>>>
>>>> * Cassandra makes use of the Thrift project.
>>>>
>>>> == An excessive fascination with the Apache brand ==
>>>> * Cassandra has already attracted a stable base of users. There are at least
>>>> 3 companies who are planning to use Cassandra in production as far as we
>>>> know. The reasons for joining Apache are not to advertise the project, but
>>>> rather to demonstrate the commitment to open source by divorcing the trunk
>>>> from any one corporation and pursuing further integration with other Apache
>>>> projects.
>>>>
>>>> = Required Resources =
>>>> == Mailing lists ==
>>>>
>>>> Once the project is approved, the following mailing lists will be used for
>>>> discussion.
>>>> * cassandra-user@incubator.apache.org
>>>> <ma...@incubator.apache.org>
>>>>
>>>> == Subversion Directory ==
>>>>
>>>> *[WWW] https://svn.apache.org/repos/asf/incubator/cassandra == Issue
>>>> Tracking ==
>>>>
>>>> * JIRA Cassandra
>>>>
>>>> = Sponsors =
>>>>
>>>> == Champion ==
>>>> * Brian McCallister == Mentors ==
>>>> * Torsten Curdt * Brian McCallister
>>>> * Matthieu Riou
>>>> * Ian Holsman
>>>>
>>>> == Sponsoring Entity ==
>>>> * Incubator
>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>
>>
>>
>> --
>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>> Apache Wicket 1.3.4 is released
>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Brian McCallister <br...@skife.org>.
On Sat, Dec 27, 2008 at 11:26 AM, Martijn Dashorst
<ma...@gmail.com> 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 <br...@skife.org> 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 <li...@holsman.net> 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.
>>>
>>> = Source and Intellectual Property Submission Plan =
>>>
>>> = External Dependencies =
>>> * All dependencies have Apache compatible licenses. Dependencies are log4j,
>>> Thrift, Apache Commons.
>>>
>>> = Cryptography =
>>> * None
>>> = Committers =
>>>
>>> * Avinash Lakshman
>>> * Prashant Malik
>>> * Kannan Muthukkaruppan
>>> * Jiansheng Huang
>>> * Dan Dumitriu
>>>
>>> = Current Status =
>>> == Meritocracy ==
>>>
>>> * Though initial development was done at Facebook, Cassandra was intended to
>>> be released as an open source project from its inception. Environment will
>>> lend itself to support meritocracy at all times.
>>>
>>> == Community ==
>>> * Folks who are actively considering deploying/prototyping Cassandra in
>>> their respective organizations.
>>>
>>> == Core Developers ==
>>> * Avinash Lakshman
>>> * Prashant Malik
>>> * Kannan Muthukkaruppan
>>>
>>> == License ==
>>> * The Cassandra codebase is Apache 2.0 licensed, and currently hosted at
>>> Google Code.
>>> = Known Risks/Avoiding the Warning Signs =
>>>
>>> == Orphaned Products ==
>>> * Cassandra is already deployed within Facebook and many other organizations
>>> are actively moving to deploy this in production. Original developers
>>> are and will actively stay involved and hence there is no realistic chance
>>> of it getting orphaned.
>>>
>>> == Homogenous Developers ==
>>> * The current list of committers includes developers from different
>>> companies. The committers are geographically distributed across the U.S.
>>>
>>> == Reliance on Salaried Developers ==
>>> * Yes. But don't expect this to be a risk of any nature.
>>>
>>> == Relationships with Other Apache Products ==
>>> * The Cassandra project is 'similar' to hbase/HDFS in concept, but Cassandra
>>> is more geared for Online web site usage than batch. It also doesn't have a
>>> single point of failure, which makes it interesting as well.
>>>
>>> * Cassandra makes use of the Thrift project.
>>>
>>> == An excessive fascination with the Apache brand ==
>>> * Cassandra has already attracted a stable base of users. There are at least
>>> 3 companies who are planning to use Cassandra in production as far as we
>>> know. The reasons for joining Apache are not to advertise the project, but
>>> rather to demonstrate the commitment to open source by divorcing the trunk
>>> from any one corporation and pursuing further integration with other Apache
>>> projects.
>>>
>>> = Required Resources =
>>> == Mailing lists ==
>>>
>>> Once the project is approved, the following mailing lists will be used for
>>> discussion.
>>> * cassandra-user@incubator.apache.org
>>> <ma...@incubator.apache.org>
>>>
>>> == Subversion Directory ==
>>>
>>> *[WWW] https://svn.apache.org/repos/asf/incubator/cassandra == Issue
>>> Tracking ==
>>>
>>> * JIRA Cassandra
>>>
>>> = Sponsors =
>>>
>>> == Champion ==
>>> * Brian McCallister == Mentors ==
>>> * Torsten Curdt * Brian McCallister
>>> * Matthieu Riou
>>> * Ian Holsman
>>>
>>> == Sponsoring Entity ==
>>> * Incubator
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.4 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Martijn Dashorst <ma...@gmail.com>.
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?
Martijn
On Sat, Dec 27, 2008 at 6:13 PM, Brian McCallister <br...@skife.org> 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 <li...@holsman.net> 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.
>>
>> = Source and Intellectual Property Submission Plan =
>>
>> = External Dependencies =
>> * All dependencies have Apache compatible licenses. Dependencies are log4j,
>> Thrift, Apache Commons.
>>
>> = Cryptography =
>> * None
>> = Committers =
>>
>> * Avinash Lakshman
>> * Prashant Malik
>> * Kannan Muthukkaruppan
>> * Jiansheng Huang
>> * Dan Dumitriu
>>
>> = Current Status =
>> == Meritocracy ==
>>
>> * Though initial development was done at Facebook, Cassandra was intended to
>> be released as an open source project from its inception. Environment will
>> lend itself to support meritocracy at all times.
>>
>> == Community ==
>> * Folks who are actively considering deploying/prototyping Cassandra in
>> their respective organizations.
>>
>> == Core Developers ==
>> * Avinash Lakshman
>> * Prashant Malik
>> * Kannan Muthukkaruppan
>>
>> == License ==
>> * The Cassandra codebase is Apache 2.0 licensed, and currently hosted at
>> Google Code.
>> = Known Risks/Avoiding the Warning Signs =
>>
>> == Orphaned Products ==
>> * Cassandra is already deployed within Facebook and many other organizations
>> are actively moving to deploy this in production. Original developers
>> are and will actively stay involved and hence there is no realistic chance
>> of it getting orphaned.
>>
>> == Homogenous Developers ==
>> * The current list of committers includes developers from different
>> companies. The committers are geographically distributed across the U.S.
>>
>> == Reliance on Salaried Developers ==
>> * Yes. But don't expect this to be a risk of any nature.
>>
>> == Relationships with Other Apache Products ==
>> * The Cassandra project is 'similar' to hbase/HDFS in concept, but Cassandra
>> is more geared for Online web site usage than batch. It also doesn't have a
>> single point of failure, which makes it interesting as well.
>>
>> * Cassandra makes use of the Thrift project.
>>
>> == An excessive fascination with the Apache brand ==
>> * Cassandra has already attracted a stable base of users. There are at least
>> 3 companies who are planning to use Cassandra in production as far as we
>> know. The reasons for joining Apache are not to advertise the project, but
>> rather to demonstrate the commitment to open source by divorcing the trunk
>> from any one corporation and pursuing further integration with other Apache
>> projects.
>>
>> = Required Resources =
>> == Mailing lists ==
>>
>> Once the project is approved, the following mailing lists will be used for
>> discussion.
>> * cassandra-user@incubator.apache.org
>> <ma...@incubator.apache.org>
>>
>> == Subversion Directory ==
>>
>> *[WWW] https://svn.apache.org/repos/asf/incubator/cassandra == Issue
>> Tracking ==
>>
>> * JIRA Cassandra
>>
>> = Sponsors =
>>
>> == Champion ==
>> * Brian McCallister == Mentors ==
>> * Torsten Curdt * Brian McCallister
>> * Matthieu Riou
>> * Ian Holsman
>>
>> == Sponsoring Entity ==
>> * Incubator
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Brian McCallister <br...@skife.org>.
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 <li...@holsman.net> 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.
>
> = Source and Intellectual Property Submission Plan =
>
> = External Dependencies =
> * All dependencies have Apache compatible licenses. Dependencies are log4j,
> Thrift, Apache Commons.
>
> = Cryptography =
> * None
> = Committers =
>
> * Avinash Lakshman
> * Prashant Malik
> * Kannan Muthukkaruppan
> * Jiansheng Huang
> * Dan Dumitriu
>
> = Current Status =
> == Meritocracy ==
>
> * Though initial development was done at Facebook, Cassandra was intended to
> be released as an open source project from its inception. Environment will
> lend itself to support meritocracy at all times.
>
> == Community ==
> * Folks who are actively considering deploying/prototyping Cassandra in
> their respective organizations.
>
> == Core Developers ==
> * Avinash Lakshman
> * Prashant Malik
> * Kannan Muthukkaruppan
>
> == License ==
> * The Cassandra codebase is Apache 2.0 licensed, and currently hosted at
> Google Code.
> = Known Risks/Avoiding the Warning Signs =
>
> == Orphaned Products ==
> * Cassandra is already deployed within Facebook and many other organizations
> are actively moving to deploy this in production. Original developers
> are and will actively stay involved and hence there is no realistic chance
> of it getting orphaned.
>
> == Homogenous Developers ==
> * The current list of committers includes developers from different
> companies. The committers are geographically distributed across the U.S.
>
> == Reliance on Salaried Developers ==
> * Yes. But don't expect this to be a risk of any nature.
>
> == Relationships with Other Apache Products ==
> * The Cassandra project is 'similar' to hbase/HDFS in concept, but Cassandra
> is more geared for Online web site usage than batch. It also doesn't have a
> single point of failure, which makes it interesting as well.
>
> * Cassandra makes use of the Thrift project.
>
> == An excessive fascination with the Apache brand ==
> * Cassandra has already attracted a stable base of users. There are at least
> 3 companies who are planning to use Cassandra in production as far as we
> know. The reasons for joining Apache are not to advertise the project, but
> rather to demonstrate the commitment to open source by divorcing the trunk
> from any one corporation and pursuing further integration with other Apache
> projects.
>
> = Required Resources =
> == Mailing lists ==
>
> Once the project is approved, the following mailing lists will be used for
> discussion.
> * cassandra-user@incubator.apache.org
> <ma...@incubator.apache.org>
>
> == Subversion Directory ==
>
> *[WWW] https://svn.apache.org/repos/asf/incubator/cassandra == Issue
> Tracking ==
>
> * JIRA Cassandra
>
> = Sponsors =
>
> == Champion ==
> * Brian McCallister == Mentors ==
> * Torsten Curdt * Brian McCallister
> * Matthieu Riou
> * Ian Holsman
>
> == Sponsoring Entity ==
> * Incubator
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, Dec 23, 2008 at 11:01 PM, Ian Holsman <li...@holsman.net> wrote:
> ...There has been some discussion around the Cassandra proposal,
> and we would now like to officially propose Cassandra to the Incubator
> for consideration...
+1
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
+1 from me.
- -- dims
Otis Gospodnetic wrote:
> +1
>
>
> Otis--
> Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
>
>
>
> ----- Original Message ----
>> From: Ian Holsman <li...@holsman.net>
>> To: general@incubator.apache.org
>> Sent: Tuesday, December 23, 2008 5:01:37 PM
>> Subject: [VOTE] Accept Cassandra into the Incubator
>>
>>
>> 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.
>>
>> = Source and Intellectual Property Submission Plan =
>>
>> = External Dependencies =
>> * All dependencies have Apache compatible licenses. Dependencies are log4j,
>> Thrift, Apache Commons.
>>
>> = Cryptography =
>> * None
>> = Committers =
>>
>> * Avinash Lakshman
>> * Prashant Malik
>> * Kannan Muthukkaruppan
>> * Jiansheng Huang
>> * Dan Dumitriu
>>
>> = Current Status =
>> == Meritocracy ==
>>
>> * Though initial development was done at Facebook, Cassandra was intended to be
>> released as an open source project from its inception. Environment will lend
>> itself to support meritocracy at all times.
>>
>> == Community ==
>> * Folks who are actively considering deploying/prototyping Cassandra in their
>> respective organizations.
>>
>> == Core Developers ==
>> * Avinash Lakshman
>> * Prashant Malik
>> * Kannan Muthukkaruppan
>>
>> == License ==
>> * The Cassandra codebase is Apache 2.0 licensed, and currently hosted at Google
>> Code.
>> = Known Risks/Avoiding the Warning Signs =
>>
>> == Orphaned Products ==
>> * Cassandra is already deployed within Facebook and many other organizations are
>> actively moving to deploy this in production. Original developers
>> are and will actively stay involved and hence there is no realistic chance of it
>> getting orphaned.
>>
>> == Homogenous Developers ==
>> * The current list of committers includes developers from different companies.
>> The committers are geographically distributed across the U.S.
>>
>> == Reliance on Salaried Developers ==
>> * Yes. But don't expect this to be a risk of any nature.
>>
>> == Relationships with Other Apache Products ==
>> * The Cassandra project is 'similar' to hbase/HDFS in concept, but Cassandra is
>> more geared for Online web site usage than batch. It also doesn't have a single
>> point of failure, which makes it interesting as well.
>>
>> * Cassandra makes use of the Thrift project.
>>
>> == An excessive fascination with the Apache brand ==
>> * Cassandra has already attracted a stable base of users. There are at least 3
>> companies who are planning to use Cassandra in production as far as we know. The
>> reasons for joining Apache are not to advertise the project, but rather to
>> demonstrate the commitment to open source by divorcing the trunk from any one
>> corporation and pursuing further integration with other Apache projects.
>>
>> = Required Resources =
>> == Mailing lists ==
>>
>> Once the project is approved, the following mailing lists will be used for
>> discussion.
>> * cassandra-user@incubator.apache.org
>>
>>
>> == Subversion Directory ==
>>
>> *[WWW] https://svn.apache.org/repos/asf/incubator/cassandra == Issue Tracking
>> ==
>>
>> * JIRA Cassandra
>>
>> = Sponsors =
>>
>> == Champion ==
>> * Brian McCallister == Mentors ==
>> * Torsten Curdt * Brian McCallister
>> * Matthieu Riou
>> * Ian Holsman
>>
>> == Sponsoring Entity ==
>> * Incubator
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAklRv/cACgkQgNg6eWEDv1mv9ACeNfGtLlM8nokn1eX0f2oRRZgG
fCgAoJCLQ8F1BoeRDEL9+clDXoM4jLwe
=NHut
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept Cassandra into the Incubator
Posted by Otis Gospodnetic <ot...@yahoo.com>.
+1
Otis--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
----- Original Message ----
> From: Ian Holsman <li...@holsman.net>
> To: general@incubator.apache.org
> Sent: Tuesday, December 23, 2008 5:01:37 PM
> Subject: [VOTE] Accept Cassandra into the Incubator
>
>
> 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.
>
> = Source and Intellectual Property Submission Plan =
>
> = External Dependencies =
> * All dependencies have Apache compatible licenses. Dependencies are log4j,
> Thrift, Apache Commons.
>
> = Cryptography =
> * None
> = Committers =
>
> * Avinash Lakshman
> * Prashant Malik
> * Kannan Muthukkaruppan
> * Jiansheng Huang
> * Dan Dumitriu
>
> = Current Status =
> == Meritocracy ==
>
> * Though initial development was done at Facebook, Cassandra was intended to be
> released as an open source project from its inception. Environment will lend
> itself to support meritocracy at all times.
>
> == Community ==
> * Folks who are actively considering deploying/prototyping Cassandra in their
> respective organizations.
>
> == Core Developers ==
> * Avinash Lakshman
> * Prashant Malik
> * Kannan Muthukkaruppan
>
> == License ==
> * The Cassandra codebase is Apache 2.0 licensed, and currently hosted at Google
> Code.
> = Known Risks/Avoiding the Warning Signs =
>
> == Orphaned Products ==
> * Cassandra is already deployed within Facebook and many other organizations are
> actively moving to deploy this in production. Original developers
> are and will actively stay involved and hence there is no realistic chance of it
> getting orphaned.
>
> == Homogenous Developers ==
> * The current list of committers includes developers from different companies.
> The committers are geographically distributed across the U.S.
>
> == Reliance on Salaried Developers ==
> * Yes. But don't expect this to be a risk of any nature.
>
> == Relationships with Other Apache Products ==
> * The Cassandra project is 'similar' to hbase/HDFS in concept, but Cassandra is
> more geared for Online web site usage than batch. It also doesn't have a single
> point of failure, which makes it interesting as well.
>
> * Cassandra makes use of the Thrift project.
>
> == An excessive fascination with the Apache brand ==
> * Cassandra has already attracted a stable base of users. There are at least 3
> companies who are planning to use Cassandra in production as far as we know. The
> reasons for joining Apache are not to advertise the project, but rather to
> demonstrate the commitment to open source by divorcing the trunk from any one
> corporation and pursuing further integration with other Apache projects.
>
> = Required Resources =
> == Mailing lists ==
>
> Once the project is approved, the following mailing lists will be used for
> discussion.
> * cassandra-user@incubator.apache.org
>
>
> == Subversion Directory ==
>
> *[WWW] https://svn.apache.org/repos/asf/incubator/cassandra == Issue Tracking
> ==
>
> * JIRA Cassandra
>
> = Sponsors =
>
> == Champion ==
> * Brian McCallister == Mentors ==
> * Torsten Curdt * Brian McCallister
> * Matthieu Riou
> * Ian Holsman
>
> == Sponsoring Entity ==
> * Incubator
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org