Skip to content
This repository has been archived by the owner on Jun 17, 2020. It is now read-only.

Translation: Metrics and Value system #960

Closed
Viraculous opened this issue Sep 12, 2018 · 9 comments
Closed

Translation: Metrics and Value system #960

Viraculous opened this issue Sep 12, 2018 · 9 comments
Assignees
Labels

Comments

@Viraculous
Copy link

Viraculous commented Sep 12, 2018

Target: The aim of this issue is to prioritize the essence of translation, get an established metrics and value system for translation.

Purpose: Translation has been one the uprising concerns amongst others in the bounty system with serious contentions on the value and metrics. More of the concerns are centered on spending on translations without any significant market for the locality that is being translated for.

Information from the Budget and reward sheet shows that an estimate of $170,000 has been spent from March to August(6months) on translation. Particularly, $22,000 was spent for translations in the month of August with little or no audience for the translation. The budget on this does not match the result.

Translations are currently being posted on two main channels; Medium and RChain Worldwide community forum. Each translation seems to have a separate medium account.

Here is a list of the media channels and followers

RChain Greek 0 follower
RChain German 2 followers
RChain Polish 0 followers
RChain Ukraine 1 follower
RChain Russia 0 follower
French(@casanwugo's personal medium) 271 followers
RChain Spanish 0 follower
RChain Italian 4 followers
RChain Chinese( I see no channel where Chinese translations are being posted)
RChain worldwide community XYZ
has only about 43 registered users.

Recommendation:

  • Replace human translation with automated translation; The essence of translation is communication, understanding, and interaction with non-English speakers. The automated translation may not be perfect but I think meets that requirement 70-80% especially for the non-technical document. (Except for technical documents)
  • Translation of technical documents will be at the approval of the dev-team and the marketing team.
  • languages to be translated to should be determined by the marketing team. Otherwise, send a request to the marketing team stating valid reasons why the doc(Technical) should support other languages.
  • Amongst others, viewership(not just from anybody but from the locality of the translation) should be the ultimate metric for translating a document.

CTA

  • Get in touch with the TAC and Marketing team to get this effected starting fully from October.

Budget: ???

@Viraculous Viraculous self-assigned this Sep 12, 2018
@Viraculous Viraculous added the zz-Translation NEEDS SPONSOR label Sep 12, 2018
@luigidemeo
Copy link

is there a suggested budget for this task. In general i agree with the approach.

@Viraculous
Copy link
Author

Viraculous commented Sep 12, 2018

@luigidemeo for now the budget is quite tentative, I look more for results.

@dckc
Copy link
Contributor

dckc commented Sep 13, 2018

See also my proposal to reboot all labels: #783 (comment)

@AyAyRon-P
Copy link
Contributor

AyAyRon-P commented Sep 14, 2018

@Viraculous @luigidemeo there is currently no budget in place for translations. Each time there was a translation issue presented, the question was always asked "is there an audience?" to which someone would reply with some long winded copy+paste from wiki/google about "how XXmillion people speak the language", "how it's a technology advanced country", and "how we need to be a global community and not only English speaking" etc, etc, etc 💩

None of those answers are good enough and quite frankly I'm glad that we're shutting down the translations label because it's a massive waste of resources. The only translation I see of value right now is Chinese because we have a sizable following and member base in China.

Here are a few of the Chinese bounties and included metrics:
#202
#565
#643
#794

@Viraculous
Copy link
Author

Viraculous commented Sep 14, 2018

@AyAyRon-P thank you very much. I have no issue at all with translations but mainly concerned about the audience and a statistical reason why documents should be translated into their language. You said

. The only translation I see of value right now is Chinese because we have a sizable following and member base in China.

There are basically 3 reasons why I also think the Chinese translation is needful and will create value.

  1. People proficient in English in China is less than 10% of 1.2 billion of their population which is very low.
  2. China is technologically improved having a good knowledge of blockchain.
  3. China has a great deal of audience around RChain(Though the entire population is a factor because they are the highest most populated country in the world).

For me, any country that meets these criteria is good for translation.

Secondly, even for Chinese, I think google translate would serve for non-technical document except for the critical ones. But on second thought, I think if a translation work that meets the value above, it would increase member participation and as well employment of skill to use for members to take up the task provided it is within the budget scope.

Thirdly, this issue as you can see was raised to streamline translation issues until there is a clear metric for it. With your comments above, I am persuaded to close this issue but will be leaving this questions.
Seeing that money has been spent on translation, what then will happen to the translation document up on medium without an audience? Do we leave them there to lie valueless or get them across to channels where they can be read and valued while it has been suspended?
Also, does this decision affect issues already completed prior to the decision being made?

I still believe value could be gotten from those translations, it's all about taking the right channels and socials where they can be valued and spread the good news about RChain.

@dckc
Copy link
Contributor

dckc commented Sep 20, 2018

This has a large overlap with #483. Let's use that one if there's any more discussion on this.

@kaka56
Copy link

kaka56 commented Oct 3, 2018

@dckc how do we continue with the discussion when both issues are closed with no conclusion ?
At least one should be left open.

@dckc
Copy link
Contributor

dckc commented Oct 3, 2018

Issues can be reopened by anyone who intends to do more work on them.

Is there actually more work to do here? Doesn't the comment in #483 noting the reboot address the issue raised here?

@kaka56
Copy link

kaka56 commented Oct 3, 2018

Alright cleared

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants