Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kickstart the Bisq Knowledge Base #156

Closed
FKrauss opened this issue Dec 20, 2019 · 2 comments
Closed

Kickstart the Bisq Knowledge Base #156

FKrauss opened this issue Dec 20, 2019 · 2 comments

Comments

@FKrauss
Copy link

FKrauss commented Dec 20, 2019

SUBJECT

Kickstart the Bisq Knowledge Base

OUTLINE

Problems

  • users raise issues on forum and/or keybase and don't get good responses (or any responses)
  • documentation is too convoluted, high level and not approachable enough for casual users - self service support is just impossible

Proposed Solutions

  • Have a knowledge base (core of this proposal)
  • have people who can regularly help users with support issues & an escalation process where higher impact cases are dealt with by Bisq contributors that have the appropriate experience for it (not in this proposal)
  • have a ticketing system (will be considered later, different proposal)

Knowledge Base

  • Build knowledge base to serve as practical, to-the-point guide to solve common issues.
  • Should use Zammad because: active, feature-rich project; multiple admin roles for support staff and translators; WYSIWYG editors (so no pull request workflow needed); self-hosted; has ticketing mechanism if we need it, etc.
  • Already have ~3 users interested in seeding content, which should cost at max. 2000 BSQ for seeding the content(assuming ~100 BSQ/hour rate for ~20 hours of work, capped at 500 BSQ per contributor)
  • Compensation and compensation guidelines - we don't yet have a proposal on how this work needs to be reported. We kindly ask contributors to show the value of the work provided (goes without saying: always keeping users' identities secret)
  • Initial deployment and ongoing hosting costs for this new infrastucture should cost ? BSQ.

How is KB different than Docs?

KB is a more fluid and tactical set of content pieces. It is meant to be dynamic as the issues appear, more knowledge is gathered and they eventually get a solution in a release or a workaround, for example. Plus, KB articles are more like tutorials and Docs are more like higher level specification of how the system works (non-technically).

KB is also different in the sense that more people can contribute to them as local relevance asks

Final Remarks

This proposal is not a complete solution to Bisq's support needs, but it should get support on the right track in the near-term. More proposals on this front will come regarding ticketing system and processes around managing the knowledge base and a possible support crew as well as related work

@FKrauss
Copy link
Author

FKrauss commented Feb 11, 2020

Things are moving in https://bisq.wiki/

@cbeams
Copy link
Contributor

cbeams commented Feb 27, 2020

Labeling as superseded by bisq-network/projects#14.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants