Discord channels
I’d like to propose a reorg of the Discord channels, there are just too many of them.
Proposed roles:
Admin
Steering Committee
DAO Steward
DAO worker
Roles only set by Admins, not self selected.
Proposed channels
👋 Welcome [New category name for “Notifications/Rules”, available to all]
• about-FIO [New channel name for “welcome”, keep as read-only, add additional resource links for deeper education on Protocol + DAO]
📢 • announcements
• rules
🐦 • twitter-feed
Support [New category name for “Help Center”, available to all]
• documentation [Read-only channel that provides links to key docs in Dev Hub, Knowledge Base?]
• integrator-help
❓ • inquiries
⛔️ • report-scams [New channel name for “report-spam-or-phishing”]
• submit-ticket [New channel name for “!?support-ticket!”]
Community Convos [New category name for “Discussion Groups”, available to all]
• general
• governance
• ideas
🦄 • jobs-bounties [Read only, wherein we list open bounties but direct all listings to Jira “FIO Contributors DAO” where interested parties can submit proposal for eval by the SC]
• marketplace [Add a public channel wherein users can coordinate domain trading p2p?]
• memes
• shout-outs [Move “cheers-for-peers” beneath public “Community Convos” to facilitate community-wide positive recognition / convo?]
FIO DAO [New category name for “DAO Work”, available to all]
• general
• dashboard
• domain-marketplace [Rename from fio-escrow-marketplace]
• ledger
• marketing
🤝 • partnerships [New channel name for “business-development”, same purpose]
• registration
• reporting
• wrapping [New channel name for “token-domain-wrapping”]
Main Stage (public)
voice (public)
Core-chain
general
tools-notifications (public) [Use existing]
sdk-notifications (public) [Use existing]
core-notifications (public) [Use existing]
pipeline-notifications (public) [Use existing. Not sure if you want to redirect the dashboard and registration CI pipeline notifications to a different channel? I am okay with keeping all pipeline notifications in one channel.]
internal (private) [Rename core-team-private]
voice (public)
(Internal Categories & Channels – available to DAO workers only)
Growth [Available to DAO workers only .. combine AM + BD + Marketing to facilitate more cross-function collab and comm]
general
account-management
integration-payments
business-development
marketing
graphics
website
marketing-pr
marketing-partnerships
Operations [Available to DAO workers only]
general
legal-financial
industry-news
out-of-office-notifications
steering-committee
notifications [consolidate dashboard and registration notifs]
Partner Channels [New category name for “Protocol/Service Provider Communication”]
Comments
I agree with @Emily Mader. I would propose retaining one general “marketing” channel under “DAO Work - Available to all,” and moving all marketing channels meant for active planning and execution of approved / funded initiatives under “DAO Internal - Available to DAO workers only.”
I’ve pulled together some of my thoughts on design / organization below. Have retained all of your original line items, @DAO Steward .. have just re-orged a bit, often only alphabetically. @Emily Mader please feel free to add any additional channels you think would be beneficial per your comment above (e.g. public-facing feature-based, additional channels for AM / BD, etc.) .. I tried to focus on Pawel’s provided channels + shaking out Marketing channels first.
Think it generally might be beneficial to keep everything community-facing very community-oriented. Have also played around with breaking out internal DAO-worker channels by workstream, but just an idea.
(Public Categories & Channels – available to all)
👋 Welcome [New category name for “Notifications/Rules”, available to all]
• about-FIO [New channel name for “welcome”, keep as read-only, add additional resource links for deeper education on Protocol + DAO]
📢 • announcements
• rules
🐦 • twitter-feed
Support [New category name for “Help Center”, available to all]
• documentation [Question: should we add a read-only channel that provides links to key docs in Dev Hub, Knowledge Base?]
• integrator-help [Question: should we move “integrator-help” channel beneath “Support” category?]
❓ • inquiries
⛔️ • report-scams [New channel name for “report-spam-or-phishing”]
• submit-ticket [New channel name for “!?support-ticket!”]
members [Question: remove? Doesn’t seem to be active]
Community Convos [New category name for “Discussion Groups”, available to all]
• general
• governance
• ideas
🦄 • jobs-bounties [Consider making this read only, wherein we list open bounties but direct all listings to Jira “FIO Contributors DAO” where interested parties can submit proposal for eval by the SC]
• marketplace [Question: add a public channel wherein users can coordinate domain trading p2p?]
• memes
🤷 • random
• shout-outs [Question: move “cheers-for-peers” beneath public “Community Convos” to facilitate community-wide positive recognition / convo?]
integrator-help [Moved beneath “Support” category]
FIO DAO [New category name for “DAO Work”, available to all]
• general
• core-chain
• dashboard
• domain-marketplace [Rename from fio-escrow-marketplace]
• ledger
• marketing
🤝 • partnerships [New channel name for “business-development”, same purpose]
• registration
• reporting
• wrapping [New channel name for “token-domain-wrapping”]
integration-support [Question: what’s the difference between this channel and “integrator-help” under “Public Groups”?]
domain-sales [Question: should we consider moving this to internal for similar reasons as Marketing?]
marketing-website [Moved beneath “DAO Internal” for protection of market impact + performance / NDA purposes as mentioned by @Emily Mader]
partner-marketing [Moved beneath “DAO Internal” for protection of market impact + performance / NDA purposes as mentioned by @Emily Mader]
content-pr [Moved beneath “DAO Internal” for protection of market impact + performance purposes as mentioned by @Emily Mader]
events [Moved beneath “DAO Internal” for protection of market impact + performance / NDA purposes as mentioned by @Emily Mader]
(Internal Categories & Channels – available to DAO workers only)
Development Workstream ? [Available to DAO workers only .. defer to Pawel, Eric]
Channel 1
Channel 2
Channel 3…
Growth Workstream [Available to DAO workers only .. combine AM + BD + Marketing to facilitate more cross-function collab and comm]
general
account-management
integration-payments
business-development
marketing
marketing-content-pr
graphics
marketing-events
marketing-partnerships
marketing-social
marketing-website
Operations Workstream [Available to DAO workers only]
general
legal-financial
internal-support
industry-news
out-of-office-notifications
steering-committee
notifications
dashboard
registration
cheersforpeers [Moved under “Community Convos”, made available to all]
Partner Channels [New category name for “Protocol/Service Provider Communication”]
I like it added to main page with a few minor tweaks. @Eric Butz chime in
Now that I see the updated list. I am not sure we need so many internal marketing channels (especially since not many of them get used currently and there is a lot of overlap).
I think we could have:
Growth Workstream:
Marketing
Graphics
Marketing website (I suggest making this a thread. I assume once the marketing website work is done, this won't be very active and thus can be archived.)
Marketing - PR
Marketing - Partnerships
For the Community Convos grouping, I would remove the “random” channel. We don't have enough people talking to need a random channel right now.
I like this – updated in main.
I think overall I am hesitant to have marketing channels be public. @Ash Howe, feel free to provide your thoughts.
PR I cant see as being public. A lot of PR is based on things being ‘newsworthy’. If the community knows about a subject then that item is no longer newsworthy.. and that would impact how things are picked up by journalists. Additionally sometimes PR relies on ‘exclusivity’, meaning that only the news outlet has information on this particular piece of news. If everyone has access to it.. then that advantage is effectively lost.
Additionally, this is a similar situation when it comes to announcements. A lot of the marketing work has some element of announcements. If everyone knows about what is about to happen as we are planning announcements… then is it really an announcement. I feel like this would significantly impact the ‘punch’ of a particular news/announcement. It will also impact messaging as discord users can just announce it on our behalf before we are ready. It will be more work for us to adjust the messaging that is already out there in the community. Additionally, some partners are obviously not DAOs, and have certain ideas about how they want information out there. Some partners signed NDAs for example. We cannot have things out there for the public view, as that will impact some of our partner relations.
With that in mind.. I definitely think that partner marketing should be an internal channel. Unsure what @Ash Howe's thoughts are general product marketing. But I feel like an internal channel is needed for this as well when I think about the situation we had with the staking announcement.
I think when it comes to the general promotion of the FIO products that have already been announced and ‘out there’, like FIO Crypto Handles, requests, etc…. I think this would make sense to be public and have people contribute.
I also think we need internal biz dev as we currently don’t have that and I think it will be useful.
I don't think we need internal support. That type of info can be posted under internal general?