Greetings from Hive account@davinci.witness!

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

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

The week #20 was a bad week for many of us. Utopian changed the behavior of the voting bot and as a result now our category has a smaller fraction of the VP allocated to vote our contributions. Overall there were 49 contributions affected.
As you can see from the graph below, many of these were good contributions that despite receiving a respectable score were skipped. As you know, every time a translator is affected also the DaVinci team is affected the same way. So we wanted to apologize to all the users that did a good job and that were not voted, but also we wanted to thank all the users that showed a positive attitude despite the difficult period.

What caused all the issues in Week #20?

Many blame the questionnaire, but we had the same questionnaire in week# 17 or 18 yet we were able to support more than 100 weekly contributions. To be realistic, I think many of the incentives we were distributing were very generous so by changing the questionnaire we can definitely distribute the incentives better and still be fair to everyone. But we will need to take into account that the supports we will receive in future are lower than what we were used to so we must adapt to the new situation.

	We had 27 posts voted on a total of 76. We can anticipate that in the next week the situation has already improved.

What can we do about it?

The DaVinci team has already submitted to utopian a new version of the questionnaire that will help us obtain more granular scores and allow us to distribute more fairly our allocated share of VP among all users that do a good job. The new questionnaire will be available soon.
In the meantime, we ask to our LMs to be very thrifty in assigning high scores beyond the normal average, because they could damage the work of other translators, depriving them of the vote to their post.
Last but not least, the DaVinci team will also explore alternatives ways to help all our collaborators. We have an interal trail that follows all your contributions, if you want to do something you can follow our trail or delegate SP to the Hive account@davinci.witness account to help us help you. At the bottom of this post, above our banner, you can find out how to do it.

Below you can find the stats for Week #20:

October 28 2018 -:- November 03 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.