Gerrit/Project ownership

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. (Sorry, you must log in to see that list. It's easy to get an account.)

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.

__NEWSECTIONLINK__

= Requests =

[ Add a request]