Sunday, October 7th, 2007
Preface: After reading Daniel Jalkut’s No More Excuses blog post, I realized that this email could easily be a blog post. So I decided to do it.
I’d like to propose a couple of changes to the way Adium does version control to get this discussion started. I definitely do want a discussion and am open to other ideas. This is just what I’ve come up with.
svn.adiumx.com/libpurpleto a Monotone repository.
Regardless of what Adium does, our version of libpurple should be using a mtn repo. pidgin folks can then pull any changes we make to that repository easily and simply, and will enable us to collaborate easily with pidgin, and hopefully with upstreams of other libraries (should we need it).
We should move Adium to some sort of distributed version control
DVCS is the way of the future. It’s not just about better merging. Developers and new contributors get access to the same tools. It makes it much easier for new contributors to get involved, since we can easily pull in their changes, and giving them “commit access” is just as easy as giving them access to push to the branch we release off of.
We should move Adium to Monotone.
Moving Adium to monotone is, at this point, the path of least resistance. The people that we collaborate the most with, pidgin, are using monotone.
Counter: They are not dead set on it, and the land of DVCS is changing rapidly (bzr is getting faster, git is getting easier to use, etc). Maybe now another VCS makes sense for both them and for us. Rlaager said that they might be willing to switch if it’ll make life easier for them and us.
What do other people think about this?