[Gforge-devel] Re: Gforge Project Enhacements Proposal

[SPISSER REINHARD]

 * A fully customizeable Role-Based Access Control system. All projects
have a number of Roles which individual developers may be assigned to
upon being added to the group. Each role has a set of privileges for
each tool, which can be set to Read, Write, or Admin by a project
administrator. All projects get a default of four pre-defined roles:
Administrator, Member, Logged-In (member of site but not of project),
and Guest (no logged in account at all). A project administrator does
have the option, though, of creating any new roles for further
granularity. Our implementation is *very* heavily tied into the 2.5
framework, so a near total reimplementation will be needed. But, I
believe that the concepts can be gleaned pretty readily and that with
GForge's increased granularity of thing we should be able to do this
one.
 
 
I'm really interested in such a functionality. Perhaps we can work together to 
get it done for Gforge. 

 * Integration of the Chora (http://www.horde.org/chora/) CVS viewing
framework into SourceForge. This negates the need for any kind of CVSWeb
or ViewCVS system external to SF. We needed it in order to secure the
CVS viewing of certain projects to only members of those projects. The
Chora viewer is an advanced tool written in PHP and on par with CVSWeb
and ViewCVS in most functions. We've even included the integration of
CVSGraph into this Chora system. In addition to the viewing
capabilities, we've added some capability to check-in files from a web
form into CVS, either individually or a directory at a time (using a ZIP
file as a transit).

 
Cool. I think it should not to be too much different to integrate it into gforge
 
 * CVS-backed Document Manager. We've done away with the traditional
Document Manager and used a CVS/Chora-backed module to create a system
with full document history and the capability to store and display
various document types, including binary files (PDFs and the like).
While this does exist to some extent in GForge already, backing it with
Chora and its viewer structures could make for a cleaner interface.

* CVS-based project webpages. This negates the need to give users shell
access to the host machine to update project webpages. The system sets
up triggers so that as soon as changes are checked into the module, the
pages get automatically updated.


 * Licence/Domain manager. We've written a system for dealing with
different licenses for people coming from different domains, as well as
filters allowing only registration from matching email addresses. This
is probably too specific to our own needs, but it's here if anyone's
interested in it.
 
I'm interested 8^)

We should continue the discussion on the gforge-devel forum; the most
people is "listening" there.
 
Reinhard