-
Notifications
You must be signed in to change notification settings - Fork 16
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
For Cycle 9 #457
Comments
I support that request as we did not had a clear decision how to go on with expenses, but I will stop supporting any translation expensed from next cycle on as I don't see it as a high priority in times of low revenue. I hope you understand that this has nothing to do with your quality of work but only a measurement to get the BSQ economy back on track. |
By the time, Spanish translations should only produce very little expenses as it just needs some maintenance for new strings. An incomplete translation looks ugly and the cost is very little, but I guess this will be discussed on next translator call. |
It would make sense to keep already fully translated languages up to speed with the latest changes in my opinion, but that's assuming it would be a very limited expense. We're not usually changing a lot of the app text so perhaps it would be possible to get some estimate for how much it would cost to just keep a language up to speed? |
Closed as accepted. |
Summary
Contributions delivered
Spanish translation, Bisq desktop.
486 words * 0.075 = 36
Contributions in progress
Reply unanswered posts on Telegram chat, reddit and bisq.community.
Participate on some Bisq Proposals.
Roles performed
Spanish Bisq Twitter account maintainer: 150
Compensation maintainer: 75
Rate used: 0.67 fiat/BSQ, as stated in #449 so requested BSQ are: 261 / 0.67 = 389.55
Tx id: tx=30ebada8f8669ec20a58635e7a8b86257cb4e8cc36d5db3547d21b0a8bd37515
The text was updated successfully, but these errors were encountered: