[bisq-network/proposals] Define Maintainer rules (#119)

[erciccione]

> Any code change in the DAO package require a ACK/utACK from @ManfredKarrer. It is consensus code and carries high risk even with small changes which might look trival to other developers.

Isn't this a bottleneck? Woudn't be better to require at least two ACKs from core maintainers? Would also be a more decentralized solution than requiring an approval from one specific person (the approval is required for one *person*, not role or figure, which is a very centralized solution).

-- 
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/119#issuecomment-536181551
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190928/c97f1fd2/attachment.html>