> > Compare this to the Github way of doing things: > > > 1. Commit messages can be seen as part of a pull request, others can add > > inline comments/suggestions to each commit diff, and the pull request > > author can add more commits in the same pull request to improve his/her > > contribution because of the review. > > > 2. Every developer or potential contributor only needs to do *one* clone > > of the project's repo. Then he only needs to create branches in his > > local copy and push them to Github to ask for a pull request. > > > Even if the move to Github doesn't attract more contributors, I think it > > will really improve our code quality and testing because we will be more > > aware of what other devs are trying to do and maybe we could easily > > avoid things like Issues 740, 863 or 880, which required more testing > > and communication between us. > > This will be a great improvement indeed. > Furthermore, if I remember correctly, github also allows to setup a > real website without any imposed frame. > > > During these vacations I reserved the 'spyder-ide' organization in > > Github, and converted our hg repo to git without problems (unfortunately > > revision references will be lost). The only thing left to do is to move > > our issues, which I haven't had time to even try. > > Maybe there is a way to convert a Mercurial repository to a git > repository with an automatic replacement of revision numbers in commit > messages? (from a programming point of view, it seems pretty much > doable) > > Anyway, I agree with your conclusion and I would gladly move to git > even if I prefer Mercurial for other reasons as I mentioned earlier in > this thread.
This being said, I've been thinking about it (for a few minutes...) and I also think that: 1. it will require some work: migrating issues and website 2. it will also cost some efforts: I personnally do only contribute/ develop/work with Mercurial repositories for now, so I'll have to adapt to git (on Linux, this is not a problem but on Windows, this means installing both TortoiseHg and TortoiseGit -- that is a problem when working on some enterprise networks) and change some automation script that I use for synchronizing things 3. we will loose some of GoogleCode advantages. One more login... I like to use my Google account to log in once and for all... (yes, I'm a lazy person :)) From a general point of view, I really like Google websites: simple, efficient and fast. GoogleCode is following this philosophy. On the contrary, I find github website very fuzzy/unclear: there are dozen of links at each page, a real mess (at least this was my impression when I first discovered this website a while ago). Cheers, -Pierre -- You received this message because you are subscribed to the Google Groups "spyder" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/spyderlib?hl=en.
