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

[sqrrm]

The lack of a CEO type of entity within Bisq is something that has been discussed before and no good solutions have been found. I think the closest model we work after is Bitcoin where everyone works on what they see fit and only very small changes can be done, and when done, very slowly since a rough consensus has to be found before moving ahead.

In Bisq we have the benefit of the voting to move decisions forward much faster, but we lack the resources and direction. Many of the point suggested here are not even contentious, just a lot of work. I think it's fine that everyone works on what they want, but it is a problem that progress is slow, many times due to the bisq client being monolithic. It makes it very hard to change anything without causing trouble for other developers in other domains and it makes it slow to move forward with dev work. Now that the API is ready I think some points could be worked on much more independently, moving certain projects forward without depending on some central reviewer or other issues stemming from the complex nature of the bisq client.

@flix1 As an aside I can mention that I'm trying to get the BSQ atomic swaps working. It touches almost all modules, p2p, dao, trade protocol, offer protocol, desktop. It would also not be easy to extend the atomic swap functionality without dependence on a wallet for the asset that needs to be swapped, how else do you verify your tx?

To get a bit more direction perhaps it would be good for a non dev to partner with a dev for work that needs to be done. Especially good if the non dev contributors would act a bit as a patron to 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-449619
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210308/223ad853/attachment.htm>