Drupal as a Sourceforge clone?

public
stodge@drupal.org - Wed, 2008-08-27 18:33

I'm investigating Drupal as an internal Sourceforge alternative. I'm having trouble understanding how the Project Manager works with issues and subversion repositories. Is there any GOOD documentation that explains how to the PM module/Drupal interact with repositories?

I'm familiar with Trac or GForge, where a project is directly tied to a specific repository and any commits you make against a specific issue are added to that ticket.

I used ClearCase/ClearQuest recently, which despite its many, major flaws, is my benchmark for functionality. One prime example is linking commits to an issue/ticket so that an auditor can clearly see the software changes that were made for that issue.

I created a project on my Drupal site. I also added a subversion repository in the project administration -> vcs repositories admin page. But I don't want to have to manually create this entry every time I create a new project. Or do I have to manually create the svn repository on the disk and then add an entry in the vcs repositories admin page?

For example in GForge, I register a new project and a crontab entry automatically creates the svn repository on disk and links it to the project. Do I have to do all this manually?

I'm confused!

Any help appreciated!
Thanks

Redmine

cirotix's picture
cirotix - Thu, 2008-09-18 11:57

While it doesn't reply to your question, I would recommend Redmine.
It is like Trac on steroid.

Damien Cirotteau
http://www.rue89.com