Closed cbeams closed 5 years ago
I 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.
/cc bisq-network/compensation#26
I conducted December voting in bisq-network/dao#26. See issue for results and other details.
/cc bisq-network/compensation#35
I conducted Feb 1st–3rd voting in https://github.com/bisq-network/dao/issues/39.
/cc bisq-network/compensation#40
I conducted Mar 1st–3rd voting in https://github.com/bisq-network/compensation/issues/44.
/cc bisq-network/compensation#57
I conducted Apr 4th–6th voting https://github.com/bisq-network/compensation/issues/56.
/cc bisq-network/compensation#68
@cbeams conducted the May 5th–7th voting at https://github.com/bisq-network/compensation/issues/58.
@cbeams started work to produce a Compensation
doc at
https://github.com/bisq-network/bisq-docs/pull/62.
/cc bisq-network/compensation#74
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.
@cbeams conducted the Jun 1st–4th voting at https://github.com/bisq-network/compensation/issues/70.
@ripcurlx took over managing the voting process starting with this month at https://github.com/bisq-network/compensation/issues/82.
@ripcurlx conducted the Jun 1st–3rd voting at https://github.com/bisq-network/compensation/issues/82.
/cc bisq-network/compensation#98
Note: I've updated the description of this issue for accuracy and removed @ManfredKarrer as a secondary owner.
@ripcurlx conducted the Jul 1st–3rd voting at https://github.com/bisq-network/compensation/issues/94.
/cc bisq-network/compensation#109
@ripcurlx conducted the September 1st–3rd voting at https://github.com/bisq-network/compensation/issues/107.
/cc bisq-network/compensation#126
Conducted the October 1st–3rd voting at https://github.com/bisq-network/compensation/issues/121.
/cc bisq-network/compensation#148
Conducted the November 1st–3rd voting at https://github.com/bisq-network/compensation/issues/149.
/cc bisq-network/compensation#177
Conducted the December 1st–4th voting at https://github.com/bisq-network/compensation/issues/165.
/cc bisq-network/compensation#195
Conducted the January 1st–4th voting at https://github.com/bisq-network/compensation/issues/183.
/cc bisq-network/compensation#206
Conducted the February 1st–4th voting at https://github.com/bisq-network/compensation/issues/204.
/cc bisq-network/compensation#224
Conducted the March 1st–4th voting at https://github.com/bisq-network/compensation/issues/222.
/cc bisq-network/compensation#247
Conducted the April 1st–4th voting at https://github.com/bisq-network/compensation/issues/243.
/cc bisq-network/compensation#269
Should we close that role as it is now done by software?
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