Page MenuHomePhabricator

Create #Repo-Ownership-Approvers
Closed, ResolvedPublic

Description

#Repo-Ownership-Approvers

Members of this group can grant Gerrit repository ownership permissions to other users.

Visible: Public

Editable: #Repo-Ownership-Approvers

Joinable: #Repo-Ownership-Approvers

The initial members of the project will be https://gerrit.wikimedia.org/r/#/admin/groups/119,members

Today it doesn't really matter who is member of this project. The list is closed for identification purposes only. Maybe this group will be more useful as such when we migrate from Gerrit to Differential.

Event Timeline

Qgil claimed this task.
Qgil raised the priority of this task from to Medium.
Qgil updated the task description. (Show Details)
Qgil added a project: Project-Admins.
Qgil added subscribers: MZMcBride, Ricordisamoa, QChris and 10 others.

I will wait for a second opinion here.

#Repository-Ownership-Approvers sounds good to me.

But I would love to hear from some of the currently 8 folks in that Gerrit group (CCed now on this task) if they are interested and willing to follow a workflow in Phabricator, by watching this project once it has been created in Phabricator, or if they would like to keep the current workflow for any reasons I am not aware of.

Also wondering if there is existing on-wiki documentation that needs updating, apart from replacing https://www.mediawiki.org/wiki/Gerrit/Project_ownership#Requests ?

Opinions about moving the process from MediaWiki to Phabricator are welcome at the parent task, T86639: Migrate Gerrit project ownership request system (+2 rights) to Phabricator.

Note Gerrit Administrators are allowed to create repositories as well https://gerrit.wikimedia.org/r/#/admin/groups/1,members

I never ever honored any request on the wiki page https://www.mediawiki.org/wiki/Gerrit/Project_ownership#Requests , merely because I hate wikitext based workflow. I have created a few that were requested either personally over IRC or via Bugzilla.

A mistake we did when creating Gerrit was lack of peer reviewed process to create repositories and changes user rights. We end up with a few people having the responsibility and no real way of tracking what is being changed nor wether the resulting configuration is consistent.

I would love to see repo creations and rights to be tracked via peer review / git as configuration changes. Then you only need a couple of folks with the actual rights to +2 (and thus merge).

I agree with Antoine. I, for example, have rights to create repositories and that's really great for me and not so great for the people that I'm supposed to help through a process I'm not familiar with.

Project created: #repository-ownership-approvers