On 10/1/08 1:02 AM, Jim Grisanzio wrote: > On 10/01/08 04:24, Glynn Foster wrote: > >> On 1/10/2008, at 3:11 AM, Jim Grisanzio wrote: >> >> >>> Also, regarding Contributors to Projects: we currently have it set that >>> Contributors have rights to access all the code repositories of a given >>> Project. However, we feel it's better to give the Leader the ability to >>> assign access on a per-repository basis. This gives an extra level of >>> control. Cool with that change/clarification? >>> >> All projects should have public repositories ideally - with everyone >> achieving read-only rights. Leaders should absolutely be the ones who >> decide whether an individual gets read/write rights. >> >> > > Agree. That's how we have it set up in the new app. But I'm asking if we > want to go another level and give leaders the ability to assign rights > on a per-repository basis. So, you and I are contributors in a project, > and you get access to x-repo and I get access to y-repo. Is that > necessary or desired? Or should all contributors in a project have > access to all repositories in that project? > >
No, I'd like to see leaders have the ability to assign rights on a per-repository basis. It seems like a regression from our current behaviour if all Contributors in a Project have access to all Project repositories. cheers, steve -- stephen lau | stevel at opensolaris.org | www.whacked.net
