Jesús Amieiro 9:27 pm on January 11, 2022
Tags: weekly meetings ( 408 )

Agenda: Weekly Polyglots Chat – Jan. 12, 2022 (07:00 UTC)

Here’s the agenda for our weekly chat.

This meeting will be held at Wednesday, January 12, 2021, 7:00 GMT in the #polyglots channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

Welcomes.
Weekly localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ stats.
Releases:
- WordPress 5.8.3 Security Release.
- WordPress 5.9 RC 2.
Help & feedback wanted:
- Feedback functionality. Screenshots. We have some screenshots to show to get feedback.
- Feedback functionality. URLs. We share the proposal format for the feedback URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org, to get feedback.
FYI:
Open floor / Achievement.

If you have any additions to the agenda, please share them in the comments.

Feedback functionality. Screenshots

Here I show the current work we are making to the feedback functionality. The translation environment will have a new link to “create a new discussion” and to see the history in all languages. I show this translating the WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. to Spanish.

We are deliberately adding this on a separate page for now, but we try to integrate it better when it’s well tested.

In the new page, the user has this information:

The project.
The original stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings..
The translation.
A tab with the discussion.
A tab with the translation history in the current language.
The translation to other localesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/.
The total number of comments.
A link to show all the comments.
A link to show the comments only in the current language.

In the next image, you can see the comments in “es” and “fr” languages. The user can make a comment and can reply to another comment.

In the second tab, the user can see the translation history in the current language.

And in the third tab, the user can see the translations in other locales.

All this works with plurals and languages with more than one plural:

Feedback functionality. URL

Currently, we are proposing a scheme like this https://wp.test/projects/wp-plugins/akismet/stable/9686/gl/default/, where:

“wp-plugins/akismet/stable” is the project and subproject: the project slug.
“9686” is the string ID in the “translate_originals” table: the original id.
“gl” is the discussion locale.
“default” is the set. More information here.

The new proposed URL is (currently don’t work) https://translate.wordpress.org/projects/$project_slug/$original_id/$locale/$set

#weekly-meetings

Naoko Takano 6:24 am on January 12, 2022

Very excited to see the discussion feature in action! Thanks for the easy-to-understand overview of the status.

Here’s my feedback, but please note these are not super critical to the main functions. Looks like what you have will work well as the first phase for us to test out.

1. Submenu

I was a little confused about the submenu (marked 7, 8, 9 in your screenshot). How about something like this instead to make it clear? (Show Spanish comments only on the first view, and show other localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ comments only instead of “all”)

2. Translation Permalinks

Both in the “History” tab and comment metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress., how about linking to the translation? Or at least link to the “Translation History” list from the “History” tab. Otherwise, we’ll have to go back to the context menu to pull this information.

Alternatively, if we could approve/reject from the “History” tab and comments, that might be even better. But I’m not sure how this plays into the future plan for integrating this feature.

3. Comment Indication

This is also something nice-to-have or for the future. Would it be possible to indicate if there are comments for the stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings.? This can also speed up the process for reviewers and translation contributors, as they don’t have to click through to see if any comments exist.
- Jesús Amieiro 2:54 pm on January 14, 2022
  
  Thank you for the comments @nao. They are very interesting. I have added each section to our roadmap to determine if we are going to implement it and when: now or in the future. Feel free to add more comments with new ideas.
Erica Varlese 9:18 pm on January 12, 2022
This looks amazing, @amieiro! I’m so excited to see the progress 😀

I just wanted to +1 @nao‘s comment about adding a link back to the original. I think it will be helpful for making revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. to easily navigate back to where you can edit the stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings..

All of my questions/feedback are really minor, and probably more appropriate for a later time – but I’ll share anyway!
- For both the Other LocalesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ tab and the Discussion view, it may be useful to filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output./search for other locales. Selfishly, I often reference es_ES and gl_ES when translating, so that would be a helpful enhancement.
- I know you’re still exploring how notifications will work. Will it be possible to @mention any WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ profile in the comments? I’m thinking of cases where you may want to easily include other GTEs or even developers in the discussion.
- Likewise, I’m wondering about moderation. Will PTEs, GTEs, and global mentors be able to moderate discussions? It might be helpful to take some practices from the Support team for adding flags, notes, etc. (or use what’s already available in forum profiles).
- Jesús Amieiro 2:55 pm on January 14, 2022
  
  Thank you for the comments @evarlese. They are very interesting. I have added each section to our roadmap to determine if we are going to implement it and when: now or in the future. Feel free to add more comments with new ideas.
