-
Notifications
You must be signed in to change notification settings - Fork 220
Open
Labels
Description
Hi,
Currently, there are 3 available informations when choosing the rank:
- author estimation: counts for 1 vote, totally isolated from the 2 other data
- users avg: ceiled value
- PU avg: not entirely sure about this one... I believe it's rounded?
problem is:
With "some" users (namely, ZED. Essentially...) who are litterally trolling the rank suggestions, those 3 datas often lead these days to a "what the hell should I do?" because those values do not mean anything anymore because of the roundings.
Suggested solution :
A way to see the partition of the votes would allow a pretty good idea about what to do (histogram: number of votes against kyu rank). Or even, about what to not do and so wait for other users giving feedback (because approval with 3 2 votes isn't a good thing, imo).
Possible implementation : a link in the edit panel that would lead to another page with the related diagrams.
cheers
Steffan153
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
Steffan153 commentedon Sep 11, 2019
Good idea. On some katas I've approved so far, it took me a long time to make up my mind what to rank it 😕
Blind4Basics commentedon Sep 11, 2019
(note: the histograms are better than "not rounded values", which would still give a lot of weight to "free electrons votes")
dinglemouse2250 commentedon Sep 11, 2019
FYI - here's an idea I suggested a long time ago #1247 which is kind of in this same area...
Voileexperiments commentedon Sep 12, 2019
But first, the ranks that can be approved should not be locked by author estimated rank and the lower of user average/power user average, because the people who can approve them either obeys them or ignores them entirely anyway. Also it's only enforced at the front-end - sending values not available to the back-end during approval will still work as expected.
Blind4Basics commentedon Sep 28, 2019
I guess that's you, Voile?
EDIT:
Nice... :/ I spent time rewritting the mess that was the description, and now, I cannot publish it. I'll bet on your endpoint game, Voile. I'll try assessing the rank, then (to 3 kyu, then, since no other choice...)
-> doesn't work either... ("server timed out"). Don't know if it's really a server problem or if something is messed up because of the rank.
Voileexperiments commentedon Sep 29, 2019
No idea, why don't you check the revisions page? It shows who approved the kata or changed the ranking.
Blind4Basics commentedon Sep 29, 2019
right...! x)
and here you are:

hobovsky commentedon Mar 3, 2025
Update: rank votes can be now checked with API. There is no UI for this in the platform, but can be done with user script: