Sam Thanks for the long response, sometimes length beats crispness. Some comments in line, summary of my thoughts towards the end. I will say - I'm glad that it looks like we're aligned with long term goals.
On Sun, Apr 9, 2017 at 1:42 PM Sam Ruby <ru...@intertwingly.net> wrote: > On Sun, Apr 9, 2017 at 11:09 AM, John D. Ament <johndam...@apache.org> > wrote: > > On Sat, Apr 8, 2017 at 2:23 PM Sam Ruby <ru...@intertwingly.net> wrote: > > > >> What's the next step? Can I just work with the infrastructure team to > >> make this happen? Do we need a formal vote? > >> > > Can you clarify what exactly you're going to ask infra to change? I see > > that infra has made a gitbox specific change, I would expect to see a > > incubator-wide change. > > I'm not certain I've got a crisp answer. I'm also not looking to make > any quick changes. See this thread, for example, of prior work along > these lines: https://s.apache.org/75Pb > > For the short term, what I am asking is that since committers are > notified of changes (good!) that the default not be that all IPMC > members are committers for all podling repositories. > > --- > > Longer term, I'm looking to establish a canonical locate for all of > our records, be it LDAP, text files, whatever. If there are multiple > locations of record, find ways to ensure that they are in sync, if > that is at all possible. An example: > > https://whimsy.apache.org/roster/members > > Click twice on status, and you will see a handful of exceptions where > LDAP doesn't match members.txt. These exceptions are intentional. > > Well, yes and no. The discrepancies are because we have to give people a certain access level to work with certain pieces of the shop, and have it tied too tightly with our corporate structure (just from looking at the names). > Separately, I'm trying to make the whimsy roster tool an interface to > find (and over time, change) these records. Note that I said "an > interface", others are possible. > > I'm glad to hear this. There are three changes I'd like to propose to incubator docs (not incubator policy) and the roster tool: 1. http://incubator.apache.org/guides/ppmc.html#Project+Status+Updates - indicate that maintaining roster in these files is DEPRECATED 2. http://incubator.apache.org/guides/ppmc.html#Voting+in+a+new+committer - indicate that additional committers should be added via whimsy 3. The interface itself needs to be able to track committers and PPMC members differently. I've created https://issues.apache.org/jira/browse/WHIMSY-84 to track this need (since all committers == all members, but not all members are on the PPMC) > --- > > More specific to the incubator, I'm proposing that we maintain in LDAP > a list of members in each podling (including mentors) and use that > list to drive everything from phonebook to commit access in gitbox to > who can view what mailing lists in ponymail to JIRA. > > Having a common place to administer the roster for a podling just > seems like a good idea. > > I encourage people to explore https://whimsy.apache.org/roster/ppmc/ > and to update the membership of podlings that they are participating > in. Things should be set up so that if you are in the list for that > podling, you can change that list. Every change made through this > interface will cause an email to be sent to the private list for the > podling, the private list for the incubator, and root@ so that the > infrastructure team is aware of the change. > > If you look at the committer vs PPMC thing, one other item may be to not email private@incubator for new podling committers - its not relevant to us. > - Sam Ruby > > > >> - Sam Ruby > >> > >> On Thu, Apr 6, 2017 at 1:06 AM, Sam Ruby <ru...@intertwingly.net> > wrote: > >> > Background, from https://issues.apache.org/jira/browse/INFRA-13804 > >> > > >> >> With this feedback and review, I believe we're still operating as > >> >> expected. > >> >> > >> >> * Per current policy, IPMC members have commit privileges on all > >> Incubator > >> >> repositories. > >> >> * The above is effected through the use of a private GitHub Team > >> >> * According to users' GitHub preferences, they will Watch new > >> repositories > >> >> * GitHub is sending notifications of changes, per Watch selections > >> >> > >> >> The "answer" here is to Unwatch repositories, as appropriate, and/or > >> >> to alter the GitHub user account preference for auto-Watching new > >> >> repositories. > >> > > >> > > >> > Here's my case: > >> > > >> > I believe that asking all IPMC members that request access to *any* > ASF > >> > github repository to get notification emails on *all* incubator > projects > >> > that participate in the gitbox experiment is unreasonable. > >> > > >> > I believe that asking all IPMC members to individually unwatch each > and > >> > every repository as they are created is unreasonable. > >> > > >> > I believe that asking all IPMC members to uncheck "Automatically > watch" > >> is > >> > unreasonable as it (a) will result in people being notified for new > >> > repositories that they should be watching, and (b) presumes that > people > >> are > >> > not participating/watching in other non-ASF GitHub repositories. > >> > > >> > Accordingly, Since I do believe that it is reasonable for every ASF > >> member > >> > to get email on all ASF repositories that they have commit privileges > >> to, I > >> > am asking that the IPMC revisit the current policy that all IPMC > members > >> > have commit privileges on all Incubator repositories. > >> > > >> > I believe that the alternative is technically feasible: have each > podling > >> > manage a list of committers for that podling: > >> > > >> > https://whimsy.apache.org/roster/ppmc/ > >> > > >> > - Sam Ruby > >> > > >> > > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> > For additional commands, e-mail: general-h...@incubator.apache.org > >> > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
