Making WordPress.org

Opened 9 years ago

Closed 6 years ago

#1202 closed enhancement (fixed)

Stats: Create an i18n dashboard

Reported by: samuelsidler's profile samuelsidler Owned by: dd32's profile dd32
Milestone: Priority: low
Component: Translate Site & Plugins Keywords:
Cc:

Description

Currently, there's not an easy way to see the status of translations of important projects. For example, we have no way of seeing if the top n languages (by downloads/usage) have translated all of Core, Rosetta, and Apps. We should create one so the polyglots team can better track the status of locales.

One thing we could include in this dashboard, to help polyglot team leads, is a way to copy the usernames of specific teams, in a comma-separated list. I have some ideas for how this might look design-wise, but we'd only want to show it to leads (or admins) not everyone.

Attachments (2)

mockup.png (50.3 KB) - added by samuelsidler 9 years ago.
meta-1202.links-to-projects.patch (1.5 KB) - added by SergeyBiryukov 9 years ago.

Download all attachments as: .zip

Change History (33)

@samuelsidler
9 years ago

This ticket was mentioned in Slack in #meta-i18n by sam. View the logs.


9 years ago

#2 @ramiy
9 years ago

I like this idea!

#3 @dd32
9 years ago

In 1852:
Translate: Add the first iteration of a general stats dashboard available at https://translate.wordpress.org/stats
See #1202

Last edited 9 years ago by dd32 (previous) (diff)

#4 @dd32
9 years ago

In 1854:

Translate: Translation stats: Don't round to the nearest integer for sorting purposes, give it 3 decimal places to allow for those close-to-but-not-yet-100% to slot in below the 100%'ers.
See #1202

This ticket was mentioned in Slack in #meta-i18n by dd32. View the logs.


9 years ago

#6 @dd32
9 years ago

In 1859:

Translate: Stats overview: Update the styles.
Props sam.
See #1202

#7 @dd32
9 years ago

In 1861:

Translate: Stats Overview: We don't want to count inactive sub projects in the percentage calculations - wp/4.2.x/twentyten exists for example, but is hidden in the UI.

See #1202

#8 follow-up: @ramiy
9 years ago

Also, it would be helpful if the links will open in new tabs.

#9 in reply to: ↑ 8 @samuelsidler
9 years ago

Replying to ramiy:

Also, it would be helpful if the links will open in new tabs.

I don't really like this idea. If someone wants to open links in new tabs, they can use a cmd/ctrl modifier.

#10 @DrewAPicture
9 years ago

  • Summary changed from Create a i18n dashboard to Create an i18n dashboard

#11 follow-up: @samuelsidler
9 years ago

Left on this ticket:

  • Add in the admin checkbox / contact feature
  • Add a Forums column (to the right of Plugin Dir)
  • Add a final column for "Waiting" with the total number of waiting strings across all projects

Separately, we should file these tickets:

  • Stats: Allow sorting by column (similar to Wikipedia tables)
  • Stats: Link to stats page from homepage
  • Stats: General design improvements (column headings / padding / etc)

#12 @dd32
9 years ago

In 1885:

Translate: Stats overview: Add the Forums and Waiting projects to the table. The Waiting column shows the number of strings waiting.
I attempted to add the Colour coding to the waiting list, but a straight percentage calculation isn't the best option, it needs to use a logarithemtric scale, on a percentage scale those with 500 waiting strings look great compared to 2000.
See #1202

#13 follow-up: @dd32
9 years ago

Add a final column for "Waiting" with the total number of waiting strings across all projects

Clarification required - Total waiting strings over the projects listed here, or over all the locales projects?
The above commit counts them for the displayed projects (and their sub projects).

#14 @dd32
9 years ago

In 1886:

Translate: Stats overview: Add colour coding to the waiting column (100% = 0 string, 0% = 500 strings or more), expand the size of the table to fit the extra 2 columns.

Props Sam for styles!
See #1202

#15 @dd32
9 years ago

In 1887:

Translate: Bump stylesheet version (and always load over SSL).
see #1202

#16 @samuelsidler
9 years ago

Since comment:11, @dd32 knocked out a couple of items (see above) and @ocean90 committed the sorting feature. Left for this ticket is just this piece: Add in the admin checkbox / contact feature.

#17 in reply to: ↑ 13 ; follow-up: @netweb
9 years ago

Replying to dd32:

Add a final column for "Waiting" with the total number of waiting strings across all projects

Should another column be added for the fuzzy count? Or merge the fuzzy count with warnings as done elsewhere?

#18 in reply to: ↑ 17 ; follow-up: @dd32
9 years ago

Replying to netweb:

Replying to dd32:

Add a final column for "Waiting" with the total number of waiting strings across all projects

Should another column be added for the fuzzy count? Or merge the fuzzy count with warnings as done elsewhere?

