đ ââī¸Community Enforcement
Enforcement
We must seek to reduce or eliminate Violations as follows:
Community Moderation
Meetings
We expect all Tech Fleet meeting attendees to support our Collective Agreement and to interject if they perceive clear Violations. We expect attendees to report any clear Violations which arenât satisfactorily resolved during a meeting.
Discord
In our main online forum of Tech Fleet on Discord, all members may forward posts which contain clear Violations to our moderators. Note that Discord also allows members to Report a message, but that function notifies Discord, not our team. We must hold each other accountable for learning to report responsibly.
Removal Rules
We may remove and quarantine persons and content from our channels according to the following rules.
About removing persons: Removals and bans are neither permanent nor temporary; see Re-admissions.
General Rules
If we see a clear Violation in any of our channels:
We MUST remove the responsible actor(s) from all of our channels as soon as feasible.
We MUST quarantine or remove any prohibited media as soon as feasible.
We MUST inform the removed actor(s) as soon as feasible, identifying which Violation(s) occurred.
We MAY directly offer an opportunity for follow-up conversation.
If weâre unsure that a Violation has occurred in our channels, but upon reflection, we strongly suspect it, We SHOULD report an issue.
If anyone âover-reportsâ, we expect them to learn from our follow-up conversations!
Admin/Mod Enforcement Procedure
Assigned administrators and moderators bear special responsibility to ensure our compliance with general rules above. They should use the following procedure:
If you see a clear Violation anywhere in Tech Fleet:
Note the personâs name, username, or other identifying information such as email address.
Remove the responsible actor(s).
Screenshot and save the media (post, comment, etcetera) which contains Violations.
If deleting a post with attached commentary, also save all of that commentary.
Delete the content which contains Violations in our channels.
Privately notify the removed actor(s), including the reason for their removal.
Privately report all removals and deletions to all Tech Fleet leadership.
Moderators or Tech Fleet leadership MAY comment publicly on removal(s) and deletion(s) but are not obliged to comment publicly.
Automated Enforcement
In addition to manually enforcing the procedure above, our representatives may install bots which execute rules for automated muting, removal and quarantine in our digital systems. Any such automations must be compatible with this Collective Agreement and should be as simple, clear and accessible as possible.
Administrative Discretion
Emergency Action
Our leadership may use personal discretion to deal with emergencies which are not addressed by this policy, but they must explicitly justify any such decisions. They will also bear special responsibility to update this Collective Agreement, if feasible, to sufficiently address such emergencies in the future.
We will review any emergency actions which are reported.
Misalignment
Our leadership may, by mutual consent, remove anyone who seems misaligned with Tech Fleet despite receiving sufficiently helpful orientation and feedback within our community. This may include cases of apparent bad faith behavior.
Re-admissions
Persons who are removed from our channels may always contact safespace@techfleet.org to discuss any potential conditions for re-admissions.
We consider re-admission discussions if someone is removed due to insufficient orientation.
We will respond as promptly as feasible to such messages, or provide explanations of unexpected delays.
Outside of clearly-justifiable Emergency Action, Tech Fleet leadership should never readmit any removed digital accounts except with the consent of the Board and Guild leadership (The Safety Committee). They should, instead, discuss and process readmission requests per Transforming Tension & Conflict, as well as any supplementary policies and procedures which they create together.
Head to the Next Section
Last updated