Dario Taraborelli, Steven Walling, James Forrester had a discussion
about how we can make article issues ("needs copyediting", "needs more
references", etc.) more accessible to software like GettingStarted,
Mobile, and VisualEditor.
The categories that some of the templates already use work for simple
cases (such as one language, one project), which is how GettingStarted
currently works. However, different languages have their own categories
and conventions for issue templates. Another issue is that it's not
always clear whether the issue applies to a single section or the
article as a whole. And some templates are used on the article, and
others on talk.
Mobile is moving the article issues to a separate area (with a pointer
to that), which requires identifying which templates identify issues.
An initial solution we discussed, with the goal of making the
GettingStarted extension cross-wiki, is using a Wikidata Q-item to
identify a cross-wiki maintenence category. An example is "Category:All
articles needing copy edit" (
https://www.wikidata.org/wiki/Q8235695).
We also discussed how Wikidata could be used further. They are already
planning on having badges
(
https://www.wikidata.org/wiki/Help:Sitelinks#Badges), which describe
aspects of a page (such as Featured Article), rather than the real-world
concept. This could be extended further to include properties for
issues with that page as well (needs copy-editing: true).
A possible way to populate those Wikidata properties is by adding Lua
calls to existing templates.
We hope this can eventually make possible a lot of interesting ways to
see, work on, and flag article issues.
Matt Flaschen