[bisq-network/proposals] Change policy for compensation requests (#38)

chirhonul notifications at github.com
Wed Sep 12 06:39:43 UTC 2018


First, let me apologise for going on a tangent in my earlier reply. This proposal was on the topic of `change the current policy from "being shipped" to "being merged to master"`. I suggest we focus the discussion here on that topic, since it seems we are mostly in agreement on that being a reasonable thing to do.

Second, thank you for your characteristically detailed and thoughtful reply @cbeams. I agree bisq is quite different from a regular company, and I do appreciate what you are expressing in terms of the potential assymetry between transaction costs placed on bisq maintainers, and bisq contributors. I however also think that empiricism is a virtue. If we are finding ourselves several years into a project where almost everyone who understands it agrees that it is genuinely novel and a promising and potentially crucial "second financial layer" on top of Bitcoin as a base "economic layer", in @ManfredKarrer's terms, but despite this we still find ourselves with less than a handful of committed contributors, we may need to consider not just tweaks but indeed more radical adjustments to the incentive structures we have. Perhaps a reasonable model to discuss something like that would be a temporary suspension of principles we all deeply believe in during critical times, similar to how [Lincoln suspended habeas corpus during the American civil war](https://www.history.com/this-day-in-history/president-lincoln-suspends-the-writ-of-habeas-corpus-during-the-civil-war)? If the project dies due to being socially centralized on 1-3 individuals, the principles we hold may not matter much.

So as mentioned, perhaps it's best to continue any discussion that's outside the specific scope of this proposal in a separate forum, like a separate proposal?

-- 
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/38#issuecomment-420529983
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180912/02c2824b/attachment.html>


More information about the bisq-github mailing list