Page MenuHomePhabricator

Document phabricator user groups in a central place
Open, Needs TriagePublic

Description

For the sake of transperancy and ease user group related dicussions, it would come in really handy if we had a central place on Phab or MediaWiki.org where all relevant group information is documented. There are two types of groups in that sense:

  1. Projects like Trusted-Contributors, acl*Project-Admins , acl*repository-admins, Triagers and #acl*phabricator, #acl*access-policy-approvers and actual Administrators. These groups to actually control access to Phabricator functionality. (It's a mystery to me why some of these projects aren't linked.)
  2. Projects that effectively give access to Phabricator functinality, but not over the actual Phabricator web interface, like acl*userdisable
  3. Some other groups that seemingly give access to confidential and concern the whole development here, like Security, acl*security_team and WMF-NDA.
  4. Some other groups that seem important and give access to… things, I guess (like #acl*releng)
  5. Some more specialized groups that seemingly give access to more specialized confidential stuff like acl*stewards or acl*otrs-admins

While MediaWiki core has a special page that covers this stuff, Phabricator doesn't have an usable automated list like that. Often, there's at least some description what the group is good for, but this sadly isn't always the case or up to date. In other cases, it's that vague that you don't really know more than before you read it. Furthemore, you have to find the given project before you can read it, which isn't really handy either. The only other way than reading project descriptions to get this "who can actually do which things" information is Application, which is in fact meant to provide this information. But as soon as a Custom Policy is in place or a permission is hardcoded in the Wikimedia Phabricator extension, it's preety useless as well.

That's why I propose to create a central place that gives an overview:

  • Which user groups of type 1-4 exist.
  • Link to the associated project(s), if possible
  • A short description of the role they have in administration and development (Any one can be a project admin, but #acl*releng has a kind of narrow focus)
  • What this group can do concretely , no matter if it's by global policy, project membership, or hardcoded in the WMF extension
  • At least in some cases how to join them.

Event Timeline

MGChecker created this task.Sep 4 2018, 9:25 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 4 2018, 9:25 PM

We should turn all of them into acl* (see e.g. T126953) and then https://phabricator.wikimedia.org/project/query/O1eugK19EhOf/#R would basically fix this?

What a group can do concretely and how to join should be in each group project description. No need to duplicate content to a webpage that gets out of sync IMO.

We should turn all of them into acl* (see e.g. T126953) and then https://phabricator.wikimedia.org/project/query/O1eugK19EhOf/#R would basically fix this?

I agree this can be a possible solution as well. By the way, an Admin should set all these project pictures read and these with the default picture to them to lock.

What a group can do concretely and how to join should be in each group project description. No need to duplicate content to a webpage that gets out of sync IMO.

The "should" is the problem here. Clear documentation is missing in some cases, for example for WMF-NDA, Trusted-Contributors and #acl*releng.