Every PMC member of a running PMC has a responsibility to keep an eye out for crazy commits. Once this is reflected in the doc, it's good practice for PPMC members.
On Wed, Dec 31, 2014 at 3:56 PM, Ted Dunning <ted.dunn...@gmail.com> wrote: > On Wed, Dec 31, 2014 at 12:27 PM, John D. Ament <johndam...@apache.org> > wrote: > >> On Wed Dec 31 2014 at 2:45:48 PM David Nalley <da...@gnsa.us> wrote: >> >> > 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. >> > >> >> I'm not sure that there will be an issue. It could just be a couple of >> IPMC members being a little more cautious that needed. It's more than >> likely no one's going to care. >> >> To date, we have always told podlings that the initial committers and your >> mentors are the ones who have write access. Now we're saying if you're >> using git, it's any of the 1k + (i might be way off) members of the >> incubator group. >> >> Would it be much harder to create the ldap group up front when the >> podling's created, and shuffle people in/out at graduation? > > > > If it ain't broke ... > > Is there even a problem? I haven't ever heard of it. > > If there isn't a problem, why are you worried about it? --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
