-
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
Conduct Mar 1st–3rd compensation request voting #44
Comments
|
Note that I have been explicitly documenting that no progress has been made with role specs in my monthly Roles Maintainer updates, e.g. bisq-network/roles#28 (comment). But it's good to do something more visible here and communicate what the next steps are. Basically, I think we can relax things a bit; just make sure that issue descriptions are up to date, and that all role assignees do monthly report comments on their roles consistently. That's enough for the moment, and we can start formalizing role specs as necessary in the future. I'd love to have everything properly tracked in Git, but it just hasn't been able to get priority next to everything else. Same thing with bonding—we may just continue waiting on it at this point, i.e. keep punting until on-chain mechanisms are implemented, instead of burning resources trying to implement it at the spreadsheet level. Not sure; need to talk with @sqrrm and @ManfredKarrer about that. In any case, it'll be good to get out of this limbo state where everything role has TODOs on it for specs and bonding, but no clear instructions / deadlines or negative consequences for not getting these things taken care of. |
The following messages have been sent to the bisq-contrib list:
[...]
|
|
(previous voting round: bisq-network/dao#39)
The text was updated successfully, but these errors were encountered: