I still find it terribly ironic that a free <i>D</i>SCM wound up at the heart of such a massive drive toward proprietary centralization. I think a lot of people envisioned things heading in a rather different direction.<p>Which is not meant as backhanded flame of GitHub's product, by the way. Rather, as far as observations go, it can only speak to the opposite - given that everybody <i>can</i> roll their own, they may be doing something right. OTOH, I think it does call for vigilence on whether they're going to start adding lock-in systems, unless they have already.
Big problems with older projects that want to move to GitHub.<p>GitHub's bug reporting API has no means of importing bugs from other systems, without losing all date and user information. Projects that have moved their issue systems over have the full expanse of issues all opened/resolved on the same date and by the same person, and are basically unreadable (sorry, comments with the original info in them don't count). Django in this case is keeping trac for issue reporting.<p>I've emailed github about this, and I got kind of a sleepy "no, we don't really do that, shrugs". I had an insight at that moment, that Github probably does this because they don't <i>want</i> big, ugly old projects moving their 8000 big ugly tickets into their shiny system (Edit: but they've just responded that they want to do this! so, great). My inspiration to move SQLAlchemy to github went to zero in an instant. Fuck that. Old projects and old history about projects matter. A lot.<p>Keeping issue reporting on Trac - AFAICT, Django hasn't solved the issue of coordinate changeset links from trac back to an external service like github. They still seem to have their SVN repo linked in trac. Though this could be solved, with a fair degree of tedium, by first converting all the SVN links in their bug reports to be the equivalent changeset id in git, then hosting a mirror of the git repo. I originally did this when we moved from SVN to mercurial.
looking at djangoproject.com they still use svn, the github repository also does not contain any of the release branches. has there been any announcement about a migration to git?<p>according to <a href="https://code.djangoproject.com/wiki/DjangoBranches" rel="nofollow">https://code.djangoproject.com/wiki/DjangoBranches</a> this is a git mirror that is synced with svn
It seems GitHub is certainly king now... But how long will it last? I feel that Version Control is such a great market that surely some significant challengers will appear in the next few years. Thoughts?
Nice, really happy about this. Hopefully our patches will finally get to go through. If you're in Europe and working with Django have a look at our Job openings, <a href="http://djangogigs.com/gigs/1182/" rel="nofollow">http://djangogigs.com/gigs/1182/</a>
good to see django on github<p>hey dowvoters i am not a troll, many python projects avoided github initially because github was powered by ruby, see it in context
chef, puppet,vagrant,heroku are of ruby origin but now loved by people from various technology backgrounds
Misleading title, I've flagged this.<p>This is an offical branch of Django on git, this github branch has been around for a while. The offical Django development is still on svn.