Making WordPress.org

Opened 7 years ago

Closed 5 years ago

Last modified 5 years ago

#2290 closed enhancement (fixed)

Progress stats for the top 100 plugins and themes

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

Description

In light of the next big goal for the Polyglots team being translating the top 100 Plugins and themes on the directory, I'd like to ask that we get an easy way to track progress on that.

We already have https://translate.wordpress.org/stats for 10 projects and to monitor the overall number of waiting strings, perhaps we can find a way to reuse this for the plugins and themes.

To avoid endless columns of projects perhaps we can load 10 projects at a time (some sort of project pagination/filter on top)?

Attachments (1)

ticket 2290 proposed locations for links.png (64.1 KB) - added by tobifjellner 5 years ago.

Download all attachments as: .zip

Change History (30)

#1 @dimadin
7 years ago

I would rather get a top 100 per locale to see are there big differences from the main list.

#2 @samuelsidler
7 years ago

In talking to @petya today, we're going to do this:

  1. Create a per-locale page with the top 100 plugins (and a separate one for themes) and their current status (all four sub-projects, I assume?) in percentage, using the same/similar design as the main stats page. Probably should be at https://translate.wordpress.org/locale/[locale-code]/stats/plugins/ and one for themes with the root of /stats/ going to plugins. (But anywhere else works too.)
  2. On the main stats page (translate.wordpress.org/stats), show a count, per locale, of how many of the top 100 plugins have been translated (aka, have a language pack).

We'll also need a script that we can run once a month or so that gives an overview of progress across the top 100 plugins/themes across all locales (for administrative purposes). But that can be a different ticket.

#3 follow-up: @casiepa
7 years ago

@samuelsidler I would love to see this directly on wordpress.org ! Can I add the requests that I tried to solve while building my http://wp-info.org/plugin-top120/?lang=Bulgarian ?

1) Can I get in 1 page the 'most used' plugins? I used the 'active installs' as a baseline. I don't have the installs per locale, but I think the idea of overall active installs is fine.

2) I'm a GTE, what are the waiting strings for my locale on the most used plugins? Check the waiting column, click on it, validate!

3) I want to help translate in my language, where do I start? Well, choose a plugin or theme that you use on your own site, if all are already translated, start from my top120.

4) We have a contributor day and are looking for some useful plugins to translate with not that many strings inside, but where there is still work to do. Well, here you go.

5) I want to focus on stable only, what is there still to do in the most used plugins? If the last column still has figures, then you know there is work to do.

Some other remarks:
People using the overview are much less interested in the readme...
And for the percentage... I prefer the real number of strings like we already receive on #polyglots, but then you move away from the other standards you have on overview pages.
Monthly? Any possibility to have weekly stats, because Polyglots is already having weekly stats and updates.

As always, I'm available to explain and share my ideas :-)
Pascal.

#4 in reply to: ↑ 3 @samuelsidler
7 years ago

Replying to casiepa:

@samuelsidler I would love to see this directly on wordpress.org ! Can I add the requests that I tried to solve while building my http://wp-info.org/plugin-top120/?lang=Bulgarian ?

1) Can I get in 1 page the 'most used' plugins? I used the 'active installs' as a baseline. I don't have the installs per locale, but I think the idea of overall active installs is fine.

I'm not sure what you're asking for here that's not already in this ticket. Each locale will have an overview of the top 100 plugins – by usage – and their current status.

2) I'm a GTE, what are the waiting strings for my locale on the most used plugins? Check the waiting column, click on it, validate!

We can add a Waiting column like the main stats page has.

3) I want to help translate in my language, where do I start? Well, choose a plugin or theme that you use on your own site, if all are already translated, start from my top120.

This sounds like UX work that needs to be done and is out of scope of this ticket. If you want to work on a GlotPress plugin that changes the UX to improve contributions, we could work on that in a separate ticket.

4) We have a contributor day and are looking for some useful plugins to translate with not that many strings inside, but where there is still work to do. Well, here you go.

Another UX idea that's out of scope for this ticket.

5) I want to focus on stable only, what is there still to do in the most used plugins? If the last column still has figures, then you know there is work to do.

It's not always best to focus on stable only, but regardless we'll be showing columns (just like the current stats page) and allow sorting by those columns.

People using the overview are much less interested in the readme...

That may be, but from a UX perspective, the readme is incredibly important. We want users to be able to discover plugins in their language and discover plugins that have been translated into their language (note the difference).

And for the percentage... I prefer the real number of strings like we already receive on #polyglots, but then you move away from the other standards you have on overview pages.

We'll stick with the the percentage because it works better overall, with Waiting strings being a total number.

Monthly? Any possibility to have weekly stats, because Polyglots is already having weekly stats and updates.

Running this script is not great on the server. It doesn't scale well. Individual locales can monitor their status, but I don't think the overall status is something that needs to be frequently reported. Is there a reason you think this number is important on a weekly basis? I couldn't come up with one other than "because it's interesting sometimes."

#5 @ocean90
7 years ago

