-
Notifications
You must be signed in to change notification settings - Fork 59
ONGOING: Label Guiding for Translations - July 2018 #869
Comments
That's circular, no? That is: we'll close the issue when the work is complete. The question is: how do you / we define complete? I suggest: this task is complete when the Translation guides have summarized the July work in a concise report that discusses rewards paid vs. value produced as well as issues / problems / solutions. Meanwhile... is there any particular reason to do this separately from the quarterly reports such as #850 ? I would rather see your July work go into an early draft of the Q3 bounty program report. (cc @TrenchFloat ) |
@dckc I have changed the "How will we measure completion?" part of the description as you suggested. Indeed, it's much more clear and informative this way. |
Separating budgets for particularly burdensome areas such as Marketing and Translation seems reasonable to me. I would still appreciate a "Translation guides are done for this month" signal in the overall monthly review issue (#847). |
Hi @dckc as soon as we're finished over here I promise to check off the "done for this month" box 👍 |
This was rewarded in 201807. As discussed in #483 etc., translation work is on hold pending sponsorship. |
Benefit to RChain
The report will provide transparency regarding the translation label issues and the actions performed by the guides.
This month we have also implemented the use of this tool for word counting and pricing of the translations now and moving forward. This is to ensure consistent and fair pricing and eliminate a guesstimate of translation values.
Budget and Objective
Estimated Budget of Task: $[1600]
Estimated Timeline Required to Complete the Task: [1 month]
How will we measure completion? [The task will be complete when the report of the translation label guides is finalized and posted here and in the quarterly reports.]
Legal
Task Submitter shall not submit Tasks that will involve RHOC being transacted in any manner that (i) jeopardizes RHOC’s status as a software access token or other relevant and applicable description of the RHOC as an “asset”—not a security— or (2) violates, in any manner, applicable U.S. Securities laws.
In PDF format
The text was updated successfully, but these errors were encountered: