Subversion, Collaboa, and Commit Access
Our repository was originally setup for internal development with the understanding it would be open source. We deployed Subversion 1.2 and Trac, which was great internally, but not so hot when we opened the source and developers started asking for commit access. In order for developers to hack, patch, and adapt SimpleTicket within the repository we will be updating the server.
First we will be upgrading Subversion from 1.2 to 1.3. Subversion 1.2 only allows for read, write, and anonymous permissions. This would allow for rogue commits and restrict us from giving someone their own branch. After a little digging, we found that using WebDAV or upgrading to 1.3 allows us to set path-based permissions on the repository. As such, please note SVN access will be unavailable for a period of time when we upgrade to 1.3.
We also ran into Collaboa, a Rails based application for SVN repositories and developer collaboration. Among other features, Collaboa provide RSS feeds for changesets which means you’ll see what we’re doing.
If you’d like to help us test this setup before it goes live, please leave a comment.
February 13th, 2006 at 1:22 pm
Alex,
I would like to test the development site/setup. I also believe that _trac_ will be a better solution than Collaboa because of the internal wiki. (For documentation purposes, obviously)
Trac is also more mature than Collaboa. I also talked with the developer of Collaboa a couple months back and he said he had no plans to integrate a wiki in that application.
FYI, Trac also has RSS feeds for changesets(Timeline), I use them all the time to watch another project.
Email me at tenthconcept (at) gmail
February 13th, 2006 at 5:17 pm
Yeah i have to agree, I’ll test whatever but i don’t see what Collaboa brings to the table would make me want to use it over Trac.