[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: project management tool using SVN

From: bruce <bedouglas_at_earthlink.net>
Date: 2005-04-04 14:10:38 CEST


thanks for the reply. we're trying to create a basic development environment
for a distributed development team. at a minimum, we need:
 -issue tracking
 -project management
 -user management
 -doc management
 -doc collaboration
 -doc repository

we want to be able to create projects/apps, and assign them to a given team.
we also need to be able to allow the user/admin to perform whatever
functions are required to deal with the respository as needed.

given that the team might be across the 'net, we would like a tool to allow
users to access user info from a directory..

of course we'd like all this to work together!!

gforge is reasonable (although some have talked about security issues) but
it seems to have some doc root/installation issues. dotproject looks
reasonable, but we'd have to modify it to contain the wiki function, as well
as the SVN/SVN Browser hooks. The same can be said for phpcollab.

It also appears that we'd have to create the user directory functionality
regardless of which app we use. and we'd like to use a single user database
for the different functionality/apps that i've described...

The end goal is to have a basic starting app, that the team could access/use
to help develop/track/test a given project.


-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2005@ryandesign.com]
Sent: Sunday, April 03, 2005 6:03 PM
To: bedouglas@earthlink.net
Cc: users@subversion.tigris.org
Subject: Re: project management tool using SVN

On 01.04.2005, at 19:23, bruce wrote:

> we're trying to find a good project management tool (open source) that
> uses
> SVN. searching of google didn't give us any insights...
> we'd like the tool to be able to allow us to manage users, handle
> multiple
> projects, track issues for multiple projects, and handle docs for the
> overall operation. we'd also like to be able to have a member/developer
> directory section.
> we've seen trac, but trac is basically good for a single project, as it
> requires a separate svn repos for a project.

We also decided against Trac for this reason, and because it's Python
and SQLite, neither of which I've ever worked with before. We're much
more comfortable with PHP and MySQL, to which end we're using Mantis
for bug tracking and a wiki for documentation and other stuff. We're
currently using phpwiki but will switch to MediaWiki when I find a
minute to install it. That probably doesn't help you with project or
user management... um, but I'm not even sure what you mean by that
exactly, so that may be part of the problem. We use a single repository
for everything, so there's no need for an interface to make
repositories. It's served with Apache2 using LDAP authentication, the
same authentication we use for our system and mail accounts, so that's
just one place we need to touch to make a new user. We have discussion
mailing lists for the major projects so the developers can discuss, and
also commit mailing lists for each project so people can see what the
others are doing. And as for a member/developer directory, we have no
need for that as we're just a dozen developers working in one building
and all pretty much know each other. :-)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 4 14:12:00 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.