Github Moderation Guidelines

This document clarifies guidelines for Github moderation in regards to the project’s Code of Conduct. Github Moderators are expected to adhere to these guidelines as a baseline for actions taken on the Github repository, but may deviate if they believe it is in the best interest of the community.

Note: If you believe these guidelines were not followed or were deviated from without good reason, you are encouraged to to contact staff via Discord or the forums, appeal your Github ban on the forums, or make a staff complaint. Incorrect enforcement of the Code of Conduct will not result in disciplinary action for staff when done in good faith, and is reserved for extreme cases where good faith does not exist.

Moderative Actions

Permanent Bans

Content that violate the examples listed under the “Be careful in the words that you choose.” bulletpoint of the Code of Conduct will result in an immediate permanent non-appeal ban and report to the Github org.

This may also apply should the offending content be located outside the Space Station 14 Github, such as on the Wizden Discord server, forums or elsewhere, at the Github Moderator’s discretion. PRs created by the offending user should be closed, though its contents may be picked up by another contributor and reused in a new PR should the license permit it.

Other Actions

As listed under the “On Community Moderation” section, content/comments that create an unwelcoming atmosphere for the project may result in moderative actions. Github Moderators have the following actions at their disposal:

• Hiding comments.
  • This should preferably be used for comments that are off-topic or otherwise inoffensive but fail to contribute to the discussion. Such comments should be marked as “Off-Topic” or “Spam”; while the interface provides other reasons for hiding a comment, they are better served below.
• Removing content & Providing a 24h Github ban.
  • For content/comments that are given in a non-constructive manner (examples listed in the Code of Conduct), the content may be removed even if it is partially constructive. Should this be necessary, the offending user should be given a 24 hour Github ban. While a ban may sometimes seem excessive, this is the only way we can communicate directly to a user that they have had actions taken against them.
• Long-duration Github bans.
  • Should a user repeatedly break the Code of Conduct, a Github ban for a longer duration may be warranted. The duration should be between 7 days to 1 month, at the Github Moderator’s discretion. Anything longer should be an appeal-only ban.
• Appeal-only bans.
  • An appeal-only ban may be given instead of a long-duration ban. These bans may only be appealed on the forums, at the soonest 6 months after the ban was issued.

Due to the limitations of Github’s moderation tools, the affected user can only receive a notification that an action has been taken against them, not the duration nor the reason. This is only possible via the “Block” option in an offending Github comment, which should be used if possible. Should an affected user inquire about their ban via one of the official channels, they are to be provided the reason.