[bisq-network/proposals] [WIP] Introduce recurring "Dev-Calls" (#231)

[Chris Beams]

As discussed yesterday, a big +1 from my side on establishing these calls. I'd lean toward a once-per-week cadence and back off if that feels like too much. As I've mentioned at https://github.com/bisq-network/proposals/issues/182#issuecomment-643223865 and https://github.com/bisq-network/projects/issues/1#issuecomment-643241451, I think these dev calls can be an excellent way to implement the (bi-)weekly reviews specified in the project management process (see https://bisq.wiki/Project_management#Review). That part of the documentation should be tweaked as appropriate to make it clear they are weekly, and that review happens as part of the dev calls, not in its own dedicated call, but my point is that they are, or can be, really one and the same thing. The project management process can be used to drive (much or most of) the dev call agenda. Talk about in-flight high-priority projects that need assistance, talk about new projects that have been proposed since the last call, etc.

In any case, I think these calls are a big opportunity to rally current and future @bisq-network/devs around what's most important, to better focus our efforts, and to really lock in the project management process as a core part of the way we work.

-- 
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/proposals/issues/231#issuecomment-643254217
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200612/05be8f1c/attachment.html>