Canonical repo location
Chris Adams
github[1] for ease of forking. Since the project has been languishing
a bit as neither Nigel nor I spend all that much time on Mac sysadmin
work any more, I wanted to do a quick straw-poll on how that's working
out for people who are interested in contributing code - would you
prefer we:
1. Stay on Google Code
2. Stick with Mercurial but make bitbucket the official repository
3. Switch to git and github, which has a superset of Google
Code/Bitbucket's features
Personally, I'd vote for #3 as I do almost all of my work with
Git/Github these days and, IIRC, that's been the source of every
external patch we've received[3], and it seems to result in my
spending less time on project maintenance and more on actual coding
but since I'm not contributing all that much actual code these days
I'd be curious in seeing how everyone else feels about this.
Chris
[1] http://bitbucket.org/acdha/pymacadmin
[2] http://github.com/acdha/pymacadmin
[3] In general, I've found that Github seems to get more activity by a
large margin and the pull request UI is pretty awesome:
http://help.github.com/pull-requests/
Nigel Kersten
> Currently we're on Google Code with mirrors on bitbucket[1] and
> github[1] for ease of forking. Since the project has been languishing
> a bit as neither Nigel nor I spend all that much time on Mac sysadmin
> work any more, I wanted to do a quick straw-poll on how that's working
> out for people who are interested in contributing code - would you
> prefer we:
>
> 1. Stay on Google Code
> 2. Stick with Mercurial but make bitbucket the official repository
> 3. Switch to git and github, which has a superset of Google
> Code/Bitbucket's features
>
> Personally, I'd vote for #3 as I do almost all of my work with
> Git/Github these days and, IIRC, that's been the source of every
> external patch we've received[3], and it seems to result in my
> spending less time on project maintenance and more on actual coding
> but since I'm not contributing all that much actual code these days
> I'd be curious in seeing how everyone else feels about this.
Ugh. I completely forgot about this.
I have no strong preference myself. I kind of like keeping it all in
Google Code, but that's because I'm lazy.
>
> Chris
>
> [1] http://bitbucket.org/acdha/pymacadmin
> [2] http://github.com/acdha/pymacadmin
> [3] In general, I've found that Github seems to get more activity by a
> large margin and the pull request UI is pretty awesome:
> http://help.github.com/pull-requests/
>
> --
> You received this message because you are subscribed to the Google Groups "PyMacAdmin" group.
> To post to this group, send email to pymac...@googlegroups.com.
> To unsubscribe from this group, send email to pymacadmin+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/pymacadmin?hl=en.
>
>
Gary Larizza
Nigel Kersten
the docs etc there too and leave the googlecode site up as a
placeholder.
Gary Larizza
amrset
Some open source projects, it takes some time to untangle which site is authoritative...
Regards,
-Roy
Chris Adams
> Would it be possible to make sure that there is a link/explanation on the
> google site that points to the canonical site?
Definitely - I hate that, too. Any move would be a complete move
(using Github's issue tracker, downloads, wiki, etc.) and I'd
definitely update the links to avoid confusion.
Chris
Jeremy Reichman
a place that supports Mercurial directly. Google Code or Bitbucket would
thus be my choice.
(Of note, Bitbucket has joined Atlassian and is adding staff quickly, so I
expect to see a bunch of changes there. I'm not sure if the changes to
their repo hosting plans work well as I have not reviewed them at all.
Your feelings on this acquisition may also depend on whether you're a fan
of Atlassian and its other products, like Confluence, or not. I think it
_is_ notable that they've thrown some weight behind Hg.)
I don't directly use Git at all right now and at this point, don't intend
to. I have enough other things in life to worry about.
However, whether I'm in a minority or not, I can clone from Git(hub) and
push patches via Mercurial. (I've done so with The Luggage, but have not
yet contributed anything to PyMacAdmin, although I have an idea or two
percolating.) Not sure if the reverse is true for Git to Hg.
I don't _like_ to use Hg-Git because it's extra setup work (and another
two extensions to maintain over time), but it's possible. Same goes for
HgSubversion, which I recently got working with the InstaDMG repo. I do
prefer having a DVCS for these projects, whatever it is (well, except for
Bzr, I suppose), since at least it becomes much easier to submit proposed
patches.
And since I haven't contributed to PyMacAdmin, I can't exactly fault
anyone for ignoring my preferences for Mercurial.
--
Jeremy
Nigel Kersten
version control is in a better state than it's been for years :)
huzzah!
We're just going to end up bike shedding here, as I don't see any
objective reasons for picking any one choice over another, and there
isn't enough recent activity by any single person to make their choice
The Right One.
How about the next person to commit > 50 lines of code gets to make
the decision? :)