Move to Github (2)

[Christian Stefanescu]

Hello all,

there was an initiative to move this lib to github (http://
groups.google.com/group/pyactiveresource/browse_thread/thread/
9d4d90aeef3b4dc8) ... as far as I can tell nothing came out of it.

Is this still interesting to you (the maintainers)?

I think it could give your project a little boost.

Thanks,
Chris

[Nick Eskelinen]

On Tue, May 24, 2011 at 9:26 AM, Christian Stefanescu
<st.c...@gmail.com> wrote:
> Hello all,
>
> there was an initiative to move this lib to github (http://
> groups.google.com/group/pyactiveresource/browse_thread/thread/
> 9d4d90aeef3b4dc8) ... as far as I can tell nothing came out of it.

It appears as though someone has already done a git-svn over to
GitHub, although it's already out of date:
https://github.com/ekarulf/pyactiveresource

> Is this still interesting to you (the maintainers)?
>
> I think it could give your project a little boost.

I'm a bit ambivalent about GitHub. Care to sell me on it? :)
/n

[Christian Ştefănescu]

That git-svn stuff needs to be put in a cron-job, otherwise it won't work. And I don't know if it's set up to work bi-directionally.

Selling you on GitHub? I'll try!

• GitHub has a lot of attention these days. It draws programmers like no other platform. Hell, people choose git over mercurial or other DVCSs because of GitHub. For other reasons, see below.
  
• The fork / pull request system is brilliant. It's a dead simple way of getting contributions in. The interface is very nicely done and it's just the way open-source contributions are meant to be.
• The issue tracker recently received a nice overhaul and is quite good now, certainly better than the one on google code.

These are just some points, maybe someone else wants to chime in with arguments I may have left out.

Chris

--
You received this message because you are subscribed to the Google Groups "pyactiveresource" group.
To post to this group, send email to pyactive...@googlegroups.com.
To unsubscribe from this group, send email to pyactiveresour...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pyactiveresource?hl=en.

[Nick Eskelinen]

On Tue, May 24, 2011 at 3:58 PM, Christian Ştefănescu
<st.c...@gmail.com> wrote:
> That git-svn stuff needs to be put in a cron-job, otherwise it won't work.
> And I don't know if it's set up to work bi-directionally.
>
> Selling you on GitHub? I'll try!
>
> GitHub has a lot of attention these days. It draws programmers like no other
> platform. Hell, people choose git over mercurial or other DVCSs because of
> GitHub. For other reasons, see below.
> The fork / pull request system is brilliant. It's a dead simple way of
> getting contributions in. The interface is very nicely done and it's just
> the way open-source contributions are meant to be.
> The issue tracker recently received a nice overhaul and is quite good now,
> certainly better than the one on google code.
>
> These are just some points, maybe someone else wants to chime in with
> arguments I may have left out.
>

Ah, looks like the new issue tracker is a lot nicer. I'm fine with
this .. Mark/Jared?

[Mark Roach]

On Fri, May 27, 2011 at 1:02 PM, Nick Eskelinen <nic...@gmail.com> wrote:

Ah, looks like the new issue tracker is a lot nicer. I'm fine with
this .. Mark/Jared?

Honestly, all I do is use git svn at the moment, so It doesn't really matter to me one way or the other...