osm-fr / osmose-frontend

Part of osmose that shows results on the website http://osmose.openstreetmap.fr
GNU General Public License v3.0
41 stars 38 forks source link

Leaderboard for most active users #382

Open brawer opened 2 years ago

brawer commented 2 years ago

On behalf of mapathons, projects of the month, and similar events, could Osmose display a leaderboard that shows how many Osmose issues were handled (either fixed or marked as false positive) by what user? The leaderboard would display the top 50 users given issue class, geographic region and time span.

For example, a query like /leaderboard?start_date=2022-05-01&end_date=2022-05-31&region=switzerland&class=31601 would display the top 50 users who handled Osmose issues for bad lane values in Switzerland during May 2022. If no value got passed for class, it would accumulate the counts across all issue classes. This would be super helpful when organizing events to fix OSM data problems.

I assume that privacy is not an issue here because the data could technically also get extracted from the OSM history (although only with a lot of effort) and because OSM nicknames are anonymous.

frodrigo commented 2 years ago

Currently the Osmose frontend do not store closed issues, and even more link to the contributor closing it.

Current contributors stats is doable. A page like this existed before, but was not ported when the last code migration occur. It has some kind of shaming and bad reaction from people listed in it.

brawer commented 2 years ago

some kind of shaming

Could the leaderbord display the most active fixers instead of the worst perpetrators? In that case, there would be no shame to appear on the leaderboard, rather the opposite. Basically, the proposal would be to count and display the users who’ve most clicked the red or green buttons in here:

image

Respectively the corresponding buttons in the iD editor:

image
Famlam commented 1 year ago

I'm afraid users would abuse such a feature, i.e. marking random issues as fixed/false positives without actually fixing it (or fixing it poorly), only to end as high as possible in the stats