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 always be an owner of the Gerrit project "foo." Sometimes, we will use a meta-group when people have ownership over multiple extensions (so you can add/remove members in one place).

For example, the project "mediawiki/extensions/DonationInterface" is owned by group "extension-DonationInterface." This group includes the meta-group "fundraising."

By keeping that naming convention, 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]

Matthias Mullie (Article Feedback Tool v5)
Matthias Mullie needs ownership rights on Article Feedback Tool v5 because he is slated to take over the project from OmniTi in July and replace Roan as primary deployer for this project needs merge rights to do this). This would free up Roan's time for VisualEditor (in the short term) and school (in the long term).

--Tychay (talk) 19:20, 24 May 2012 (UTC)

Comments

 * Fabrice Florin (talk) 20:27, 24 May 2012 (UTC) For what it's worth, you have my vote! Matthias has already proven himself to be an excellent developer, highly qualified and very responsive. Plus, he's a really nice guy! Who could ask for more? ;o)
 * Asking the current Gerrit project owners for their thoughts; will process this request on Tuesday, 29 May. Sumana Harihareswara, Wikimedia Foundation Engineering Community Manager (talk) 04:04, 25 May 2012 (UTC)
 * I'm OK with this in the understanding that Matthias won't review his own code, someone else will still need to review that. --Catrope (talk) 11:27, 25 May 2012 (UTC)
 * I hope not! I reminded Matthias just in case.. ;-) Tychay (talk)

MediaWiki core - MaxSem
Request for Max Semenik (MaxSem) to be part of the "mediawiki" Gerrit group; he's being given deployment cluster access, I believe, so this makes sense. Code samples. Sumana Harihareswara, Wikimedia Foundation Engineering Community Manager (talk) 20:38, 25 May 2012 (UTC)
 * Support - No reason I can think of not to give it to him. ^demon (talk) 20:42, 25 May 2012 (UTC)
 * -- Platonides (talk) 17:09, 28 May 2012 (UTC)

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)