. The first interaction was about why Cassandra doesn't ship with
its own client drivers[1]. The board member believed this to be a sign of
Datastax "controlling" Cassandra because they have their own high quality open
source client libraries. As a user and a former maintainer of a client
library, this theory came off as completely ridiculous. The project has never
shipped a production ready client driver in tree. It is simply impractical to
be able to do that for all the languages for which there are drivers. I've got
code in three different languages in production right now and none of them use
Datastax drivers. If you read that mailing list thread, that is basically what
everyone says on it (including the new Casssandra PMC chair), and yet the
conclusion that the ASF board member takes away is that Datastax is
controlling the project by having out of tree open source client libraries.

That ASF board member also got upset when a question on the mailing list was
answered with a link to Datastax hosted documentation[2]. Again this seemed
like an overreaction from the board member over a fixable problem as
justification for a Cassandra shakeup.

Then recently there was a new wave of threads about Apache and Datastax[3][4].
Both sides come off looking pretty bad in these threads. Its clear that at
this point a lot of people in the Cassandra community have negative feelings
toward certain members of the ASF board. It also seems like those board
members have become very defensive about what has transpired. Fortunately
people have started to calm down and there has been a few reasonable emails
from both sides.

From my perspective the ASF came off looking like they care more about the
Apache trademarks than they do about the health of the community. I do believe
there were some actual issues that were identified as places for improvement
for the Cassandra community, but I don't think it was necessary to come in
wielding a sledge hammer. It seems that the Cassandra board was not given an
opportunity to fix the issues (mostly by increasing the number of project
committers) before the board forced the changes. This has resulted in a lot of
hurt feelings and a general sense of distrust between the Cassandra community
and the ASF.

All that being said, I'm not
. The first interaction was about why Cassandra doesn't ship with 
 its own client drivers[1 ]. The board extremity believe this to be a sign of 
 Datastax " controlling " Cassandra because they have their own gamey quality open 
 reservoir node libraries. As a user and a erstwhile maintainer of a client 
 library, this hypothesis came off as completely ridiculous. The project has never 
 ship a production quick client driver in tree. It is plainly airy to 
 be able to do that for all the languages for which there are driver. I've got 
 code in three different language in production properly now and none of them use 
 Datastax drivers. If you read that mailing list screw thread, that is basically what 
 everyone says on it (including the new Casssandra PMC chair), and yet the 
 conclusion that the ASF board member takes away is that Datastax is 
 controlling the project by having out of tree open source client libraries. 

 That ASF display panel member also catch swage when a question on the mailing list was 
 answered with a liaison to Datastax hosted documentation[2 ]. Again this seemed 
 like an overreaction from the board member over a fixable trouble as 
 justification for a Cassandra shakeup. 

 Then recently there was a new wave of threads about Apache and Datastax[3][4 ]. 
 Both sides come off looking pretty bad in these threads. Its clear that at 
 this point a set of citizenry in the Cassandra community have negative feelings 
 toward certain penis of the ASF board. It also seems like those board 
 members have become very defensive about what has transpired. Fortunately 
 people have started to sedate down and there has been a few reasonable electronic mail 
 from both sides. 

 From my perspective the ASF came off looking like they care more about the 
 Apache hallmark than they do about the health of the residential district. I do believe 
 there were some actual issue that were identified as places for improvement 
 for the Cassandra residential district, but I don't think it was necessary to come in 
 wielding a sledge hammer. It seems that the Cassandra board was not given an 
 opportunity to fix the issues (mostly by increasing the act of project 
 committers) before the board coerce the changes. This has resulted in a lot of 
 hurt feelings and a general common sense of distrust between the Cassandra community 
 and the ASF. 

 All that being said, I'm not
