I find this idea interesting and worth a strong discussion. Something to consider is an argument floating around in the admin tool/side car discussion: if we take an existing project wholesale, we inherit all of it's design decision and technical debt (every project has these). On the other hand, we also get working code that is running in production. I haven't looked at the gocql code (and probably won't until we're a bit beyond the 4.0 code freeze), so I can't speak to anything beyond a cursory reading of the docs.
As we consider bringing in drivers under the project umbrella, we need to evaluate each driver implementation's merit on a case-by-case basis. I'm not sure how we divvy up that work, or whom to entrust with that work, but it's something to keep in mind. Thanks, -Jason On Fri, Aug 31, 2018 at 8:38 AM, Chris Bannister <c.bannis...@gmail.com> wrote: > I intend to stay on and continue to contribute. > > On Fri, 31 Aug 2018 at 4:37 pm, Jonathan Ellis <jbel...@gmail.com> wrote: > > > On Fri, Aug 31, 2018 at 9:14 AM Nate McCall <zznat...@gmail.com> wrote: > > > > > Hi folks, > > > So I was recently talking with, Chris Bannister the gocql [0] > > > maintainer, and he expressed an interest in donating the driver to the > > > ASF. > > > > > > > Is he looking to continue to maintain it or is he looking to give it a > good > > home when he moves on? > > > > We could accept this along the same lines as how we took in the dtest > > > donation - going through the incubator IP clearance process [1], but > > > in this case it's much simpler as an individual (Chris) owns the > > > copyright. > > > > > > > Is that actually the case? Github says 128 contributors, and I don't see > > any mention of a CLA in > > https://github.com/gocql/gocql/blob/master/CONTRIBUTING.md. > > > > -- > > Jonathan Ellis > > co-founder, http://www.datastax.com > > @spyced > > >
