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 · 15 comments

Comments

Projects
None yet
3 participants
@cbeams
Copy link
Member

cbeams commented Sep 4, 2017

@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

This comment has been minimized.

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 cbeams referenced this issue Jan 4, 2018

Closed

For December 2017 #26

@cbeams

This comment has been minimized.

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 cbeams referenced this issue Feb 1, 2018

Closed

For January 2018 #35

@cbeams

This comment has been minimized.

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 cbeams referenced this issue Mar 1, 2018

Closed

For February 2018 #40

1 of 1 task complete
@cbeams

This comment has been minimized.

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 cbeams referenced this issue Apr 4, 2018

Closed

For March 2018 #57

1 of 1 task complete
@cbeams

This comment has been minimized.

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 cbeams referenced this issue May 3, 2018

Closed

For April 2018 #68

1 of 6 tasks complete

@cbeams cbeams removed the a:role label May 4, 2018

@cbeams

This comment has been minimized.

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

@cbeams cbeams referenced this issue Jun 1, 2018

Closed

For May 2018 #74

0 of 5 tasks complete
@ManfredKarrer

This comment has been minimized.

Copy link
Member

ManfredKarrer commented Jun 30, 2018

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

This comment has been minimized.

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 cbeams referenced this issue Jun 30, 2018

Closed

For June 2018 #89

6 of 6 tasks complete
@cbeams

This comment has been minimized.

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

@cbeams cbeams referenced this issue Jul 31, 2018

Closed

For July 2018 #101

@ManfredKarrer

This comment has been minimized.

Copy link
Member

ManfredKarrer commented Jul 31, 2018

I think we should reconsider a bit the close policy. I would prefer to close only proposals which got negative feedback or no attention at all. Though even those might have valuable content which even if not implemented soon might be useful for further ideas. I fear if they are closed they are kind of forgotten and harder to re-discover. To have more open stalled proposals gives us also the sign that there is much work open but due lack of resources they are stalled - which is largely the main issue with most proposals IMO.

@cbeams

This comment has been minimized.

Copy link
Member Author

cbeams commented Aug 31, 2018

2018.08 report

I have not been actively managing proposals this month. Per @ManfredKarrer's request above, we're letting proposals stay open longer, and we can see how this goes over the next months.

BSQ Requested: 25

/cc bisq-network/compensation#114

@cbeams

This comment has been minimized.

Copy link
Member Author

cbeams commented Sep 30, 2018

2018.09 report

Discussion continued this month around bisq-network/proposals#35 and bisq-network/proposals#38. On the former, we decided not to enforce a listing fee, and on the latter we decided to allow compensation requests for work merged to master, not just work that has shipped in a release.

BSQ Requested: 25

/cc bisq-network/compensation#139

@cbeams

This comment has been minimized.

Copy link
Member Author

cbeams commented Oct 31, 2018

2018.10 report

I've made @ManfredKarrer a secondary owner of this role, as he's been caring for proposals more than I lately, and indicated (a while ago) that he's fine with doing so.

I won't itemize the proposals added / updated this month here, but there are a good number of them. It seems that the approach we've taken to proposals works rather well so far.

BSQ Requested: 25

/cc bisq-network/compensation#160

@cbeams cbeams referenced this issue Oct 31, 2018

Closed

For October 2018 #160

@cbeams

This comment has been minimized.

Copy link
Member Author

cbeams commented Nov 30, 2018

2018.11 report

I took no action around maintaining proposals this month, @ManfredKarrer did everything. Manfred, it probably makes sense for you to take the primary role here, since you've actually been performing that duty in practice for the last months are you good with that?

BSQ Requested: 0

@cbeams cbeams removed their assignment Dec 6, 2018

@cbeams

This comment has been minimized.

Copy link
Member Author

cbeams commented Dec 6, 2018

Per #1 (comment), I'll be away for the next ~2 months. I've made @ManfredKarrer the primary owner of this role, which makes sense anyway as he's been doing the actual work of maintaining the issues there over the last months.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.