Shae Matijs Erisson:
I have a simple plan for a darcsforge as well: If Cabal includes a darcs-repository field, developers will be able to upload their project.cabal file to Hackage or to a darcsforge server. That server will run darcs pull on the repositories once a night or so. The developers can include an index.html in their repo that points to a doc/ subdirectory, or is the entire docs and description for simple projects. That way a single site can host the equivalent of cvs and webspace for darcs. That site could do http://host/projectname urls for each project.
This is roughly a darcs equivalent to RSS aggregators. It does require that developers have a publically accessible repo, but anyone can get space from geocities or angelfire for that.
Advantages of this include:
* easy indexing and searching of projects and sources * easy references to other darcs/cabal projects * host needs nearly zero admin effort, notably zero user accounts required.
Disadvantages are:
* no bug tracker * no mailing lists
Though maybe those could have darcs backends also?
I think darcsforge is an excellent idea, but why not complement it by a combined wiki/ticket tracker at haskell.org? Then, the disadvantages would go away. Manuel