[bisq-network/proposals] [WIP] Compensation and valuation of translations/reviews (#37)
BravoIndia
notifications at github.com
Sat Aug 25 05:51:29 UTC 2018
@ripcurlx Thank you again for having me on the call and for writing up this proposal.
I believe you left out @HarryMacfinned's suggestion in order to make organic valuations practical:
> Begin with a small first bunch, eg 300/500 words, make your compensation request for that,
> and tell what are your following plans (and the associated comp. request)
> So you'll know precisely 1/ if stakeholders agree or not with the compensation and 2/ with your plan
> and if it's worth for you to continue.
And in my opinion I think there should be a vote on whether translation work is compensated when:
- Partial translation on Transifex
- Threshold translation on Transifex (say ~50%)
- Full translation on Transifex
- Released translation on Bisq client
As I said in the call, if partial translations are not compensated then organic valuations won't work, because @HarryMacfinned's proposal can't be implemented. Practically speaking, the two are mutually exclusive. It's either a well-defined valuation criteria compensated on release, or an organic valuation that allows for people to submit exploratory requests on initial work.
There is a reason Transifex has been practically barren in the past few months until @initCCG showed up--and it seems from their responses that they've done all of their incredible contribution at great personal risk and expense because they were under the **completely false impression** they'd get much higher compensation for their work.
I don't see that happening again without either:
- partial translations being compensated + organic valuations (allowing for initial 'feeler' requests).
Or
- pre-determined valuations + compensation only upon translation completion.
In my opinion you're guarantying Transifex will return to how it was before June without enacting one of these two. Just look at the evidence:
![untitled](https://user-images.githubusercontent.com/33473721/44615396-aba8df80-a863-11e8-90dc-a094ef100c8c.jpg)
This seems to me to be a complete waste of considerable potential added-value to Bisq at remarkably low cost (Does anybody not think each full translation adds at least $10,000 to a hypothetical Bisq client valuation? Well, @initCCG translated 3 languages for $1,000!). Yet we insist on adding hurdles at every turn--now we won't compensate translation work if the translators aren't market makers too?!
There are also other problems. Such as how compensating only upon release and not upon full translation on Transifex incentivizes premature release and arbitration risk (e.g. avoiding good practices, like ensuring a language is reviewed by a separate entity). Why do this? Compensate well done translation work, and then work carefully to determine the best time to release the language, taking into consideration market-making resources, review quality, arbitration resources, encoding & character limitation, etc.--all the time having the completed translation at your disposal.
As well as many other such points I've made on the call and in previous threads. Frankly, I'm just repeating myself here and making comprehensive, coherent arguments that don't seem as though they'd be addressed. So I suggest putting it the above to a vote (4 options when to compensate and valuation criteria), and if the community decides to only compensate upon release--which I expect they likely will, we'll just see the results on Transifex.
In any case, I acknowledge that development work is (of course) the priority here. So I'd be content with bringing this issue to a close. Thank you all for your thoughts and ideas throughout this discussion and for indulging my long-winded posts.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/37#issuecomment-415941001
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180824/8ff8fb40/attachment-0001.html>
More information about the bisq-github
mailing list