We have Documentation tag.
Then we have tasks tagged MediaWiki-Documentation.
And they are also tagged with Documentation.
Seems it would make a sense to have a single tag for tasks about documentation only.
We have Documentation tag.
Then we have tasks tagged MediaWiki-Documentation.
And they are also tagged with Documentation.
Seems it would make a sense to have a single tag for tasks about documentation only.
I would look at it going the other wise and look at removing the generic #documentation tag usage where possible.
People that are interested in watching relevant tasks (example: #pywikibot documentation/#mediawiki documentation) will want to watch the smaller more dedicated projects compared the generic #documentation tag that for an example has ~450 tags alone in its incoming/triage column and a lot of these would be irreverent for these people and would generate unwanted emails for people that want to watch etc.
I would start by de-activating {H11}, There isn't any need to double tag these tasks. and keep #documentation for the tasks that don't fall under the dedicated documentation subtasks.
If people want to see all documentation tasks they could always do a search etc.
In response to @Peachey88 's proposal: the opposite could just as well be said.
Those who are interested in working on specific project documentation could easily search for the two tags (say, Pywikibot and Documentation ).
I usually prefer combining two generic tags in a search and taking the intersection, instead of creating gazillions of very specialized tags.
This. Please. Dear lord. Can we clean up the unmanageable pile of #MediaWiki-SomeRandomThing
That works for search, yes. But is it possible to subscribe to an intersection of tags? Right now I can subscribe to #MediaWiki-SomeRandomThing and get emails for all those tasks - is it still possible once the tag is split?
I agree with @Legoktm, I'm interested in Pywikibot-Documentation, but I don't want to be flooded by tasks from MediaWiki-Documentation. Maybe the Documentation is the one we should close in favor of the more specific two (but first analyze its content)
Unless we could have separate workboards and members/watchers under Documentation, this should be declined. The same for #rfc, I18n, etc.
Maybe simple MediaWiki-Documentation should be considered to be merged into Documentation instead?
See T142345#3655080. (High-level: We can likely repeat any on-wiki category discussions communities already had (having "Female writer" vs "Female" × "Writer").
As a small and non-definitive gesture towards considering this, I've disabled the herald rule that hard-enforced addition of Documentation to other projects. (H11)
The difference between MediaWiki-Categories + Documentation search and MediaWiki-Categories + MediaWiki-Documentation search seems too little to me. You could consider to merge MediaWiki-Documentation and Documentation as pywikibot does not need Documentation at all.
I removed the Pywikibot part as we have no interest in merging. The discussion about mediawiki and documentation can continue here.
With a Herald rule. Not super intuitive though.
At a minumum the project descriptions should make it clear which to use when.