[bisq-network/proposals] Shut down Slack (#144)

Manuel notifications at github.com
Mon Dec 16 13:59:43 UTC 2019


In theory the proposal should be closed once the discussion about executing or not the proposal is over and a decission about the proposal has been taken (accepted, rejected, ignored, invalid, etc) or the proposal stalls. 

These are the rules about  closing proposals (although I am being much more flexible than what is described here):

>Step 3. Evaluate
After the two-week review period is over, a maintainer will evaluate reactions to and discussions about the proposal and will close the issue with a comment explaining that it is approved or rejected based on whether a rough consensus was achieved.

>Approved proposals will be labeled with was:approved. Rejected proposals will be labeled with was:rejected.

>If rough consensus has not been achieved, e.g. because discussion is still ongoing, dissenting concerns have not been addressed, or the proposal has turned out to be contentious, the maintainer will indicate that they cannot close the proposal, and that it is up to the submitter to take next steps to move the proposal forward. If the proposal does not move forward after another two weeks, the maintainer will close and label it was:stalled.

>If there have been no or very few reactions to a proposal after the two-week period, the maintainer will close it and label it as was:ignored.

However, if you still think I should reopen the issue, I´ll do.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/144#issuecomment-566072940
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191216/72c2a8ff/attachment.html>


More information about the bisq-github mailing list