John D. Ament wrote on 4/6/17 6:57 AM: > This solution describes one of the many reasons I feel the incubator itself > is broken. We're trying to rewrite policy, as a means to work around some > awkward setup sitting around, instead of just treating podlings as regular > projects, with some restrictions in place.
+1. The restrictions on podlings are in terms of branding and mentoring. We don't *need* any technical restrictions, other than those which make maintaining the branding & mentoring easier. > Create something in ldap that is org.apache.incubator.$podling. When > secretary processes new accounts, they're being added into this area, > instead of the incubator area. > > IPMC members have access to execute something that adds committers to > podlings. It could be a special ou for mentors, which VP incubator has > access to. IPMC members should be able to fill out a form to request commit for any podling. Mentors should be automatically added to podlings they are working on, to make it seamless if they do need to help out (especially on websites). > This has to net less maintenance from infra to make podlings more like TLPs. > > The one thing Sam misses in this email, there is a way to fix your > notification scheme easily in github - > https://github.com/settings/notifications - uncheck "Automatically Watch > Repositories" Yes, but I don't want to *have* to set this to just opt-out of getting stuck on all new podlings. 8-) > > John > > On Thu, Apr 6, 2017 at 1:07 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 >> >> > -- - Shane https://www.apache.org/foundation/marks/resources --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
