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

Roles Maintainer #28

Open
cbeams opened this Issue Sep 4, 2017 · 17 comments

Comments

Projects
None yet
5 participants
@cbeams
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

This comment was marked as outdated.

Member

cbeams commented Dec 12, 2017

@csacher, I've added you as an assignee, reflecting that we're in the middle of a handover process for this role.

@bisq-network/contributors, the plan is that @csacher and I will continue work together over the next weeks, getting the process and infrastructure around roles solidly in place and working with individual role owners to take control of their respective role specs, etc. Ultimately, the goal is to have @csacher bond into this role and for me to drop out of it, i.e. hand it off completely to him.

In the meantime, @csacher will start doing monthly reporting for this role in the form of comments on this issue, and you can expect to see various messages and requests from him in Slack / on the bisq-contrib mailing list and elsewhere.

Thanks, @csacher!

@cbeams cbeams changed the title from roles maintainer to Roles Maintainer Jan 2, 2018

@cbeams cbeams added role and removed role:doc labels Jan 3, 2018

@cbeams

This comment has been minimized.

Member

cbeams commented Jan 4, 2018

2017.12 report

I worked with @csacher to begin delegating at least some aspects of maintaining the roles repository. This primarily consisted of on-boarding activities and so on, but still produced a number of positive changes, such as the friendly overview table we now see at https://github.com/bisq-network/roles. In any case, I'm doing the monthly report this time around, and we'll see if it makes sense for @csacher to take this over in the future.

The big push is to get every role spec'd out and bonded. This takes time, and a number of specs have been coming in, but many more need to be filled out. We'll keep pushing this ball forward over the coming month.

Right now, there are too many manual moving parts involved in managing roles, including:

  1. Role specs themselves, checked in as AsciiDoc files in the root of the roles repository
  2. Role issues that track ownership and monthly reporting comments like the one you're reading now
  3. The overview table in the roles repository readme.

Each one of these is valuable and important, but having to manage them all manually is a pain, and makes the process of delegating maintenance of the roles repository a challenge. For this reason, I've begun reaching out to the Atomist team about finding ways to automate this infrastructure (Atomist is all about 'development automation', and they have sophisticated tools for automating Slack and GitHub-based workflows like the one that the Bisq DAO is based on). You'll see the @atomist bot doing various stuff in Slack, and I'll have more updates on this front next month. In any case, we'll keep the good stuff about the roles repository and automate the painful stuff.

