Bryce, JFYI:
Gitlab has a couple more levels of access, e.g. Guest and Reporter (in addition to Developer, Master and Owner) status. Reporter status means they can manage bugs, but don't have access to the code.
Guest means they can look at things that someone allowed them to look at. It's kind of an 'honorary' or non-developing, non-bug-managing member.
More info here: https://gitlab.com/help/user/permissions.md
i.e. if someone does not fulfill the 2-patch-rule, they could still become a project member - if project policy wants to make use of the different levels that are available. (btw. I think I do have push access..., not that I'd ever make use of it, of course.)
Also, there's a distinction between group members and project members.
E.g. I am a member with Developer status of the Inkscape group, which contains a couple of projects, that can have their own, additional members. The higher level of access status decides which permissions one has - e.g. I have at least developer status for any sub-project, and have master status on some sub-projects.
So policy would need to decide whether to add new Inkscape code developers just to the /inkscape/inkscape project, or to the whole /inkscape group, giving them access also to translations, website, manual and possible other subprojects (not a bad thing, as long as critical stuff, like the branches the website pulls from, are still specially protected - and I don't think that vice versa is a good idea - i.e. someone makes two contributions to po files, and gets developer access to everything... so perhaps having the same level for all would be more consistent).
Maren
Am 14.06.2017 um 01:35 schrieb Bryce Harrington:
On Tue, Jun 13, 2017 at 02:17:37PM -0400, Martin Owens wrote:
Dear Bug hunters and Developers,
GitLab contact Connor Shea has asked us what we might need in the GitLab issues tracker to consider using it as our bug tracker instead of launchpad.
After talking with su_v and bryce on IRC, I've drafted this possible email detailing some of the issues:
Not particular to bug tracking exactly, but it would be nice if when people request access to the devel team, if it could automatically check that they fulfil the two patch rule.
Like, maybe, the emails sent to the admins could append a list of recent patches that were accepted and landed in trunk from the developee. It'd save some time having to verify they satisfy the requirements.
Bryce
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel