[bisq-network/proposals] Introduce recurring "Bisq-Calls" (#231)
notifications at github.com
Sat Jun 20 10:06:09 UTC 2020
A couple thoughts:
- The title reads "Bisq Calls", but as I think we agreed (and as the text in the description and comments above reads), I think these are best called "dev calls" to clearly communicate the scope and intended audience. You might want to retitle the issue accordingly.
- One of the sticking points around better dev collaboration, and so a good thing to talk about in conjunction with these new calls, has been the lack of an effective dev email list. Any tech startup or larger software company would have this, and larger open source projects (e.g. Bitcoin, Linux) do too. I discussed this at https://github.com/orgs/bisq-network/teams/dao/discussions/1 a while back, and it came up again recently with @dmos at https://github.com/bisq-network/proposals/issues/222#issuecomment-645359924. The reason I think we need such a list is so that we can open up pure discussions, bounce around ideas, ask questions without (a) losing track of longer or more important conversations in the more ephemeral Keybase environment or (b) resort to prematurely creating proposal issues, which I think happens fairly often. If folks are agreed that a dev list would be a good thing, then the question becomes how to implement it. We have GitHub Discussions and could, for example, treat the @bisq-network/bisq-devs team as the Bisq dev email list, but the big downside of doing this is that the list isn't public. It can only be seen by those who are members of the bisq-network organization (and strictly speaking, we do archive all GitHub Discussion messages [here](https://lists.bisq.network/pipermail/bisq-github/)), but that's a read-only firehose no one is going to read and use in practice. Furthermore, there is no guarantee that members of @bisq-devs have their notifications configured correctly such that they actually get email delivery of messages sent to that team. So GH Discussions are there, but not ideal. Another option would be to use our Mailman server to maintain a proper bisq-dev at lists.bisq.network email list, and deal with making sure that active Bisq devs know about it and subscribe if they want to participate. Sorry for the sort of breathless brain dump here, but I do think a bisq-dev list could really help and wanted to suggest it in the context of rolling out the new dev calls.
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...
More information about the bisq-github