Recently I had the opportunity to talk with the authors of Version Control with Subversion. In this interview, they discuss what Subversion is, migrating to Subversion, and, of course, music.

What is Subversion?
Subversion is an open source version control system. It was designed to be a compelling replacement for CVS - preserving the basic workflow and user experience of that system, but providing significant improvements over CVS's model (and its implementation).

Who hosts it and what license is it distributed under? Is the license OSI approved?
Subversion is hosted by CollabNet (www.collab.net), which also funds large parts of Subversion's development. The project calls Tigris.org - an online open source collaborative software development community - its home. Subversion is developed under CollabNet's license, which is a modified version of the Apache license (and fully compliant with the Debian Free Software Guidelines).

Are any large projects using Subversion now?
Absolutely. Subversion is currently being used by many large development teams, both open source and commercial. Some examples of large open source projects using Subversion include the folks at Samba, Zope, and Xiph. Notably, the Apache Software Foundation started using Subversion in early 2003, and started migrating projects to Subversion in earnest when Subversion reached 1.0 last February. Both Apache Geronimo and Apache SpamAssassin are using Subversion, and Apache HTTP Server is preparing to convert any day now.

What was wrong with CVS? Why was a new source control system needed?
CVS works just fine for file-based version control (as does RCS, the system atop which CVS is constructed). As it turns out, most projects typically involve more than one file, and that's when you start noticing creaks in the floors and cracks in the walls. CVS does not provide atomicity for changes across multiple files - does not, in fact, even have a notion of such a change "set." CVS does not do version changes to directory structure, such as file and subdirectory additions or removals, or items that are renamed. It's extremely inefficient in its handling of "binary" (nontextual) files. It was never designed with networks in mind; that support was entirely an afterthought.

Fixing these problems within the constraints of the basic CVS architecture was already a nonviable solution. But when you then examine the state of CVS's source code and lack of a modular, extensible design, you come away without a shadow of doubt - it was time to begin anew.

What are some of the cool new features of Subversion?
Besides fixing most of the major problems found in CVS, Subversion has additional perks. For example, the file and directories you keep under version control can have property lists - arbitrary name/value pairs - attached to them. Subversion itself uses these lists to track stuff like the MIME type, preferred line-ending style, keyword expansion setting, executability, etc. But users can set their own properties willy-nilly, and use them for whatever they would like. The properties themselves are versioned, too.

Another neat feature involves Subversion's network connectivity. Since one of the available server options is an Apache WebDAV module, you have at your fingers all the functionality and extensibility that Apache offers, plus a fair degree of WebDAV interoperability, all for free. This means you can refer directly to a Subversion repository URL when trying to get your grandmother to view the latest version of something you keep under version control, and Apache will just serve up that document like any other Web resource.

Readers should check out the Subversion Web site (http://subversion.tigris.org) for news about the latest and greatest coolness flowing from that community.

What steps should I take to migrate from CVS to Subversion?
Perhaps the biggest decision involved in a migration like this is what to do with all the versioned data you currently have stored in CVS repositories. For some folks, the answer is to just leave that data in CVS, take a "top-skim" of the latest versions of all the files in that repository, and import them into a new Subversion repository. But for those who desire a full migration of their CVS history, the cvs2svn tool (http://cvs2svn.tigris.org/) is the way to go.

Along the way you'll hit other decision-making points (a beautiful side effect of Subversion's modular design). For example, you'll have to choose between a pair of back-end storage mechanisms and decide which of a handful of network access routes you'd like to use with your repository.

Of course, you'll need a copy of Version Control with Subversion by your side! There is a section entitled "How to Read This Book" in the preface, which is perhaps the best launching point for the various audiences of the book, as well as a quick-start guide at the end of Chapter 1 aimed at helping folks get set up with enough of Subversion to start experimenting with it.

So you three helped write Subversion? Why did you get involved?
Ben: In 2000, I was still working as a Unix sysadmin, pining for a chance to code again. My buddy Karl Fogel and I had started writing some free software in our spare time, but then he got the call from CollabNet. Karl wasn't willing to move to San Francisco, so he got permission to pull together a Chicago-area team. Getting paid to write open source software (with your friends) is an almost unbelievable dream come true, so I jumped at the opportunity. Karl and I still joke that we originally thought it would take six months - not four years - to finish a 1.0 product!

Fitz: Back in 2000, Karl Fogel called me up to tell me that Brian Behlendorf had hired him at CollabNet to start work on the successor to CVS. I was very excited about the idea of Subversion (which was actually called "Inversion" back then) and started following Subversion's development and helped out here and there as time permitted. Eventually, I joined CollabNet full-time where I work with Karl, Mike, and Ben on Subversion and other various mind-control, um, I mean version-control related projects. I would like to state for the record that I do not and have never played the banjo.

Mike: Ben made me do it! Seriously, working on Subversion afforded me the opportunity to help design and implement a piece of software that promised to alleviate frustrations I was running into daily using CVS and Visual Source Safe. As my first foray into the open source culture, it gave me a chance to experience firsthand what all the buzz was about. When Ben and Karl called me up to say that they were now a year into their six-month project and needed a hand, I went to work for CollabNet.

In your office, musical instruments outnumber computers two-to-one. Are you really programmers?
No, we're musicians.

Although we're programmers by day, we've all got musical interests to some degree or other.

Fitz: Ben is an amazing musician who plays piano, guitar, and banjo, not to mention the fact that he's quite the barbershop singer too. When he's not programming, writing books, answering e-mail, or helping out Subversion users on IRC, Ben composes musicals and does sound design for theater with his collaborator, Andre Pluess. Quite frankly, I don't think he sleeps. Much to Ben's chagrin, floating around in my head are a handful of songs that he and Andre have written.

Ben: Mike is the "rocker" in our office. He's got a sweet PRS electric at home, but that doesn't prevent him from playing the same songs and progressive-rock licks on his acoustic guitar at the office. Mike plays in a very talented, very tight band called Autumn War. But he also writes and records a lot of his own thoughtful songs in his home studio. Call his cellphone sometime and listen to the outgoing message; it's hilarious. Though Mike's incessant desk drumming sometimes makes Fitz want to jump out the window.

Mike: Fitz grew up in the deep south. So while he claims the high tenor line during office barbershop quartet time (between morning snack and recess), his blues guitar licks are low-down, gritty goodness. In addition, he's the office DJ. He's got more muscle in his "iPod thumb" than the average hacker has on his whole body, and he has a truckload of diverse music to boot.

About Ben Collins-Sussman
Ben Collins-Sussman has been a sysadmin and programmer for 10 years, and is one of the original designers and authors of Subversion. He currently works for CollabNet as a Subversion developer and community leader. When away from his computer, he moonlights as a musical theater composer at theaters around the city of Chicago. He lives with his lovely wife, three cats, and a house full of computer and music gizmos.

About Brian W. Fitzpatrick
Brian W. Fitzpatrick is a member of the Apache Software Foundation and currently works for CollabNet. He has been involved with Subversion in one way or another since its inception in early 2000. Originally from New Orleans, Brian moved to Chicago to attend Loyola University where he received a degree in Latin and Greek.

About C. Michael Pilato
C. Michael Pilato (Mike) is a core Subversion developer, and a leader in the Subversion community. He is currently employed by CollabNet, where he spends his days (and many nights) improving Subversion and other tools with which it integrates. A husband and father, this North Carolina native also enjoys composing and performing music, freelance graphic design work, hiking, and spending quality time with his family. Mike has a degree in computer science and mathematics from the University of North Carolina at Charlotte.