This has been a very busy year for our "Lunatics" project (a free-film/free-culture animated web series about the first settlers on the Moon). As with many software projects, we keep our assets in a version-control system -- specifically "Subversion". In principle, Subversion does everything we need. The command line interface, however, does not make the right things easy for us (it's far too obsessed with parsing text files, which are incidental to our project, and it balks when given binary data files (which are essential). To keep a handle on the file tree, we need something a little smarter, and I've recently adopted "kdesvn" to do that job. This seems to solve the biggest annoyances.
Film is a very comprehensive art form, probably the most that we have available to us at the moment, so it should be no surprise that a free film project severely tests the limits of available free software, not only for authoring the film, but also for collaborating on its creation. In the case of "Lunatics", we need to combine some of the community development software that is frequently used for free software development with tools allowing a lighter-weight interaction more comfortable for creative contributors, and finally, a fan-friendly public face. It's tricky, and I don't think we're really all the way there yet, but over this Summer, I've managed to find and assemble the necessary parts for our online presence. My solution combines several different platforms, and uses a few remote or "cloud" services as well.
Subversion is a modern free software Revision Control System (RCS) that the Subversion community’s developers have designed from the bottom up to be more efficient in form than CVS. Subversion has a structured architecture and has other notable advantages such as the ability to function efficiently with binary files and the relatively low cost of tagging and branching. Yet thankfully, Subversion still manages to maintain a workflow similar to CVS, thus potentially simplifying the learning curve.