Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(12)

Issue 11479043: Leaderboard for median review time

Can't Edit
Can't Publish+Mail
Start Review
Created:
12 years, 3 months ago by hlynson
Modified:
12 years, 3 months ago
Reviewers:
M-A
CC:
codereview-list_googlegroups.com
Visibility:
Public.

Description

Leaderboard for median review time

Patch Set 1 #

Total comments: 7
Unified diffs Side-by-side diffs Delta from patch set Stats (+395 lines, -0 lines) Patch
M codereview/urls.py View 1 chunk +1 line, -0 lines 0 comments Download
M codereview/views.py View 2 chunks +5 lines, -0 lines 3 comments Download
M settings.py View 1 chunk +1 line, -0 lines 1 comment Download
A static/startfont/FONTLOG.txt View 1 chunk +69 lines, -0 lines 0 comments Download
A static/startfont/LICENSE.txt View 1 chunk +94 lines, -0 lines 0 comments Download
A static/startfont/PressStart2P.ttf View Binary file 0 comments Download
A static/top-score-style.css View 1 chunk +94 lines, -0 lines 0 comments Download
A static/topstyle.css View 1 chunk +61 lines, -0 lines 0 comments Download
A templates/top.html View 1 chunk +70 lines, -0 lines 3 comments Download

Messages

Total messages: 2
hlynson
12 years, 3 months ago (2013-07-17 22:00:19 UTC) #1
M-A
12 years, 3 months ago (2013-07-18 01:50:25 UTC) #2
So that gives an idea of how the final file layout would look like, without the actual implementation. As we discussed previously, the goal here is to implement a scoring function and use this present the last reviewers in the N days doing at least M reviews, sorted by the score value. Think of gamification to incentive lower review response time. The score value would be defined by the median initial review latency. I had given as the reference implementation _process_issue_latency() in https://chromium.googlesource.com/chromium/tools/depot_tools.git/+/master/my_... as an example. Note that we cannot commit mocks, so in this specific case, the actual python code would have to be implemented. I've still attached a few review comments. https://codereview.appspot.com/11479043/diff/1/codereview/views.py File codereview/views.py (right): https://codereview.appspot.com/11479043/diff/1/codereview/views.py#newcode122 codereview/views.py:122: please remove https://codereview.appspot.com/11479043/diff/1/codereview/views.py#newcode1422 codereview/views.py:1422: Please keep 2 lines between file level symbols, e.g. one additional line here, one additional line after 1425. https://codereview.appspot.com/11479043/diff/1/codereview/views.py#newcode1424 codereview/views.py:1424: return respond(request, 'top.html') So basically, there would be a TODO here to implement the actual code. https://codereview.appspot.com/11479043/diff/1/settings.py File settings.py (right): https://codereview.appspot.com/11479043/diff/1/settings.py#newcode63 settings.py:63: Not needed? https://codereview.appspot.com/11479043/diff/1/templates/top.html File templates/top.html (right): https://codereview.appspot.com/11479043/diff/1/templates/top.html#newcode1 templates/top.html:1: That's interesting, because the rest of Rietveld's UI is quite consistent, but somehow we'd *want* to get this page definitely outstanding in its design. Normally, I would have said that you need to use: {%extends "base.html"%} and then create the remaining below the standard header. See search.html for an example but then the white on black effect would probably not work well. Then you need a proper html page with a doctype. https://codereview.appspot.com/11479043/diff/1/templates/top.html#newcode23 templates/top.html:23: <tr> For the record, we don't commit mocks but that gives an idea. https://codereview.appspot.com/11479043/diff/1/templates/top.html#newcode56 templates/top.html:56: 10 POINTS FOR CQ IN THE PAST 24 HOURS<br> This would have to be updated to the actual calculations involved once coded.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b