Roles Maintainer

[cbeams]

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

[cbeams]

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]

2018.01 report

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

• P2P Network Developer (Bisq P2P Maintainer #62)
• JavaFX UI Developer (Bisq Maintainer #63)
• Support Staff (L1 Support Agent #64)
• Events Maintainer (Events Maintainer #65)
• Bitcoin Node Maintainer (Bitcoin Node Maintainer #66)
• Bitcoin Node Operator (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]

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]

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]

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.

• @alfsbs took on the Payment Method Maintainer role (Payment Method Maintainer #38), welcome!
• @dsbeasley took on a secondary YouTube Admin role (YouTube Admin #56), welcome!
• @alexej996 has agreed to go from secondary Support Staff (L1 Support Agent #64) role owner to primary, thus he'll be taking over reporting duties there. Thanks, Aleksej.
• @alexej996 is also taking over primary ownership of the Reddit Moderator role (Reddit Moderator #25).
• @csacher has begun reporting on his activities as Facebook Admin (Facebook Admin #48). Thanks, Chris.
• @cbeams wrote a proposal around distinguishing primary / secondary role owners. This proposal was accepted, and is being enacted now.
• @cbeams wrote a proposal to have primary role owners write monthly reports. This proposal was submitted on short notice just prior to this month's voting round, but has already been accepted in the sense that pretty much everyone did it in conjunction with submitting their compensation requests. (thanks all).
• @cbeams wrote a proposal to drop the requirement for role specifications. This too was accepted, and stay tuned for the forthcoming roles documentation that will lay out a different, better way of handling things than the role specification approach.
• @cbeams decommissioned the Vimeo Admin role, along with its infrastructure, see Vimeo Admin #36 (comment) for details.
• @cbeams is in the process of decommissioning the MailChimp Admin role in light of our account getting shut down by MailChimp. See MailChimp Admin #27 for details.
• @cbeams in in the process of breaking up the old Exchange Maintainer role (Exchange Maintainer #3) to reflect the new modular repository infrastructure. This is not yet complete, but will be by the next voting/reporting round.
• @cbeams set up the new https://github.com/bisq-network/design repository in light of designers @pedromvpg and @diogorsergio getting involved and having cross-cutting design artifacts to work with, and a new Design Maintainer role and GitHub team are forthcoming.
• @cbeams and @blabno created the new https://github.com/bisq-network/bisq-assets repository, and a new Assets Maintainer role and GitHub team are forthcoming.

/cc bisq-network/compensation#68

[cbeams]

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

[ManfredKarrer]

2018.06 report

I took over primary role ownership that month.

Nothing to report so far.

/cc bisq-network/compensation#92

[cbeams]

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]

Cycle 51 report

Nothing to report

/cc bisq-network/compensation#1385

[cbeams]

Cycle 52 report

Nothing to report

/cc bisq-network/compensation#1404

[cbeams]

Cycle 53 report

Nothing to report

/cc bisq-network/compensation#1430

[cbeams]

Cycle 54 report

Nothing to report

/cc bisq-network/compensation#1452

[solomon1923]

Hi @cbeams

I made a proposal to assume the growth lead role it was accepted.

I would like to:

• Be added as a member of the role’s GitHub Growth Team
• Be added them as an assignee to role’s GitHub Growth Lead Issue
• Have the relevant access to growth repo to close, assign issues etc

Is this something you can help with? Or point me in the direction of someone that can?

[cbeams]

Hi @solomon1923

I would like to:

• Be added as a member of the role’s GitHub Growth Team

One of the @bisq-network/github-admins should be able to handle this for you (and the @mention in this sentence should serve as their Bat-Signal).

• Be added them as an assignee to role’s GitHub Growth Lead Issue

Done, as per #100 (comment)

• Have the relevant access to growth repo to close, assign issues etc

This should happen automatically when one of the @bisq-network/github-admins adds you to the @bisq-network/growth team.

[cbeams]

Cycle 55–56 report

Nothing to report

/cc bisq-network/compensation#1486

[solomon1923]

Please can one of the @bisq-network/github-admins add me to the growth repo.

[cbeams]

Cycle 57 report

Attempts to get @solomon1923 added to @bisq-network/growth (and by extension the growth repo) have stalled. Will escalate.

Nothing else to report.

/cc bisq-network/compensation#1517

[cbeams]

Cycle 58 report

Attempts to get @solomon1923 added to @bisq-network/growth (and by extension the growth repo) have stalled. Will escalate.

Sorry for the continued delay; @solomon1923, I'll follow up with you about this.

Nothing otherwise to report.

/cc bisq-network/compensation#1530

[cbeams]

Cycle 59 report

Attempts to get @solomon1923 added to @bisq-network/growth (and by extension the growth repo) have stalled. Will escalate.

This is now resolved, in that @solomon1923 has been invited to be the Owner of the growth team:

See #100 (comment) for more context on the growth team lead role and growth efforts in general.

Nothing further to report.

/cc bisq-network/compensation#1554

[cbeams]

Cycle 60 report

@runbtc has taken on the role of Operating the Grafana instance at monitor.bisq.network (#10), but the role issue has not been updated yet. These and possibly other role changes around running bitcoin and seed nodes will be updated shortly.

/cc bisq-network/compensation#1572

[solomon1923]

This is now resolved, in that @solomon1923 has been invited to be the Owner of the growth team:

Thank you for sorting this. I have now retired from the Growth Lead role #100 (comment)

I am not sure what needs happening with both the Growth repository and the Growth Lead role issue. I think they should both be closed. As I never accepted the invite to the role I am unable to do this.

[cbeams]

Cycle 61 report

Nothing to report.

/cc (no CR filed for cycle 61 due to travel)

[cbeams]

Cycle 62 report

Nothing to report.

/cc bisq-network/compensation#1618

[cbeams]

Cycle 63 report

Nothing to report.

/cc bisq-network/compensation#1636

[cbeams]

Cycle 64 report

Nothing to report.

/cc bisq-network/compensation#1656