DAO Maintainer

[cbeams]

This role is responsible for maintaining the bisq-network/dao repository, which principally exists as a place to capture issues about the Bisq DAO itself, often dealing with high-level 'meta' issues that don't fit in any other specific repository, or dealing with DAO activities like monthly voting. The dao repository is also where we aggregate all our ZenHub boards. So (with the ZenHub browser extension installed), one can go to https://github.com/bisq-network/dao#boards and see "one board to rule them all"—where all other @bisq-network org repositories show up in the same place.

This role is not about maintaining BSQ validation logic, voting logic, or other DAO-related code that resides in the bisq-network/exchange repository. This is, for now, at least, still a function of the Exchange Maintainer role (#3).

[cbeams]

2017.12 report

The most important change we introduced this month around the DAO was beginning to institute a policy of radical transparency with our communications. Per this Slack chat, the idea is to have as many of our chats and discussions in public as possible, and to, by default, record and publish all our video calls (usually done via Zoom, which makes this easy). I recommend that folks read the first sections of Part III of Ray Dalio's book Principles for a deep dive on the philosophy behind and practicality of this approach.

We're also continuing the process of getting role specs and bonding officially in place. Some progress was made this month, and the goal is to get everybody bonded by Feb 1st. I'll keep managing that process over the coming month.

Here is a quick list of other more minor changes throughout the month:

• Created #growth infrastructure (Create #growth infrastructure  dao#16)
• Created #slack-ops infrastructure (Create Bisq DAO Google calendar dao#17)
• Created #youtube infrastructure (Create #youtube infrastructure dao#21) in preparation for the video(s) that @flix1 is managing production-wise
• Conducted November voting (Conduct November voting dao#18)
• Created the Bisq DAO Google calendar (Create Bisq DAO Google calendar dao#17) at https://bisq.network/calendar and integrated it with Slack

/cc bisq-network/compensation#26

[cbeams]

2018.01 report

Role specs and role bonding were entirely on hold this month while handling high-pri support issues around reimbursements.

Otherwise, here's what happened this month:

• Created #explorer infrastructure (Create #explorer infrastructure dao#23)
• Created #support infrastructure (Create #support infrastructure dao#27)
• Created #btcnode infrastructure (Create #btcnode infrastructure dao#28)
• Created #events infrastructure (Create #events infrastructure dao#29)
• Created #markets infrastructure (Create #markets infrastructure dao#30)
• Conducted December voting (Conduct December voting dao#26)

/cc bisq-network/compensation#35

[cbeams]

2018.02 report

• Conducted Feb 1st–3rd voting (Conduct February 1st–3rd voting dao#39). Note that these "conduct voting" issues will be managed under bisq-network/compensation going forward (e.g. Conduct Mar 1st–3rd compensation request voting compensation#44)
• @csacher revamped Bisq's presence on Facebook. We created a #facebook channel to organize future work. No dedicated repo yet, not clear there'll be one necessary.

Role specs and bonding remained on hold. Right now just updating the descriptions of role issues has been enough.

/cc bisq-network/compensation#40

[cbeams]

2018.03 report

This role is in a bit of flux at the moment. I introduced the https://github.com/bisq-network/bisq repository as a new, more intuitively-named "root level" repository in the @bisq-network GitHub organization (see README within), and the https://github.com/bisq-network/dao repository is now less important. It is still present, but it serves only to aggregate "non-code" repositories under a single umbrella. The following directory structure explains:

$ tree -d -L 2 ~/Work/bisq
bisq
├── btcnode
├── common
├── core
├── dao
│   ├── analytics
│   ├── archive
│   ├── bitcoinj
│   ├── btcd-cli4j
│   ├── compensation
│   ├── dns
│   ├── events
│   ├── forum
│   ├── github
│   ├── growth
│   ├── libdohj
│   ├── lists
│   ├── newsletter
│   ├── proposals
│   ├── roles
│   ├── slack
│   ├── style
│   ├── support
│   ├── twitter
│   └── youtube
├── desktop
├── docs
├── explorer
├── markets
├── monitor
├── p2p
├── pricenode
├── seednode
├── statsnode
└── website

This new organization is not perfect, but it does suggest that the main ZenHub board for code-related stuff should be https://github.com/bisq-network/bisq#boards and that everything else, i.e. all non-code, DAO-related stuff should be managed under a separate board at https://github.com/bisq-network/dao#boards

I need to think about it more and play around a bit, but such a split might make a lot of sense. Right now, our ZenHub board is basically unused, probably in part because there's just too much going on there. If we can narrow down the bisq board to being software-only, that might help make things more inviting and obvious as to what needs to be done.

Anyway, comments welcome, and I'll experiment with this over the coming month.

/cc bisq-network/compensation#57

[cbeams]

2018.04 report

Nothing to report. Again, the new purpose of the dao repository as described in last month's report comment is pretty minimal, so there probably won't be much to report on here until / unless something changes with it. I'm still not fully happy with this arrangement, but it's fine for the time being.

/cc bisq-network/compensation#68

[cbeams]

2018.05 report

@ManfredKarrer and @cbeams had useful conversations this month about the definition of the Bisq DAO, how it relates to—and is really separate from—BSQ. This naming and general distinction will likely find its way into the BSQ implementation, the in-progress efforts at docs.bisq.network, and ultimately into the way we think and talk about these items. More to come.

/cc bisq-network/compensation#74

[cbeams]

2018.06 report

Nothing to report.

/cc bisq-network/compensation#89

[cbeams]

2018.07 report

I'm closing this role for now, as it doesn't make much sense. It's really just about the bisq-network/dao repository at this point, which is a kind of aggregator for non-code / management repositories. It's more trouble than it's worth to keep the issue around and update it every month. If that changes, we can reopen this.

BSQ requested: 0

/cc bisq-network/compensation#101

[cbeams]

Note: I've also closed the few issues that were open in the bisq-network/dao repository and archived it.