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)

CURRENT STATUS: User:^demon said he'd fix it this week (before 2012-07-21, presumably).
 * We fixed the branch, but HEAD is still pointing at the wrong place. Filed ticket in RT for Ryan to fix. ^demon (talk) 12:42, 30 July 2012 (UTC)

Semantic MediaWiki group
repo: extensions/SemanticMediaWiki

A new group named SemanticMediaWiki or SMW-trusted or whatever, next to our existing extension owner group. This group should be able to


 * Merge in stuff of others (but not themselves)
 * Push tags
 * Create branches (and if possible be able to merge their own commits to these)

Initial members:


 * Kghbln
 * Nischayn22
 * Mwjames
 * yaron
 * Foxtrott
 * Daniel Werner
 * Denny Vrandecic

Ideally this group would be manageable (both permission and member wise) by either the extension-SemanticMediaWiki group or both Markus and me. --Jeroen De Dauw (talk) 15:19, 24 July 2012 (UTC)

And a similar group for extensions/SemanticResultFormats with same rights and same initial members.

Comments

 * SMW isn't a WMF extension so I don't see a problem with this. Tychay (talk) 22:57, 24 July 2012 (UTC)
 * Yeah more Semantic people :-] Antoine &#34;hashar&#34; Musso (talk) 08:28, 27 July 2012 (UTC)
 * Why not. Maybe this will reduce the self-merges. --Nikerabbit (talk) 11:26, 1 August 2012 (UTC)
 * Not completely possible right now - We can do the branch creations, review, and tagging. But limiting it to "only people other than yourself" requires some Prolog-writing. There's a commit pending upstream for a "Prolog cookbook" to illustrate how to do this and other things. ^demon (talk) 12:42, 1 August 2012 (UTC)
 * Then please create the stuff without this restriction - if that works in core, it will probably work here as well --Jeroen De Dauw (talk) 18:12, 3 August 2012 (UTC)
 * Will do. It'll take me a little bit to sort all this out properly, but I'll get to it this week. ^demon (talk) 22:47, 6 August 2012 (UTC)

Santhosh for MediaWiki core ownership
Siebrand suggests Santhosh for MediaWiki core ownership.

Jeroen De Dauw for MediaWiki core ownership
And yes, I will only approve stuff of others that I'm qualified to review :) -- Jeroen De Dauw (talk) 18:14, 3 August 2012 (UTC)

DumpHTML
I'd like to become a project owner for mediawiki/extensions/DumpHTML. I'm using it actively at my site (http://spiele.j-crew.de). I just submitted a few changes to unbreak the extension (it has been broken in SVN/Git since several months). My Gerrit username is tbleher. Best regards -- Tbleher (talk) 15:38, 5 August 2012 (UTC)
 * . Aaron (talk) 19:50, 7 August 2012 (UTC)

Requsting admin for UploadWizard and TimedMediaHandler projects
I only aim to +2 the areas that I am qualified to review. thanks --Mdale (talk) 15:08, 6 August 2012 (UTC)

Deployment Branch Access for Ori.livneh
My Gerrit username is Ori.livneh. I intend to only use this to sync the E3Experiments extension to master. I was granted deployment rights in RT: 3325. --Ori.livneh (talk) 21:50, 7 August 2012 (UTC)
 * ✅ Confirmed you already have deploy access, so this group is a no-brainer. ^demon (talk) 17:14, 8 August 2012 (UTC)