Note also the work on https://issues.apache.org/jira/browse/CASSANDRA-9459 , reaching out to other “competitors” before major versions to ensure compatibility and awareness.
I think there’s a ton of evidence supporting the assertion that datastax-employed committers and PMC members acted in good faith when it comes to code going into the database. I would wager that most of the ‘wont fix’ tickets in JIRA were opened by Datastax employees, so folks claiming bias because committers refused to merge a patch are assigning malice when there is none (perhaps too high a bar for contributions, but as a user, I appreciate that high bar). On 11/4/16, 5:31 PM, "Aleksey Yeschenko" <alek...@apache.org> wrote: >You got this one completely wrong, my friend. > >It’s the PMC who reached out to stratio and helped them get the changes they >required into Cassandra, >so that they could abandon the fork. > >I know because I was that PMC member. > >cc Andres from Stratio > >-- >AY > >On 5 November 2016 at 00:14:42, Chris Mattmann (mattm...@apache.org) wrote: > >Some decisions made in past by project PMCs lead to situation that project was >forked and maintained outside ASF (ie. stratio cassandra which eventually >ended up as lucene indexes plugin over a year ago)
smime.p7s
Description: S/MIME cryptographic signature