I'm still not a big fan of Git, but I've seen that Github is pretty
nice. If there's a majority of people here who would prefer to move
the project there, I'm happy to cooperate with that. If such a
consensus would emerge, it would be great if someone could contribute
a high-fidelity conversion of the repository (and preferably the
issues, as well!) to Git/Github.
> I'm still not a big fan of Git, but I've seen that Github is pretty
> nice. If there's a majority of people here who would prefer to move
> the project there, I'm happy to cooperate with that. If such a
> consensus would emerge, it would be great if someone could contribute
> a high-fidelity conversion of the repository (and preferably the
> issues, as well!) to Git/Github.
> Cheers,
> Dirkjan
> --
> You received this message because you are subscribed to the Google Groups "CouchDB-Python" group.
> To post to this group, send email to couchdb-python@googlegroups.com.
> To unsubscribe from this group, send email to couchdb-python+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/couchdb-python?hl=en.
> I'm still not a big fan of Git, but I've seen that Github is pretty
> nice. If there's a majority of people here who would prefer to move
> the project there, I'm happy to cooperate with that. If such a
> consensus would emerge, it would be great if someone could contribute
> a high-fidelity conversion of the repository (and preferably the
> issues, as well!) to Git/Github.
> Cheers,
> Dirkjan
> -- > You received this message because you are subscribed to the Google Groups "CouchDB-Python" group.
> To post to this group, send email to couchdb-python@googlegroups.com.
> To unsubscribe from this group, send email to couchdb-python+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/couchdb-python?hl=en.
I'm have nothing against GitHub, but what about Bitbucket? It also has
pull requests, commits and source reviewing and more same things that
GitHub have, but it doesn't requires migration from hg to git.
On Sat, Sep 8, 2012 at 1:17 PM, Carlton Gibson <carlton.gib...@gmail.com> wrote:
> +1 for moving to GitHub.
> Sent from my iPhone
> On 8 Sep 2012, at 09:26, Dirkjan Ochtman <dirk...@ochtman.nl> wrote:
>> Addressing this separately.
>> I'm still not a big fan of Git, but I've seen that Github is pretty
>> nice. If there's a majority of people here who would prefer to move
>> the project there, I'm happy to cooperate with that. If such a
>> consensus would emerge, it would be great if someone could contribute
>> a high-fidelity conversion of the repository (and preferably the
>> issues, as well!) to Git/Github.
>> Cheers,
>> Dirkjan
>> --
>> You received this message because you are subscribed to the Google Groups "CouchDB-Python" group.
>> To post to this group, send email to couchdb-python@googlegroups.com.
>> To unsubscribe from this group, send email to couchdb-python+unsubscribe@googlegroups.com.
>> For more options, visit this group at http://groups.google.com/group/couchdb-python?hl=en.
> --
> You received this message because you are subscribed to the Google Groups "CouchDB-Python" group.
> To post to this group, send email to couchdb-python@googlegroups.com.
> To unsubscribe from this group, send email to couchdb-python+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/couchdb-python?hl=en.
I don't have an informed opinion (I've only used github, so I can't
compare with bitbucket), but I've been using github here at work for a
couple years now, and have been very pleased. I'd advocate for using
github for any project looking to move to a DVCS (ie. coming from
csv/svn). It looks like bitbucket has a very similar feature set, and
not having to migrate out of Hg is probably a killer feature.
On Sat, Sep 8, 2012 at 2:28 AM, Alexander Shorin <kxe...@gmail.com> wrote:
> Hi,
> I'm have nothing against GitHub, but what about Bitbucket? It also has
> pull requests, commits and source reviewing and more same things that
> GitHub have, but it doesn't requires migration from hg to git.
> --
> ,,,^..^,,,
> On Sat, Sep 8, 2012 at 1:17 PM, Carlton Gibson <carlton.gib...@gmail.com> wrote:
>> +1 for moving to GitHub.
>> Sent from my iPhone
>> On 8 Sep 2012, at 09:26, Dirkjan Ochtman <dirk...@ochtman.nl> wrote:
>>> Addressing this separately.
>>> I'm still not a big fan of Git, but I've seen that Github is pretty
>>> nice. If there's a majority of people here who would prefer to move
>>> the project there, I'm happy to cooperate with that. If such a
>>> consensus would emerge, it would be great if someone could contribute
>>> a high-fidelity conversion of the repository (and preferably the
>>> issues, as well!) to Git/Github.
>>> Cheers,
>>> Dirkjan
>>> --
>>> You received this message because you are subscribed to the Google Groups "CouchDB-Python" group.
>>> To post to this group, send email to couchdb-python@googlegroups.com.
>>> To unsubscribe from this group, send email to couchdb-python+unsubscribe@googlegroups.com.
>>> For more options, visit this group at http://groups.google.com/group/couchdb-python?hl=en.
>> --
>> You received this message because you are subscribed to the Google Groups "CouchDB-Python" group.
>> To post to this group, send email to couchdb-python@googlegroups.com.
>> To unsubscribe from this group, send email to couchdb-python+unsubscribe@googlegroups.com.
>> For more options, visit this group at http://groups.google.com/group/couchdb-python?hl=en.
> --
> You received this message because you are subscribed to the Google Groups "CouchDB-Python" group.
> To post to this group, send email to couchdb-python@googlegroups.com.
> To unsubscribe from this group, send email to couchdb-python+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/couchdb-python?hl=en.
Thinking about this more, I think that the killer feature for GitHub
is the network effect, not so much the specific DVCS used, etc.
However, I also think that spending a lot of effort on something that
doesn't actually get the project closer to releasing 0.9 doesn't seem
like a good use of energy right now. As long as we've got active
owners/committers on the project, I think migration would be a
distraction. Just MHO, of course.
Eli
On Mon, Sep 10, 2012 at 4:37 PM, Eli Stevens (Gmail)
<wickedg...@gmail.com> wrote:
> I don't have an informed opinion (I've only used github, so I can't
> compare with bitbucket), but I've been using github here at work for a
> couple years now, and have been very pleased. I'd advocate for using
> github for any project looking to move to a DVCS (ie. coming from
> csv/svn). It looks like bitbucket has a very similar feature set, and
> not having to migrate out of Hg is probably a killer feature.
> Cheers,
> Eli
> On Sat, Sep 8, 2012 at 2:28 AM, Alexander Shorin <kxe...@gmail.com> wrote:
>> Hi,
>> I'm have nothing against GitHub, but what about Bitbucket? It also has
>> pull requests, commits and source reviewing and more same things that
>> GitHub have, but it doesn't requires migration from hg to git.
>> --
>> ,,,^..^,,,
>> On Sat, Sep 8, 2012 at 1:17 PM, Carlton Gibson <carlton.gib...@gmail.com> wrote:
>>> +1 for moving to GitHub.
>>> Sent from my iPhone
>>> On 8 Sep 2012, at 09:26, Dirkjan Ochtman <dirk...@ochtman.nl> wrote:
>>>> Addressing this separately.
>>>> I'm still not a big fan of Git, but I've seen that Github is pretty
>>>> nice. If there's a majority of people here who would prefer to move
>>>> the project there, I'm happy to cooperate with that. If such a
>>>> consensus would emerge, it would be great if someone could contribute
>>>> a high-fidelity conversion of the repository (and preferably the
>>>> issues, as well!) to Git/Github.
>>>> Cheers,
>>>> Dirkjan
>>>> --
>>>> You received this message because you are subscribed to the Google Groups "CouchDB-Python" group.
>>>> To post to this group, send email to couchdb-python@googlegroups.com.
>>>> To unsubscribe from this group, send email to couchdb-python+unsubscribe@googlegroups.com.
>>>> For more options, visit this group at http://groups.google.com/group/couchdb-python?hl=en.
>>> --
>>> You received this message because you are subscribed to the Google Groups "CouchDB-Python" group.
>>> To post to this group, send email to couchdb-python@googlegroups.com.
>>> To unsubscribe from this group, send email to couchdb-python+unsubscribe@googlegroups.com.
>>> For more options, visit this group at http://groups.google.com/group/couchdb-python?hl=en.
>> --
>> You received this message because you are subscribed to the Google Groups "CouchDB-Python" group.
>> To post to this group, send email to couchdb-python@googlegroups.com.
>> To unsubscribe from this group, send email to couchdb-python+unsubscribe@googlegroups.com.
>> For more options, visit this group at http://groups.google.com/group/couchdb-python?hl=en.
On Wed, Sep 19, 2012 at 7:07 PM, Eli Stevens (Gmail)
<wickedg...@gmail.com> wrote:
> However, I also think that spending a lot of effort on something that
> doesn't actually get the project closer to releasing 0.9 doesn't seem
> like a good use of energy right now. As long as we've got active
> owners/committers on the project, I think migration would be a
> distraction. Just MHO, of course.
On 20 September 2012 08:40, Dirkjan Ochtman <dirk...@ochtman.nl> wrote:
> On Wed, Sep 19, 2012 at 7:07 PM, Eli Stevens (Gmail)
> <wickedg...@gmail.com> wrote:
> > However, I also think that spending a lot of effort on something that
> > doesn't actually get the project closer to releasing 0.9 doesn't seem
> > like a good use of energy right now. As long as we've got active
> > owners/committers on the project, I think migration would be a
> > distraction. Just MHO, of course.
> Sounds about right.
Agreed. I prefer Git to Mercurial, and github to Google Code, but I don't
think it's worth moving right now.
- Matt
