Another thing to keep in mind--even core pieces like the Linux kernel are dominated by corporations. Less than 20% of contributions last year were made by non-corporate sponsored contributors. Obviously, this is a bit different, but many parts of the open source world depend on upstream contribution. If Datastax decides to stop this (I hope they don't), that would probably yield some pretty bad press as well.
I'd like to think that the people at DSE are like you and me, and the individual developers _want_ to contribute these changes upstream, but that may just be naive. :) On Fri, May 23, 2014 at 10:42 AM, Robert Coli <rc...@eventbrite.com> wrote: > On Fri, May 16, 2014 at 10:56 AM, Kevin Burton <bur...@spinn3r.com> wrote: > >> Perhaps because the developers are working on DSE :-P >> > > FWIW, and I am not necessarily known for being the biggest defender of > Datastax and the relationship of their commercial interests to the > architectural direction of Cassandra... > > ... Datastax contribute a huge amount of work back to Apache Cassandra by > the simple method operating on "Cassandra issues" raised by DSE customers > inside of the Apache JIRA. If they are not out there selling DSE to these > (often quite large) customers, there is not necessarily a commercial driver > for fixing these "Cassandra Issues." > > The DSE features are mostly isolated enough from the main codebase, and > from my understanding the teams are separated enough internally, that I'm > pretty confident Datastax is a significant net positive for contribution to > and promotion of Apache Cassandra. > > =Rob >
