On 1 Sep 2009, at 18:36, Duane Taylor wrote:
I've used SVN for document assets once, but the downside is that the front-end tools are primitive (like Tortoise SVN)and some folks would rather not be bothered w/ having to understand all the SVN lingo. To be honest, almost all the projects I've worked on we have a commercial CMS like Stellant or Sharepoint. Recently, I started looking into Jive (http://www.jivesoftware.com/), which we are beginning to set up at my work and it does a good job of version management and other things, but it is pricey.
One _really_ big advantage of using Subversion[1] in my experiences is that it's easier to communicate with the rest of the development team if everybody is storing things in the same way/place.
It's much easier to for a developer to miss a design change (or vice versa) if they have to remember to go look somewhere different from where they spend most of their time.
It reinforces that everybody involved is working on the "same thing". Cheers, Adrian [1] Or whatever source control system is being used[2] by your dev team [2] If they're not using one get a better dev team :-) -- http://quietstars.com - twitter.com/adrianh - delicious.com/adrianh ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
