[kforge-dev] requirements + existing tools

Wed Dec 8 14:17:08 UTC 2004

Possible features for the kforge system
=======================================

[Core]
1.1 users
1.2 projects
1.3 Web interface to this

[Repositories]
2.1 file versioning system (svn)
2.2 raw database (postgres)
2.3 archive system such dspace (dspace)
2.4 permission system tying users to these items

[Project Management]
3.1 bug tracking (bugzilla, etc)
3.2 mailing lists (mailman etc)
3.3 forums + wiki (...)

[Misc]
4.1 shell access
4.2 ability to set up servers e.g. jsp server
4.3 Ability to have subdomain and your own web site for a project a la sourceforge

Existing Tools
==============

1. GForge
   * Satisfies:
		+ 1.*
		+ 2.1,2.3 (?)
		+ 3

2. Svn + Trac
	* Satisfies
		+ 2.1
		+ 3

Remarks
=======

0. Any others features or tools?

1. Strong presumption in favour of getting something off the shelf. In which 
case likely to be gforge.

2. The real issue is what occurs when you try and extend an existing tool (for 
example add database repositories to gforge)

3. It would also be very useful to factor out the user system but this may be 
difficult (e.g. gforge system is tightly integrated).

4. General architecture of core system (user + projects) off which you want to 
hang ancillary services and modules. Suggests a plugin framework (which gforge 
has to some extent) ....

See also http://www.okfn.org/wiki/KnowledgeForge