Page MenuHomePhabricator

Discussing #Wikimedia-Site-requests after #Wiki-Setup creation
Open, Needs TriagePublic


This task aims to resolve T21986#3546359. Since now membership is only allowed to the subprojects, this can be a problem or annoying for some users.

My proposals:

  • try to manually de-subproject Wiki-Setup and convert it to an independent project if possible, or
  • create more subprojects for Wikimedia-Site-requests for site-requests and extension-setup.

If you have another proposal, feel free to add it.

Ping @mmodell

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 5 2017, 10:36 AM

If we go for the subprojects road, what about the following hierarchy?

If we go with subproject road, I'd suggest instead:

Plus, if they're going to be subprojects, maybe we can just get rid of the Wikimedia prefixes?

  |-- #siteconfig
  |-- #extension-setup
  |-- #site-setup

untangling subprojects is easier said than done. I recently wrote some hacky code to handle moving a subproject tree into another subproject tree but making a subproject into a standalone project is probably not feasible without just deleting it and starting over.

@mmodell So is it possible to delete Wiki-Setup and recreate it as a standalone project? Tasks can be moved to Wikimedia-Site-requests and re-tagged later with the new tag.

Collaboration-Team-Triage seems also, results new member users can't join without asking sysops

@Liuxinyu970226: Isolated and manually set parent project permissions are unrelated to the topic of this very task (subprojects and membership invocations). For your topic, please file a separate task under Collaboration-Team-Triage to revert and . There are no "sysops" involved in this at all. Thanks!