-
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
Update compensation request maintainer role duties to include adding a calendar event for issue submission deadline #56
Comments
@MwithM, you have edit access to the calendar now, and I've also just added https://bisq.wiki/Events_Calendar. |
I tried to simplify the calendar using concrete days instead of periods. All DAO phase beginnings are announced -the start of phases are close to the end of the last phase of a cycle-, and the most critical deadline (DAO submission) is detailed by the block and estimated hour to be mined and also by the day it should happen as well. |
Did you see the dao discussion this morning as to why I deleted the phases from the calendar? They are always wrong by default due to the block time mismatch and I don’t think they’re adding value to anyone. I think it’s just noise to have them there (as periods or specific times). The only thing that really matters is that folks get a reminder about the issue submission deadline. Could we leave it to just that on the calendar? It’s less work for you that way as well.
… On Feb 26, 2020, at 6:02 PM, MwithM ***@***.***> wrote:
I tried to simplify the calendar using concrete days instead of periods. All DAO phase beginnings are announced -the start of phases are close to the end of the last phase of a cycle-, and the most critical deadline (DAO submission) is detailed by the block and estimated hour to be mined and also by the day it should happen as well.
At the wiki, I just stated that the announce for submission deadline will be also made at the Bisq Events calendar, together with DAO discussions and Compensation Board. Maybe this needs more concretion.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
To me, the noise came because periods were announced instead of specific times. You don't need to be reminded every day you're in the proposal phase, but it might be good to remind reveal phase. I thought that if I edit the times as the blocks are getting nearer, mismatch won't be very high. |
Thanks, @MwithM. Note that I changed the text of the invitation and the link in the notes. Using an abbreviation like "CR" (as the calendar event previously read) is cryptic for newcomers. Even I didn't know what people were talking about the other day when I saw CR mentioned in a chat conversation. This change spells it out and makes it clear that there is a deadline for submitting compensation request issues. It's verbose, but clear. |
/cc bisq-network/roles#86
The text was updated successfully, but these errors were encountered: