I’m working at Nelen & Schuurmans and we’ve got some 10 people working with Django (out of 30-40 total). Quite a sizable group. And virtually all our software is open source (GPL). Quite specific software, but GPL nonetheless.
Of course, everything is in version control. In our case subversion, combined with trac for issue tracking. Works fine. But all those new-fangled distributed version control systems (bzr, git, hg/mercurial) looked mighty fine, too. I won’t delve into too many details, but here are some observations:
Also important is the psychological effect of djangocon.eu. We attended with three of us. When you’re watching three days of presentations and see that most of them have a github link on their last slide... The bitbucket talk was one of the few without a github link :-) Some conclusions we/I drew from that:
In the end, we had to make a choice between github and bitbucket. I was in favour of bitbucket, but switched to the github camp after much thinkwork. The basic dilemma is simple:
git stdoesn’t work. You need to type in the full
git statuscommand. Every subversion user types
svn stinstead of
svn status. “It is good to irritate everyone used to subversion in order to get them to understand git better” is apparently the thought. Even though hg, which does virtually the same as git, has sane names and commands for the very same concepts.
The reason for me to eventually make my choice and to suggest github: https://github.com/plone. Plone (the biggest Python CMS, for those that don’t know it) is switching over to github from their own subversion repository. I worked with Plone for a long time and know and respect a lot of technically very adept people there. So their judgment is important to me.
There was a questionaire a year ago or so about the options. Keep svn, own git, github, own hg, bitbucket. The results were clear: I’m amazed how clear the vote result is! We don’t have to wait any longer to draw a conclusion: We want to move to Github.
Well, we at Nelen & Schuurmans have two accounts now:
setings.py, some fixtures and a customer logo. We did want a separate account for this as it makes it easier to treat the django apps as the re-usable generic apps that we want them to be. And they’re part of our Lizard information system that we intend as an open source platform for water-related geographical data, so it is good to keep that separate from our company’s github account.
Github, here we come.
Now if I only can get all those commands loaded in my head... :-)
Well, at least github publicly says that biking to work is awesome, so that earns them a couple of points in their favour from me.
My name is Reinout van Rees and I work a lot with Python (programming language) and Django (website framework). I live in The Netherlands and I'm happily married to Annie van Rees-Kooiman.
Most of my website content is in my weblog. You can keep up to date by subscribing to the automatic feeds (for instance with Google reader):