Great..please start the vote to get consensus.
On Wed, Sep 12, 2018 at 8:06 AM Nate McCall wrote:
> Yep - that sounds like the best next step to me.
>
> (apologies for spotty comms folks - been/still on vacation).
> On Wed, Sep 12, 2018 at 8:03 AM sankalp kohli
> wrote:
> >
> > Hi Nate,
> >
Yep - that sounds like the best next step to me.
(apologies for spotty comms folks - been/still on vacation).
On Wed, Sep 12, 2018 at 8:03 AM sankalp kohli wrote:
>
> Hi Nate,
> Looks like we had a lot of discussion here and everyone seems
> to be in favor. What is the next step? A
Hi Nate,
Looks like we had a lot of discussion here and everyone seems
to be in favor. What is the next step? A vote?
Thanks,
Sankalp
On Fri, Aug 31, 2018 at 10:48 PM Alex Lourie wrote:
> Same here. I've been working on this project for a bit now, and I'm
> planning to continue and
Same here. I've been working on this project for a bit now, and I'm
planning to continue and contribute.
I also like the idea of this project becoming an officially endorsed golang
Cassandra driver. Makes a lot of sense too.
Alex.
On Sat., 1 Sep. 2018, 01:08 Chris Bannister, wrote:
> I
> On Aug 31, 2018, at 4:06 PM, Michael Shuler wrote:
>
> Yep! I was going to comment similarly. I would be in full support of a
> committer who focused purely on documentation and website content, for
> instance. It's a matter of trusting a contributor to know what and where
> to commit, as
On 08/31/2018 05:20 PM, Brandon Williams wrote:
> On Fri, Aug 31, 2018 at 4:24 PM Gary Dusbabek wrote:
>
>> At what point is the project comfortable/trusting with granting commit bits
>> to someone who is very familiar with a facet of the project (say, a go
>> client, or dtests), but hasn't made
On Fri, Aug 31, 2018 at 4:24 PM Gary Dusbabek wrote:
> It would also make sense to think about how existing maintainers are
> brought in as committers, if appropriate (official vote, etc.). I'm under
> the impression that Apache commit bits are granted in a binary fashion -
> you have access to
It would also make sense to think about how existing maintainers are
brought in as committers, if appropriate (official vote, etc.). I'm under
the impression that Apache commit bits are granted in a binary fashion -
you have access to everything or nothing. <-- Is this incorrect?
At what point is
I like the idea of having an officially supported Go Driver under ASF. It would
mean easier contributions.
I don't think we should necessarily limit it to a reference implementation. The
industry has a strong interest in building server side as well as client
software in Go.
Dinesh
On
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,
I intend to stay on and continue to contribute.
On Fri, 31 Aug 2018 at 4:37 pm, Jonathan Ellis wrote:
> On Fri, Aug 31, 2018 at 9:14 AM Nate McCall wrote:
>
> > Hi folks,
> > So I was recently talking with, Chris Bannister the gocql [0]
> > maintainer, and he expressed an interest in donating
On Fri, Aug 31, 2018 at 9:14 AM Nate McCall 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
Definitely does not belong in the same repo.
I’m all for folding drivers in / writing our own, just needs active
committers.
On Fri, Aug 31, 2018 at 7:45 AM Michael Shuler
wrote:
> On 08/31/2018 09:34 AM, Jay Zhuang wrote:
> > That's great. Could that be in the same repo as Cassandra or a
> >
It sounds great to have an official GoCQL driver. I like the mentioned end
goal of having a reference implementation that evolves with the core C*
project.
Thanks,
Sumanth
On Fri, Aug 31, 2018 at 7:45 AM Michael Shuler
wrote:
> On 08/31/2018 09:34 AM, Jay Zhuang wrote:
> > That's great.
On 08/31/2018 09:34 AM, Jay Zhuang wrote:
> That's great. Could that be in the same repo as Cassandra or a
> separate repo?
For similar reasons as discussed for an admin tool, separate
repositories are quick and simple to create, as well as allow handling
contribution, CI, build, release, etc.
That's great. Could that be in the same repo as Cassandra or a
separate repo?
On Fri, Aug 31, 2018 at 7:14 AM Nate McCall 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.
>
> We
16 matches
Mail list logo
