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

[Chris Beams]

> I'm concerned that hyper-public conversations would be rigid

Based on prior experience with various kinds of calls around Bisq, I doubt that we'll have a problem with too many people joining. So long as we're not broadcasting invitations to the calls e.g. via Twitter, it will likely be something that folks already interested in Bisq (i.e. hanging out in Keybase) will pay attention to.

Regardless of how many people join the call in real time, though, I agree that posting the calls after the fact to YouTube can have a chilling / self-censoring effect, and will definitely prevent certain contributors from showing their faces and in at least one case from using their voice.

I think the main thing would be to get the calls scheduled and happening, to iron out a good process / regular agenda, and to evaluate as we go what the right tradeoffs are with recording and publishing the calls. We could err on the side of being more private / ephemeral for a start if that's what feels more comfortable. I think recording calls and uploading them to Keybase is a nice option; doesn't have to be YouTube. The value of the recorded calls is going to decay pretty quickly; the main use case for recording and uploading them is probably just to make sure those who would have but couldn't attend the calls can catch up afterward. I don't see a strong requirement to make them permanent and "hyper-public" on YouTube.


> If we want to invite users or outsiders for discussions

Again, I think if we target the invitations at @bisq-network/bisq-devs, that mostly who will attend is existing members or those who are interested in becoming members. (And for those who don't know, the criteria for inclusion in @bisq-network/bisq-devs is having had substantial contributions merged into the main repo within the last three months.)

-- 
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-643354960
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200612/a4260bc1/attachment.html>