Difference between revisions of "Community Manager"
Jump to navigation
Jump to search
Plebeian9000 (talk | contribs) m (specify role issue) |
m (Reverted edits by HunterNyan (talk) to last revision by Plebeian9000) Tag: Rollback |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 29: | Line 29: | ||
*** YouTube | *** YouTube | ||
*** IRC and Matrix | *** IRC and Matrix | ||
| − | * Propagate messaging relevant to current campaigns | + | * Propagate any messaging relevant to current campaigns |
* Jump in to correct the record when inaccurate information is being disseminated | * Jump in to correct the record when inaccurate information is being disseminated | ||
* Join Bisq PULSE growth calls to discuss #pulse findings | * Join Bisq PULSE growth calls to discuss #pulse findings | ||
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.
Issue
https://github.com/bisq-network/roles/issues/95
Team
@bisq-network/community-managers
Duties
- 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:
- 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
Rights
- Write access to the #pulse channel on Keybase
Bonding
Not required.
