Tagging also Collaboration-Team and Community-Tech with the hope that it will interest them. Again, feel free to adjust the tags.

Finally, tagging TCB-Team, German-Community-Wishlist and Community-Wishlist-Survey, because this task is a follow up to T137318.

We have one dashboard for edit conflicts : https://grafana.wikimedia.org/dashboard/db/mediawiki-edit-conflicts
It shows how many conflicts appear, everywhere. @Addshore has also made a patch to differentiate more in which namespace the conflict actually occurs, which should be added to the dashboard soon.

Nice! What is the exact definition of Subject, Talk and Project pages?

In T139019#2429402, @Amire80 wrote:

Nice! What is the exact definition of Subject, Talk and Project pages?

Talk pages are all pages in a talk namespace
Subject pages are all pages that are not in a talk namespace
Project pages are all pages in the project namespace (the namespace id is defined by NS_PROJECT)

The patch that introduced this can be seen at https://gerrit.wikimedia.org/r/#/c/289837/

talk page: every talk page, examples:

• https://de.wikipedia.org/wiki/Diskussion:Haus_Weitmar,
• https://www.wikidata.org/wiki/User_talk:Lydia_Pintscher_(WMDE)
• https://www.mediawiki.org/wiki/Help_talk:OAuth

project page: project subject page namespace

subject page: everything that is not a talk page, so:

• main namespace project pages,
• help pages,
• category pages
• image pages

Please note that "subject page" includes "project page"

Would be nice if we could also gather statistics on 'follow through' though:

1. How often do people just give up, vs have a successful save after an edit conflict
2. Do people accept the 3rd party version, amend the 3rd party version, or overwrite the 3rd party version.

In T139019#2429416, @Lea_WMDE wrote:

Please note that "subject page" includes "project page"

Hmmmm. Project pages come in a lot of varieties. There are probably many more edit conflicts on Village Pumps, Noticeboards and other discussion pages many of which are under the Project namespace than on essays which are not edited much. It would be nice to at least separate the Project namespace from the Subject namespace. If articles and Village Pumps are lumped together, the picture may be not as precise as it should be.

Putting this on our Radar until the project is better defined (right now it's a bit more like a research project than an infrastructure project). I'll also add that we have edit conflicts logged for a sample of 25% of our users via the Schema:Edit event logging instrumentation, I can point you to that data if you're interested.

Hmmph, in context of current edithaton it seems that it would be very nice that in case of edit conflict system would save the revision to log (like Abuse Filter log) or to some special page like sandbox where it could be recovered. It should not be too hard to implemet afaik and this would fix some saddest feelings which users will get from edit conflict and losing the content. (in this case back button didn't save the day)

fyi: @Addshore just updated https://grafana.wikimedia.org/dashboard/db/mediawiki-edit-conflicts to show edit conflicts divided by name spaces. In short: Most edit conflicts appear on "Real Content, Article" pages (ID 0)

The tags removed are more meant to be used for the epic umbrella task regarding the wishes form the wishlists not for concrete requests.

Product Analytics has no plans to work on this, but I'm putting it in the general research backlog to help surface it for other researchers.