Skip to content
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

Proposals Maintainer #30

Open
cbeams opened this issue Sep 4, 2017 · 77 comments
Open

Proposals Maintainer #30

cbeams opened this issue Sep 4, 2017 · 77 comments
Assignees
Labels
team:admin https://bisq.wiki/Admin_Team

Comments

@cbeams
Copy link
Member

cbeams commented Sep 4, 2017

Docs: https://docs.bisq.network/proposals.html#maintainer
Team: @bisq-network/proposals-maintainers

@cbeams cbeams added the role:doc label Sep 4, 2017
@cbeams cbeams self-assigned this Sep 4, 2017
@cbeams cbeams changed the title proposals maintainer Proposals Maintainer Jan 2, 2018
@cbeams cbeams added role and removed role:doc labels Jan 3, 2018
@cbeams
Copy link
Member Author

cbeams commented Jan 4, 2018

2017.12 report

There was no activity around proposals this month.

/cc bisq-network/compensation#26

@cbeams
Copy link
Member Author

cbeams commented Feb 1, 2018

2018.01 report

We had one new proposal issue this month around how to turn Bisq nodes into Lightning nodes, and it's begun to get some activity. See bisq-network/proposals#3.

/cc bisq-network/compensation#35

@cbeams
Copy link
Member Author

cbeams commented Feb 28, 2018

2018.02 report

Just one new proposal this month, around building native mobile apps. It's only an issue at this point and could use more feedback: bisq-network/proposals#4

/cc bisq-network/compensation#40

@cbeams
Copy link
Member Author

cbeams commented Apr 4, 2018

2018.03 report

We had an uptick in new proposals over the month of March (some of which were my own), but not a lot of resolution / coming to consensus about them. To a certain degree, it's fine for proposals to hang around for a while, in order for people to have time to read, think about, and respond to them, but at a certain point, proposals basically "go cold" and either need to be brought back to life or closed due to inactivity. I'm not sure about what to do here, process-wise, but in any case, I think we want the proposal process to have a high degree of integrity, where people who submit proposals are fully responsible for their resolution (one way or another), and proposals don't "die on the vine" due to inattention.

I'll make a point to care for my proposals in this way over the coming month; perhaps others can do the same.

/cc bisq-network/compensation#57

@cbeams
Copy link
Member Author

cbeams commented May 3, 2018

2018.04 report

@cbeams wrote a proposal on refining the proposal process, which was approved and led to putting together the https://docs.bisq.network/proposals.html doc in bisq-network/bisq-docs#40. This new doc defines the proposals process and all @bisq-network/contributors are encouraged to read and understand it.

There were a number of other proposals accepted and rejected this month, and several proposals remain open right now. In the future come, these monthly maintainer updates will recap the proposals that were created, accepted and rejected throughout the month.

/cc bisq-network/compensation#68

@cbeams
Copy link
Member Author

cbeams commented Jun 1, 2018

2018.05 report

As can be seen in the results of this query:

  • 6 proposals were closed as approved
  • 1 proposal was closed as stalled
  • 2 new proposals were created

I believe the proposals process is working quite well now, and it's reasonable to believe it'll only get better from here as more contributors get familiar with it.

