Mailing-List: contact client-dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: client-dev@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of gdusbabek@gmail.com designates
 209.85.220.172 as permitted sender)
MIME-Version: 1.0
Reply-To: gdusbabek@gmail.com
In-Reply-To: 
 <CAGYDNRtppb9-cZfUvbGk6xT8b9YzV-BWpG4YX-streEsyKvQzQ@mail.gmail.com>
References: <5796F49E-F2F9-45F4-AA36-68BF5DFB1313@rubyscale.com>
	<CAGYDNRtppb9-cZfUvbGk6xT8b9YzV-BWpG4YX-streEsyKvQzQ@mail.gmail.com>
Date: Fri, 3 Feb 2012 13:41:38 -0600
Message-ID: 
 <CALTRSK=O5EJXEPg74fjD=yoPoZSmbTxTkZpSWrnzDL3c4kUN_A@mail.gmail.com>
Subject: Re: Moving from apache-extras back to github
From: Gary Dusbabek <gdusbabek@gmail.com>
Cc: client-dev@cassandra.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Moved to just client-dev...

Are there any negative aspects of renaming the driver?  It seems as
there is already an audience for cassanda-node.

Gary.


On Wed, Feb 1, 2012 at 23:56, samal <samalgorai@gmail.com> wrote:
> +1 ( to Eric )
>
> Also I would suggest renaming cassandra-node to "node-cql" ( it only has
> CQL drivers). this name convention is very popular for noders & will make
> module consistent to be get searched on npm.
>
> On Wed, Feb 1, 2012 at 12:48 AM, Kelley Reynolds <
> kelley.reynolds@rubyscale.com> wrote:
>
>> On Tue, Jan 31, 2012 at 9:12 AM, Gary Dusbabek <gdusba...@gmail.com>
>> wrote:
>> >> When first starting work on the CQL driver for node[1] , work was don=
e
>> >> on github. =C2=A0After a while it was moved to apache-extras so it co=
uld be
>> >> more uniform with the other drivers. =C2=A0However, the experience on
>> >> apache-extras is not good as collaboration is difficult.
>> >>
>> >> That, and because the node.js community does almost all of its work
>> >> via github, I'd like to move the node cassandra client back to
>> >> github[2].
>> >>
>> >> Any strong objections against this?
>> > I don't have any objections, but I wonder, is there someway to salvage
>> > the "discover-ability", and/or consistency aspects?
>> > One option would be to make Github The Place. =C2=A0I'd be cool with t=
hat,
>> > but it means the disruption of a move, and doesn't rule out the
>> > possibility that someone won't want to host elsewhere down the road
>> > (say because they want to use mercurial, or svn).
>> > Could we retain the Google Code pages as project hosting somehow,
>> > disabling everything but the Downloads tab and adding prominent links
>> > to Github for issue tracking? =C2=A0You might even be able to leave th=
e
>> > source tab enabled and keep it updated as a mirror.
>>
>> For the ruby-cql driver, it's easy enough to just have both github and
>> apache-extras upstream and to let people use whichever one makes them ha=
ppy
>> to push patches around, I don't find it particularly onerous at all. Mos=
t
>> people appear to prefer github but pushing changes back to apache-extras=
 is
>> trivial. As long as the 'official' drivers are linked to from some
>> officialish place so that people don't have to go searching for which
>> version of what to use, I think we're good. Few things are more irritati=
ng
>> than spending hours trying to find the right version of something to use=
.
>>
>> Kelley Reynolds
>> CTO / Cofounder, RubyScale
>>