I've taken care this month to add a monthly update for all roles I'm responsible for (again, like the one you're reading right now). Aside from the practical purpose of letting everyone know how the stuff I'm responsible for is going, this is also to set an example of how these monthly report comments should go. There is no particular structure necessary—just a 2nd level heading that reads ## 2017.12 report like you see above, and then whatever commentary and links you believe will be useful / helpful / informative to others, especially as regards making decisions about compensation request voting for your work as a bonded contributor.

Also, note below👇 how I've referenced my current month's compensation request in this update. Doing this for every role I'm responsible for creates a nice effect on the compensation request issue side, creating links between these issues in the issue timeline. This all helps with discoverability / ease of evaluating stuff at voting time, and is also just good practice for posterity's sake.

/cc bisq-network/compensation#26

@cbeams

This comment has been minimized.

Member

cbeams commented Feb 1, 2018

2018.01 report

We added a number of new roles over the last month, including:

  • P2P Network Developer (#62)
  • JavaFX UI Developer (#63)
  • Support Staff (#64)
  • Events Maintainer (#65)
  • Bitcoin Node Maintainer (#66)
  • Bitcoin Node Operator (#67)

See each for details.

As for ownership of this role (the Roles Maintainer role), I worked with @csacher over the last couple of months to hand off certain responsibilities, and in the end it was probably too early to try to do this. I'm still working out the design of things here, and I ended up running @csacher around in circles trying to hand stuff off to him that wasn't really ready to be handed off. Sorry about that, @csacher, and thank you for everything you did! I've removed you as an assignee from this role for now so that we're clear there are no further expectations.

Role specifications and bonding continue to be on hold as other priorities have taken precedence. I'll get back to this as time allows.

/cc bisq-network/compensation#35

@cbeams cbeams referenced this issue Feb 1, 2018

Closed

For January 2018 #35

@cbeams

This comment has been minimized.

Member

cbeams commented Mar 1, 2018

2018.02 report

No new roles were added this month, and that's the first time that's happened since the inception of phase zero in October. This means we're approaching a reasonably complete model of all the roles required to make the Bisq DAO function. There are 44 roles at present—and plenty of them are labeled help wanted.

/cc bisq-network/compensation#40

@cbeams

This comment has been minimized.

Member

cbeams commented Apr 4, 2018

2018.03 report

Since the inception of the roles repository, and the original writing of the Phase Zero paper, the idea has been to put together specifications for each role under the Bisq DAO. After 6 months, however, this hasn't happened, and the fact that it hasn't been able to get priority during that time I think this tells us that we simply don't need it yet.

So I'd like to officially defer putting together specifications for each role, and instead make it a practice for everyone playing a role to create monthly report comments like this one for each of the roles they play. @ripcurlx, @alexej996 and I have already been doing this for months, and it's been a simple and effective way to share information about what's going on with each role. Just as importantly, it is a kind of 'heartbeat' signal that lets everyone know that role assignees are in fact on top of their responsibilities.

See my comments to @mrosseel to this effect in the Freenode Admin role at #22 (comment), and stay tuned for a proposal issue I'll create shortly regarding this change.

/cc bisq-network/compensation#57

@cbeams

This comment has been minimized.

Member

cbeams commented May 4, 2018

2018.04 report

There were a lot of changes around roles this month. Some of the following items are still in progress as I write, but I'm listing them all out here to give a comprehensive overview.

/cc bisq-network/compensation#68

@cbeams cbeams referenced this issue May 4, 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.

Member

cbeams commented Jun 1, 2018

2018.05 report

Thanks everyone for continuing to write monthly report comments on your respective role issues. I think that's beginning to work quite well.

As mentioned in last month's report, role specs are being phased out in favor of a more integrated approach, where roles will be documented under the new docs.bisq.network website. In this new approach, rather than having a dedicated documents for, say the "Proposals Maintainer", we have a dedicated document for the concept of "Proposals" under the Bisq DAO, and then there is a section in that doc for the different roles that interact with proposals. And of course one of these roles is that of "Proposals Maintainer". You can see one of the first examples of this at https://docs.bisq.network/proposals.html#maintainer. I like this approach quite a bit better, because it focuses on what matters (Proposals) rather than focusing on what is basically an implementation detail (the need for a Proposals Maintainer). This way, lots of people are likely to see and read about the various roles under the Bisq DAO in a more intuitive and natural context than if we went ahead with dedicated "role spec" documents as originally envisioned.

I have yet to add the new roles and GitHub teams mentioned in last month's comment. I'll get that done as soon as I can.

/cc bisq-network/compensation#74

@cbeams cbeams referenced this issue Jun 1, 2018

Closed

For May 2018 #74

0 of 5 tasks complete

@ManfredKarrer ManfredKarrer self-assigned this Jun 20, 2018

@ManfredKarrer

This comment has been minimized.

Member

ManfredKarrer commented Jun 30, 2018

2018.06 report

I took over primary role ownership that month.

Nothing to report so far.

/cc bisq-network/compensation#92

@cbeams

This comment has been minimized.

Member

cbeams commented Jun 30, 2018

2018.06 report

Refining the documentation and process around roles has been a major focus for me over the last week, primarily because of the efforts to hand off some of my roles to other contributors. That effort has shined a pretty bright light on the gaps, and so I'm at work now on (a) making it much clearer how things should work and (b) making it possible for things to work without requiring me or Manfred to invoke GitHub Owner rights along the way. My work-in-progress 'Roles' doc at bisq-network/bisq-docs#46 is nearing completion, and I'll have a number of other updates on this front over the days to come.

Thanks again to everyone who has stepped up to take on some of my roles. In the meantime, I'm going to continue owning this one until (a) it's really ready to hand off and (b) a contributor shows up who is really passionate about owning this infrastructure and process (it's pretty cool stuff, actually, and at the heart of our DAO organizational approach).

/cc bisq-network/compensation#89

@cbeams cbeams removed the help wanted label Jun 30, 2018

@cbeams cbeams referenced this issue Jun 30, 2018

Closed

For June 2018 #89

6 of 6 tasks complete
@cbeams

This comment has been minimized.

Member

cbeams commented Jul 31, 2018

2018.07 report

There was a lot delivered around roles this month, but I've already documented it and claimed compensation for it as individual contributions in my compensation request for this month (linked below). Here's a screenshot of what I wrote there:

image

BSQ requested: 25 (for basic administrative overhead, including writing this update)

/cc bisq-network/compensation#101

@cbeams cbeams referenced this issue Jul 31, 2018

Closed

For July 2018 #101

@cbeams

This comment has been minimized.

Member

cbeams commented Aug 31, 2018

2018.08 report

Nothing to report.

BSQ Requested: 25

/cc bisq-network/compensation#114

@cbeams cbeams referenced this issue Aug 31, 2018

Closed

For August 2018 #114

@cbeams

This comment has been minimized.

Member

cbeams commented Sep 30, 2018

2018.09 report

Nothing to report.

BSQ Requested: 25

/cc bisq-network/compensation#139

@cbeams

This comment has been minimized.

Member

cbeams commented Oct 31, 2018

2018.10 report

Nothing to report.

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.

Member

cbeams commented Nov 30, 2018

2018.11 report

Several new roles were created this month:

  • Rocket.Chat Admin #79, to capture the work @m52go is taking on to manage this potential new Slack alternative (and we may want a separate role for Rocket.Chat Operator, which @sqrrm @chirhonul is taking on)
  • Arch Linux AUR maintainer #78, capturing the work @freimair has already been doing for some time
  • Domain name owner #77, to distinguish the role of owning and renewing Bisq domain names from the work of managing Bisq's DNS

BSQ requested: 25

/cc bisq-network/compensation#179

@sqrrm

This comment has been minimized.

Member

sqrrm commented Nov 30, 2018

Correction, @chirhonul is hosting the rocket.chat.

@cbeams

This comment has been minimized.

Member

cbeams commented Dec 1, 2018

Sorry, of course that's right. Thanks. I've corrected the original post above.

@cbeams cbeams assigned m52go and unassigned cbeams Dec 7, 2018

@cbeams

This comment has been minimized.

Member

cbeams commented Dec 7, 2018

@m52go has agreed to take on this role going forward. Thanks, Steve!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment