++added: Handle multiple repositories per project ----------------------------------------
Except for CVS and SVN, the VCSes we provide can easily support several repositories for a single project. For Arch, there's no server-side and it's done directly via SFTP. For Git and Hg, we do it manually on request. So it would be good to have a web interface to manage those additional subrepositories, plus a backend script to create them on the filesystem. There are several applications for this: * reproduce the CVS/SVN concept of "modules" and split a project in different parts * manage repository metadata (e.g. gitweb or hgweb "description") * add a "fork" feature, where people not part of the project (yet) could start a fork; for clarity, they could be stored in a "forks/" subdirectory * support non-centralized development models, where each dev has its own subrepository, instead of sharing a main repository In all cases, the subrepositories need to be clearly parented to the Savannah project; it's not a way to create arbitrary repositories for project that weren't validated through the Savannah project registration procedure. ++added: -- forwarded from https://savannah.gnu.org/maintenance/[EMAIL PROTECTED]://savannah.gnu.org/maintenance _______________________________________________ Savannah-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/savannah-cvs
