[bisq-network/growth] [CALL] Addressing the Bisq Support Workflow - Bisq BRIEF for November 21 (#164)

[Christoph Atteneder]

> Can we do deeplinking? you know, like slack has: you log in the browser and then redirects to the app (although they are an electrum app, i.e. a mini browser).

Haven't looked into it how difficult it is to do it cross OS properly for Java apps.

 

> - What is the current state of support (to put everyone in the same page) @Steve, could you talk about this? - 10 min - What is the desired state of support (ignoring any constraints how would it work from the user and the DAO perspective, assuming problems exist and users don't have to become sys admins to get support) - I can moderate this one - 15 min - What are the tools / functionalities we need to have in place - 5 min - Outcome: a clear list of agreed functionality we need to do - What are the constraints we have in bisq specifically? - 5 min @chris, could you talk a bit about this? - Which tools exist that could fill these and which functionality would have to be built? @Steve and I can talk about these - 10 min - Assigning implementation goals - who owns what and who helps who? @Steve and I can also lead these, I can also take ownership of further research or writing docs/specs for whatever we uncover above - 10 min

Sounds good! For me the goal of this call is to have someone that leads this feature request, creates a proposal based on the decisions made in the call and after it finds consensus pushes it to get implemented and integrated into the client asap.

-- 
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/growth/issues/164#issuecomment-557107085
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191121/10a1c3a4/attachment-0001.html>