From d7cc271fe73c5e4bbb667b7da1dc14f2d8b3c744 Mon Sep 17 00:00:00 2001 From: Anna Cottrill Date: Wed, 17 Dec 2025 15:54:49 -0500 Subject: [PATCH] remove some references to forums --- src/content/docs/legal/community-support-policy.md | 1 - src/content/docs/legal/license.md | 4 ++-- src/content/docs/legal/security.md | 10 ++++------ src/content/docs/legal/subprocessors.md | 2 -- .../docs/staff/training/cross-platform-coordination.md | 3 +-- 5 files changed, 7 insertions(+), 13 deletions(-) diff --git a/src/content/docs/legal/community-support-policy.md b/src/content/docs/legal/community-support-policy.md index dbaaba2..1b66a50 100644 --- a/src/content/docs/legal/community-support-policy.md +++ b/src/content/docs/legal/community-support-policy.md @@ -24,7 +24,6 @@ This Community Support Policy establishes the framework for how community member This policy applies to all forms of support exchange within our community platforms, including: - Discord channels and direct messages -- Forums and discussion boards - Reddit community spaces - Social media interactions - GitHub collaborative spaces diff --git a/src/content/docs/legal/license.md b/src/content/docs/legal/license.md index 726a0f6..149058b 100644 --- a/src/content/docs/legal/license.md +++ b/src/content/docs/legal/license.md @@ -1877,7 +1877,7 @@ When We elect to provide notice of termination, such notice may be delivered thr **(a)** Email to Your last known email address; -**(b)** Posting on Our website, repository, or community forums; +**(b)** Posting on Our website or repository; **(c)** Direct communication through any platform or service You use to access Our Software; @@ -1927,7 +1927,7 @@ We reserve the unrestricted right to modify, amend, update, or replace any terms When We make changes to this Licence, We will make reasonable efforts to notify affected users through: -**(a)** Announcements in Our community forums and chat channels; +**(a)** Announcements in Our chat channels; **(b)** Updates and notifications in Our software repositories; diff --git a/src/content/docs/legal/security.md b/src/content/docs/legal/security.md index 5042fc4..6dcfa41 100644 --- a/src/content/docs/legal/security.md +++ b/src/content/docs/legal/security.md @@ -272,7 +272,7 @@ While we do not currently offer financial rewards, we deeply appreciate security **(a)** **Hall of Fame Recognition:** Public acknowledgement in our security contributors hall of fame; -**(b)** **Community Recognition:** Acknowledgement in our community forums and social media channels; +**(b)** **Community Recognition:** Acknowledgement in our social media channels; **(c)** **Professional References:** With your consent, we may serve as a reference for your security research activities; @@ -510,11 +510,9 @@ Additional resources available to security researchers: **(a)** **Documentation:** Comprehensive security policy documentation and guidelines; -**(b)** **Community Support:** Access to our community forums for general security discussions; +**(b)** **Educational Resources:** Links to security research best practices and legal guidelines; -**(c)** **Educational Resources:** Links to security research best practices and legal guidelines; - -**(d)** **Feedback Mechanisms:** Opportunities to provide feedback on our security policies and procedures. +**(c)** **Feedback Mechanisms:** Opportunities to provide feedback on our security policies and procedures. ## 11. POLICY UPDATES AND MAINTENANCE @@ -536,7 +534,7 @@ Changes to this Policy will be communicated through: **(a)** **Direct Notification:** Email notification to researchers who have previously submitted reports; -**(b)** **Public Announcement:** Updates posted on our website and community forums; +**(b)** **Public Announcement:** Updates posted on our website; **(c)** **Documentation Updates:** Version-controlled updates to our official documentation; diff --git a/src/content/docs/legal/subprocessors.md b/src/content/docs/legal/subprocessors.md index 666eb3a..19301bf 100644 --- a/src/content/docs/legal/subprocessors.md +++ b/src/content/docs/legal/subprocessors.md @@ -384,8 +384,6 @@ We will notify users of changes to subprocessor arrangements through: **(c)** **Service Notifications:** In-app notifications where technically feasible; -**(d)** **Community Announcements:** Public announcements in community forums. - ### 7.2. Types of Changes Requiring Notification Changes requiring advance notification include: diff --git a/src/content/docs/staff/training/cross-platform-coordination.md b/src/content/docs/staff/training/cross-platform-coordination.md index 7873c6e..744eade 100644 --- a/src/content/docs/staff/training/cross-platform-coordination.md +++ b/src/content/docs/staff/training/cross-platform-coordination.md @@ -60,7 +60,6 @@ This training operates within our policy framework: **Examples:** - **Discord**: Real-time moderation with immediate response capabilities -- **Forums**: Considered, documented responses with longer discussion threads - **Code Repositories**: Technical focus with professional communication standards - **Social Media**: Public-facing brand representation with broader audience considerations @@ -549,7 +548,7 @@ This training operates within our policy framework: ### 10.1. Scenario 1: Cross-Platform Crisis Coordination -**Situation**: A crisis situation occurs that affects multiple platforms simultaneously. The crisis involves a safety threat that's being discussed across Discord, forums, and social media. Information is spreading rapidly and inconsistently across platforms. +**Situation**: A crisis situation occurs that affects multiple platforms simultaneously. The crisis involves a safety threat that's being discussed across Discord, and social media. Information is spreading rapidly and inconsistently across platforms. **Your Response:** 1. How do you coordinate response across all platforms?