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
Cycle 3 #302
Comments
Hi Drazen. |
Hi Drazen, As MwithM rightly pointed out, Hebrew is not a core languge for Bisq right now, and therefore, translations into it are not compensated. We really appreciate your help, but this is how it is right now. If we expand the scope of core languages in future, you can definitely submit your compensation request then. |
I edited my request. |
@Drazen-V during the proposal phase, you can delete your proposal and submit a new one. After the proposal phase is over, proposals are locked in. FYI you will lose the 2 BSQ fee you paid to make the original proposal, and you will need to pay another 2 BSQ to make the new proposal. |
@Drazen-V Reimbursement requests are intended for the new trade protocol (not in place yet). Please use a normal compensation request! |
I removed the original request, it got removed from the "Proposals for current cycle" window in the app. I placed a new Compensation request, as suggested above. Any idea why the removed proposal shows now (meanwhile we got advanced from the Proposal phase to the Blind vote phase)? Is this a bug? |
Something similar happened in the last cycle...seems like it might be a bug after all. |
It seems the network and seed nodes have stability issues atm and the remove message was not well propagated. People should down-vote the old proposal.... |
Closed as old. |
Summary
Contributions delivered
Bug reports:
bisq-network/bisq/issues/2938 includes an analysis about the source of the problem.
bisq-network/support/issues/260
Contributions in progress (not asking for compensation in this cycle)
Translation
Translation to Hebrew: #Bisq-desktop
As the photo below shows, 280 strings (3500 words) were translated.
The text was updated successfully, but these errors were encountered: