Didnt we previously agree we should use our self hosted git instance as primary because it would make lives easier for sheriffs?
On 27 June 2014 09:04, Ed Morley <[email protected]> wrote: > (If you are not on the mozilla-b2g owners team, you can stop reading now > :-)) > > The mozilla-b2g Github organisation currently has 38 members of the owners > team: > https://github.com/orgs/mozilla-b2g/teams/owners > > Recently the main mozilla organisation culled their list of owners for > security reasons. > > I believe we should do the same for mozilla-b2g, not just for security, > but also to reduce the number of people who can (and do) accidentally push > to gaia when the sheriffs have 'closed' the tree by revoking PUSH > permissions to !owners (it is not possible to revoke for owners & we have > no other way of closing the tree, due to B2G's use of a third party service > for which we cannot create custom git hooks). > > Unless you regularly have a need to create/move repositories (those in > releng responsible for B2G branching) or some other owner-only ability (eg > closing the trees, so sheriffs), being a member of the 'Chefs' group should > be sufficient. > > If people fall into both the "need owner permissions" and "regularly > commit to gaia" bucket, then they will need to check the mailing lists > and/or https://github.com/mozilla-b2g/gaia/settings/collaboration to see > if access has been revoked to the Chefs/Cooks groups before pushing - or > else use two github accounts. > > Is there someone with more context as to who needs permissions who is able > and willing to own this for the sheriffs (so we don't get stung each time > the tree is closed and people push anyway)? > > Many thanks, > > Ed > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g >
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
