-=| Gunnar Wolf, Sat, Sep 13, 2008 at 11:53:44AM -0500 |=- > Well, thing is we would have to set up as many public-facing Alioth > git repositories as packages we have, all with the same setup > (i.e. permission-wise, to all group members and DDs). Of course, it > could be templated/done... But it sounds suboptimal! I think the user management on alioth is set up in such a way, that the current situation with regard to access permissions to SVN repository would be kept for the git repositories too. It happens transparently and we don't need to do anything when creating the Git repositories. What worries me more is the impact on the git.debian.org index of all available repositories. That could of cource be addressed by grouping the repoitories by alioth project. That is, show only "pkg-perl/" in the main index, making it a link to the index of all pkg-perl/* git repositories. I am Cc-ing admin@alioth.debian.org in case the admins have something to add to this. Additional data points: we're talking about 950 git repositories; there is no immediate plan to make the transition, we still discuss *if* we want it. My other concern is somehow opposite of Gunnar's: I worry about the project-wide changes, i.e. changes affecting all packages. These don't happen very often, but I personally find it useful to have all of the packages checked out. This is now achieved by checking out trunk/. running "svn up" in it from time to time brings in the newly added packages too. Perhaps this can be addressed by using mr. Anyone having experience with it? -- dam JabberID: dam@jabber.minus273.org
Attachment:
signature.asc
Description: Digital signature