...once our worst data quality issues like T157898 are sorted out.
Inform to wikitech-l@ and maybe engineering@.
For example mention that stuff like T179240 is possible and link to https://www.mediawiki.org/wiki/Community_metrics for docs. People can provide feedback on the talk page.
...once our worst data quality issues like T157898 are sorted out.
Should those tasks be actual blockers of this one, to make it clear?
I "advertised" it a bit more at the last Hackathon in T194799 but the subtasks listed here won't get fixed this month.
Hence unfortunately punting.
Not happening for Q4/2018 and not soon either: Due to changes to "increase security" and introduction of Hatstall (which does not cover all my use cases) there is currently no way to get a database dump which I've always used to identify accounts which need affiliation updates.
Hence the data will unavoidably become less correct and less reliable until Bitergia provides some API or other access again.
Reference (non-public): https://gitlab.com/Bitergia/c/Wikimedia/support/issues/44
Split the last item into T212009: Allow admins to get a database dump, or some way (REST API?) to review new accounts to set affiliations etc and made it blocking this task
I have no idea how to create criteria when this has been advertised "enough" (=when this task would be resolved). So I'm just closing this task.
There will likely be more announcements coming as we move forward in the next month with tasks under wikimedia.biterg.io which have high or normal priority.