[bisq-network/proposals] Role owners should itemize compensation on a per-role basis in monthly compensation requests (#30)

Chris Beams notifications at github.com
Fri Jul 13 09:47:34 UTC 2018


@HarryMacfinned, this is becoming a different conversation now, and I'd prefer to take it offline from this specific proposal thread. I don't understand what you mean by "running things (nodes/repos/etc) in an unsafe way".

If this is about non-mission critical infrastructure that surrounds Bisq, such as YouTube, please keep in mind that it is completely optional for both users and contributors to interact with. We must strike a balance between "going where the (potential) users are" with tools like YouTube and Twitter and being perfectly decentralized, perfectly private, perfectly "safe". We could set up videos on DTube (or whatever) instead of YouTube, we could use Mastodon instead of Twitter, we could set up our own GitLab instance, etc etc, but all of this is a giant waste of time when what we need is to attract users and developers to Bisq. We need to show up where people are, such that they know we exist in the first place. Most people in the larger Bitcoin space still have no idea about Bisq.

Anyone is welcome to set up a Bisq presence on some YouTube alternative, anyone is welcome to start tweeting on Mastodon, etc. These things don't require permission from anybody. In the meantime, regarding contributor safety, what matters is that those contributors who wish to remain pseudonymous can. We have had several pseudonymous contributors who have contributed meaningfully to the project, and YouTube, etc were never a showstopper for them. The bottom line is that people need to be able to use GitHub. Everything else, at the end of the day, is optional.

If you have a specific proposal about changing infrastructure, please submit it as you see fit. If there's something I'm missing about your concerns, please take the time to make a clear case for them elsewhere. In any case, I'll look for interest and consensus from other contributors about this topic before I weigh in further about it.

-- 
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/30#issuecomment-404784298
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180713/98d5341c/attachment-0001.html>


More information about the bisq-github mailing list