On Wed, Dec 31, 2014 at 2:40 PM, John D. Ament <johndam...@apache.org> wrote: > On Wed Dec 31 2014 at 2:24:36 PM David Nalley <da...@gnsa.us> wrote: > >> On Wed, Dec 31, 2014 at 11:59 AM, John D. Ament <johndam...@apache.org> >> wrote: >> > Hi, >> > >> > So something Jan and I ran into on the infra list, does anyone know >> > definitively what the access rights given to a podling's git repo are, if >> > they request one (instead of a svn directory)? >> > >> > If nothing else we should document it somewhere on the incubator site >> > indicating the permission sets for both svn and git. My current >> > understanding is that svn sites are typically incubator wide, svn repos >> are >> > confined to a specific list, and git repos are incubator wide. The git >> one >> > in particular because we don't create ldap groups for podlings and I've >> > heard that we only do groups in git (not individual lists). >> > >> >> git is tied to LDAP, and all podling repos are writable by anyone in >> the incubator LDAP group. (there are no podling LDAP groups) >> > > Got it thanks. I'll update the docs to reflect this as the permission > scheme. > > And here I think will come in Jan's bigger question - do we really want all > podling committers to be able to commit to all other podlings? >
My question is: What problem are you trying to solve? And has it really proven to be a problem? I don't think anyone has abused their ability to commit to all projects, and it's been this way as long as git has been available. --David --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
