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 wrote:
> +1 ( to Eric )
>
> Also I would suggest renaming cassandra-node to "node-cql" ( it only has
> CQL d
+1 (to samal's suggestion ) about the discoverability of node modules, as
per the convention.
--
Karthik.
On Wed, Feb 1, 2012 at 9:56 PM, samal wrote:
> +1 ( to Eric )
>
> Also I would suggest renaming cassandra-node to "node-cql" ( it only has
> CQL drivers). this name convention is very p
+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.reyno...@rubyscale.com> wrote:
On Tue, Jan 31, 2012 at 9:12 AM, Gary Dusbabek wrote:
>> When first starting work on the CQL driver for node[1] , work was done
>> on github. After a while it was moved to apache-extras so it could be
>> more uniform with the other drivers. However, the experience on
>> apache-extras is not good
On Tue, Jan 31, 2012 at 9:12 AM, Gary Dusbabek wrote:
> When first starting work on the CQL driver for node[1] , work was done
> on github. After a while it was moved to apache-extras so it could be
> more uniform with the other drivers. However, the experience on
> apache-extras is not good as
Hi everybody,
When first starting work on the CQL driver for node[1] , work was done
on github. After a while it was moved to apache-extras so it could be
more uniform with the other drivers. However, the experience on
apache-extras is not good as collaboration is difficult.
That, and because t
