Changes:
Should Start On: Fri 01/30/2004 at 17:00 -> Fri 01/30/2004 at 00:00
Should be Finished on: Sat 07/30/2005 at 17:00 -> Sat 07/30/2005 at 00:00
_______________________________________________________
Follow-up Comment #32:
well atm the svn extensions in sv_groups work like the cvs stuff .. it creates
an empty repository for all projects. then it's just a matter of having the
web page print the basic info ( read access, read/write access over ssh )
done: creating the empty repository and sv_membersh with svnserve control (
for svn+ssh:// url types )
todo:
- anonymous read access ( over svnserve on 3690, and over http )
- viewcvs for svn repositories ( port 80 as well )
- email reports
- backup
- hooking in the crons
more, possibly for later:
- read/write access over https. this would be a bit harder because of the way
we do auth atm. and client side certificates for https are not simple either.
so that would be only login/password based, which may not be good enough
- converting cvs repositories to svn. there is a reliable cvs2svn
implementation, we can convert repos manually on a ticket basis, or figure
some partly automated way..
_______________________________________________________
This item URL is:
<http://gna.org/task/?func=detailitem&item_id=118>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Project mailing list
[email protected]
http://mail.gna.org:8080/listinfo/project
