Some communities are maintaining on-wiki lists of bugs-tasks. They could use Phabricator projects instead, reducing maintenance effort and improving their direct feedback to the contributors capable of solving those tasks.
Imagine tags like #Wikisource-radar, #German-Radar or #MediaWiki-Stakeholders-Radar to identify tasks that an organized community has decided that matter to them over the rest. Projects with plenty of tasks in their backlogs would be influenced when one task or two get several of these Radar tags. Smaller projects might welcome when one of these tags lands in one of their open tasks.
These tags would have optional boards, with optional names of columns, and the maintainers of these tags could use them to fine tune the relevance of that task for their community, i.e. "Top 5 requests", "Blocking local development", "Usual complaints by newcomers"...
There are some on-wiki lists of tasks maintained by communities aligned to a family project or a language. These lists are good to bring Phabricator (and before Bugzilla) information closer to editors and potential technical contributors active at a local level. This approach has two main problems:
- It is quite tedious to maintain, as it requires a lot of copy & paste, and back&forth when the tasks are updated/fixed.
- Quite often the authors of the tasks and/or the maintainers of the projects related are unaware that a certain task is especially relevant to a community.
In Bugzilla, some projects tried to fix this problem by creating a tracking task blocked by tasks identified as relevant. Now we can solve this problem in a more elegant way, creating tags. Since tags are projects and projects have boards, the maintainers of these tags could even organize the tasks in their own ways for better followup and feedback.
- A proliferation of different tags, many of them becoming unmaintained after an initial phase of enthusiasm. We might want to request a minimum of 2-3 contributors clearly active in their projects - even better if they have some history here in Phabicator as well.
- A flood of tags caused by massive tagging. Inflation would bring devaluation. We might want to set a basic principle of being selective when using these tags, to keep their strength. For instance, no more than 50 open tasks per tag.
- Just anybody could request the creation of a tag and use this to push a personal agenda, without an actual link to the community the tag is supposed to represent. We might need to require proof of community consensus for the creation of the tag.
Current lists (links welcome, thanks @He7d3r for yours)
- de:Wikipedia:Umfragen/Technische Wünsche
- pt:Wikipédia:Histórico de configurações
- pt:Wikilivros:Histórico de configurações
- T37925: [DO NOT USE. Please use the Wikisource project] Wikisource related bugs and enhancements (tracking)
- T58295: [DO NOT USE] Malayalam Wiki Projects (tracking) [superseded by #Malayalam-Sites]
- T76447: [DO NOT USE] Wiktionnaire / fr.wiktionary bugs (tracking) [superseded by #wiktionary-fr]