-
Notifications
You must be signed in to change notification settings - Fork 0
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
Close all Cycle 10 compensation requests when vote reveal is complete #40
Comments
I think that this is complete, just a little thing is missing: I'm not sure where to announce when contributors should send their requests. |
You should send a message to
If by "message" you mean "GitHub notification", this is incorrect. Labeling an issue does not create a notification, meaning that the people involved with that compensation request issue will not be notified of the label unless they also see it mentioned in the closing comment.
What you should do is the following:
I realize that it requires an extra step (away from the board) to close the issue with a comment, but it really is the best thing to do so that interested parties get notified properly of the end state of the request. So: first label the issue, then type the comment and click the "Close and comment" button. Additionally, I see that you archived all issues immediately after closing them. I see that my instructions here didn't fully make sense, because I wrote that we should wait until the next cycle to archive them. Given that the next cycle comes almost immediately after the vote reveal phase is complete, this doesn't leave much time for the issues to sit in the I have also un-archived Cycle 10 issues so that they comply with the process as documented above. Please archive them accordingly at the end of the Cycle 11 proposal phase. I have also renamed the @MwithM, when you have read this comment and reviewed the process changes in the documentation, please add a comment here saying you've done so and close this issue or leave it open if you have outstanding questions / feedback. Thanks. |
@cbeams It's done, I just didn't know how to send a message to bisq DAO. Steve told me the address for it, I'm changing that for wiki compensation. It seems I can't close issues here, please proceed to do so. |
Closing as complete. Thanks @MwithM! |
Adding this tracking issue just to make sure this happens per process the first time around. No need for such issues in the future as it's all part of the documented process at https://bisq.wiki/Compensation.
@bisq-network/compensation-maintainers to
was:approved
orwas:rejected
The text was updated successfully, but these errors were encountered: