-
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 14 #601
Comments
tx id: 4acd9e1424927008c239f6963030734d2e32e7828b2fbb3bca705a469bec3201 |
Contributors should wait for team lead review before submitting compensation request to DAO. |
@MwithM If a person's only contributions during a cycle were for ops roles which are basically pre-approved, I think it's fine to submit without waiting for ops team lead review, per ops budget https://github.com/orgs/bisq-network/teams/ops/discussions/1 |
@wiz Placing a budget doesn't mean that tasks of that the tasks of the role have been properly done, but as team leader, if you think that ops related requests can be pre-approved, I'm ok with it. |
@MwithM badly done ops jobs can still be rejected at DAO level but I agree that it's better to intercept before DAO voting. Maybe the bot can also add a 'this request has been approved, reply with your tx id' comment. |
Believe me bro, if you're not doing a good job at running your nodes I will let you know about it way before it gets to the compensation proposal stage. I monitor the performance of all the Bisq infrastructure, and I get alerts whenever anything goes down. Just ask @m52go how I trolled him today into fixing his BSQ explorer 😉 |
No one avoids the sarcastic hammer of @wiz |
Issuance by Team:
Total Issuance: 476.00 BSQ (equivalent to: 300.00 USD) |
Closed as: accepted |
Summary
476
Contributions delivered
Contributions in progress
The text was updated successfully, but these errors were encountered: