Skip to content
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

Closed
1 of 4 tasks
cbeams opened this issue Feb 26, 2020 · 5 comments
Assignees

Comments

@cbeams
Copy link
Contributor

cbeams commented Feb 26, 2020

/cc bisq-network/roles#86

@cbeams
Copy link
Contributor Author

cbeams commented Feb 26, 2020

@MwithM, you have edit access to the calendar now, and I've also just added https://bisq.wiki/Events_Calendar.

@MwithM
Copy link

MwithM commented Feb 26, 2020

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 to be more specific.

@cbeams
Copy link
Contributor Author

cbeams commented Feb 26, 2020 via email

@MwithM
Copy link

MwithM commented Feb 27, 2020

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.
Anyway, it's less work and nobody asked for it, so I've performed the changes. Now only the day for CR ready for review is indicated on the calendar.

@cbeams
Copy link
Contributor Author

cbeams commented Feb 27, 2020

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.

image

@cbeams cbeams closed this as completed Feb 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants