[bisq-network/bisq] Priorities (Bigger Picture Solutions) (#5271)

[Christoph Atteneder]

@Conza88 Thanks for your compilation of priorities! I think it contains most of the challenge we need to tackle. Before getting into the resources allocation issue here is my personal priorities list for now.

## Operational priorities (need to be tackled)
- Bug fixes
- Upgrade Java/JavaFX (to get required security patches) #4242 
- Move nodes to Tor v3 until 3rd October 15th, 2021 (https://blog.torproject.org/v2-deprecation-timeline)

We do have a [priorities board](https://github.com/orgs/bisq-network/projects/18?fullscreen=true) which covers the current challenges, but no further roadmap. This is mainly because of the lack of resources. It is great to have a long-term roadmap, but we just need devs to be able to tackle them.

## Priorities
- API
- Improve reporting
- Reduce or eliminate mining fees wherever possible (BSQ, trade protocol,...)
- Improve onboarding

I think what Bisq needs is a small team (4-6) of full-time contributors, who steer the ship, so other contributors can come and go doing stuff for Bisq every now and then. I wasn't able to contribute more than to review/merge and ship new versions in the last couple of months because of my paternity leave which will continue until summer. I should be able to contribute more time to Bisq again afterwards. 

I personally think what we need to do is first to enable contributors to make changes to Bisq and to be able to see if it has a positive effect or not. To enable that the whole Bisq monitor project was started that never reached a stable state and was recently taken over by @Emzy (https://monitor.bisq.network/d/dEVJDduWz/key-performance-indicators?orgId=1). It has with `offers per node` and `trades per offer` two metrics that could be used to make comparisons between app versions if we improved the status quo or not. It is not perfect and has no control groups, but as we need to protect everyone's privacy it is a good first start. Unfortunately it is not working right now and I need to find the time to look into the implementation/setup to get it up and running again. 

A good first step could be as @sqrrm mentioned to establish small project teams of new devs and long-time non-dev Bisq contributors. Maybe we could come up with a list of non-dev contributors who are willing to join such project teams so they can be matched with new devs coming in.

-- 
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/bisq/discussions/5271#discussioncomment-453013
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210309/f847e8df/attachment.htm>