I don't see that we have reached sufficient consensus on this yet. We've had a brief discussion about the pros and cons of in-tree cassandra vs separate ASF repo here, but let's not frame it like it's either or. From my perspective, there hasn't been any final decision yet whether the proposed side-car solution should be further developed as part of the Cassandra project, or not.
On 18.08.18 03:12, Dinesh Joshi wrote: > Thanks, Nate. I’ll create this request. > > Dinesh > > On Aug 17, 2018, at 5:09 PM, Nate McCall <zznat...@gmail.com> wrote: > >>> I'm not sure logistically how we get a new repo created and licensing and >>> such, but if someone helps make it we can cut the patch against it >>> >> This is pretty straight forward. For precedent, see: >> https://issues.apache.org/jira/browse/CASSANDRA-13634 >> >> We currently have three repositories: >> https://git-wip-us.apache.org/repos/asf >> >> I'm +0 on what approach we take. >> >> --------------------------------------------------------------------- >> 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
