I've only ever used Trac for Issue Tracking and Wiki. Looking at the documentaiton on the Trac website, it looks like working copy operations (commit, update, etc.) are done through an "ordinary" SVN client. Maybe I am missing something, but (in 5 minutes) I could not find anything about commiting changes and updating working copies.
If I am right that you just use a SVN client for working copy operations, then using the SVN command line client is very, very similar to using Fossil for working copy operations. In particular, file/directory names with spaces in them need to be quoted. Of course, there are also GUI clients available for both SVN and Fossil. I don't know what your non-developer users are trying to do with Fossil or Trac, but perhaps a GUI front end would be a good idea for your users. Where I work, the non-developer users use only the issue tracking features of Fossil, so only ever use Fossil through it's web interface. Amoung our developers, some of them have configured a few Fossil commands in to the IDE we use. I have not and the IDE does not provide an easy way to share subsets of the configuration. (when a new developer joins us, she/he gets a copy of an existing IDE configuration, then is free to change settings as desired (within coding style guidlines). _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