#1677 was marked as a duplicate.

#6 @dd32
5 years ago

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

#7 @dd32
5 years ago

In 8249:

Translate: Add a per-locale stats page which lists plugin/theme translation status.

Notes:

  • This is currently not linked from anywhere.
  • The number displayed (250) may be lowered, currently only ~245 theme projects and ~200 plugin projects are displayed due to filtering.
  • Plugins displays based on Code (Dev+Stable) + Readme (Dev+Stable).

Examples:

See #2290.

#8 @dd32
5 years ago

In 8256:

Translate: Update the plugin translate stats overview to only use the Code project, as many locales do not translate the entire readme which results in a skewed stats page.

A toggle may be included in the future, or a separate view for Readme status.

See #2290.

#9 @casiepa
5 years ago

@dd32 Great work! Thanks a lot.

I will redirect people from our current top120 plugins and themes pages to the ones on translate.wordpress.org . So according to me the top 200 would be awesome (no need to go deeper)

Comparing http://wp-info.org/plugin-top120/?lang=German with https://translate.wordpress.org/locale/de/default/stats/plugins I would like to ask if you could consider:
1) 'Untranslated' refers to Stable only, could this somewhere be mentioned in the title?
2) Translators will use this page also to keep the top plugins fully translated BEFORE they get moved into production, so an extra column with the Untranslated in Dev (next to Stable) would be helpful

Again, thanks a lot!
Pascal.

This ticket was mentioned in Slack in #polyglots-events by casiepa. View the logs.


5 years ago

#11 follow-up: @tobifjellner
5 years ago

You can save some space by combining fuzzy+waiting into one column. (That might be useful, having in mind the comment above from @casiepa )

#12 in reply to: ↑ 11 @casiepa
5 years ago

+1 !

Replying to tobifjellner:

You can save some space by combining fuzzy+waiting into one column. (That might be useful, having in mind the comment above from @casiepa )

#13 @nilovelez
5 years ago

It might sound silly, but a row number column would be really helpful.

On es_ES we use stats a lot to encourage volunteers, like in "top100 done, let's go for top120!!"

It could be added to the tooltip of the first column "#1 - 5,000,000 active installs", that would not add unnecessary clutter.

https://lh3.googleusercontent.com/-Ae7lifdFi3A/XGb9hbsk9fI/AAAAAAACISY/fXV3_BEeP-kTH_zXW7s_ICN1YWNBktL_ACL0BGAYYCw/h262/2019-02-15.png

Last edited 5 years ago by nilovelez (previous) (diff)

#14 follow-up: @nilovelez
5 years ago

In the theme view, it would be nice to have a toggle to switch the order between "Number of active installs" and "Popularity", using the order used in https://wordpress.org/themes/browse/popular/

#15 in reply to: ↑ 14 ; follow-up: @dd32
5 years ago

Replying to casiepa:

1) 'Untranslated' refers to Stable only, could this somewhere be mentioned in the title?

Sure, a preamble intro is needed on these pages, maybe someone could suggest one?

2) Translators will use this page also to keep the top plugins fully translated BEFORE they get moved into production, so an extra column with the Untranslated in Dev (next to Stable) would be helpful

I guess adding Stable / Dev / Readme (Stable+Dev) as separate columns could be useful, personally I don't like the idea though as it makes it much harder to glance over.
It also doesn't help that many plugins no longer make use of the Development option, as they've moved away from using plugins.svn as the primary development location.
I think this is probably the only use-case that's come up where having an option/toggle/whatever to switch to using only-stable(or development when no stable), Development (when it exists), and Readme (Of both Stable and Development combined) is reasonable, but probably as separate views.

I don't consider it a priority to add though, and that might have to wait until another iteration on it (As it's not as straight forward to add)

Replying to tobifjellner:

You can save some space by combining fuzzy+waiting into one column. (That might be useful, having in mind the comment above from @casiepa )

Having seen the resulting lisst, I tend to agree and will make that happen. Turns out there was a bug though, and Fuzzy wasn't being shown at all anyway :)

Replying to nilovelez:

It might sound silly, but a row number column would be really helpful.
It could be added to the tooltip of the first column "#1 - 5,000,000 active installs", that would not add unnecessary clutter.

While that's easy enough to add, I didn't include it as I didn't want it to become the go-to location for plugin/theme authors to go to say "See, I'm #30!" - which is unfortunately something that happens.
I also don't see the value in including the Active Install count anymore, so might remove that for the time being.

Replying to nilovelez:

In the theme view, it would be nice to have a toggle to switch the order between "Number of active installs" and "Popularity", using the order used in https://wordpress.org/themes/browse/popular/

For consistency with the plugins view, I don't think adding an option to use the popularity value here is very useful, it'd also result in a constantly changing list that's mostly not that useful.
If many locales start to make a huge dent into these lists, we can consider adding alternate filters or pagination.

#16 @casiepa
5 years ago

@dd32

