Add Matrix Saftey Guild WG

content/foundation/working-groups/matrix-safety-guild.md

@@ -0,0 +1,4 @@
++++
+title = "Matrix Safety Guild WG"
+template = "governing-board/working_group.html"
++++

content/foundation/working-groups/working_groups.toml

@@ -207,6 +207,122 @@ sponsor = "Nico"
 matrix_room_alias = "#room-dir-wg-office:neko.dev"
 email = ""
 
+[[working_groups]]
+name = "Matrix Safety Guild"
+summary = "The Matrix Safety Guild is an autonomous community of safety contributors."
+description = """
+The guild provides space for contributors to discuss safety sensitive problems that they have encountered.
+"""
+charter = """
+### Overview
+
+The Matrix Safety Guild is an autonomous community of safety contributors.
+The guild encourages projects to share transparent updates in advance of upcoming work.
+In order to provide opportunity for early feedback and collaboration.
+The guild provides space for contributors to discuss safety sensitive problems that they have encountered.
+All members, including foundation staff and representatives participate within the guild as equal partners in mutual understanding and cooperation.
+This charter formalises the governance of the guild to safe guard the space.
+
+[Matrix Safety Guild - Join Here - Landing](https://matrix.to/#/#shared-safety-guild-landing:matrix.org)
+
+### Membership
+
+Membership is maintained to foster a collaborative environment of mutual trust between contributors.
+
+#### Eligibility
+
+To be eligible, applicants must either:
+
+- Contribute to an open source project in the Matrix ecosystem and be responsible for a safety-sensitive concern within that project.
+- Be actively involved with the moderation of a community on the public Matrix network that has significant ties to, or contributes feedback to, a safety guild project.
+
+Guild members may introduce other applicants to the gateway procedure when they can provide sufficient reasoning to the rest of the guild and address any raised concerns.
+
+### Gateway Procedure
+
+To join the guild, first join the [landing room](https://matrix.to/#/#shared-safety-guild-landing:matrix.org) and answer the following questions:
+
+1. Which project are you affiliated with? Can you please also link the repository url?
+2. Why are you interested in the guild specifically?
+
+This could be answered as follows:
+
+> Hi, I am applying to join the safety guild.
+>
+> I contribute to the Draupnir project https://github.com/the-draupnir-project/Drapunir. I want to share the work I have been doing with other safety contributors, particularly on standardising admin APIs between homeserver implementations.
+
+### Application Review Process
+
+1. On receipt of an application, the application is announced to other guild members internally and members are prompted to raise concerns.
+  They may ask follow-up questions or clarifications to the applicant.
+  Guild members should acknowledge this notification with a thumbs-up emoji.
+
+2. Chairs are responsible for ensuring enough feedback has been gathered before proceeding, including acknowledgements from active members.
+
+3. After feedback has been gathered, and there are no concerns remaining, a chair accepts the application and invites the applicant to the space.
+
+### Removal Process
+
+If trust has been violated, chairs are obligated to try to mediate the concern or remove contributors.
+
+### Confidentiality Notice
+
+#### Within the announcements channel:
+
+Project updates made in the announcements channel are public information unless explicitly stated in the announcement.
+
+#### Within the space:
+
+The [Chatham House Rule](https://www.chathamhouse.org/about-us/chatham-house-rule) applies within the safety guild space.
+The Individual membership roster of the working group is not to be disclosed publicly in order to protect the privacy of contributors.
+
+Security-sensitive or confidential details could intentionally or unintentionally be disclosed anywhere within the space as a result of discussion. These details may not even be explicitly noted.
+In these situations, members must maintain confidentiality in order not to undermine the mutual trust between guild members.
+
+Generally, members are expected to be considerate of the work of other projects and act responsibly with details discussed with them.
+
+Chairs reserve the right to remove members from the guild if it has been established that trust has been broken.
+
+### Responsibilities
+
+#### Reporting
+
+The guild produces a report to inform the T&S Committee of guild activities.
+The report is split into two parts: one informs the committee with a general summary of guild activity, and another specifically highlights anything that may require committee attention.
+
+The informational section summarises project updates and announcements, and any notable discussion undertaken within the guild.
+
+The attentive section is used to escalate discussion or make the committee aware of events.
+An example would be a new spam pattern within the community that is driving people away.
+
+#### The Foundation
+
+Amendments to the charter must be explicitly agreed by consensus of safety guild contributors.
+The sponsor and chairs are responsible for proposing amendments when changes are requested by the Foundation.
+Foundation staff or other representatives are not exempt from the membership process.
+
+### Decision Making
+
+All decisions are made by proposing changes and eliminating raised concerns.
+The autonomy of decision-making lies with contributors.
+
+### Chairs
+
+Chairs are highly trusted contributors responsible for maintaining the space. Chairs are selected by contributors in consensus.
+Chairs are responsible for ensuring continuity of the community. Chairs have final authority on a way forward in times of crisis.
+
+Should chairs become vacant, it is the responsibility of guild members to field volunteers and elect new chairs.
+Should the position of sponsor and both chairs become vacant or unaccountable, the Foundation's Trust & Safety Committee should organise replacements or amend the charter while respecting the membership process, autonomy, and consent of contributors.
+If this option has been exhausted, the Foundation should close the Working Group.
+"""
+committee = "Trust & Safety Committee"
+members = []
+chairs = ["Gnuxie, Cat"]
+sponsor = "@Gnuxie"
+meetings = ""
+matrix_room_alias = "#shared-safety-guild-landing:matrix.org"
+email = ""
+
 [[working_groups]]
 name = "Governance"
 summary = "Discuss the governance of the Governing Board and the Foundation"