> Another less ugly solution would be to force GNU projects to have 2 > savane accounts, one "$project" and another called "www-$project" > (with only CVS as active feature), and have a simple homemade backend > script that would add all members of the WWW group to add www-$project > groups, in the database. So you would not have to make with the actual > useradd/usermod stuff. > > You just have to get a script clever enough to notice when there is a > user added or removed in the WWW group, so it updates all www-$project > groups. > > That would be clean and sensible. But indeed, it will mean that you'll > have to create www-$projects. > Somehow, you can maybe also write another little script that would > review groups of the gnu type, and create the www-$project if missing, > by setting everything up. > > There an additional plus: GNU packages could maintain separate list > from people that have write access on the repos and the ones that have > write access to the webpages.
This sounds good. Actually there is already www$project (--webgroup option). The trick would be to use --webgroup for sv_groups, and avoid that option for sv_users; I'd do theat work manually and replicate $project to $wwwproject (adding 'www' members along the way). Not using --webgroup at all cause issues during group creation (webcvs needs to be appropriately chown'd, the group needs to exist already). -- Sylvain
