I'm taking this task to define with Bitergia what needs to be done.

I think the best solution here is to bring the generic graphs from http://korma.wmflabs.org/browser/gerrit_review_queue.html, which have received a lot more work on words and definitions.

http://korma.wmflabs.org/browser/scr.html could contain all the general graphs and the tables of contributors. "pending" can be substituted by "Backlog of open changesets (monthly snapshots)".

http://korma.wmflabs.org/browser/gerrit_review_queue.html could keep only the ranking of repositories.

A single sentence at the top of the page would refer to the other page, helping users to find the data.

I agree that this is confusing, not just because of the labels, also because of the data. It needs clarification:

80	code reviews waiting for reviewer	162	code reviews waiting for submitter

Other confusing labels listed in the description have gone away. I will remove them from the description for clarity.

This task was part of the June sprint but then slipped off the July sprint. Proposing it for August.

In T97118#1399396, @Qgil wrote:

I agree that this is confusing, not just because of the labels, also because of the data. It needs clarification:

80 code reviews waiting for reviewer 162 code reviews waiting for submitter

These are upstream strings hence I created https://github.com/Bitergia/grimoire-dashboard/issues/1 - once the strings are clearer we can look at the data (preferably in a separate ticket). Same for data in "median time to review in days".

In T97118#1399396, @Qgil wrote:

bring the generic graphs from gerrit_review_queue.html. scr.html could contain all the general graphs and the tables of contributors. "pending" can be substituted by "Backlog of open changesets (monthly snapshots)".

Yes. Comparing both graphs, "Pending reviews" and "New changesets" are extremely similar lines over the last two years.

gerrit_review_queue.html could keep only the ranking of repositories. A single sentence at the top of the page would refer to the other page

Quick attempt in https://github.com/Bitergia/mediawiki-dashboard/pull/60/files

In T97118#1565922, @Aklapper wrote:

These are upstream strings hence I created https://github.com/Bitergia/grimoire-dashboard/issues/1

Upstream comments were reasonable enough that I closed that ticket (hard to find a better word than "Code Review" for the entire process)... @Nemo_bis (as you brought this up originally): If you have better ideas how to rephrase, please join the conversation in the upstream ticket. Thanks.

I already gave a better proposal above.

For example, when a code review process starts, by submission of a proposed change, in a sense the process is "waiting for reviewer"

No, it's waiting for a review. Reviewers may already be provided (e.g. cc'd). Hence I proposed/guessed "commits waiting for reviews" ("commits" can be replaced by "patch", "code" or whatever generic term the dashboard desires to use consistently across the board).

@Nemo_bis: It requires a better word than "Code Review". See and join the conversation in the upstream ticket. Thanks.

My proposal doesn't use the word "code review".

Yeah. But your proposal cannot be used in other concatenated strings. See the upstream ticket, discuss in the upstream ticket. Thanks.

@Dicortazar: https://github.com/Bitergia/mediawiki-dashboard/pull/63

@Aklapper not sure about the impact of this changes, I mean, everything work but makes a bit difficult the maintenance of newer versions of the product. In any case, we're starting the dash from scratch so I guess we can live with this for the following months. We hope to have a newer version by FOSDEM/OSCON

What do you think @Dicortazar?

Merged. Thanks!
I'm going to close this task once it's live on korma.