Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Let users award translators too #2900

Closed
nomennescio opened this issue Jan 13, 2023 · 0 comments
Closed

Let users award translators too #2900

nomennescio opened this issue Jan 13, 2023 · 0 comments
Labels
kind/feature-request Use this when the request includes specific feature. Otherwise, use generic enhancement.

Comments

@nomennescio
Copy link

In Codewars the author of a Kata can get awarded by users for their experience with the Kata, by upvotes or downvotes.
Translators are currently not rewarded. I request the introduction of a similar feature to let users award translators too.

Translating a Kata requires quite some effort, first by writing a solution in a language of choice, but also to write all testcode.
Typically the quality of translation is not consistent between languages for the same katas, which shows there are "good" and "bad" translations. The user's experience of solving the kata is tightly coupled to the (translated) language he solves it in. By rewarding (or punishing) the author only, the role of the quality of the translation gets fully attributed to the Kata author only, although the translator plays a significant role too.

Introducing such a feature requires some careful thoughts and a matching design. I will elaborate.

Note that it might be helpful to think of author and translator not as two different persons, but to discern between two concepts:

  1. quality of the kata experience: how well was the description, the challenge, the abstract concept, the story etc.?
  2. the quality of the implementation of the language of choice: how well where the tests written, could the sample code be easily studied to understand detailed requirements, how well were language specific details explained, how well were errors detected, how relevant were the test vectors?

In such a way, the author of the kata is both responsible for 1 and for 2 in language of the first implementation. He might also translate to more languages.

Incentives both for "authors"/1 and "translators"/2 act as a stimulant to give good katas to users. Having a fair distribution of incentives between authors and translators will stimulate more translations and better translations of katas, which will improve the overall Codewars experience for users. However, how to determine what incentives scheme will result in such a better experience, while avoiding negative effects of such a scheme that might deter translators to produce more and better translations?

A careful consideration should be made how different incentive schemes impact . Also, how are users going to show their appreciation, and how can they tell how much they like the kata idea ("author"/1) and how much they like the kata implementation ("translator"/2) ? Should that be two concepts they can vote on? Or a single combined one?
If a combined one, a more sophisticated mechanism could be used to "calculate" which part of could be attributed to the "author" and which part to the "translator" e.g. by comparing votes in different languages of the same kata and see if there are significant differences which might show difference in quality of translations.

Also next to distribution of rewards, how will a "punishment" impact the overall amount and quality of translations?

And last I would also like to mention the role of translation approvals, and incentives to help that (e.g. #1518), which is somewhat related to the grander scheme of how incentives can help improve the overall Codewars experience

@kazk kazk added the kind/feature-request Use this when the request includes specific feature. Otherwise, use generic enhancement. label Jan 17, 2023
@codewars codewars locked and limited conversation to collaborators Jan 18, 2023
@kazk kazk converted this issue into discussion #2907 Jan 18, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
kind/feature-request Use this when the request includes specific feature. Otherwise, use generic enhancement.
Projects
None yet
Development

No branches or pull requests

2 participants