From 59655ac5ef7578da7d37698ae3e7eb0143fa6e85 Mon Sep 17 00:00:00 2001 From: Chris Beams Date: Fri, 4 May 2018 15:45:29 +0200 Subject: [PATCH] Replace README content with link to new roles doc See bisq-network/bisq-docs#46 --- README.adoc | 220 +--------------------------------------------------- 1 file changed, 3 insertions(+), 217 deletions(-) diff --git a/README.adoc b/README.adoc index 1e9ff1b..258247b 100644 --- a/README.adoc +++ b/README.adoc @@ -1,219 +1,5 @@ -= Bisq DAO Roles -:gh-org: https://github.com/bisq-network -:issues: {gh-org}/roles/issues -:specs: {gh-org}/roles/blob/master += Bisq Network Roles -This repository provides complete information about all roles within the Bisq DAO. It provides the reader with details about the purpose, motivation, privileges, requirements and responsibilities of all roles. This ensures clarity about one's own role, helps in understanding other roles and facilitates the compensation process. +The issues in this repository track specific _roles_ within the Bisq DAO, including who owns each role, and they provide a space for those role owners to write monthly reports in the form of comments on their respective issues. -The owner of a given role is responsible for creating and maintaining their role specification as an AsciiDoc file here in this repository. Each role also has a dedicated GitHub issue in this repository, where ownership of a given role is tracked by issue assignment. Owners issue periodic (usually monthly) reports in the form of comments on their role issue. - -== How to Create a New Role - -1. Discuss and make sure there is consensus about the need for and purpose of this role in the Slack `#roles` channel or elsewhere. -1. Create a GitHub issue that will be used to track this role ({issues}[see other role issues for examples]). -1. Create and edit a _specification_ document for this role based on `SPEC-TEMPLATE.adoc`. See existing role specifications linked from the table below for examples. -1. Submit the new specification as a pull request. Be sure to mention the role issue ID, e.g. {issues}/28[#28] somewhere in the pull request title or description to ensure that the pull request shows up in the timeline of the role issue. Also, be sure to edit this file (`README.adoc`) and add an entry to the table of roles below. -1. The {issues}/28[roles repository maintainer] will review your new role spec, provide any feedback, and merge it when ready. - - -== Roles Overview - -|=== -|Role |Issue |Specification |BSQ Bond - -|Ambassador -|{issues}/35[#35] -|TODO -|TODO - -|Arbitrator -|{issues}/13[#13] -|TODO -|4000 - -|{gh-org}/btcnode[Bitcoin Node] Maintainer -|{issues}/66[#66] -|TODO -|TODO - -|{gh-org}/btcnode[Bitcoin Node] Operator -|{issues}/67[#67] -|TODO -|TODO - -|{gh-org}/bitcoinj[Bitcoinj] Maintainer -|{issues}/8[#8] -|TODO -|5000 - -|https://bitcointalk.org/index.php?topic=647457[BitcoinTalk] Admin -|{issues}/37[#37] -|TODO -|500 - -|{gh-org}/compensation[Compensation] Maintainer -|{issues}/31[#31] -|TODO -|TODO - -|{gh-org}/analytics[Analytics] Maintainer -|{issues}/40[#40] -|{specs}/analytics-maintainer.adoc[analytics-maintainer.adoc] -|TODO - -|{gh-org}[DAO] Maintainer -|{issues}/4[#4] -|TODO -|5000 - -|{gh-org}/dns[DNS] Admin -|{issues}/18[#18] -|TODO -|20000 - -|{gh-org}/docs[Docs] Maintainer -|{issues}/29[#29] -|TODO -|TODO - -|{gh-org}/exchange[Events] Maintainer -|{issues}/65[#65] -|TODO -|TODO - -|{gh-org}/exchange[Exchange] Maintainer -|{issues}/3[#3] -|TODO -|20000 - -|https://explorer.bisq.network/testnet/[Explorer] Operator/Maintainer -|{issues}/11[#11] -|TODO -|2000 - -|https://www.facebook.com/bisqnetwork/[Facebook] Admin -|{issues}/48[#48] -|TODO -|TODO - -|https://bisq.community[Forum] Operator -|{issues}/19[#19] -|{specs}/forum-operator.adoc[forum-operator.adoc] -|TBD - -|Founder -|{issues}/1[#1] -|TODO -|TODO - -|https://webchat.freenode.net/?channels=bisq,bitsquare[Freenode] Admin -|{issues}/22[#22] -|TODO -|TODO - -|{gh-org}[GitHub] Admin -|{issues}/16[#16] -|TODO -|TODO - -|{gh-org}/growth[Growth] Maintainer -|{issues}/42[#42] -|{specs}/growth-maintainer.adoc[growth-maintainer.adoc] -|TODO - -|[Keybase Admin -|{issues}/60[#60] -|TODO -|TODO - -|https://lists.bisq.network/pipermail/bisq-contrib/[Mailman] Operator -|{issues}/27[#26] -|{specs}/mailman-operator.adoc[mailman-operator.adoc] -|2000 - -|https://markets.bisq.network[Markets] Website+API Operator/Maintainer -|{issues}/9[#9] -|TODO -|TODO - -|{gh-org}/monitoring[Monitoring] Operator/Maintainer -|{issues}/10[#10] -|TODO -|TODO - -|https://us9.campaign-archive.com/home/?u=fee3c64b1504e7835a98b0ed3&id=dc09b9ca64[Newsletter] Editor -|{issues}/27[#27] -|TODO -|2000 - -|{gh-org}/pricenode[Pricenode] Maintainer -|{issues}/5[#5] -|TODO -|5000 - -|{gh-org}/pricenode[Pricenode] Operator -|{issues}/14[#14] -|TODO -|TODO - -|{gh-org}/proposals[Proposals] Maintainer -|{issues}/30[#30] -|TODO -|TODO - -|https://reddit.com/r/bisq[Reddit] Admin -|{issues}/25[#25] -|TODO -|1000 - -|{gh-org}/roles[Roles] Maintainer -|{issues}/28[#28] -|TODO -|TODO - -|{gh-org}/exchange/tree/master/seednode[Seednode] Maintainer -|{issues}/6[#6] -|TODO -|5000 - -|{gh-org}/exchange/tree/master/seednode[Seednode] Operator -|{issues}/15[#15] -|TODO -|2000 - -|https://bisq.network/slack-invite[Slack] Admin -|{issues}/23[#23] -|TODO -|2000 - -|{gh-org}/support[Support] Staff -|{issues}/27[#27] -|TODO -|TODO - -|https://telegram.me/bitsquare[Telegram] Admin -|{issues}/24[#24] -|TODO -|500 - -|https://www.transifex.com/bitsquare/bitsquare/[Transifex] Admin -|{issues}/20[#20] -|TODO -|1000 - -|https://twitter.com/bisq_network[Twitter] Admin -|{issues}/21[#21] -|{specs}/twitter-admin.adoc[twitter-admin.adoc] -|2000 - -|https://bisq.network[Website] Operator/Maintainer -|{issues}/12[#12] -|TODO -|TODO - -|YouTube Admin -|{issues}/56[#56] -|TODO -|TODO - -|=== +See https://docs.bisq.network/roles.html for complete documentation.