[bisq-network/roles] Founder (#1)

[Chris Beams]

## 2018.05 report

I missed posting my report here last month in part because I had a serious health issue come up and was short on time. I've since documented what's going on at https://chris.beams.io/posts/hello-aml/, and it's very likely that this issue will continue to affect my availability over the months to come.

This is actually a life-threatening problem, and while everything may turn out just fine in the end, it's appropriate for me to focus as much energy as I can now on turning over many of my roles and responsibilities to other contributors. It's been my express goal to do this in any case under the Phase Zero plan, but I now want to accelerate that process even more.

I believe the best way I can facilitate this transfer of knowledge and duties is to focus relentlessly on building out https://docs.bisq.network. This has already been a major focus for me over the last couple months, but I now plan to make it my main priority and to put my head down on it as much as possible. This effort will affect everyone, and you'll probably see and hear lots from me about it over the weeks to come. Keep in mind that the docs we're talking about here are not only the _user-facing_ docs that cover Bisq features; they are also the _contributor-facing_ docs that cover every aspect of Bisq DAO infrastructure and operations, roles and responsibilities, principles and processes. The goal for docs.bisq.network is that it become a comprehensive operators' manual for all things Bisq, one useful page at a time. This is why, as you can see in https://github.com/bisq-network/bisq-docs/pull/60, I'm currently working on a comprehensive table of contents for the site, even before all the pages are written. The purpose of that effort is to lay out a scalable structure for these docs into which everything we need to write can fit. As I continue to build out that table of contents, it should get clearer and clearer for everyone involved how important these docs can be for Bisq's future, as well as how you can personally contribute to them. 

So I have a couple things to ask of everyone:

1. Please pay attention to what's going on with docs, and understand that it is deeply strategic for us to build them out now. Good documentation can create a lot of leverage and can make a big difference as to whether Bisq and the Bisq DAO continue to scale up smoothly or not. If we continue growing like we have, we will soon be dealing with truly large numbers of users and contributors. We absolutely must have scalable ways to transfer knowledge and culture to them. Great docs are key to making that happen, and I'm hell-bent on putting them together now. This has to be a team effort to succeed though. Please ask yourself how and where you can contribute, and consider writing docs yourself, especially for anything you're already responsible for. @m52go has already contributed a lot, @blabno is working on some docs related to the new HTTP API right now, @alfsbs has started putting together docs for various payment methods, and everybody else is welcome to do the same for their own stuff too. Read the description and comments of https://github.com/bisq-network/bisq-docs/pull/60 for deeper context on all this, and come talk with us in the #docs Slack channel. We'll figure out what might make sense for you to work on, and even if you don't write anything, simply paying attention to what's going on, including reading and reviewing the docs that others write is itself an important contribution. If you haven't done so already, put a watch on the https://github.com/bisq-network/bisq-docs repository, and you'll be plugged into everything as it happens. Thanks!

2. Please start thinking about roles I currently play that you could take over. I've taken a conservative approach to handing off roles so far, and I need to relax and start giving stuff away to others, both so that I can focus on docs, and so that I don't burn myself out or try to do too much while I'm dealing with this health issue. Take a look at my recent compensation requests (including this month's at bisq-network/compensation#74) and ask yourself which roles you might be well-suited to take on. Even if it's a stretch for you, and you're not certain whether you're "qualified" or fully up to the requirements for some reason, that may not be a problem. What matters most is that you take on a role and manage it with pristine integrity, i.e. respond to all requests relating to that role in a timely fashion, monitor whatever resources you're responsible for, write monthly reports about your role on time every time, etc. It's all pretty simple really, and in most cases it's not the end of the world if you make a mistake. The most important things are that you're proactive and in communication at all times; that you take 100% responsibility for the roles you own and that you never let your role become someone else's problem. In any case, please look at the roles I'm playing and if you see one that makes you think "I would really like to do that work", then come talk to me about it the Slack channel associated with that role. Even if you think it won't work for some reason, I'd still like to have the conversation and see what might be possible. Thanks, all.

/cc bisq-network/compensation#74

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/roles/issues/1#issuecomment-393893906
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180601/37c8d7ee/attachment-0002.html>