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

[Florian Reimair]

> * 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.

well, "dev calls" has always been a working title for me. And I am not sure we agreed on calling them "Dev Calls". And it seems that the term "dev calls" does not at all communicate the scope. Here is why:

- these calls will be there to keep Bisq's projects aligned and running and our projects are not dev-team only (and Bisq grew to be not dev-team only)
- if we limit these calls to the dev-team, then important projects of other teams do not get the attention they may need
- having non-dev projects out of scope will not improve triaging of non-dev projects

but certainly, I agree that the name needs to be more specific. Still a working title. Will think about it though.

-- 
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-647528171
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200622/3cd9b9cc/attachment.html>