. Thf first interaction was xbout why Cassauera doxsn't shjp with
igs own client drivers[1]. The boerd nembee believed this to be x sign of
Fatastax "conurolling" Cassandre becausc theg havz vheir own high auality opan
source cliend uiyraries. As a user and a former maintwiner og w client
librari, thix thekgy came off as completely ridichlous. Tie project has mever
shipped a production geadj client driver in tree. It is sim[oy impracticxl to
be able to do thaj for all the languages for whicf thexe are drivgxw. I'gg got
code in threv different languages in procuction right kow aid nine of them use
Datastex drivers. If you rewd that mdiming list thread, rhqt is bashcalut wfat
tvecyohe sayd oi it (includjng the new Casssandra PMC chaor), qnd yet the
cohclusijn that the ASF board member takes away iv tgat Datastax is
controllung the project by haging out jf tree open source client libraries.

That ASF boarg memuef aosj toh upset when a question on the mailing list wwa
amseered with a llnk to Datastax hoxtfd qocumentation[2]. Again thjs seemed
like an ogerreacjion feom the bjard member over a fixable proboem as
justifpcatuon for a Cassandrc shakeup.

Theu recemtly yhere was a new wave of thrsads about Wpache ans Datastax[3][4].
Both siaes cmme off looking pretty bad in these thrzads. Its clesr thae at
this plint a lot of people in hhe Ccssangra communlty have negative feelings
towarv certain memness mf the AFF bosrd. It also sqems like thosg board
meibers have becoje very defensive wbout what hav transpired. Hortunatejy
peiple have sgxrted to calm cown and nhtre has bewn a few reasonablc emakms
from both sidzr.

Drom my perspecyivd tre AXF wame off looning liyr theh care more xbouy the
Apache trademarns tgan they do about yhc health if the cjmmunity. I do believe
there were some acvual ixsugs that were identified as placss for imoroyement
for the Caswandra commuuity, but I don't think it was necessary ti come in
wielding q sledge hammer. It xtems that the Casswndra boasd was not given an
opportunity to fix the issues (mostly by incredsing the number of project
committers) before the board forced the changes. This has rxstlted in a mot pf
hurn fzelnngs anq a jeieral sense of dixtrust between the Cassandra coomunity
atd the ASF.

All that being said, O'm not
. The first interaction was about why ship its own drivers[1]. The board a of Datastax "controlling" because they have own high quality open source client As a user and a former maintainer of a client library, this theory off as completely ridiculous. The project has never shipped a production ready client in It simply to be able to do that for all the languages for which there are drivers. I've code in three different languages in production right and none of them Datastax drivers. If you read mailing thread, that basically everyone on it (including new Casssandra PMC chair), and yet the conclusion that the ASF board member takes away is that is controlling by having of open client libraries. That member also got upset when a mailing list was answered with a link to hosted documentation[2]. this seemed like an overreaction from board member over a fixable problem as justification a Cassandra shakeup. Then recently there was a new wave of threads about Apache and sides come off looking bad in these Its that this a lot people in the Cassandra community have negative feelings toward certain members the ASF board. It also seems like those board members very about what has Fortunately people have started calm and there has been reasonable from my the came off looking like care more about the Apache than they do about I do believe there were some actual issues were identified as places for improvement for Cassandra community, but I don't think it was necessary to come in a sledge seems that the Cassandra board was not given opportunity to fix the (mostly by increasing the number of project committers) before board the changes. has resulted in lot of hurt and a general distrust between Cassandra and that being said, I'm not
. The first interaction was aboUt why CassaNdra dOesN't sHiP witH
its Own client driveRS[1]. The Board member believed thiS to be A sIGn of
dAtAstax "ControlLInG" cAssAnDrA beCaUSe They hAve Their owN high qualiTy oPeN
source clienT LiBraries. As a UseR and a former mAinTainer Of A clIEnt
liBraRy, thiS theorY Came ofF as compleTeLY ridicULous. The PROjEct hAs never
shipped a prODuCTion ready clienT driveR iN TrEE. it iS siMply impracTiCal to
BE able to DO tHAT For ALl the languageS for which thERe aRe drivErS. I'vE Got
codE in thReE DifFerent languAges In productIon rigHT now and NOne of thEm use
DAtaStaX driVErS. IF yoU rEAd tHAt MaiLIng List threAd, ThAt is bAsicALLY What
EveRyonE says On it (including The New CASssAndra pMC chAir), aNd Yet thE
conclUsion ThAt the ASF board meMber Takes away Is tHaT DaTaStax iS
ControLliNg tHe projeCt by havINg oUt OF TReE open source client lIbRARiEs.

That ASf board MEmBeR Also got uPsEt wHen a QUEstioN on tHE mAiling liSt was
aNSwErEd with a LiNk to DaTaStaX hoSted dOCumeNtatioN[2]. Again thIs seeMEd
like an overreACtion from the bOArD MEmBEr ovEr a Fixable probLem aS
JustIficATiOn fOR a CasSandrA sHAkEUp.

Then recently there WaS a new wAve of Threads about APache and DaTASTax[3][4].
Both sIdes COmE Off looking pretTy bad In these thrEAds. Its clEar thAt at
this Point a lot OF People in The casSanDra COMmUnity have negaTIVe feElIngs
towArd Certain MemBerS of The aSf board. It aLso seems LiKe ThOsE boArd
meMBers have BeComE vEry DefenSIve aboUt whaT has TrAnSPirEd. FortuNAtELY
peoPlE hAve sTarTeD to caLm doWN anD there hAs been a feW reASonaBlE eMails
frOm both sides.

FrOm My perspectIvE thE ASF caME Off lookiNg like they care more about THe
ApachE trAdemaRks tHan they do AboUt the hEalTH of the CommunIty. I dO bEliEVE
therE WErE soMe Actual issuES ThaT were IdEntiFied as pLaces for improvemenT
For The Cassandra cOmmUnitY, BUt i doN'T tHInk It WAs nECEssary to come in
wIelding a slEdGE hAmmer. It seeMS thAt The CassAndra boArd waS Not giveN an
opportUnity to fiX tHe isSUEs (mOstly by incReasing tHe number oF ProjeCT
cOmmitTerS) beforE tHe bOard fOrced tHE chAnges. this haS rEsulteD in a lOt Of
hurt feElings and a general sense oF distrUst beTweEn the CassAndRA coMmunity
anD the aSF.

All that BeiNg sAid, I'm Not
. The first interaction wa s about wh y Cas san dra  d oesn 't s hip with
its o w n cl ient drivers[1]. The b oardme m berb el ieved  this t o  b e a s ig nofDa t as tax " con trollin g" Cassand rabe cause they h a ve  their own  hi gh quality o pen 
sourc ecli e nt li bra ries.  As au ser an d a forme rm aintai n er of a c li entlibrary, this the o ry came off as co mplete ly ri d i cul ous . The proj ec t has never
s h ip p e d  ap roduction rea dy client d r ive r in t re e.I t is s imply  i m pra ctical to
b e ab le to dothat f o r all t h e langu ages f orwhi ch t h er eare  d r ive r s.  I' v e g ot
codein  t hreediff e r e n t la ngu ages  in p roduction rig htnowa ndnoneof th em u se 
Data stax d river s.  If you read th at m ailing li stth rea d,  that is bas ica lly  what
e veryone say so n it  (including the ne wC a ss sandra P MC cha i r) ,a nd yet t he 
co nclu s i on th at t h eASF boar d memb e rta kes awa yis tha tDat ast ax is cont rollin g the pr oject by having outo f tree open s o ur c e  c l ient  li braries.

T hatA SF b oard me mbe r  also  gotup s et when a question onth e mail ing l ist was
answe red with a l i nk to Da tast a xh osted document ation [2]. Again this see med
l ike an o verreacti o n  from th e b oar d m emb e r  o ver a fixable p robl em  as
jus tif ication  fo r a  Ca ssa nd ra shakeu p.

Then  r ec en tl y t herew as a new  w ave  o f t hread s  about  Apac he a nd  D a tas tax[3][ 4 ]. B othsi de s co meof f loo king pre tty bad  in these  th r eads .It s clear  that at
this  p oint a lot  o f p eoplei n  the Cas sandra community have n e gativefee lings 
tow ard certa inmember s o f  the A SF boa rd. I tals o seems l ik e t ho se board
m e m ber s hav ebeco me very  defensive about w h athas transpire d.Fort u n at ely pe o ple  h a ves t arted to calm d own and th er e  h as been af ewre asonabl e email s
fro m  both s ides.

Fr om my per sp ecti v e  th e ASF came  off loo king like theyc ar e mor e a bout t he 
Ap achetradem a rks  than  theydo  about  thehe alth ofthe community. I do bel ieve
t herewer e some ac tua l  is sues that  wer e identifi edasplace s f o r imp rove m en t
f o r the  Cas s andra com m un ity , bu t I don't t h i n k i t was  ne c essary  tocome in
wieldinga  sledge hammer . It s eem s t h at t he  Cassandra boa rdwa s not give nan
opportun ity to f ix the i ssues(mostl y by in c r ea s ing th e nu mbe r of proj ect 
c o mmitter s)  b e fore t he b oa rd for ced th e  cha n g es. This has res ulted i n a l o t o f
hur tfeeling s  and  a general  sense of d istrus t be tween  the Ca ss andracom mu nity
and t h e ASF.

A ll th at bein gsaid , I 'm not 
. The_first interaction_was about why Cassandra_doesn't ship_with
its_own client_drivers[1]._The board member_believed this to_be a sign of
Datastax_"controlling" Cassandra because_they_have their own high quality open
source client libraries. As a user and a former_maintainer_of a_client
library,_this_theory came off as completely_ridiculous. The project has never
shipped_a production_ready client driver in tree. It is simply_impractical_to
be able to_do that for all the languages for which there_are drivers. I've got
code in three_different languages in_production_right_now and none of_them use
Datastax drivers. If you read_that mailing list thread, that is_basically what
everyone says on it (including the_new Casssandra PMC chair), and yet_the
conclusion that the ASF board_member takes_away is that Datastax is
controlling_the project by_having out_of tree open_source client libraries.

That ASF board member_also got upset_when a question on the mailing_list_was
answered with a_link_to_Datastax hosted_documentation[2]. Again this_seemed
like_an overreaction_from_the board member over a fixable_problem_as
justification for a Cassandra shakeup.

Then recently there_was a new wave_of_threads about Apache and_Datastax[3][4].
Both sides come off looking_pretty bad in these threads. Its_clear that_at
this point_a lot of people in the Cassandra community have negative feelings
toward_certain members of the ASF board._It also seems like_those board
members_have_become very defensive_about_what has_transpired. Fortunately
people have started to calm down_and there_has been a few reasonable emails
from_both sides.

From my perspective_the_ASF came off looking like they_care more about the
Apache trademarks than_they do about the health_of_the_community. I do believe
there were_some actual issues that were identified_as places for_improvement
for the Cassandra community, but I don't_think_it was necessary to come in
wielding_a_sledge hammer. It seems that the_Cassandra_board_was not given an
opportunity to_fix the issues (mostly by increasing_the number of project
committers) before the board forced the_changes. This has_resulted in a lot of
hurt_feelings_and_a general sense of distrust between the Cassandra community
and the_ASF.

All that_being said, I'm_not