diff --git a/src/content/docs/legal/community-support-policy.md b/src/content/docs/legal/community-support-policy.md index dbaaba2..d190afa 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 @@ -101,7 +100,6 @@ This policy applies to all forms of support exchange within our community platfo #### 2.2.1. Identifying Appropriate Support Channels **Platform-Specific Guidelines:** -- **Discord**: Use designated support channels (#general-support, #tech-help) or reach out to trusted community members - **Discord Forums**: Create posts in appropriate forum channels with clear, descriptive titles - **Reddit**: Utilise community-specific support threads and appropriate flair - **GitHub**: Use issue templates for bug reports, feature requests, and technical support diff --git a/src/content/docs/legal/dmca.md b/src/content/docs/legal/dmca.md index c75553d..85accf4 100644 --- a/src/content/docs/legal/dmca.md +++ b/src/content/docs/legal/dmca.md @@ -618,7 +618,7 @@ Changes to this Policy will be communicated through: **(b)** Email notifications to registered users; -**(c)** Community forum announcements and discussions; +**(c)** Community announcements and discussions; **(d)** Documentation updates with clear change logs. diff --git a/src/content/docs/legal/license.md b/src/content/docs/legal/license.md index 726a0f6..be6133d 100644 --- a/src/content/docs/legal/license.md +++ b/src/content/docs/legal/license.md @@ -2047,7 +2047,7 @@ For questions, clarifications, or other matters related to this Licence, We may ### 17.1. Primary Communication Channels -#### 17.1.1. Community Forum +#### 17.1.1. Discord Community Our primary venue for Licence-related discussions and inquiries: diff --git a/src/content/docs/staff/roles.md b/src/content/docs/staff/roles.md index 07f5f2a..0262a83 100644 --- a/src/content/docs/staff/roles.md +++ b/src/content/docs/staff/roles.md @@ -681,7 +681,7 @@ Technical Contributors provide development support, code contributions, and tech **Community Platform Expertise:** - Discord bot development and community tool creation -- Forum and community platform customisation and enhancement +- Community platform customisation and enhancement - Documentation system development and maintenance - Accessibility implementation and testing - Security assessment and improvement recommendations diff --git a/src/content/docs/staff/training/cross-platform-coordination.md b/src/content/docs/staff/training/cross-platform-coordination.md index 7873c6e..6c2af72 100644 --- a/src/content/docs/staff/training/cross-platform-coordination.md +++ b/src/content/docs/staff/training/cross-platform-coordination.md @@ -16,17 +16,15 @@ Our community operates across various platforms including: **(a)** **Discord Servers**: Real-time communication, voice chat, gaming coordination; -**(b)** **Forum Systems**: Long-form discussions, documentation, support; +**(b)** **Code Repositories**: Development collaboration, issue tracking, contributions; -**(c)** **Code Repositories**: Development collaboration, issue tracking, contributions; +**(c)** **Social Media**: Community outreach, updates, public engagement; -**(d)** **Social Media**: Community outreach, updates, public engagement; +**(d)** **Game Platforms**: MMOs, gaming communities, virtual events; -**(e)** **Game Platforms**: MMOs, gaming communities, virtual events; +**(e)** **Documentation Sites**: Knowledge bases, policies, guides; -**(f)** **Documentation Sites**: Knowledge bases, policies, guides; - -**(g)** **Other Platforms**: Emerging technologies and specialised tools. +**(f)** **Other Platforms**: Emerging technologies and specialised tools. ### 1.3. Integration with Existing Policies @@ -60,7 +58,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 @@ -93,69 +90,46 @@ This training operates within our policy framework: - Meme and humour sharing common - Real-time community events and activities -### 3.2. Forum Systems +### 3.2. Code Repositories #### 3.2.1. Unique Characteristics -- Asynchronous, threaded discussions -- Long-form content and detailed explanations -- Searchable, persistent content -- Structured topic organisation -- Advanced formatting and multimedia support - -#### 3.2.2. Moderation Considerations -- **Thoughtful Responses**: Time for considered, well-researched replies -- **Documentation Focus**: Posts serve as long-term resources -- **Thread Management**: Keeping discussions on-topic and organised -- **Archive Value**: Content remains accessible long-term -- **SEO and Discoverability**: Public content may be indexed - -#### 3.2.3. Community Culture -- Professional, informative tone expected -- Detailed technical discussions -- Educational resource creation -- Mentorship and knowledge sharing -- Formal support and troubleshooting - -### 3.3. Code Repositories - -#### 3.3.1. Unique Characteristics - Technical development focus - Version control and collaboration workflows - Issue tracking and project management - Code review and quality assurance processes - Documentation and technical writing -#### 3.3.2. Moderation Considerations +#### 3.2.2. Moderation Considerations - **Technical Accuracy**: Focus on correctness and best practices - **Professional Standards**: High expectations for communication quality - **Intellectual Property**: Copyright and licensing considerations - **Contribution Guidelines**: Specific workflow and process requirements - **Code of Conduct**: Technical community behavioural standards -#### 3.3.3. Community Culture +#### 3.2.3. Community Culture - Professional, technical communication - Constructive feedback and collaboration - Learning and skill development focus - Open source values and practices - Quality and excellence standards -### 3.4. Gaming Platforms +### 3.3. Gaming Platforms -#### 3.4.1. Unique Characteristics +#### 3.3.1. Unique Characteristics - Game-specific contexts and terminology - Real-time coordination and strategy - Achievement and progression systems - Competitive and cooperative elements - Virtual world social dynamics -#### 3.4.2. Moderation Considerations +#### 3.3.2. Moderation Considerations - **Game-Specific Rules**: Understanding in-game behaviour standards - **Performance Pressure**: Dealing with competitive stress - **Time-Sensitive Coordination**: Event and activity scheduling - **Cross-Platform Gaming**: Integration with external gaming services - **Virtual Asset Management**: In-game resources and shared assets -#### 3.4.3. Community Culture +#### 3.3.3. Community Culture - Gaming-focused communication - Strategy and coordination discussions - Achievement celebration and recognition @@ -286,7 +260,6 @@ This training operates within our policy framework: #### 5.3.1. Cross-Platform Integrations **Available Integrations:** -- **Discord-Forum Bridges**: Share announcements across platforms - **Repository Notifications**: Development updates in community channels - **Social Media Coordination**: Consistent messaging across public channels - **Event Synchronization**: Calendar integration across platforms @@ -321,43 +294,29 @@ This training operates within our policy framework: - **Channel Management**: Create, modify, and organise channels as needed - **Server Settings**: Understand security and moderation settings -### 6.2. Forum-Specific Responsibilities +### 6.2. Repository-Specific Responsibilities -#### 6.2.1. Content Curation -- Organise and categorise discussion topics -- Create informative and educational content -- Moderate long-form discussions and debates -- Maintain knowledge base and FAQ resources - -#### 6.2.2. Forum Tools and Features -- **Thread Management**: Move, merge, and organise discussion threads -- **User Management**: Handle user accounts, permissions, and restrictions -- **Content Tools**: Edit, format, and enhance community-generated content -- **Search and Organisation**: Maintain findable, well-organised content - -### 6.3. Repository-Specific Responsibilities - -#### 6.3.1. Technical Moderation +#### 6.2.1. Technical Moderation - Review contributions for quality and standards - Moderate technical discussions and code reviews - Enforce coding standards and best practices - Support contributor onboarding and development -#### 6.3.2. Development Tools +#### 6.2.2. Development Tools - **Issue Management**: Track, prioritise, and organise development tasks - **Pull Request Review**: Evaluate and approve code contributions - **Documentation**: Maintain technical documentation and guides - **Community Building**: Foster inclusive development community -### 6.4. Social Media Responsibilities +### 6.3. Social Media Responsibilities -#### 6.4.1. Public Representation +#### 6.3.1. Public Representation - Maintain professional brand representation - Respond to public inquiries and comments - Share community updates and achievements - Monitor for brand mentions and community discussions -#### 6.4.2. Community Outreach +#### 6.3.2. Community Outreach - **Content Creation**: Develop engaging social media content - **Community Engagement**: Interact with broader tech and gaming communities - **Crisis Communication**: Handle public relations during difficult situations @@ -443,12 +402,6 @@ This training operates within our policy framework: - Quick community communications and updates - Voice chat crisis intervention if needed -**Forum Crisis Response:** -- Detailed written responses and explanations -- Long-form crisis resources and support -- Archived information for future reference -- Community discussion facilitation - **Repository Crisis Response:** - Technical issue assessment and response - Code security and integrity protection @@ -549,7 +502,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? @@ -563,7 +516,7 @@ This training operates within our policy framework: ### 10.2. Scenario 2: Policy Inconsistency Report -**Situation**: A community member reports that the same behaviour resulted in different moderation actions on different platforms. They received a warning on Discord but were banned on the forum for the same behaviour. They're confused and feel the moderation is inconsistent. +**Situation**: A community member reports that the same behaviour resulted in different moderation actions on different platforms. They received a warning on Discord but were banned on another platform for the same behaviour. They're confused and feel the moderation is inconsistent. **Your Response:** 1. How do you investigate this inconsistency? @@ -577,7 +530,7 @@ This training operates within our policy framework: ### 10.3. Scenario 3: Cross-Platform Event Coordination -**Situation**: The community is planning a major event that will happen across multiple platforms simultaneously. The event involves Discord voice channels, forum discussions, social media promotion, and GitHub collaboration. Coordination is complex and requires seamless experience. +**Situation**: The community is planning a major event that will happen across multiple platforms simultaneously. The event involves Discord voice channels, social media promotion, and GitHub collaboration. Coordination is complex and requires seamless experience. **Your Response:** 1. How do you coordinate event logistics across platforms? @@ -614,4 +567,3 @@ This training document is part of the comprehensive mandatory training curriculu --- *This Cross-Platform Coordination Training document is part of our comprehensive staff development programme designed to create seamless community experiences across all platforms. For questions about cross-platform coordination techniques or to report training completion, please contact leadership through designated staff channels.* - diff --git a/src/content/docs/staff/training/data-analytics-reporting.md b/src/content/docs/staff/training/data-analytics-reporting.md index 1c72782..8b58496 100644 --- a/src/content/docs/staff/training/data-analytics-reporting.md +++ b/src/content/docs/staff/training/data-analytics-reporting.md @@ -321,7 +321,6 @@ This training provides comprehensive guidance for Team members serving as Data a **Cross-Platform Analytics:** - **Discord Analytics**: Integration with Discord for community server analytics -- **Forum Analytics**: Analysis of forum participation and engagement patterns - **Social Media Analytics**: Integration with social media platforms for broader community insights - **Event Analytics**: Integration of event participation and satisfaction data diff --git a/src/content/docs/staff/training/documentation-transparency.md b/src/content/docs/staff/training/documentation-transparency.md index 173031b..3f123c5 100644 --- a/src/content/docs/staff/training/documentation-transparency.md +++ b/src/content/docs/staff/training/documentation-transparency.md @@ -177,7 +177,7 @@ This training operates within our comprehensive framework: ``` **Incident Type**: [Policy violation category] **Date/Time**: [Exact timestamp] -**Platform**: [Discord/Forum/Repository/etc.] +**Platform**: [Discord/Repository/etc.] **User(s) Involved**: [Anonymized identifiers] **Team Member**: [Your name/identifier] **Policy Violated**: [Specific policy section]