Difference between revisions of "Community Manager"

From Bisq Wiki
Jump to navigation Jump to search
m (Fixed links)
m (Reverted edits by HunterNyan (talk) to last revision by Plebeian9000)
Tag: Rollback
Line 2: Line 2:
== Issue ==
== Issue ==
* [https://github.com/bisq-network/roles/issues/95 Community Manager #95]
== Team ==
== Team ==
* [https://github.com/orgs/bisq-network/teams/community-managers @bisq-network/community-managers]
[https://github.com/orgs/bisq-network/teams/community-managers @bisq-network/community-managers]
== Duties ==
== Duties ==

Latest revision as of 05:29, 19 June 2020

Community Managers keep an "ear to the ground"—monitoring Bisq chatter throughout key social channels, reactively and proactively managing the channels they follow.






  • Follow social channels, keeping an eye out for posts explicitly mentioning Bisq as well as other posts that could be relevant to the project
    • Post notable findings in #pulse channel on Keybase
    • Relevant topics include:
      • key software updates
      • user feedback
      • opinions of the software
      • prevalent support issues
      • notable media mentions
      • misinformation
      • milestones
      • competitor intelligence
      • clever opportunities
    • Target channels:
      • Twitter
      • reddit (/r/bitcoin, /r/monero, /r/bitcoinbeginners, /r/xmrtrader, /r/cryptocurrency)
      • Telegram (bisq_p2p, monero, bitmonero)
      • Bisq GitHub
      • Bisq forum
      • YouTube
      • IRC and Matrix
  • Propagate any messaging relevant to current campaigns
  • Jump in to correct the record when inaccurate information is being disseminated
  • Join Bisq PULSE growth calls to discuss #pulse findings


  • Write access to the #pulse channel on Keybase


Not required.