Skip to content

Latest commit

 

History

History
45 lines (27 loc) · 2.02 KB

forum-operator.adoc

File metadata and controls

45 lines (27 loc) · 2.02 KB
Raw

Forum operator

Purpose

To maintain a forum suitable for support in using Bisq and other Bisq related discussions by users as well as members of the Bisq team.

Motivation

In order to provide quality user experience and understanding of the software, the Bisq forum is maintained to allow users to help each other with issues they might be having with the software, as well as with general questions about it, including feedback and suggestions users and others might be having about Bisq. Bisq developers, arbitrators and other roles are also present on this forum to provide further assistance and information if needed.

Privileges

The forum operator will have full administrative access to Discoruse forum, root access to server that hosts it, as well as the ownership of the domain of the forum.

General Requirements

Bonding

The operator MUST post a bond of TBD BSQ to assume this role.

Reporting

The operator SHOULD post a monthly report in the form of a comment on the linked GitHub issue for this role.

Secondary operator

The operator MUST ensure that there is a secondary forum operator with root access to the server that is hosting the Discourse forum. Secondary operator SHOULD respond to critical failures of the forum when primary forum operator is not available to respond.

Special Requirements

The operator MUST:

  • keep the Discourse installation up and running

  • keep the Discourse installation up to date with latest patches

  • download Discourse backups at least twice a week and store latest backup on a local drive

  • respond promptly to any questions / requests in the #forum Slack channel (recommendation: set your Slack notification preferences for that channel to be notified on "all new messages" so you don’t miss anything)

  • acknowledge / respond promptly to any issues submitted to the bisq-network/forum GitHub repository