the-convocation
Setup public discord
I think the server should focus on being a support server and not really a chat server. I think we should follow suit with goatplace and have general chat locked behind a role and hidden away to discourage people from treating it like social hour and requiring a bunch of moderation.
A lot of this is just my thrown together thoughts I am likely missing things and obviously its all up for discussion but I wanted to get what my general framework is down for us.
Roles
- Lead Developers/Admin
- Keys to the Kingdom Users. Github Gods, Discord Owners, ETC
- Moderators
- Mod Powers Go BRRRRRRR
- All mod actions should go through bot so it can be logged.
- Core Developers
- Works on Venat-Core primarily
- Module Developer
- Works on Modules primarily
- Should be open to users that create third party modules/modules not made by the core staff?
- Developer
- Reveals Developer Channels
- Contributor
- Used to identify and recognize non-code contributors.
- Helpful Troubleshooters
- If we receive enough of this category we can break it out into its own role maybe or just do it from the start.
- Service/Command Testers
- If we receive enough of this category we can break it out into its own role maybe or just do it from the start.
- Translators
- If we receive enough of this category we can break it out into its own role maybe or just do it from the start.
- Friends?
- Role for people we know and trust to add to private social channels?
- Shouldn't have any increased permissions, @ everyone++ basically
Channels
Sub-Headings refer to the categories. Top level bullet points are channel-names, each tier in is additional information for clarification.
Admin
This category is entirely hidden from anyone who is not a mod/admin.
- Moderators
- To discuss moderation practices/discord server wide decisions.
- Mod Log
- Log of all moderation actions
- Read Only
Readme
All channels should be read-only for everyone. Primary Devs should have access to edit/post as needed.
- Announcements
- Rules
- Roles
- Bot Information
- Invite link
- Tech Stack
- GitHub
- Known Issues
General
Thin and Light. Chit-chat channels so if you don't want to chat you can just minimize and pretend they never existed.
- General
- Locked behind role
- Spoilers
- Locked behind role
- Because we will eventually have to deal with the inevitable patch day conversation.
Contributing
- Core Dev
- Module Dev
- Translators
- Contributor-Social
- Devs
- Translators
- Troubleshooters
- Feedback
- Module/Bot/Discord feedback?
- Lead Devs
- Core Devs
- Module Devs
- Moderators
- Maybe Contributors?
- Module/Bot/Discord feedback?
Support
- Known Issues
- Duplicate of the channel in Readme
- Read Only
- General Help
- Suggestions
- Suggestions should be submitted via a bot command, any message that isn't the command or from the bot should be deleted. The bot should then post an embed containing suggestion info and create a public thread off of the embed for suggestion discussion.
- Maybe attach two buttons to the suggestion embed to accept or decline it that will have the bot gen a github issue?
Very well thought out! Maybe a role for community developers - those who have services we'll be building integrations for.
I think I like the idea of merging Contributors into one role, especially for now.
So what I am actually doing for now after some more thought into it is breaking it out into multiple self-assignable roles and the contributor role is going to be for confirmed contributors.
For example:
This way someone who wants to translate can get the role and access the translation channels/be pinged for things via @ translators and find out how they can help, but they won't necessarily get the contributor role and access to contributor-social channel until they actually have confirmed contributions.
If there is any disagreement with this I can just nip it in the bud now and combine them into contributor.