Quote:
Originally Posted by cryptomail
In my opinion, there is no need for subversion or CVS.
|
Actually it would be nice to have a version control system in place... For one, it would show that you're serious about supporting your contributors; for another, it would allow commentary on the reason a change was applied. It looks right now like you have several codebases for the client and also for the server... you could have -one- for each.
Examples of additions where a version control system could be very helpful (due to complexity and the need to support -teams- of contributors)...
- Adding jack audio connection kit support to linux-based ninjam clients (and maybe servers too?), which would open the door to the LADSPA effect plugins, ardour, spiral synth modular, many others
- developing one (or many!) gui wrappers for clients and servers, especially under linux/macos
- adding support for various external authentication methods (postgres, ldap, mysql, unix passwd/shadow, kerberos, others, combinations)
In short, my opinion is that while you don't -need- version control, it would be very helpful for reasons stated and implied above, and I especially highlight the need to support teams of contributors.
I already have a set of arch archives... maybe I'll make it available generally if I can without too much trouble. If the ninjam gatekeepers develop interest in hosting it, moving the archive is very simple.