Translate Yearn.fi Docs into Spanish - Budget Request

socopower commented 4 months ago

Scope

Hello guys, I am opening this new budget request to start contributing to the translation of all Yearn.fi docs into Spanish which has no active contributors.

Since last year I participated in the Translatathon held by the Ethereum Foundation to finish promoting the translation of all the foundation's content in several key languages, I realized how important it is for other protocols/projects to do the same in order to do so. break the linguistic barrier that may occur to users who want to consult their respective documentation.

I haven't contributed to Yearn before, but this would be the first of many contributions I would like to make.

Plan

The entire plan will be carried out in HackMD, there I will create a main page for the Yearn documentation, you can follow my latest translation so that you have an example of what this page would look like.

About my action plan:

Divide each chapter of the documentation into milestones
Translate each milestone
Review each milestone in search of possible errors and correct them.
Let it be known that the milestone was successfully translated and is now available to be attached.

Deadline

2024-06-1 to 2024-08-20

People

@socopower (as a translator and reviewer)

Money

I would like to give you 3 options on how to execute this project (if approved ofc):

Option A: Translate the Yearn documentation in full, including the chapters: Introduction, Develop, Contribute, Resources and Security.

Option A, Budget:

6.2k DAI, total.

Option B: Translate the Yearn documentation, focusing on the user, this would only be the chapters: Introduction, Contribute, and Resources

Option B, Budget:

4k DAI, total.

Option C: This option is more than anything to give "support" to the translation, whether the Yearn team has decided to move forward with Option A or Option B, let me explain:

Option C = Option A + Support
Option C = Option B + Support

Option C, Budget:

This Support service would only cost 500 DAI/Month, with this support service, the Yearn team will not have to pay any extra amount to translate the new changes or chapters that they add to the original documentation no matter what however long these changes or chapters are.

These budgets (Option A & B) described here are not monthly, they would be a one-time payment for the translation, (except Option C, which is a monthly payment of 500 DAI.)

Obviously, it could be divided into several parts or by milestone (usually, I establish each chapter of the documentation as a milestone) so that the Yearn team feels more confident when proceeding.

P.S: I am avoiding the Smart Contracts chapter because it is very technical (but if the team wants it, I can include it)

Amount (Total)

6.2k DAI - 4k DAI in total, + 500 DAI/Montly If the Yearn team decides to choose Option C

Wallet address

0x009b6aaA8DBE9B36150bbf0cEaeD9d88Cb7710A1

Reporting

Weekly

0xPickles commented 4 months ago

Status: Not approved

1 in support, 9 against (I am not a voter)

After reviewing the request, it did not receive enough support to pass.

Here are some concerns that were raised:

Is there a real need for translations?
Can contributors who don't read English well still be productive in the collaboration-heavy environment of Yearn?
How will maintenance be managed over time, and are the ongoing costs justified?

socopower commented 4 months ago

Hi, about the concerns that arose to the Yearn.fi team when reading the proposal...

1- Is there a real need for translations? Knowing with certainty the answer to that question is somewhat difficult, but... if you ask me as a Spanish speaker, I would tell you that it is necessary because I do want to know the protocol in depth but I do not have a good level of English, I could misinterpret something in the documentation.

And also from the point of view of comfort, there is nothing more comfortable than consulting a guide, a documentation in the best language that the person can use.

2- Can contributors who don't read English well still be productive in the collaboration-heavy environment of Yearn? If Yearn opens up the opportunity for them to do it, of course I believe it.

3- How will maintenance be managed over time, and are the ongoing costs justified?

About the maintenance: Maintenance (if I did it) could be set to be performed quarterly, or whenever there is a significant change in the documentation. Also, I believe that at the time of having a complete base of all the Yearn documentation already translated, Spanish-speaking people within the Yearn community can collaborate to maintain said documentation because most of it is already done and they will only added/remove few things over time.
About ongoing costs: Sorry for not detailing this part very well in the original proposal... The complete Yearn documentation has around 47,200 words that can be translated, I am setting a translation fee of 0.13 USD per 1000 words due to the length of the translation and its complexity (which I set as a medium).

About option C in the budget: I established it at that cost mainly because I do not have data on how much the Yearn team adds or modifies the current documentation, if you do not make significant changes so often, I can easily adjust it to a smaller amount.

defiglenn commented 4 months ago

Hey @socopower, feel free to jump into the discord and we can chat more about this.

I contribute to ySupport so maybe there is an avenue to join our team and start a Yearn/DeFi Spanish telegram group as a first step. This would be voluntary until you proved value add.

We've got/had telegram groups for different languages in the past.

yearn / budget