It's the count of strings available in the Waiting Tab for the projects listed on this screen, as such, it includes both Waiting and Fuzzy. Waiting is simply the Project/tab name.

Replying to dd32:

Add a final column for "Waiting" with the total number of waiting strings across all projects

Clarification required - Total waiting strings over the projects listed here, or over all the locales projects?
The above commit counts them for the displayed projects (and their sub projects).

@samuelsidler got back to me and said it should be the waiting count of all projects, however currently it's only for the projects displayed on the screen. Expanding to have the count of all projects in the Waiting tab is possible, but I was running into performance barriers.

#19 in reply to: ↑ 18 @netweb
9 years ago

Replying to dd32:

Replying to netweb:

Replying to dd32:

Add a final column for "Waiting" with the total number of waiting strings across all projects

Should another column be added for the fuzzy count? Or merge the fuzzy count with warnings as done elsewhere?

It's the count of strings available in the Waiting Tab for the projects listed on this screen, as such, it includes both Waiting and Fuzzy. Waiting is simply the Project/tab name.

I thought this is what we _should_ do though based on the following is why I asked:

Currently https://translate.wordpress.org/stats en_AU shows the waiting count for en_AU as 0 strings waiting, this should be 4 based on the current fuzzy count https://translate.wordpress.org/locale/en-au here.

#20 follow-up: @dd32
9 years ago

Currently https://translate.wordpress.org/stats en_AU shows the waiting count for en_AU as 0 strings waiting, this should be 4 based on the current fuzzy count https://translate.wordpress.org/locale/en-au here.

Yes.. as per the first, and second parts of my comment. It's currently operating correctly, but not ideal as it doesn't include strings for projects not listed on the stats screen.

#21 in reply to: ↑ 20 @netweb
9 years ago

Replying to dd32:

Currently https://translate.wordpress.org/stats en_AU shows the waiting count for en_AU as 0 strings waiting, this should be 4 based on the current fuzzy count https://translate.wordpress.org/locale/en-au here.

Yes.. as per the first, and second parts of my comment. It's currently operating correctly, but not ideal as it doesn't include strings for projects not listed on the stats screen.

Hehehe, my bad, thanks ;)

#22 @samuelsidler
9 years ago

Oh, I remembered one more thing we should do on this ticket:

  • Make link works from /stats or /stats/ (or pick one and redirect the other)

Right now links in the table are broken if you navigate to /stats/ because GlotPress. We should either redirect trailing slashes, settle on using trailing slashes everywhere across translate.wordpress.org (my favorite!), or simply fix links so that you can visit either with or without the trailing slash.

#23 in reply to: ↑ 11 @samuelsidler
9 years ago

  • Summary changed from Create an i18n dashboard to Stats: Create an i18n dashboard

Replying to samuelsidler:

  • Stats: General design improvements (column headings / padding / etc)

Spun this off into #1238.

This ticket was mentioned in Slack in #meta-i18n by sam. View the logs.


8 years ago

This ticket was mentioned in Slack in #polyglots by petya. View the logs.


8 years ago

#26 follow-ups: @Savione
8 years ago

For me as a GTE for sk_SK it would be great to have the possibility to:

  1. see the usernames of all the people, who contributed to the translation of a specific project
  2. to be able to contact them (in order to notify them about changes or to make a meeting). Maybe to send an email through some contact form.

#27 in reply to: ↑ 26 @samuelsidler
8 years ago

Replying to Savione:

For me as a GTE for sk_SK it would be great to have the possibility to:

  1. see the usernames of all the people, who contributed to the translation of a specific project

Can you file a new ticket for this? It might be something we need to do in GlotPress, but we can consider doing it just for translate.wordpress.org, if it makes sense.

  1. to be able to contact them (in order to notify them about changes or to make a meeting). Maybe to send an email through some contact form.

Somewhat related to #1162, but somewhat different too. I think giving a way for GTEs to contact the entire team is a good idea, but it should be something we do via Rosetta. Can you file a ticket for that, too? (In the "International Sites" component.) :)

Fwiw, neither of these items make sense for the stats dashboard, but could both be interesting separately.

#28 in reply to: ↑ 26 @SergeyBiryukov
8 years ago

see the usernames of all the people, who contributed to the translation of a specific project

Related: #1044

#29 @dd32
8 years ago

In 2055:

Translate: Include Plugins/Themes waiting/fuzzy strings in the Waiting column on https://translate.wordpress.org/stats
See #1202

#30 @obenland
6 years ago

  • Owner set to dd32
  • Status changed from new to assigned

Is there anything left to do here?

#31 @dd32
6 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

No action in 3 years, i'm going to call it fixed.

If there's anything missing, please open new tickets for it! Thanks!

Note: See TracTickets for help on using tickets.