-
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
Compensation Maintainer #31
Comments
2017.12 reportI conducted November compensation request voting in bisq-network/dao#18, and everything went well. See that issue for links to voting results and other details. |
2018.01 reportI conducted December voting in bisq-network/dao#26. See issue for results and other details. |
2018.02 reportI conducted Feb 1st–3rd voting in bisq-network/dao#39. |
2018.03 reportI conducted Mar 1st–3rd voting in bisq-network/compensation#44. |
2018.04 reportI conducted Apr 4th–6th voting bisq-network/compensation#56. |
2018.05 report@cbeams conducted the May 5th–7th voting at bisq-network/compensation#58. @cbeams started work to produce a |
Note: @ripcurlx has taken on the role of secondary owner for this role, and will conduct this month's compensation request voting. The assignees and description of this role issue have been updated accordingly. |
2018.6 report@cbeams conducted the Jun 1st–4th voting at bisq-network/compensation#70. @ripcurlx took over managing the voting process starting with this month at bisq-network/compensation#82. |
2018.09 report@ripcurlx conducted the September 1st–3rd voting at bisq-network/compensation#107. |
2018.10 reportConducted the October 1st–3rd voting at bisq-network/compensation#121. |
2018.11 reportConducted the November 1st–3rd voting at bisq-network/compensation#149. |
2018.12 reportConducted the December 1st–4th voting at bisq-network/compensation#165. |
2019.01 reportConducted the January 1st–4th voting at bisq-network/compensation#183. |
2019.02 reportConducted the February 1st–4th voting at bisq-network/compensation#204. |
2019.03 reportConducted the March 1st–4th voting at bisq-network/compensation#222. |
2019.04 reportConducted the April 1st–4th voting at bisq-network/compensation#243. |
Should we close that role as it is now done by software? |
I agree. The only reason to keep this role active would be to remind contributors to file compensation requests. It will be difficult to automate that properly within Slack as our timing is now based on blocks. Not sure if it is worth to continue to set the different phases in the Google Calendar as well. I'm definitely not the one who wants to keep this role alive 😉 |
Ok, I will close. People will learn to take care themself on the phases. Once missed one is probably enough to remember next time... |
Note that this role was resurrected in #86, as there are management duties to be carried out around each cycle, e.g. sending out announcements about BSQ/USD rate, submission deadlines, keeping the (new) compensation board up-to-date, etc. |
In lieu of a proper spec, here are the basic requirements for this role:
See also: https://github.com/bisq-network/docs/blob/master/dao/phase-zero.adoc#track-stake-voting-and-bonding-via-spreadsheet
Docs: none, other than the above and a WIP PR
Team: @bisq-network/compensation-maintainers
Primary owner: @ripcurlx
Team: @bisq-network/compensation-maintainers
The text was updated successfully, but these errors were encountered: