Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document how to set up Discord for an SR year #126

Open
PeterJCLaw opened this issue Oct 16, 2021 · 3 comments
Open

Document how to set up Discord for an SR year #126

PeterJCLaw opened this issue Oct 16, 2021 · 3 comments
Labels
Content Relates to the content (i.e: SR documentation) rather than runbook build/serving platform

Comments

@PeterJCLaw
Copy link
Member

For SR2021 we used Discord in place of traditional forums. It seems likely that we're going to use (a fresh) Discord again for SR2022, so we should ensure that the configuration is documented (and ideally automated, but that may not be possible though would obviously supersede plain docs).

I summarised the setup of the SR2021 Discord at srobo/tasks#15 (comment), though that doesn't provide anywhere near the level of detail needed to set up an instance afresh.

@PeterJCLaw PeterJCLaw added the Content Relates to the content (i.e: SR documentation) rather than runbook build/serving platform label Oct 16, 2021
@PeterJCLaw
Copy link
Member Author

PeterJCLaw commented Oct 6, 2023

Other things to note:

  • the details of the content of the blueshirt-onboarding channel: safeguarding configuration, screenshots & rules, plus the bot which enables people to become blueshirts when they acknowledge completion of the rules. Blueshirts should:
    • disable Direct Messages and Activity Joining
    • set their name as their nickname (rather than an online handle)
    • read the safeguarding policy & our discord rules
  • the tags for within the "support" Q&A section (if using a Q&A mode and starting from scratch; if templating from a previous year then these are likely to be copied over)
  • if doing challenges and doing challenge-submissions as a channel then that channel may want to be made non-visible to competitors until Kickstart (hint: a Slack reminder is a good way to ensure we remember to make it visible at Kickstart)
  • if doing challenges and doing challenge-submissions as a Q&Q channel then consider adding tags for each of the challenges
  • if setting up by templating from the previous year's server then be sure to undo any changes which were made to prevent people from posting in the previous year's server

@PeterJCLaw
Copy link
Member Author

PeterJCLaw commented Oct 6, 2023

srobo/ansible#57 provides automation of setup for the gated-entry bot. Other aspects of the Discord server setup remain manual.

@PeterJCLaw
Copy link
Member Author

PeterJCLaw commented Oct 6, 2023

Tests:

  • competitors:
    • accept the invite using a random team's password
    • check that you can see & post in the expected channels -- the common social ones, the one for the team whose password you submitted, plus the support etc. Q&A sections (including new posts and replying there)
    • check that you were welcomed in the say-hello channel
    • check that you cannot post in e.g: the blog & announcement channels
    • check that you cannot see any channels which should be hidden (e.g: blueshirt ones, other teams, anything game related before kickstart)
    • check that you cannot see your welcome channel any more (so that you can't submit another password)
    • check that when joining the stage channel you cannot un-mute
  • volunteers:
    • accept the invite
    • check that you're dropped into the blueshirt onboarding flow (check any screenshots match the real UI and that the instructions make sense)
    • complete that flow
    • check that you can see & post in all the common social channels, the blueshirt channels and the team channels
    • check that you were not welcomed in the say-hello channel
    • check that when joining the stage channel you can un-mute
    • check that you do not have access to delete messages, kick or ban users (blueshirt or otherwise)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content Relates to the content (i.e: SR documentation) rather than runbook build/serving platform
Projects
None yet
Development

No branches or pull requests

1 participant