[bisq-network/proposals] Establish project management process (#182)

Chris Beams notifications at github.com
Sat Jun 20 11:10:45 UTC 2020

Thanks, @wiz. As discussed in our team leads chat and most recent weekly call, I think it probably makes sense to rename @bisq-network/pmc to @bisq-network/projects-maintainer and treat it as a normal rules-based maintainer role, i.e. where the job is straightforward an non- or minimally-subjective: do triage on new projects to ensure well-formedness, mark project issues as approved or rejected based on feedback, etc. This can be a single-owner role, and all other, more subjective decision making like prioritization can happen as a function of the dev calls and the process around them. Budget allocation has to be worked in too, but that would remain the domain of the team leads as it already is.

The projects maintainer role duties would/should also include maintaining the process itself, i.e. keeping the docs up to date, working with contributors and team leads to make sure the process is working well. It's an important role that we need someone well suited to take on. It's not obvious to me who that should be, but in the meantime, the process is at risk if that role isn't filled. It can easily become an "everybody owns it, so nobody owns it" kind of thing. I'd just keep moving forward on the dev calls and getting that in order and make it known that we're looking for someone to own the project management process and be its maintainer.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200620/11c9ddaf/attachment-0001.html>

More information about the bisq-github mailing list