We will be moving all event_comment values that were sent with app edits to Special:Tags, will track new tags in this ticket once we hammer out a consolidated set of appropriate tags.

Cross-referencing: there was recently a short discussion about these edit summaries on English Wikipedia too, with a couple of responses from WMF folks: https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(miscellaneous)/Archive_77#Why_is_"%23article-section-source-editor"_appearing_in_edit_summaries%3F

Following are new values for Android and iOS app edits revision tags (Special:Tags).

Next step tickets (to be created by me and @Seddon) will be linked here:

1. Task for adding tags to mobile apps extension. Tags will be registered everywhere (all wikis/langs)
2. Task for replacing/migrating within the iOS and Android app
3. Data validation/QA

In the idea of unifying user experience, when implementing the tags, you should reuse the format Growth uses, with similar pages to point users to.

Hey @Trizek-WMF do you mean the text format having spaces instead of dashes? We are using dashes like the Editing Team (see Edit Check). We can also point folks to a page.

I like the idea that all the proposed tags start with a common prefix, making it easier for filter writers to treat them as a group. I'm not that familiar with tag usage, but I'm wondering if there's some written standard for how this should be done. And if not, then maybe this is a good time to formally establish one so all future projects like this can just do it the same way instead of inventing their own way.

I see two broad categories of tags emerging; those that represent user behaviors (mw-replace, mw-rollback, etc), and those that represent essentially internal markers for UX experiments, such as the ones proposed here. A little bit of planning now to nail down syntax, semantics, and namespaces will probably yield good dividends later.

I maintain SPI tools (https://toolhub.wikimedia.org/tools/toolforge-spi-tools). One of the features I have is showing a matrix of which sockpuppet suspects used which tags. It's a bit of a mess because there's so many tags and most of them aren't relevant for my purpose. If there was a way I could easily filter out whole sets of tags to ignore, that would be useful. Having some sort of standardized convention for how tag names are constructed would help with that.

In T360164#9820803, @JTannerWMF wrote:

Hey @Trizek-WMF do you mean the text format having spaces instead of dashes? We are using dashes like the Editing Team (see Edit Check). We can also point folks to a page.

No, it's not a matter of dashes or spaces; just using tags with a link that clearly goes to a proper explanation page for experienced users. GRowth does this for suggested images: https://www.mediawiki.org/wiki/Help:Growth/Tools/Newcomer_Tasks#s-image

In T360164#9821116, @RoySmith wrote:

I like the idea that all the proposed tags start with a common prefix, making it easier for filter writers to treat them as a group. I'm not that familiar with tag usage, but I'm wondering if there's some written standard for how this should be done. And if not, then maybe this is a good time to formally establish one so all future projects like this can just do it the same way instead of inventing their own way.

I see two broad categories of tags emerging; those that represent user behaviors (mw-replace, mw-rollback, etc), and those that represent essentially internal markers for UX experiments, such as the ones proposed here. A little bit of planning now to nail down syntax, semantics, and namespaces will probably yield good dividends later.

I maintain SPI tools (https://toolhub.wikimedia.org/tools/toolforge-spi-tools). One of the features I have is showing a matrix of which sockpuppet suspects used which tags. It's a bit of a mess because there's so many tags and most of them aren't relevant for my purpose. If there was a way I could easily filter out whole sets of tags to ignore, that would be useful. Having some sort of standardized convention for how tag names are constructed would help with that.

In a certain way, the standardization work started.

For Suggested images, Growth highlights the audience with Newcomer task and then the task type with Suggested: add images. We did it It allows patrollers to have several options, as they can either select all Newcomers tasks, or specific tasks. We did it for each tag: https://www.mediawiki.org/wiki/Help:Growth/Tools/Newcomer_Tasks.

I'm currently working on changing Editing's tagging as well, for Edit Check. The goal is to follow the same idea of granularity of tagging and to provide more meta information to the other users.