And have been since the end of 2005.
It's a great way to have one, central, online filing system for church. It's a great way to make sure that everyone has the same, up-to-date version of everything.
We use Subversion to manage our church documents
Subscribe to:
Post Comments (Atom)
7 comments:
I'm impressed. When will you be migrating to git? ;)
Thanks for tipoff, we'll check it out.
'When'? Well you know the turnaround rate of a volunteer IT team :-)
SVN rocks -- but how do you get the IT illiterate users to understand it? Do you teach 'em Tortoise SVN?
We use TortoiseSVN and SVNX and we have tried to write accessible procedure to get people to set it up.
For others in the church we just keep repeating - make sure you send things through to the church admin. So that they can commit to repository.
The advantage of there being a certain degree of alienation is that it communicates to the church that the filing system is a big deal.
Recently we've discovered the autoversioning option with Subversion and that's even better for low-level users.
Interesting - do you use the $Id$ auto-props to get the revision info into the docs? Any chance you could screenshot or dump your directory/file structure to illustrate your setup sometime?
Oops... you're not jml, you're another Jonathan.
If you were jml, I would use git. If jml tells me to I will ;-)
In future, I'll make sure I sign off appropriately.
notjml.
Post a Comment