Bounty Proposal: Portuguese and Spanish Translations Curator
Bounty Proposal: Portuguese and Spanish Translations Curator
Proponent: Maria Clara
Proponent Address: Cd2ZnAqGpiWbyqCwkc3r3jXcad3AxdKTcRWvda31QAFxjrr
Date: 16.12.2020
Requested allocation: 110 KSM
Proposed Curator reward: 20%
Short description: This bounty is being proposed as a 3-month pilot for language curation for Kusama in Portuguese and Spanish. The plan is to execute on this bounty, take the learnings, then apply for a longer-term bounty once the latest updates have been incorporated into the code. Curator proposed is a Polkadot Ambassador, native Portuguese speaker and fluent in Spanish.
1. Context of the bounty: we aim to have as much context as possible, please include here:
- any points discussed in advance in any channel related to the bounty proposal and background research for your project.
- The central topic of the bounty, in which of the general categories does the bounty needs to be included. If the category does not exist, please include the information here.
Latin America, Portugal and Spain represent a large community of technologists, developers and people from all backgrounds interested in getting to know and contribute to decentralized networks. Local groups (e.g. Polkadot Español ~1000 very active members and Polkadot Português >275 members) have been created and are growing on different social medias contributing to the discussions about Kusama and Polkadot networks, promoting local workshops/meetups and helping on move Kusama forward into their regions and languages.
Although there are several resources available to assist the community education, language has been proven as a barrier to their development, since most of resources are currently published only in English. Therefore, there is an opportunity to boost the potential of local contributions in different countries (Portuguese and Spanish-speaking countries in this case) by translating resources to their native language and also by publishing them at local media.
**2. Problem statement: what problem is this proposal trying to solve? If no problems are being solved, which topics does the bounty cover? Make it as granular as possible to allow token holders to understand the logic behind it. **
Kusama’s communities are growing in several countries through a decentralized localization model that currently exists without a standard process of quality review and reward. It’s essentially a free-for-all of people randomly translating things, posting to various personal websites or blogs, with no tracking or coordination among the community.
Also, Kusama’s Council Members are responsible for controlling the Treasury and by allocating funds to projects that bring value to the network; however, councilors do not always have expertise (e.g. other languages) or available time to make a proper assessment of the activities described in treasury proposals. Having a curator with fluency in Portuguese and Spanish and project management skills will have a major positive impact on Kusama in order to establish and manage a process to review, coordinate publishing and reward the translators in these languages. This will allow Kusama to scale the Council’s activities and time and will help to expand Kusama’s reach into these important Spanish and Portuguese-speaking communities around the world.
**3. Proposal Objective/solution/s to point 2: What is the goal of the bounty? What does 'success' look like? **
Please add high level objectives and success factors. Assign an informed budget. Explain what your solution is after taking into consideration the context and the problem. Make sure to consider all points included in the problem statement to ensure a complete and balanced scope, and try to be as granular as possible.
- Include milestones, tasks, or specific goals of the bounty if any;
- Include tools used to develop the tasks, if any;
- Try to quantify the milestones: this will give you a more accurate idea of the total allocation to be requested;
**- If possible include a budget proposal on the bounty. **
- Include how many people you estimate will work on this bounty, including the curator.
Quantified milestones and process overview
Translations included in this bounty:
- Portuguese
- Polkadot Lightpaper (1,889 words)
- Kusama Documentary (7035 words)
- Spanish
- First Polkadot Whitepaper (17,224 words)
Payment Methodology
I plan to pay translators by the number of words in order to more accurately, according to the methodology below:
**Content of translation: **
- Simple Translation: conventional translation without requirement of specific knowledge.
- Advanced Translation: technical translation which requires a specialized professional with both technical and language domain knowledge.
Size of translation: pre-defined prices per word in USD, according to the content/type of translation. USD to KSM conversions will be done on the day of payment, and the KSM amount will be rounded to the nearest 1 KSM.
- Simple Translation: USD $0.16/ word
- Advanced Translation: USD $0.20/word
**Execution speed bonus: **
High quality translations executed in less than 1 week will have an additional 10% over the price defined above.
Translation Review:
If a 3rd party review is necessary to adjust technical vocabulary, reviewer will have 15% of the fee paid to the translator (item b).
This specific bounty proposal would require:
- Polkadot/Kusama Lightpaper: 1 community review and 1 agency review (to be coordinated with Parity)
- Kusama Documentary video captions: No reviews
- Polkadot/Kusama Whitepaper: 1 agency review (to be coordinated with Parity)
The translated materials and documentation of the translator, reviewer 1, and reviewer 2 (if required) will be documented in a Google Sheet document and will be shared in the Kusama Direction channel when updating on translation progress for the curator.
Tools used to complete bounty
-
Crowdin – Used for translation tracking and uploading new documents for translation such as Wiki and websites
-
Trello – Used for project management and task tracking
-
Discord – Used for coordination and communication
How many people will work on this bounty, including the curator.
I expect a handful of people within the Portuguese and Spanish-speaking community to contribute to working on this bounty, most likely 3-5 people.
Publishing
Once translations are ready, the final documents will be delivered to the team in charge of communications and publications on social media, blogs and websites for them to use them as required.
Comments (6)
I'm a member of the technical education team and I would love to see this content in more languages. The bounty feels okay to me, though I kind of feel like Polkadot should pay for this, not Kusama, not least because Kusama has its own dedicated guide (admittedly from the same source as the wiki).
I'm curious about long term maintenance of these pages. Parameters change, source code evolves, best practices get obsoleted - we frequently need to update docs and those changes will be out of sync with your translations. I would rather not have a translated wiki than have a translated and outdated one. What steps can we take to make sure the translated content remains up to date?
Hi Bruno, thanks for your questions! About your first comment, there are a few reasons we had for funding this through the Kusama Treasury. First, as you mentioned, the Kusama guide is directly sourced from the Polkadot wiki, so by translating the Polkadot wiki, we are also translating the Kusama guide. Also, the Kusama community is always led to the Polkadot lightpaper and whitepaper, since these were never created for Kusama itself. A translated lightpaper and whitepaper benefits Kusama. Last, this is just a pilot period to help us test with the Kusama Treasury, and we plan on this leading to a longer-term and larger translation curator to appear on Polkadot once we learn from this experience. About long term maintenance of these pages, these translations are all being done and managed through Crowdin. Crowdin has version management which makes sure all versions match the master files. As long as the source code is updated, then Crowdin will automatically indicate that a new translation is required for changes in the text. I recently talked to Hutch and we are also going to try to get a Kusama Crowdin page set up for future Kusama-specific translations.