Fernando Tellado 4:30 pm on January 20, 2022
Really nice @amieiro

I would like to know how PTEs or GTEs are going to be noticed about new discussions placed in the translations chains.

I have some questions about how the workflow should be:
- First, notification (I don’t know where or how) to PTEs?
- If there isn’t any PTEProject Translation Editor A Project Translation Editor (often referred to as PTE) is a person, who has access to validate strings on a specific project (for example BuddyPress, WooCommerce or Twenty Fourteen) for one specific locale. A project translation editor can approve strings that are added by translation contributors. Per project translation, editors are appointed by a general translation editor after a request by the project author or by the contributors themselves. then, notification to GTEs? (how and where?)
- If is there any PTE but nobody answers the discussion, what happens?
- Will be any notification icon to see at a glance if is there any discussion pending (with no answer, answered or anything else)?
Thank you 🙂
- Jesús Amieiro 9:21 pm on January 20, 2022
  Hi, @fernandot
  
  In the first version, we are going to send an email notification with each discussion:
  - If the project has a PTEProject Translation Editor A Project Translation Editor (often referred to as PTE) is a person, who has access to validate strings on a specific project (for example BuddyPress, WooCommerce or Twenty Fourteen) for one specific locale. A project translation editor can approve strings that are added by translation contributors. Per project translation, editors are appointed by a general translation editor after a request by the project author or by the contributors themselves., we will send it to the PTE.
  - If the project has not a PTE, we will send it to all the GTEGeneral Translation Editor A General Translation Editor (often referred to as GTE) is a person, who has global access to validate strings on all projects for a specific locale..
  In the future, if the PTE/GTE receive a lot of emails, we will think about a different approach: a daily email (or with different periodicity) or a dashboard where you can see all the notifications.
  
  The PTE is the responsible for receiving and addressing the queries, but could be that a PTE doesn’t respond to the discussion. Could be interesting that the GTE receive all the emails, including the projects with a PTE, to avoid this situation?
  
  It would be interesting to have an icon showing that there is a discussion pending for this stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. in your language. I add it to our roadmap.
  
  Thank you very much for your feedback.
Angelika Reisiger 9:37 am on February 9, 2022

Great, after 6 years (and earlier polyglots asked for a comment option) this comes back to topic.
We had discussed this en detail there:

https://github.com/GlotPress/GlotPress-WP/issues/209
https://github.com/GlotPress/GlotPress-WP/issues/324
https://github.com/GlotPress/GlotPress-WP/issues/852
https://github.com/GlotPress/GlotPress-WP/issues/323#issuecomment-195243378
https://github.com/GlotPress/GlotPress-WP/issues/323#issuecomment-195285569

We have tons of waiting stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings., but fewer and fewer active PTEs and GTEs.
Where are we going to find the time to discuss countless strings on an extra page?

How are we supposed to notice when a stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. has been commented?

Very good suggestions were made at the time, see this one there:
https://github.com/GlotPress/GlotPress-WP/issues/324#issuecomment-384315517

A default preset of feedbacks in the form of checkboxes would save a lot of time and should become the main feature of the comment function, plus an additional field that can be filled in freely.
Angelika Reisiger 9:57 am on February 9, 2022
```
In the future, if the PTE/GTE receive a lot of emails, we will think about a different approach: a daily email (or with different periodicity) or a dashboard where you can see all the notifications.
```
Me as GTEGeneral Translation Editor A General Translation Editor (often referred to as GTE) is a person, who has global access to validate strings on all projects for a specific locale. would extremely dislike to receive every day an email with hundreds of comments. With comments for rejected stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings., that other PTEs have rejected.

+ 1 👍 for dashboard with all the notifications.
- Presskopp 11:25 am on February 9, 2022
  
  + 1 👍 for a Dashboard and making E-Mails optional.
- aThemeArt 6:21 pm on August 30, 2022
  
  👍
Angelika Reisiger 10:15 am on February 9, 2022

I wrote a comment here that is waiting for approval because it contains a lot of URLs (to GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ threads via the feedback function).

I wrote the same comment there and it has since been approved (sorry for the double posting, but I don’t know where it fits better).

https://make.wordpress.org/polyglots/2022/02/08/call-for-early-testers-glotpress-feedback-feature/#comment-293763

So that the suggestions from the Github threads at that time are not lost, I point it out here again.