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

[Florian Reimair]

> _This is a Bisq Network proposal. Please familiarize yourself with the [submission and review process](https://docs.bisq.network/proposals.html)._

<!-- Please do not remove the text above. -->

- it feels like there is something wrong and not open-source when it comes to discussion and deciding priorities, be it for projects, bugs, dev issues or other topics
- lack of communication might just
  - paint a false picture of how things are handled
  - result in people loosing interest
- limiting budget isn't enough to focus our efforts
  - another big factor is the limited amount of resources (ie. people who can get stuff done)

- propose
  - revive the ol' dev calls but with a slightly changed concept
  - weekly or bi-weekly
  - open to everyone
  - go over projects and their priorities
  - go over issues and their priorities
  - assign people, ask for help
  - be open about what is important right now (not in depth, but provide references)
  - be open about the limited dev resources we have
  - allow everyone to participate in the discussion and let them bring ideas
  - so it is clear who is making the decisions (that would be all of us)
  - let the general public participate

format
  - jitsi meet
  - calls will be streamed to youtube
  - keep it compact and short
    - branch off focus-calls
  - agenda
    - give an overview what happened in the last week/weeks
    - revisit priorities of last call, shift if necessary
    - assign people
    - AOB
 


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