Authors ≠ Committers: why most Open Source projects should switch to distributed revision control

I had been thinking about the idea behind this post for a while now, but reading this post about getting newbies involved in open source just convinced me to write it down.

Being a concept developed in the Open Source world, it is no wonder that distributed revision control systems give their best in that context. There are many pros and cons, that other people described in detail better than I can do. Of all the features they offer, however, the one I prefer is the least technical one, and it is related to the way they encourage new developers to contribute to open source projects. In that perspective, git and mercurial are a lot more effective than svn, for example.

It all comes as a side effect of authors and committers being two different roles. This can encourage new contributors, who are approaching a new project for the first time, and individuals who may not have the time and energy to dedicate long periods of their time to a project, but may be able to contribute with just a few patches.

How GitHub displays both the author and the committer of a single change. Oh, and yes, there is something wrong with the dates. 😉

Think about that. Recognition is one of the most important drivers for Open Source contributors but, unfortunately, centralized revision control (subversion, CVS and the like) doesn’t help in giving credit to newcomers or occasional contributors.

That’s because, generally, sending a single patch (or even a few of them) is not enough to be granted commit access to a project repository (and rightly so) and the commit itself must be done by a project member with enough privileges.

With svn or cvs, the committer of a changeset figures as its author, and the original author of the code is often just mentioned in the notes or in some “credits” list.

With git or mercurial, on the other hand, the author and the committer of a changeset are not necessarily the same person: each commit can then retain the original author name.

I believe that some coders would be much more willing to contribute to Open Source software if they know their name will be included in the official commit logs, especially given the existence of sites like Ohloh, that track contributions by single commits. I would be much more willing to engage in a project if I knew that my changes would be attributed to me no matter who commits them.

That is why I believe what I said in the title: if you are about to start a new Open Source project, you should pick git or mercurial as your revision control system. Do it not just because they are better (and I strongly believe they are), but also because they will make it easier for you to credit any contributor you’ll get.

If you are unfamiliar with the whole concept of distributed revision control, I suggest you to visit or, they both offer intuitive and effective tutorials about the benefits of using mercurial or git.

Alessandro Bahgat
Software Engineer & Manager

I am an engineer and manager of engineers, I sometimes play with side projects and write about my experiences in my spare time.

Liked this?

You can sign up here to be notified of new content. Low frequency, no spam.

comments powered by Disqus