 Hello, I am Samiero and I am here with Alice Crick. In this video we are going to explain you the new feedback tool that we have implemented at translate.wordpress.org. Why do we develop this tool? This tool was developed because we need to give feedback between the translators and the validators, the GTEs, the PTEs and the CLPTEs. For example, one translator is validating some strings and the translator is not correct. The GTE, for example, can send some feedback to the translator and the translator can improve the translation and get the credit for this work. Okay, so first we are going to explain that you have to obtain to receive the notifications. So you have to go, you need to go to translate.wordpress.org slash settings. And in the button checkbox you have to activate the I want to receive notifications on discussions and then click on the Save Settings button. Okay, now you are going to receive notifications related with the strings you have suggested when translated. And if you are GTE, PTE or CLPTE, then you are going to receive notifications related with the discussions in these strings. Okay, so now that you know that you have to obtain to receive notifications, we are going to explain the single feedback tool. This tool was developed mainly for the validators, for the GTEs, PTEs and CLPTEs. And it makes sense when they are reviewing a suggested translation for a translator. And they can approve, reject or mark as fuzzy a suggested translation. Okay, so we are going to explain how to do this in a suggested translation. If you have a link with a gif feedback element, then you can click there as a validator. And if now if you click on the reject button, the suggested translation is going to be rejected as usual. But now you can click in six items, the style guide, the branding element, the punctuation, grammar, glossary or typo. And these optional types are made to classify the different types of problems that you have done when you are translating. And the validator can add some optional comments. When you have clicked one element or when you have made some comments, you will see that the reject button changes. And now you can see the request changes button. Okay, once you click on this button, you will see that this translation gets a new status, the change requested status. It's not rejected. And now the string is in this new status. The translator will receive a new email saying that the validator has reviewed this string. And you have to make some updates or changes to get this string approved. Okay, you can see that you can filter these new status in the main filter. And when you see the rows in the table, you will see a new color, the blue color, related with the change requested status. Okay, the second item we are going to show is the bulk feedback. This is related with when a validator wants to reject a set of a few strings. So they select using the checkbox in the left column and then select the reject element and click on the apply button. When the validator clicks on this button, she's going to see a new pop-up element with the same items that you see in the Seagal Rejection. And this workflow is the same that we see in the previous element. When you click on one checkbox or when you add some comment in the text area, the reject button is going to change to request button. Request change button. So the workflow will be the same. If you only click in the reject button, this translation is going to be discard. But if you add some feedback and you click on this request changes button, all these strings will be in this new status, in the change requested status. And the translator will receive only a new email with all these strings. Okay, all this information will be shown in the discussion page. Here you can access to this discussion page. In one row you will see a hamburger icon. You can click on this hamburger icon and then you will see a discussion link or a row image to open this discussion link in a new tab. Okay, what you can see in this new discussion page, you can see a filter to filter all the discussions. The discussion is only for your language or the discussion involving a reactant feedback. In each discussion you will see the comment if the validator has made a comment. And the comment reasons if the validator has checked some checkboxes. Okay, at the right you will see a reply button where you can reply to this comment. And you can make a thread, something like this, something like you can see in a forum. Okay, in the same discussion page you can see the translation history. So you can see all the history for this string in this language. And in the third tab you will see the current translation in other languages. For example, in this situation, in this link from site original string, it only has been translated to three languages. Okay, at the bottom all the users of the translation environment can start a new discussion. Why a translator or a critic wants to start a new discussion. We have different motivations. The first is to notify the developer of the plugin theme or the core element that she has found a typo in the source code. So the developer will receive these notifications to improve the original string. Another request is to send a notification, start a discussion, to send a notification to the developer, requesting more contests. Because a lot of translations, originals, doesn't have enough information in the contest. For example, sometimes in the English word, it's the same for the better and for the known, but in some languages the translation is different if the original is unknown or it's a better. And in the third element is to notify to a GTPT or CLPT and to a CPLPT around a question related with this translation in this local. For example, in this form we will send a notification to the GTPTs requesting some explanation around the translation for this original. And you can see at the bottom two links to opt-in or opt-out for the current discussion or for the global notifications. Okay, this will be the new, the main functionality we have implemented in the feedback tool. Okay. Cool, so let's look at the local screen of Translator wordpress.org. So when you are on the language page, you can go into a specific language and then arrive on the translation. Teams page eventually, where you can see the local managers that would be notified if you, for example, submitted a comment to a string in that language. So here you can see a discussion page and the comments that happened on that page. So if I click on the reply button, you can comment here. We also wanted to talk about the reject reasons that can appear. So for example, the glossary, it's important to know that for glossary terms, there are specific translations that you should be using. So you can see them when you hover over here. You can access the whole local glossary if you click up here. Another reject reason is the style guide. So for certain translations that have been, the community has agreed on some certain translations that they want to follow through. So style guides for those translations can be found in the translator's handbook and the glossaries and style guides per locale. And then for each language that has defined a style guide, you can click through to the style guide over there. All right. Finally, I think we wanted to show one tool for GTS to view all the comments that have been made in the language. So for that, you would go to your own locales. I'll go to German here. And here you'll find the discussions link that will take you to a dashboard that shows all the recent discussions that happened in your language. So here you can see the original for which they were made. Who was the author, etc. And if you click on the comment itself, you will arrive at this page. That this comment that was made. So in some cases you might need to intervene or add a comment as a GTE on a thread in order to clarify. This page was made so that you can find those discussions that are happening. Yeah. I think it's important to share with the community that this GTE dashboard are open to all the people. So if you get the link, you can take a look to another locale because we can make all this feedback transparent for the community. For example, if you click on the Galician locale, it's not a Galician GTE, but he can access to all the information and sharing with the Galician translators. Okay, here you can see all the feedback that I shared with the translators. All right. It's okay. I think that's enough. Okay, I'm going to stop the recording.