Gerrit/Project ownership

__NEWSECTIONLINK__ This page queues individuals' requests to be added to the Gerrit project owner groups for specific Gerrit projects (each of which corresponds to a Git repository). A Gerrit project owner has the power to approve changes for merger into that Gerrit project's master branch, and to veto changes.

"When/how we'll add, remove people from Gerrit project owner groups" has procedural details. Sumana Harihareswara will regularly look at new requests for project owner membership and contact the existing project owners. If the candidate gets zero vetoes and at least one yes from the existing project owners, then we'll approve the candidate. For each new candidate the process shouldn't take more than two weeks, and usually much less.

If your codebase/extension/tool isn't in Gerrit yet, use this form: Git/New repositories

To see the current list of Gerrit project owners for a specific Gerrit project, visit https://gerrit.wikimedia.org/r/#/admin/groups/.

Ownership structure
Example: an extension is named foo.
 * The Gerrit group "foo" should usually be an owner of the Gerrit project "foo."
 * Sometimes, meta-groups will be included in the group. This is for people have ownership over multiple extensions, so you can add/remove members in one place.
 * Rights to the group may be inherited from other groups (Look for a "Rights Inherit From:" in the project access.)

Specific example: the project "mediawiki/extensions/DonationInterface" is owned by group "extension-DonationInterface." This group includes the meta-group "fundraising." Also members of the group "mediawiki" has ownership via "Rights Inherit From: "mediawiki/extensions access"

By keeping the naming convention ("extensions/foo" is owned by group "extension-foo"), it'll make the "automatically setup a repo" process much more scriptable when we hit that bridge.

(Note to Gerrit group creators: remember to check the "Make group visible to all registered users." checkbox and leave the group type as "Internal group" and not LDAP.)

= Requests =

[ Add a request]

UploadWizard - Jeroen De Dauw
Right now I cannot approve stuff submitted by others, while I'm one of the people most familiar with the code of this extension --Jeroen De Dauw (talk) 18:10, 28 May 2012 (UTC)

Comments

 * Makes sense to me. The more eyes we have on the project the less backlog. Tychay (talk) 17:36, 29 May 2012 (UTC)
 * We need more reviewers for this extension. I'll talk to Jeroen a bit more about reviewing standards for it (e.g. how to handle UX issues).--Eloquence (talk) 17:51, 1 June 2012 (UTC)
 * Antoine &#34;hashar&#34; Musso (talk) 18:22, 10 June 2012 (UTC)

Nuke - Jeroen De Dauw
I sort of ended up maintaining nuke somewhere in the last 12 months so I'd be good if I could review and merge changes of others --Jeroen De Dauw (talk) 19:08, 2 June 2012 (UTC)
 * Thanks for maintaining Nuke :-] Antoine &#34;hashar&#34; Musso (talk) 18:22, 10 June 2012 (UTC)

WikimediaIncubator - SPQRobin
I request to be a project owner of the WikimediaIncubator extension (extension page) of which I am the primary developer. I of course won't review&merge my own commits, unless they're simple typo fixes or such. FYI, I was/am already a coder on this wiki. Thanks, SPQRobin (talk) 20:32, 29 May 2012 (UTC)


 * I fully trust SPQRobin :-] Antoine &#34;hashar&#34; Musso (talk) 18:22, 10 June 2012 (UTC)

Editor Engagement (meta-group)
This is a request for a new meta-group to be created for the Editor Engagement and the Editor Engagement Experimentation team (as they will be working on the same extensions). Instead of individually assigning extension access (for things like Page Triage) to each member, we can just request the meta-group be given control (like Fundraising does with the DonationInterface).

Group members:
 * Ryan Kaldari (already in the mediawiki group, but can't hurt)
 * Andrew Garret (already in the mediawiki group, but can't hurt)
 * Benny Situ
 * Ori Livneh
 * Matthias Mullie

This is not a request that the meta-group be given ownership of anything (yet).