Commons, All-and-every-Wikisource, All-and-every-Wiktionary seem to be quite useful. Suggest we add projects for the other distinct communities as well. We seem to have plenty tickets that would qualify for them.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T93486 There should be wikibooks, wikiquote and wikivoyage community projects | |||
| Resolved | Aklapper | T196740 Rename Wikimedia project tags in Phab (#Wikisource; #Wiktionary) to clarify that they are not about language specific instances? |
Event Timeline
Comment Actions
Please see T802 for criteria. I only want to create such projects if there's a committed team looking at tasks associated to these projects.
Comment Actions
Why ? We have dozens of unmaintained extensions that no one is looking after that get a tag.
If the problem is the color and the team character of the other community projects, then I propose we create generic 'wikibooks.org' and 'wikiquote.org' and 'wikivoyage' yellow tag labels.
Comment Actions
Please see my concerns in T802 and (in short:) define a scope and how this helps somebody with her/his work and who is committed to set that tag on tasks and triage them.
When that's sorted out and clear I'm happy to create such projects.
(Also, having dozens of unmaint. projects isn't a great argument to add a few more to them... :)
Comment Actions
I could help maintaining those projects. I have no experience in wikivoyage but I think I could manage to help.
Comment Actions
Any updates here? Is there still an intrest concerning creating these project? In this case I would do this, but I need a update first.
Comment Actions
Just noting as a reminder to prevent forgetting without commenting anything: Wikiversity and Wikispecies haven't been mentioned.
Comment Actions
Some use cases:
- find out config requests/changes related to such project
- find out stuff influencing such projects (typically bugs in extensions, extension set up etc...)
Comment Actions
Re how this helps - see my comment above - whoever is interested in such project (by which I mean Wikibooks sites, Wikiquote sites, etc... not projects in Phab) may need to find relevant info on how is the status quo on other language versions of it...
Re setting the tag - myself (and @Gerardduenas offered himself in T93486#1144382)
Re triaging the tasks - since it is rather tag to group related tasks, it does not need triaging that much, besides now we can turn workboards off. However I can imagine even triaging of such tasks on such workboards (as I've triaged already several tags)
Since I see more pros and supports as well as tokens I am willing to create such projects and do the appropriate tagging.
Comment Actions
Config changes for Wikimedia sites can already be found under Wikimedia-Site-requests. They are usually language / site specific and not on a sister project level, which this task is about.
- find out stuff influencing such projects (typically bugs in extensions, extension set up etc...)
I am worried of adding twelve sister project tags to each and every extension task which will only heavily clutter the interface and create lots of noise for no gain. Because many folks already add those tags incorrectly; see T196740#6008994. I nowadays do not consider this a good idea at all, as I wrote in T802#6270647.
Comment Actions
In general, as I tried to express in T93486#1140230: If interest by a specific group is expressed and that group will maintain the Phabricator project and look at its tasks regularly, that could be an option. But also see T254555#6195459 for an extensive list of links and past conversations about this topic.