> A key portion of your software’s stack, a client driver to use it, exists outside of Apache in separate communities. This is an inherent risk to the project.
That's not at all obvious to me. The driver you're concerned about is not under ASF, but it is Apache licensed, if DataStax took it in a direction unfavorable to the community, the community would be able to just fork it. Your concern here seems mostly to be surrounding one project vs two. At worst this is a layout concern. > I would ask you all this - has there been a PR or patch in the past year or two that wasn’t singularly reviewed by DataStax committers and PMC? There are numerous non-PMC non-DataStax committers. Regardless, this is the wrong question to ask. The question is not how well reviewed the code is and whether there are a tight set of gate keepers, but rather whether there are contributions being rejected which would advance the product in a material way, but are being rejected by reviewers due to, for example, a conflict of interest. > Does anyone in the community see this “controlling” behavior going on? ... Thanks for any help you can provide in rooting this out. > ... > Unfortunately it seems like there is a bit of control going on...There is definitely some control going on You asked the community for feedback on this, and it was pretty clear to me that nobody here felt like that was the case. If you're aware of *actual* examples of impropriety in this or another sense, I think the community would like to hear about it. Something more substantial than vague assertions and hand waving. However, claiming repeatedly that you see control going on, but without something to substantiate the accusation feels like an expedition fishing for drama. On Mon, Jun 6, 2016 at 5:36 AM Jeremiah D Jordan <jeremiah.jor...@gmail.com> wrote: > The Apache Cassandra project has always left development of its drivers up > to the community. The DataStax Java Driver is not part of the Apache > Cassandra project, it is an open source project created by DataStax. You > can find a large list of drivers for Cassandra here: > https://wiki.apache.org/cassandra/ClientOptions some of them developed by > DataStax, some developed by Netflix, and many others. > > -Jeremiah > > > On Jun 3, 2016, at 9:29 PM, Chris Mattmann <mattm...@apache.org> wrote: > > > > Hi All, > > > > I’m investigating something a few ASF members contacted > > me about and pointed out, so I’m hoping you can help > > guide me here as a community. I have heard that a company, > > DataStax, whose marketing material mentions it as the only > > Cassandra vendor, “controls” the Java Driver for Apache > > Cassandra. > > > > Of course, no company “controls” our projects or its code, > > so I told the folks that mentioned it to me that I’d investigate > > with my board hat on. > > > > I’d like to hear the community’s thoughts here on this. Does > > anyone in the community see this “controlling” behavior going > > on? Please speak up, as I’d like to get to the bottom of it, > > and I’ll be around on the lists, doing some homework and reading > > up on the archives to see what’s up. > > > > Thanks for any help you can provide in rooting this out. > > > > Cheers, > > Chris > > > > > > > > > >
