While someone could always study this, it has lost the significance it had in 2016. The conflict around the visual editor has largely disappeared and as a result there is not much value to investigating how users choose between the two editors.

Hive is on its way out; Presto and Spark have better date functions.

I don't think there's any real value in this, particularly since we are now moving to a world of temporary accounts where it will be easy to analyze return times of non-permanent editors without a very complex mechanism like this.

Declining this task for now.

removing inactive project tag.

Declined since different aspects are already covered (or planned to be as part of other efforts).

I don't know when it was fixed, but it seems to work now. Viewing https://m.mediawiki.org/wiki/Reading/Web/Chores?trackdebug=1#/editor/0 shows me that a mf.schemaEditAttemptStep.init and other events are logged.

This would be nice to do, but we haven't managed to do it in the past five years and might not in the next five years either. Also, this task doesn't have any important information.

These schemas will probably be retired when schema migrate to MEP

Reflecting reality.

Hi, this ticket was resolved five years ago. Please file new tickets for new requests - thanks a lot! :)

Could someone please update the statistics? Can I do it myself? Where? Toolserver VPS?

Proposing to decline - nobody following up, no active project tag, task seems not to happen.

Removing task assignee due to inactivity, as this open task has been assigned to the same person for more than two years (see the emails sent to the task assignee on Oct27 and Nov23). Please assign this task to yourself again if you still realistically [plan to] work on this task - it would be welcome.
(See https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup for tips how to best manage your individual work in Phabricator.)

Thanks – that’s great! I created the calculation in JavaScript but did not have an R version yet.

@Jan_Dittrich https://www.rdocumentation.org/packages/REAT/versions/3.0.2/topics/hoover

I calculated the hoover index for some contribution metrics recently and it was rather easy to do using a table with the columns edit count | count of accounts with this edit count which has somewhat between 100 and 1000 rows. Hoover also seems to be rather easy to understand, working without area-under-the-curve and varies between 0 (all equal) and 1 (maximum unequal).

@nshahquinn-wmf: Any progress / news to share, or info how someone could help? Thanks!

@nshahquinn-wmf: Any progress / news to share, or info how someone could help? Thanks!

Thanks :)

Ok, deployed in prod; should be ready for train deployment next week.

Change 618535 merged by Ottomata:
[operations/deployment-charts@master] eventgate-main - bump image version to get schema mediawiki/revision/create/1.1.0

Change 618535 had a related patch set uploaded (by Ottomata; owner: Ottomata):
[operations/deployment-charts@master] eventgate-main - bump image version to get schema mediawiki/revision/create/1.1.0

Tested in beta, it works! I just _manually_ reverted some wikitext via an edit:

Change 618531 merged by Ottomata:
[eventgate-wikimedia@master] blubber.yaml - bump schema repo versions to get revision/create/1.1.0

Change 617477 merged by jenkins-bot:
[mediawiki/extensions/EventBus@master] Revision create event: add revert-related fields