Re: Moving from apache-extras back to github
+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 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 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. I'd be cool with that, > > > 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? You might even be able to leave the > > > 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 > happy > > to push patches around, I don't find it particularly onerous at all. Most > > 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 > irritating > > than spending hours trying to find the right version of something to use. > > > > Kelley Reynolds > > CTO / Cofounder, RubyScale > > >
Re: Moving from apache-extras back to github
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 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 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. I'd be cool with that, >> > 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? You might even be able to leave the >> > 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 happy >> to push patches around, I don't find it particularly onerous at all. Most >> 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 irritating >> than spending hours trying to find the right version of something to use. >> >> Kelley Reynolds >> CTO / Cofounder, RubyScale >>