I guess adding Stable / Dev / Readme (Stable+Dev) as separate columns could be useful, personally I don't like the idea though as it makes it much harder to glance over.

We have discussed this over the years with several translators in #polyglots . The reason for the creation of http://wp-info.org/plugin-top120/ was because a lot of locales want to be ready with translation before the plugin gets into global roll out. If translations are not done before, non_US users get plugins that are only half in their own language.
Readme is for most of the languages not translated at all and kept in English as this is mainly useful for the admin that installs the plugin on a site. So if that column is hidden at first, that's not an issue.

It also doesn't help that many plugins no longer make use of the Development option, as they've moved away from using plugins.svn as the primary development location.

We have contacted some of the main players there. Some of them have already opened the dev section where they put at least some time before all strings so we can start translating, others have it on their todo list. In the top120, about 5% are not localized, but most of the others have both stable and dev.

So, having dev strings there seems to me the first thing to tackle. All other things like toggles and more info can indeed be seen in the next round for sure.

But thanks again for this great addition to translate.wordpress.org . You are now at the top of the polyglots list of most admired persons :-)

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


5 years ago

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


5 years ago

#19 @pedromendonca
5 years ago

Hi, as mentioned in #4191, all these tables sould have sorting icons on the table header cells.

For the specific cases of Top 100 pages, should also be made clear that is being sorted by Active Instalations and not by Plugin/Theme name.

Last edited 5 years ago by SergeyBiryukov (previous) (diff)

#20 follow-up: @garrett-eclipse
5 years ago

I'm loving these new stat pages thanks everyone for the work.
I just opened #4193 to flag the 'Scroll to xx_XX' buttons on the new Top 100 pages should be removed.
Thanks

#21 in reply to: ↑ 20 @garrett-eclipse
5 years ago

Replying to garrett-eclipse:

I'm loving these new stat pages thanks everyone for the work.
I just opened #4193 to flag the 'Scroll to xx_XX' buttons on the new Top 100 pages should be removed.
Thanks

Ignore me, sorry this was a GlotDict feature so moved the issue there.

#22 @tobifjellner
5 years ago

Great job. Thanks, @dd32
I guess there's more or less only one thing left: namely to put links to these great pages in a good spot.

I think the link to "Stats for most popular Themes" / "Stats for most popular plugins" could be added as a banner on
https://translate.wordpress.org/locale/[locale code]/default/wp-themes and https://translate.wordpress.org/locale/[locale code]/default/wp-plugins respectively.

See Attached image: ticket 2290 proposed locations for links.png

This ticket was mentioned in Slack in #meta by tobifjellner. View the logs.


5 years ago

#24 @garrett-eclipse
5 years ago

Along with the placements @tobifjellner mentioned, I wonder if providing the references on the Theme and Plugin localized directories would assist users in picking plugins/themes that are already translated in their language.
https://de.wordpress.org/themes/
https://de.wordpress.org/plugins/
Placing the stats there would help users choose themes/plugins that are already translated in their locale.

#25 follow-up: @tobifjellner
5 years ago

@garrett-eclipse Hmm. Interesting idea with regards to to themes.
Probably should be a separate ticket, though, since it's about functionality inside the themes catalog.

When it comes to plugins, nobody searches for just "any popular plugin". They want specific functions. But yes, when I search, say, for https://sv.wordpress.org/plugins/search/transients (i.e. within the Swedish plugin directory), it would be wonderful to see details about translation status for the matches. But that would be a different ticket.

#26 in reply to: ↑ 25 @garrett-eclipse
5 years ago

Replying to tobifjellner:

@garrett-eclipse Hmm. Interesting idea with regards to to themes.
Probably should be a separate ticket, though, since it's about functionality inside the themes catalog.

When it comes to plugins, nobody searches for just "any popular plugin". They want specific functions. But yes, when I search, say, for https://sv.wordpress.org/plugins/search/transients (i.e. within the Swedish plugin directory), it would be wonderful to see details about translation status for the matches. But that would be a different ticket.

Thanks @tobifjellner as suggested I spawned some additional tickets for my thoughts;
#4271 - Place a reference to the new locale stats for Theme/Plugin on the Theme/Plugin directories.
#4272 - Add translation status to the Plugin/Theme tiles in the directories to indicate how translated for the current locale the item is
#4270 - Add a localized filter/view to Plugin and Theme directories
#4273 - The Plugin/Theme name column on the new stat pages should link to the localized page

#27 @ocean90
5 years ago

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

In 8499:

Translate: Add link for per-locale plugin/theme stats to the filter header.

Fixes #2290.

#28 @garrett-eclipse
5 years ago

Thanks @ocean90 just checked out the dropdown. It looks good and works nicely, cheers

#29 in reply to: ↑ 15 @zolikonta
5 years ago

Replying to dd32:

Turns out there was a bug though, and Fuzzy wasn't being shown at all anyway :)

It still shows zeros in every row in the fuzzy column for me. Is this what I think it is, or did you say something else about this was fixed?

Note: See TracTickets for help on using tickets.