[bisq-network/roles] Proposals Maintainer (#30)

pazza notifications at github.com
Mon Jun 7 01:44:17 CEST 2021

### Cycle 25 Report

This was my first cycle as proposal maintainer.

This cycle I mainly tidied up the proposals. This resulted in about ~20-30 proposals being closed. Most of the closed ones had been superseded or had become stalled. 

There are currently 9 open proposals. 

My first impressions are:

- There is not enough engagement on many of the issues. Some of which are pretty important. This leads to some proposals being enacted with limited engagement and other just getting stalled. 
- There seems to be a bit of a disconnect between proposals being accepted and the resultant work being completed and/or project being created 

To help with the former it would be great if everyone can give a quick reaction to the current [9 open proposals ](https://github.com/bisq-network/proposals/issues?q=is%3Aopen+is%3Aissue)

👍: I agree with the proposal and want to see it enacted

😕: I am uncertain about the proposal and I need more information

👎: I disagree with the proposal and do not want to see it enacted

I think @refund-agent2 [proposals](https://github.com/bisq-network/proposals/issues?q=assignee%3Arefund-agent2+is%3Aopen) are especially important as they has implications for all users / contributors.

Hopefully moving forwards with less open issues it will make it easier for people to contribute / engage on the issues.

I am looking forward to developing the role and will try and keep the proposals organized, also will have a think about how accepted proposals can be better connected to future work. 

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210606/d34c278c/attachment.htm>

More information about the bisq-github mailing list