One potential area for improvement, though, is around reviewing proposals. On average we're getting just 3–5 reactions to proposals. If that is a reflection of how many contributors actually care about each proposal, then that's fine (we don't want people wasting their time weighing on on stuff they don't know about or don't care about), but if these numbers are a reflection of the fact that people just don't know that the proposals are there, or haven't prioritized reading through them, then it would be good to get more engagement. Be sure to watch the repository if you're not already doing so.

If you have feedback on this process, please speak up. You can do that in a comment here, in the `#proposals' Slack channel, or in an issue on the proposals repository.

/cc bisq-network/compensation#74

@ManfredKarrer
Copy link
Member

2018.06 report

I took over primary ownership of that role that month.

  • 7 proposals have been opened.
  • 1 was closed

Unfortunately there is still not a lot of discussion and feedback on most of the proposals. We need to try to spread that better to the other channels and invite people to actively participate in the discussion.

/cc bisq-network/compensation#92

@cbeams
Copy link
Member Author

cbeams commented Jun 30, 2018

2018.06 report

Thanks, @ManfredKarrer and @ripcurlx for agreeing to temporarily take on this role, but on review, I don't think it makes sense to hand it off. Proposals are a vital part of how we do things, and I'm happy to continue caring for the process there until someone shows up who is really eager to take it over.

I think it's much better, @ManfredKarrer, for you in particular to spend your time with proposals either (a) submitting your own proposals (as you've done to good effect a number of times now) or (b) reviewing others' proposals. The actual duties of Proposals Maintainer are quite easy, so I'll keep doing them for now.

Note that I've clarified what those duties are in the Proposals doc. It hasn't been merged yet, but you can see a draft here: https://deploy-preview-46--bisq-docs.netlify.com/proposals.html#duties

I've updated the description of this issue to reflect what I've written above.

/cc bisq-network/compensation#89

@cbeams
Copy link
Member Author

cbeams commented Jul 31, 2018

2018.07 report

I have been behind in my proposals maintainer duties over the last couple months, and let a few proposals linger longer than they should have without being closed or otherwise pushed along.

I've caught up now, however, on open proposals, including closing serveral, and will endeavor to keep up with the normal two-week review cycle going forward.

In the meantime, it's great to see all the productive ideas and conversation happening around proposals. Keep it coming!

BSQ requested: 150

/cc bisq-network/compensation#101

@pazza83
Copy link

pazza83 commented Oct 24, 2023

Cycle 52 Report

Quiet cycle for proposals for this cycle.

Good time to remind users to comment / upvote / downvote any of the current open issues.

0 proposals were opened:

0 proposals were rejected this cycle:

1 proposal was approved cycle:

@pazza83
Copy link

pazza83 commented Jan 24, 2024

Cycle 55 Report

Quiet cycle for proposals.

0 proposals were opened:

0 proposals were rejected this cycle:

1 proposals were approved cycle:

@pazza83 Plan for Projects Maintainer role: First Stage

@pazza83
Copy link

pazza83 commented Feb 23, 2024

Cycle 56 Report

Quiet cycle for proposals.

1 proposals were opened:

@403State Application to become a bonded pricenode operator

0 proposals were rejected this cycle:

2 proposals were approved cycle:

@MwithM BSQ trading fee update on Cycle 55
@solomon1923 Proposal to assume Growth Lead role

@pazza83
Copy link

pazza83 commented Mar 27, 2024

Cycle 57 Report

Quiet cycle for proposals.

1 proposals were opened:

@salokiam Show a Warning for potentially misconfigured network settings

0 proposals were rejected this cycle:

1 proposals were approved cycle:

@403State Application to become a bonded pricenode operator

@pazza83
Copy link

pazza83 commented Apr 26, 2024

Cycle 58 Report

Quiet cycle for proposals.

0 proposals were opened:

0 proposals were rejected this cycle:

0 proposals were approved cycle:

@pazza83
Copy link

pazza83 commented May 28, 2024

Cycle 59 Report

Quiet cycle for proposals.

1 proposal was opened:

@HenrikJannsen Reduce max. trade amount via DAO voting

0 proposals were rejected this cycle:

0 proposals were approved cycle:

@pazza83
Copy link

pazza83 commented Jul 11, 2024

Cycle 60 Report

Another quiet cycle for proposals.

2 proposals were opened:

@runbtc Restore mempool fork
@refund-agent2 Reduce max refund amounts

0 proposals were rejected this cycle:

1 proposal was approved cycle:

@HenrikJannsen Reduce max. trade amount via DAO voting

@pazza83
Copy link

pazza83 commented Jul 11, 2024

Cycle 61 will be my last cycle for this role. I will look to tidy up the current open proposals before passing this role over to @suddenwhipvapor should they accept taking it on.

@suddenwhipvapor
Copy link

Thank you @pazza83 I will be available to take on this role from cycle 62

@pazza83
Copy link

pazza83 commented Aug 4, 2024

Cycle 61 Report

This will be my last cycle as the proposals maitainer. @suddenwhipvapor will be taking over from next cycle.

2 proposals were opened:

@philipmw Application to become a bonded price node operator
@ChrisSon15 Single Transaction Multisig Protocol for Bisq using UTXO swap

0 proposals were rejected this cycle:

0 proposals were approved this cycle:

@suddenwhipvapor
Copy link

Cycle 61 Report

This will be my last cycle as the proposals maitainer. @suddenwhipvapor will be taking over from next cycle.

2 proposals were opened:

@philipmw Application to become a bonded price node operator @ChrisSon15 Single Transaction Multisig Protocol for Bisq using UTXO swap

0 proposals were rejected this cycle:

0 proposals were approved this cycle:

Thank you, I think this is where I officially ask to be given moderation privileges for this repository?

@pazza83
Copy link

pazza83 commented Aug 5, 2024

Thank you, I think this is where I officially ask to be given moderation privileges for this repository?

@cbeams please can you give @suddenwhipvapor the necessary permissions for the proposals repository and this issue.

Many thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team:admin https://bisq.wiki/Admin_Team
Projects
None yet
Development

No branches or pull requests

8 participants