-0 The project seems to have a hard time getting on top of reviewing his backlog of 'patch available' issues, so that I'm skeptical adopting more code to maintain is the thing the project needs the most right now. Besides, I'm also generally skeptical that augmenting the scope of a project makes it better: I feel keeping this project focused on the core server is better. I see risks here, but the upsides haven't been made very clear for me, even for end users: yes, it may provide a tiny bit more clarity around which Golang driver to choose by default, but I'm not sure users are that lost, and I think there is other ways to solve that if we really want.
Anyway, I reckon I may be overly pessimistic here and it's not that strong of an objection if a large majority is on-board, so giving my opinion but not opposing. -- Sylvain On Wed, Sep 12, 2018 at 5:36 PM Jeremiah D Jordan <jeremiah.jor...@gmail.com> wrote: > +1 > > But I also think getting this through incubation might take a while/be > impossible given how large the contributor list looks… > > > On Sep 12, 2018, at 10:22 AM, Jeff Jirsa <jji...@gmail.com> wrote: > > > > +1 > > > > (Incubation looks like it may be challenging to get acceptance from all > existing contributors, though) > > > > -- > > Jeff Jirsa > > > > > >> On Sep 12, 2018, at 8:12 AM, Nate McCall <zznat...@gmail.com> wrote: > >> > >> This will be the same process used for dtest. We will need to walk > >> this through the incubator per the process outlined here: > >> > >> > https://urldefense.proofpoint.com/v2/url?u=https-3A__incubator.apache.org_guides_ip-5Fclearance.html&d=DwIFAg&c=adz96Xi0w1RHqtPMowiL2g&r=CNZK3RiJDLqhsZDG6FQGnXn8WyPRCQhp4x_uBICNC0g&m=g-MlYFZVJ7j5Dj_ZfPfa0Ik8Nxco7QsJhTG1TnJH7xI&s=rk5T_t1HZY6PAhN5XgflBhfEtNrcZkVTIvQxixDlw9o&e= > >> > >> Pending the outcome of this vote, we will create the JIRA issues for > >> tracking and after we go through the process, and discuss adding > >> committers in a separate thread (we need to do this atomically anyway > >> per general ASF committer adding processes). > >> > >> Thanks, > >> -Nate > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > >> For additional commands, e-mail: dev-h...@cassandra.apache.org > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > For additional commands, e-mail: dev-h...@cassandra.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
