Roles

Duties are actions that must be performed for a certain resource or process to function normally.

For example, a repository maintainer’s duties include merging pull requests in a timely fashion, and a website operator’s duties include keeping the site available at all times.

Rights are special permissions or other access required to perform the Duties of a role.

For example, a repository maintainer’s rights include write permissions to their repository, and a website operator’s rights include administrative access to site hosting infrastructure.

Owners are contributors who have the Rights required to perform the Duties of a role.

One owner is designated as primary and any other owners are designated as secondary.^[1] The primary is responsible for performing the Duties of the role, while secondaries stand by, ready to take over for the primary at any time.

Each role should be documented at docs.bisq.network, not in a document of its own, but in a section of a document dedicated to the larger resource or process in question.

For example, there is no "Proposals Maintainer" document, but rather there is a Proposals document having a Maintainer section within.

Each role’s documentation should enumerate its Duties and Rights and link to its Team and Issue.

Each role has a dedicated GitHub team where each of the role’s Owners are members. The team is used to manage access to GitHub repositories that the role is responsible for and to send notifications to role owners with @mentions in GitHub issues and pull requests.

For example, the @bisq-network/desktop-maintainers team has write access to the bisq-network/bisq-desktop repository.

The primary role owner is also assigned as the maintainer of their role’s GitHub team, such that they may manage the team without requiring the intervention of a GitHub admin.

Each role has a dedicated GitHub issue in the bisq-network/roles repository, wherein:

See the docs/30[Proposals Maintainer] role issue for an example.

A Maintainer is a contributor responsible for enforcing process in a given GitHub repository.

Examples: docs/63[Bisq Desktop Maintainer], docs/30[Proposals Maintainer].

An Operator is a contributor responsible for keeping a given resource running and functioning normally.

Examples: docs/19[Forum Operator], docs/14[Bisq Pricenode Operator].

An Administrator ('Admin') is a contributor responsible for managing a given resource.

Examples: docs/16[GitHub Admin], docs/23[Keybase Admin].

A Moderator is a contributor responsible for enforcing process and standards in a given communications channel.

Examples: docs/37[Bitcointalk Moderator], docs/25[Reddit Moderator].

Primary role Owners should report once a month in the form of a comment on their Issue.^[2] The report should contain whatever information the owner believes would be valuable to other users, contributors and stakeholders. The comment should be formatted in Markdown as follows:

Where <content> is the content of the report itself, and <number> is the number of that contributor’s monthly compensation request. docs/16#issuecomment-393852612[Example].

Some roles may have nothing to report in a given month. In this case, a report should still be written stating that there is "nothing to report". docs/18#issuecomment-393217596[Example].

Primary role Owners should document changes to their role by submitting pull requests to their role’s Docs.

Primary role Owners should respond in a timely fashion to feedback comments on their role Issue, issues created in their repositories, @mentions of their Team, and questions in their Keybase channel.

Typically, proposing a new role is one part of a larger proposal to introduce some new resource or process.

For example, see the proposal to support Tor Relays and the resulting docs/72[Tor Relay Operator] role issue.

A primary role owner may add a secondary owner with the following steps:

A primary owner may transfer ownership to another with the following steps:

docs/28[bisq-network/roles#28]

@bisq-network/roles-maintainers