The new notifications’ system at translate.wordpress.org

We are developing a new feedback plugin to enable the discussions at translate.wordpress.org.

This pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party will have a notification system, with different situations, related with the users that will be notified:

  • Typo or context request: a user notify a typo in the original stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. (usually in English), or request more information about the context.
  • Question in one language: a user requests some explanation to the reviewer about the translation to one language.
  • A reviewer bulk rejects some stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings..
  • A reviewer rejects one string.

1. translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.

The users will be opt-out by default, so they have to opt-in to receive notifications, at https://translate.wordpress.org/settings/

The discussions will have a link to the settings at the bottom (something similar to text marked text in the next image) to opt-in/opt-out globally or only for the current discussion.

In the replies to a comment, all the users that write in the thread will receive an email.

1.1. Typo or context request

Here we have 2 different situations:

1.1.1. Plugins and themes

The plugin/theme authors will receive an email (Themes: only one email address. Plugins: all the plugin authors.). In the replies, all the users that write in the thread will receive an email. If none of these users is an author, the other authors will receive an email.

1.1.2. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., Patterns, 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. and apps

Some special users (to be determined, we want to get users from the Polyglots community) will receive an email each time a request of this type is sent in a translation of this type (all translations of projects that are neither themes nor plugins). In the replies, all the users that write in the thread will receive an email. If none of these users is a special user, the other special users will receive an email.

1.2. Question in one language

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./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./CLPTECross-locale Project Translation Editor A Cross-Locale Project Translation Editor is an account owned by a plugin or theme author (or the authoring organization), which uses professional translators to localize their product. The cross-locale project translation editor can import/validate strings on a specific project for more than one locale. This role has the same capabilities as a Project Translation Editor over multiple locales instead of one. Cross-Locale Project Translation Editors need to meet a set of criteria before being appointed by General Translation Editors. for this project and 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/ will receive an email. In the replies, if none of these users is a GTE/PTE/CLPTE, all the GTE/PTE/CLPTE for this project and locale will receive an email.

1.3. Bulk rejection

The GTE/PTE/CLPTE can reject all the strings without making any comment, clicking on the “Reject” button on the popover. The translator will receive one email with all the rejected strings and the comment if the GTE/PTE/CLPTE had made a comment.

1.4. Single rejection

The GTE/PTE/CLPTE can reject the string without giving feedback, clicking on the “Reject” button on the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.. The translator will receive one email with the rejected string and the comment if the GTE/PTE/CLPTE had made a comment.

2. Number of notifications

At translate.wordpress.org, we know that some users will receive (not in the first days/months) an significant amount of notifications. Once we release this new functionality, we want to get feedback from the users to know if this situation is happening, and we’re committed to quickly make adjustments where necessary so that the notifications will be useful. In this case, we will talk about developing a dashboard for the users (GTE/PTE/CLPTE/translators) that would allow to say up to date by checking the dashboard instead of receiving notifications.

3. Opt-in and opt-out

All users will be opt-out by default, and they should opt-in to receive notifications, at https://translate.wordpress.org/settings/

We’re concerned about due to the opt-in, many people will initially miss that conversations are going on because they won’t get notified. We’re thinking about how to make people aware of the opt-in possibility and how they’d benefit from it.

  1. A banner on the top explaining that you can opt in. That banner can be closed and won’t show again.
  2. A one-time full screen opt-in screen that can be closed and will never appear again.
  3. Allow opting in with a checkbox when submitting a translation.
  4. Other ideas?

In the footer of all discussions, the user will have some links to opt-in/opt-out in the whole system or only for the current discussion.

Do you have some comments? Please, write them in the comments.

#feedback

Feedback Wanted: 2020 Polyglots Survey Questions

Update!

The scope for leaving feedback is closed now and the team is currently preparing the 2020 Polyglots Survey. Thanks to everyone for helping us out!

Dear Polyglots,

Hope you are all doing well. As you are aware, in the past few weeks we have been quite active with the ‘Translation Day 2020‘ Mini Events across different 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/. We appreciate the input by the locales who have been posting updates of their activities with the community. As planned earlier we are conducting a survey across the community to gather information on the Translation Day initiative. We have created a draft set of questionnaire thanks to @nao, @evarlese, @devinmaeztri & @psmits1567. The document has suggestion/comment option enabled for all.

We request you all to share your feedback to help finalize the questionnaire for the 2020 Polyglots Survey.

#2020-polyglots-survey-questions, #feedback, #survey