More project hosting spam: found a recent and interesting comparison between Github and Bitbucket here: https://nudowdeployer.wordpress.com/2013/07/23/github-vs-bitbucket-2/
On 15 November 2013 10:33, Dave Hirschfeld <[email protected]> wrote: > > > On Thursday, 14 November 2013 23:42:13 UTC, David wrote: >> >> I would like to chime in to voice support for moving away from Google >> Code: either Bitbucket or Github would be an improvement in my opinion. >> Bitbucket and Github both offer a social dimension (=easily visualize and >> share your contributions to various projects) to coding, and I would partly >> ascribe the success Matplotlib/Numpy/Scipy have on Github to that (so in >> addition to the pull request mechanism). Personally, I think Github's >> interface is very nice, but the arguments mentioned in this thread in >> favour of Hg/Bitbucket sound very reasonable as well. >> >> Given Google's recent history of killing of projects, I wouldn't be too >> surprised if Google Code is the next one to die. I am not sure, but the >> fact Google Code hasn't seen any (?) change in the last years isn't >> reassuring my gut feeling about its future. >> >> I use both Git and Mercurial, and wouldn't consider myself as in expert >> in either of them. However, I have the impression that both are powerful >> enough to support many different work flows to tailor everybody's needs. >> For instance, the two stage git commit strategy reduces to one with "git >> commit -a". >> >> Two additional features I really like about Github are: >> + automatic cross-referencing of issue's and pull requests >> + github pages for hosting the project web site: http://pages.github.com/ >> >> And it seems Bitbucket has a very similar issue trakcer actually: >> https://confluence.atlassian.com/display/BITBUCKET/Use+the+issue+tracker >> >> Automatic closing issues when committing: >> Bitbucket: https://confluence.atlassian.com/display/BITBUCKET/Resolve+ >> issues+automatically+when+users+push+code >> Github: https://github.com/blog/1386-closing-issues-via-commit-messages >> >> For reference, Github features: https://github.com/features >> and Bitbucket documentation: https://confluence.atlassian. >> com/display/BITBUCKET/Bitbucket+Documentation+Home >> >> Regards, >> David >> > > +10 for git/github here! I have some local changes but haven't submitted > them because I don't know mercurial and don't know the Google Code workflow. > Since almost every other project in the scientific ecosystem uses git & > github I've needed to know it so have taken the time to learn it and have > never looked back. > I can get away with my lack of mercurial / Google Code knowledge because > it only affects Spyder for me. > > I agree with Carlos though - the tools and workflow have to be right for > the main contributors and given my lack of time (and Qt expertise) I'm > unlikely to ever be one of those. > I am proud though to have my name (very far down) in the list of official > contributors to An Afternoon Hack, and maybe if Spyder were on GitHub I'd > someday get similar recognition in this great project too. > > Yours Anecdotally, > Dave > > > PS: Even though I'm on Windows I prefer command-line interfaces. For those > who like guis though there's GitHub Windows - http://windows.github.com/ > > > > -- > You received this message because you are subscribed to the Google Groups > "spyder" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/spyderlib. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "spyder" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/spyderlib. For more options, visit https://groups.google.com/groups/opt_out.
