Discord channels

Owned by Pawel Mastalerz
Last updated: May 25, 2022
2 min read

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”]