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]

Move branch svg-chart to be new master, get rid of old master (orgcharts)
master has never been used for orgcharts, because A) by the time it was on Gerrit, I had moved to a separate branch for all development and B) the master branch won't merge easily with the svg-chart branch anymore. I've totally abandoned anything in master, so I'd just like svg-chart to be moved over, if possible. MarkTraceur (talk) 21:49, 18 June 2012 (UTC)

Tpt: ProofreadPage
I have been working on ProofreadPage for the past few months in order to clean the code and add new features required by Wikisource contributors. Here is my activity on Gerrit:. Sumanah has told me that it would be a good idea to ask for the ownership in order to save time in the process of merging code. Tpt (talk) 23:39, 15 July 2012 (UTC)
 * Aaron (talk) 21:45, 18 July 2012 (UTC)
 * Even if my opinion shouldn't have a lot of weight because I'm not active enough in the development of this extension. I just want to say, that I follow carefully Tpt's work on the extension and that I think that giving ownership to him is a good idea. Zaran (talk) 22:26, 18 July 2012 (UTC)

TimedMediaHandler / MwEmbedSupport
I would need +2 rights for TMH and MwEmbedSupport to review and fix code while in SF. My Gerrit username is J

https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/TimedMediaHandler https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/MwEmbedSupport


 * Suport. TMH will receive additional security review from Chris Steipp. Giving J +2 on it will help to keep things moving.--Eloquence (talk) 17:26, 17 July 2012 (UTC)
 * Antoine &#34;hashar&#34; Musso (talk) 09:55, 18 July 2012 (UTC)

OfflineImportLexicon

 * Gerrit username: liaveja
 * Gerrit project: mediawiki/extensions/OfflineImportLexicon

--LiaVeja (talk) 15:36, 18 July 2012 (UTC)