remove some references to forums
Node.js CI / Lint and Test (pull_request) Successful in 57s
Security Scan / Security Audit (pull_request) Failing after 5m4s

This commit is contained in:
2025-12-17 15:54:49 -05:00
parent b718aa650b
commit d7cc271fe7
5 changed files with 7 additions and 13 deletions
@@ -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: This policy applies to all forms of support exchange within our community platforms, including:
- Discord channels and direct messages - Discord channels and direct messages
- Forums and discussion boards
- Reddit community spaces - Reddit community spaces
- Social media interactions - Social media interactions
- GitHub collaborative spaces - GitHub collaborative spaces
+2 -2
View File
@@ -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; **(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; **(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: 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; **(b)** Updates and notifications in Our software repositories;
+4 -6
View File
@@ -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; **(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; **(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; **(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; **(c)** **Feedback Mechanisms:** Opportunities to provide feedback on our security policies and procedures.
**(d)** **Feedback Mechanisms:** Opportunities to provide feedback on our security policies and procedures.
## 11. POLICY UPDATES AND MAINTENANCE ## 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; **(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; **(c)** **Documentation Updates:** Version-controlled updates to our official documentation;
-2
View File
@@ -384,8 +384,6 @@ We will notify users of changes to subprocessor arrangements through:
**(c)** **Service Notifications:** In-app notifications where technically feasible; **(c)** **Service Notifications:** In-app notifications where technically feasible;
**(d)** **Community Announcements:** Public announcements in community forums.
### 7.2. Types of Changes Requiring Notification ### 7.2. Types of Changes Requiring Notification
Changes requiring advance notification include: Changes requiring advance notification include:
@@ -60,7 +60,6 @@ This training operates within our policy framework:
**Examples:** **Examples:**
- **Discord**: Real-time moderation with immediate response capabilities - **Discord**: Real-time moderation with immediate response capabilities
- **Forums**: Considered, documented responses with longer discussion threads
- **Code Repositories**: Technical focus with professional communication standards - **Code Repositories**: Technical focus with professional communication standards
- **Social Media**: Public-facing brand representation with broader audience considerations - **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 ### 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:** **Your Response:**
1. How do you coordinate response across all platforms? 1. How do you coordinate response across all platforms?