Greetings from @davinci.witness!

_{Thanks to @pab.ink for making this fantastic drawing!}

This is report #19 of the translation activity conducted in collaboration with @utopian-io (you can find the previous report HERE).

This week we see the effects of some of the limits we imposed to decrease the number of contributions below 100. We did this to avoid that many contributions would not receive the incentives from utopian. We wanted to front-run the change in voting behavior by utopian and at least in Week #19 we managed to keep the situation stable. However, we don't know yet about the current week, there are still several contributions pending and this tells us we need to take further action.

We do not want to impose more limits because we would like to maintain high activity and we think we can find maneuvering room in the scores we get from the questionnaires. Judging by your feedback there are things that need to be improved in questionnaire, I don't think it's much about rewards or about the incentives the translators get, but it's more about fairness. Teams want to be treated equally and a source of frustration for many was to see the LM assigning different difficulty scores for the same projects.
The new questionnaire will address this issue, we will also increase the number of questions and the choices available to make the score more granular. Overall, we need to push for an increase in the number of words translated per post and add more penalties for translators that make mistakes, for formatting issues and for plagiarism. Currently it's relatively easy to obtain high scores. Although we are happy to see high quality translations, we need to be more realistic about the scores. We need to tweak the questionnaire to generate scores that reflect more fairly the quality and the effort placed in the contribution.
This is a consolidation period, we will need to make several adjustments and some contributions will inevitably go unvoted. We will also be working on improving the internal communication to make sure all the LM are aware of the changes as we implement them. In the meantime it would be a good habit to read and interact on these reports. This is by far one of the most direct ways to convey information.

Below you can find the stats for Week #19:

October 21 2018 -:- October 27 2018

Instruction for a correct application:

The application post should be posted from your Steem profile. In the post you should tell us what are your qualifications and why you should be considered as a translator or Language Manager (LM). Moreover, it is mandatory to post a link to a voice recording of you speaking your native language and English. You can find more details on this post: https://steemit.com/witness-update/@davinci.witness/davinci-witness-update-6-utopian-io-translation-rewards-are-coming-back. Also, your post should contain the tag davinci-application. And after you drop a link to your application post in this room: #job-application-room on Davinci's discord server.

Please note:

Your translation contribution post is as important as the translation itself. Through that post you describe your activity to the Steem community (and to your followers). Please let's avoid copy/paste types of posts and try to make these posts as engaging as possible. We understand that it's not an easy task to morph a report into something interesting to read but we will also try to provide you with some tools that will help you in this task.

---

Additional Charts

Scores assigned by our LMs

1	2	3	4	5

Averages of the scores assigned to the translations by our LMs, the points vary from a minimum of 1 to a maximum of 4 for the following categories:

1. formatting, language and overall presentation of the post
2. overall value of this contribution on the open source community
3. total volume of the translated text
4. overall difficulty rate of the translated text (this value depends on the type of text to be translated)
5. rate the semantic accuracy of the translated text

In the first chart, there is overall average score assigned per week.
In the second chart, there is average time taken to review a translation. Calculated between the date and time of publication of the post and the comment left by the LM. It is not intended as time spent in the review, but only after how long the post is reviewed.

---

Stay tuned for the next report!

The aim of this report was to provide complete transparency
about the development of this project.