From f8f787bde920ab505c18444feef14e7294ba7c84 Mon Sep 17 00:00:00 2001 From: Naomi Carrigan Date: Thu, 13 Nov 2025 21:59:23 -0800 Subject: [PATCH] feat: time for another audit/overhaul/revamp (#13) ### Explanation _No response_ ### Issue Closes #11 ### Attestations - [ ] I have read and agree to the [Code of Conduct](https://docs.nhcarrigan.com/community/coc/) - [ ] I have read and agree to the [Community Guidelines](https://docs.nhcarrigan.com/community/guide/). - [ ] My contribution complies with the [Contributor Covenant](https://docs.nhcarrigan.com/dev/covenant/). ### Dependencies - [ ] I have pinned the dependencies to a specific patch version. ### Style - [ ] I have run the linter and resolved any errors. - [ ] My pull request uses an appropriate title, matching the conventional commit standards. - [ ] My scope of feat/fix/chore/etc. correctly matches the nature of changes in my pull request. ### Tests - [ ] My contribution adds new code, and I have added tests to cover it. - [ ] My contribution modifies existing code, and I have updated the tests to reflect these changes. - [ ] All new and existing tests pass locally with my changes. - [ ] Code coverage remains at or above the configured threshold. ### Documentation _No response_ ### Versioning _No response_ Reviewed-on: https://git.nhcarrigan.com/nhcarrigan/docs/pulls/13 Co-authored-by: Naomi Carrigan Co-committed-by: Naomi Carrigan --- src/components/navigation.ts | 4 +- src/content/docs/about/contact.md | 150 +++++-- src/content/docs/about/donate.md | 254 +++++++++-- src/content/docs/about/hire.md | 276 ++++++++++-- src/content/docs/about/mentorship.md | 252 ++++++++++- src/content/docs/about/mission.md | 12 +- src/content/docs/about/sustainability.md | 6 +- src/content/docs/community/appeal.md | 54 +-- src/content/docs/community/coc.md | 198 ++++----- src/content/docs/community/feedback.md | 106 ++--- src/content/docs/community/guide.md | 302 ++++++------- src/content/docs/community/leadership.md | 154 +++---- src/content/docs/community/recognition.md | 136 +++--- src/content/docs/dev/contributing.md | 297 +++++++------ src/content/docs/dev/covenant.md | 10 +- src/content/docs/dev/environment.md | 126 ++++-- src/content/docs/dev/labels.md | 18 +- src/content/docs/dev/servers.md | 111 ++++- src/content/docs/dev/style.md | 92 +++- src/content/docs/legal/aup.md | 96 ++-- .../docs/legal/community-growth-policy.md | 105 +++-- .../docs/legal/community-support-policy.md | 131 +++--- src/content/docs/legal/content-moderation.md | 110 +++-- .../docs/legal/crisis-mental-health.md | 98 ++-- src/content/docs/legal/dmca.md | 126 +++--- src/content/docs/legal/export-control.md | 102 ++--- src/content/docs/legal/government.md | 92 ++-- src/content/docs/legal/liability.md | 90 ++-- src/content/docs/legal/license.md | 420 +++++++++--------- src/content/docs/legal/privacy.md | 95 ++-- src/content/docs/legal/security.md | 120 +++-- src/content/docs/legal/sla.md | 98 ++-- src/content/docs/legal/subprocessors.md | 96 ++-- src/content/docs/legal/terms.md | 124 +++--- src/content/docs/mentorship/00-faq.md | 145 +++++- src/content/docs/mentorship/01-onboarding.md | 134 +++++- .../docs/mentorship/02-goal-setting.md | 139 +++++- .../docs/mentorship/03-project-plan.md | 103 ++++- .../docs/mentorship/04-user-stories.md | 122 ++++- .../docs/mentorship/05-technical-breakdown.md | 132 +++++- .../docs/mentorship/06-priority-and-effort.md | 162 ++++++- .../docs/mentorship/07-writing-code.md | 164 ++++++- .../docs/mentorship/08-final-polish.md | 165 ++++++- src/content/docs/mentorship/09-career-prep.md | 147 +++++- src/content/docs/mentorship/10-graduation.md | 138 +++++- src/content/docs/misc/music.md | 65 ++- src/content/docs/misc/prompts.md | 70 ++- src/content/docs/misc/templates.md | 78 +++- src/content/docs/projects/a4p-bot.md | 136 +++--- src/content/docs/projects/altaria.md | 13 +- src/content/docs/projects/amari.md | 106 ++--- src/content/docs/projects/aria-iuvo.md | 10 +- src/content/docs/projects/becca-lyria.md | 16 +- src/content/docs/projects/blog.md | 10 +- src/content/docs/projects/boost-monitor.md | 26 +- src/content/docs/projects/caelia.md | 8 +- src/content/docs/projects/callista.md | 85 ++-- src/content/docs/projects/celestine.md | 8 +- src/content/docs/projects/chibika.md | 13 +- src/content/docs/projects/cordelia-taryne.md | 16 +- src/content/docs/projects/data-api.md | 93 ++-- .../docs/projects/discord-analytics.md | 6 +- src/content/docs/projects/docs.md | 30 +- src/content/docs/projects/eclaire.md | 11 +- src/content/docs/projects/eslint-config.mdx | 2 +- .../projects/freecodecamp-review-generator.md | 24 +- src/content/docs/projects/gwen-abalise.md | 2 +- src/content/docs/projects/hikari.md | 21 +- src/content/docs/projects/keiko.md | 14 +- src/content/docs/projects/liora.md | 113 +++-- src/content/docs/projects/logger.md | 12 +- src/content/docs/projects/lynira.md | 6 +- src/content/docs/projects/maylin-taryne.md | 16 +- src/content/docs/projects/meeting-minutes.md | 32 +- src/content/docs/projects/melody-iuvo.md | 6 +- src/content/docs/projects/mommy-bot.md | 18 +- src/content/docs/projects/mommy.md | 18 +- src/content/docs/projects/nomena.md | 95 ++-- src/content/docs/projects/pavelle.md | 6 +- src/content/docs/projects/portfolio.md | 11 +- src/content/docs/projects/resume.md | 18 +- .../docs/projects/rosalia-nightsong.md | 6 +- src/content/docs/projects/saisoku.md | 10 +- src/content/docs/projects/scripts.md | 62 ++- src/content/docs/projects/serenya.md | 4 +- src/content/docs/projects/sorielle.md | 9 +- src/content/docs/projects/static-pages.md | 148 +++--- src/content/docs/projects/tyche.md | 25 +- .../docs/projects/typescript-config.md | 64 +-- src/content/docs/projects/umbrelle.md | 8 +- src/content/docs/projects/veluna.md | 4 +- src/content/docs/projects/vivicrea.md | 123 +++-- src/content/docs/projects/vscode-themes.md | 110 ++--- src/content/docs/projects/website-headers.md | 28 +- src/content/docs/staff/apply.md | 40 +- src/content/docs/staff/handbook.md | 166 +++---- .../docs/staff/policy-self-assessment.md | 102 ++--- .../docs/staff/professional-conduct.md | 139 +++--- src/content/docs/staff/roles.md | 292 ++++++------ src/content/docs/staff/rubric.md | 43 +- .../training/accessibility-coordination.md | 131 +++--- .../training/community-growth-specialist.md | 153 ++++--- .../training/community-support-specialist.md | 173 ++++---- .../staff/training/conflict-resolution.md | 209 +++++---- .../docs/staff/training/crisis-response.md | 83 ++-- .../training/cross-platform-coordination.md | 199 ++++----- .../training/data-analytics-reporting.md | 139 +++--- .../training/documentation-transparency.md | 161 ++++--- .../staff/training/guild-wars-2-leadership.md | 123 +++-- .../staff/training/inclusive-moderation.md | 241 +++++----- .../mentorship-training-coordination.md | 135 +++--- .../staff/training/social-media-management.md | 163 ++++--- .../staff/training/technical-contributor.md | 119 +++-- 113 files changed, 6384 insertions(+), 4254 deletions(-) diff --git a/src/components/navigation.ts b/src/components/navigation.ts index a735390..fe1a743 100644 --- a/src/components/navigation.ts +++ b/src/components/navigation.ts @@ -12,11 +12,11 @@ export const navigation = [ link: "/about/sustainability", }, { - label: "Hire us!", + label: "Professional Services and Commission Policy", link: "/about/hire", }, { - label: "Support Our Work 💜", + label: "Donation and Support Policy", link: "/about/donate", }, { diff --git a/src/content/docs/about/contact.md b/src/content/docs/about/contact.md index 7f4f8d2..9770c35 100644 --- a/src/content/docs/about/contact.md +++ b/src/content/docs/about/contact.md @@ -2,11 +2,25 @@ title: Contact Policy --- -## Introduction and Legal Framework +**ESTABLISHING COMMUNICATION STANDARDS AND CHANNELS FOR ORGANISATIONAL INTERACTIONS** -This Contact Policy establishes our communication standards, channels, and expectations for all interactions with our organisation. This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, and all applicable legal protections by reference. +## 1. INTRODUCTION AND LEGAL FRAMEWORK -**IMPORTANT: All communications are subject to our Limitation of Liability and Indemnification Policy, Community Code of Conduct, and applicable legal frameworks. By engaging in communication with us, you acknowledge and agree to comply with all relevant policies.** +### 1.1. Policy Overview + +This Contact Policy ("Policy") establishes our communication standards, channels, and expectations for all interactions with our organisation. This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, and all applicable legal protections by reference. + +### 1.2. Legal Framework Integration + +**IMPORTANT: All communications are subject to our Limitation of Liability and Indemnification Policy, Community Code of Conduct, and applicable legal frameworks. By engaging in communication with us, you acknowledge and agree to comply with all relevant policies. Comprehensive warranty disclaimers and liability limitations are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.** + +### 1.3. Scope of Application + +This Policy applies to: +**(a)** All communications with NHCarrigan ("we," "us," "our," or "the Company"); +**(b)** All communication channels, platforms, and methods used to contact our organisation; +**(c)** All support requests, inquiries, and interactions with our team; +**(d)** All public and private communication channels operated by our organisation. --- @@ -60,7 +74,7 @@ ssh-keygen -Y verify -f /path/to/saved/key -I naomi@nhcarrigan.com -n socials -s ## 1. Support and Communication Channels -### 1.1 Public Support Channels +### 1.1. Public Support Channels We offer FREE support through several PUBLIC channels, including: @@ -74,7 +88,7 @@ These channels are ideal for: - Community discussions and knowledge sharing - Open-source collaboration opportunities -### 1.2 Private Support Options +### 1.2. Private Support Options While we encourage the use of public channels, we understand that some situations may require private communication. Please note: @@ -85,7 +99,7 @@ While we encourage the use of public channels, we understand that some situation To request private support, please contact us through `support@nhcarrigan.com`. -### 1.3 Engagement Opportunities +### 1.3. Engagement Opportunities Our platforms offer various ways to engage with our projects and community: @@ -94,13 +108,13 @@ Our platforms offer various ways to engage with our projects and community: - Seek mentorship in software development - Participate in casual discussions with our team and community members -### 1.4 Contact Form +### 1.4. Contact Form We offer a [contact form](https://forms.nhcarrigan.com/form/HyqoJ9Th5QDiOn_GPLNIRhe1a5ON7mDQf-O_ukM6R4g) for direct, low-priority communication requests. It is often faster to reach out through one of the below platforms, and best to consider this contact form as a backup in the event of a severe outage. -## 2. Communication Platforms +## 2. COMMUNICATION PLATFORMS ### 2.1. Discord @@ -129,9 +143,9 @@ Our code repositories are all self-hosted. You will need to request an account v - Before asking a question, check if it has been answered in pinned messages or FAQs. - When seeking help, provide as much relevant information as possible. -## 3. Announcements and Updates +## 3. ANNOUNCEMENTS AND UPDATES -### 3.1 Announcements Page +### 3.1. Announcements Page We have a dedicated page where we post all of our organisational updates. @@ -144,7 +158,7 @@ We have a dedicated page where we post all of our organisational updates. - Major policy changes - Best for: Comprehensive, detailed announcements and long-form updates -### 3.2 Blog +### 3.2. Blog Our blog contains more personal posts and updates. @@ -156,17 +170,17 @@ Our blog contains more personal posts and updates. - Cool insights into our decision making processes - Best for: People who want more insight into the team behind NHCarrigan. -### 3.3 Interacting with Announcements +### 3.3. Interacting with Announcements -All of our announcements are read-only, but you can discuss them in any of our platforms mentioned in Section 2! +All of our announcements are read-only, but you can discuss them in any of our platforms mentioned in Section 2. -### 3.6 Historical Announcements +### 3.4. Historical Announcements All announcements on our board are archived and remain accessible for future reference. -## 4. Professional Engagement and Portfolio +## 4. PROFESSIONAL ENGAGEMENT AND PORTFOLIO -### 4.1 LinkedIn Profile +### 4.1. LinkedIn Profile LinkedIn serves as our primary professional networking platform. @@ -180,11 +194,11 @@ LinkedIn serves as our primary professional networking platform. - Professional collaborators - Industry peers -#### 4.1.1 Connecting on LinkedIn +#### 4.1.1. Connecting on LinkedIn When sending a connection request, please include a brief message explaining your interest. We typically respond to LinkedIn messages within 2-3 business days. -### 4.2 Professional Inquiries +### 4.2. Professional Inquiries When reaching out for professional reasons, please consider the following: @@ -192,23 +206,23 @@ When reaching out for professional reasons, please consider the following: - Relevant Background: Provide brief context about yourself or your company. - Specific Questions: If you have particular queries, include them in your initial message. -### 4.3 Services +### 4.3. Services If you're interested in hiring us to perform some work for you, fill out the form at https://forms.nhcarrigan.com/form/XRlQjeu8CbMrTA-v0IPOxlUPEPitLKXTWg70UUCIORA. -### 4.4 Speaking Engagements and Events +### 4.4. Speaking Engagements and Events If you're interested in having us speak at your event or contribute to your publication, fill out the form at https://forms.nhcarrigan.com/form/Xqap3Q8hazzJd4Rrp9OOs9ip8Pa7C9zOVThlyFoPCbU. -### 4.5 Keeping Professional Connections Updated +### 4.5. Keeping Professional Connections Updated We regularly update our professional profiles with new projects, skills, and achievements. Follow us on these platforms to stay informed about our professional journey and potential opportunities for collaboration. -## 5. Email Communication +## 5. EMAIL COMMUNICATION We offer several email addresses for specific types of inquiries. Please use the appropriate email address to ensure your message reaches the right team and receives the most efficient response. -### 5.1 General Inquiries +### 5.1. General Inquiries - Email: contact@nhcarrigan.com - Use for: @@ -217,7 +231,7 @@ We offer several email addresses for specific types of inquiries. Please use the - Media or press inquiries - Any queries that don't fit other categories -### 5.2 Billing and Financial Matters +### 5.2. Billing and Financial Matters - Email: billing@nhcarrigan.com - Use for: @@ -226,7 +240,7 @@ We offer several email addresses for specific types of inquiries. Please use the - Refund requests - Updating billing information -### 5.3 Technical Support +### 5.3. Technical Support - Email: support@nhcarrigan.com - Use for: @@ -234,7 +248,7 @@ We offer several email addresses for specific types of inquiries. Please use the - Reporting bugs or technical issues - Documentation clarifications -### 5.4 Privacy Concerns +### 5.4. Privacy Concerns - Email: privacy@nhcarrigan.com - Use for: @@ -243,7 +257,7 @@ We offer several email addresses for specific types of inquiries. Please use the - Reporting potential privacy breaches - Opting out of data collection (where applicable) -### 5.5 Security Matters +### 5.5. Security Matters - Email: security@nhcarrigan.com - Use for: @@ -251,7 +265,7 @@ We offer several email addresses for specific types of inquiries. Please use the - Questions about our security practices - Concerns about potential security breaches -### 5.6 Legal Inquiries +### 5.6. Legal Inquiries - Email: legal@nhcarrigan.com - Use for: @@ -260,7 +274,7 @@ We offer several email addresses for specific types of inquiries. Please use the - Requests for legal documentation - Formal notices or communications -### 5.7 Feedback and Suggestions +### 5.7. Feedback and Suggestions - Email: feedback@nhcarrigan.com - Use for: @@ -269,7 +283,7 @@ We offer several email addresses for specific types of inquiries. Please use the - Sharing your experience with our services - Offering ideas for future developments -### 5.8 Press/Media Inquiries +### 5.8. Press/Media Inquiries - Email: press@nhcarrigan.com - Use for: @@ -277,7 +291,7 @@ We offer several email addresses for specific types of inquiries. Please use the - Scheduling interviews for your media outlet - Attribution requests in academic articles -### 5.9 Event Requests +### 5.9. Event Requests - Email: events@nhcarrigan.com - Use for: @@ -286,7 +300,7 @@ We offer several email addresses for specific types of inquiries. Please use the - Workshop or training session requests - Event sponsorship inquiries -### 5.10 Marketing Inquiries +### 5.10. Marketing Inquiries - Email: marketing@nhcarrigan.com - Use for: @@ -295,7 +309,7 @@ We offer several email addresses for specific types of inquiries. Please use the - Advertising inquiries - Content licensing requests -### 5.11 Career Information +### 5.11. Career Information - Email: careers@nhcarrigan.com - Use for: @@ -304,7 +318,7 @@ We offer several email addresses for specific types of inquiries. Please use the - Inquiries - Following up on job applications -### 5.12 Partnerships +### 5.12. Partnerships - Email: partners@nhcarrigan.com - Use for: @@ -313,7 +327,7 @@ We offer several email addresses for specific types of inquiries. Please use the - Brand ambassador programmes - Product placement or sponsored content inquiries -### 5.13 Email Communication Guidelines +### 5.13. Email Communication Guidelines - Subject Line: Please use a clear, concise subject line that summarizes your inquiry. - Content: Provide all relevant details in your initial email to expedite the response process. @@ -321,7 +335,7 @@ We offer several email addresses for specific types of inquiries. Please use the - Response Time: We aim to respond to all emails within 2 business days. Complex inquiries may require additional time. - Follow-ups: If you haven't received a response after 3 business days, feel free to send a polite follow-up. -### 5.14 Email Privacy and Security +### 5.14. Email Privacy and Security **Reference to Comprehensive Privacy Framework**: Detailed privacy protections, data handling procedures, and security measures are set forth in our Privacy Policy, which is incorporated herein by reference. @@ -333,13 +347,13 @@ We do not share your email address or the content of your messages with third pa - As part of public safety measures related to Code of Conduct violations - As necessary for service provision and technical operations -### 5.15 Spam and Unsolicited Emails +### 5.15. Spam and Unsolicited Emails We have a strict no-spam policy. If you receive any unsolicited emails claiming to be from us, please report them to security@nhcarrigan.com. By using the appropriate email address for your inquiry, you help us provide you with the most efficient and accurate response possible. If you're unsure which email to use, feel free to send your inquiry to contact@nhcarrigan.com, and we'll direct it to the appropriate team. -### 5.16 Acceptable Use and Consequences +### 5.16. Acceptable Use and Consequences We are committed to maintaining a respectful and productive communication environment. To ensure this: @@ -358,13 +372,13 @@ We reserve the right to report serious abuses to relevant authorities if necessa By communicating with us via email, you agree to adhere to these guidelines and understand the consequences of misuse. -## 6. Direct Messages +## 6. DIRECT MESSAGES -### 6.1 Direct Message Policy +### 6.1. Direct Message Policy -We offer direct messaging as a private, personalized communication channel. However, to manage our time effectively and ensure the highest quality of service, direct messages are the lowest priority of communication. Instead, we strongly encourage you to reach out via our Discord community. +We offer direct messaging as a private, personalised communication channel. However, to manage our time effectively and ensure the highest quality of service, direct messages are the lowest priority of communication. Instead, we strongly encourage you to reach out via our Discord community. -### 6.2 Purpose and Use +### 6.2. Purpose and Use Direct messages should be used for: @@ -372,26 +386,64 @@ Direct messages should be used for: - Sensitive information that shouldn't be shared publicly - Personalized support or consultation requests -### 6.3 Response Time +### 6.3. Response Time - We aim to respond to direct messages within 5-7 business days. - Complex inquiries may require additional time, which will be communicated to you. -### 6.4 Appropriate Use +### 6.4. Appropriate Use - Direct messages should be used responsibly and for legitimate purposes only. - Abusive, harassing, or spam messages will not be tolerated and may result in blocking or reporting to the platform. -### 6.5 Alternatives +### 6.5. Alternatives We encourage users to consider the following alternatives before sending a direct message: - Use our public support channels for general inquiries (see Section 1.1) - Check our FAQ or documentation for commonly asked questions -- Post in our community forums for non-urgent matters +- Post in our Discord community forum channels for non-urgent matters -### 6.7 Consent and Acknowledgment +### 6.6. Consent and Acknowledgment -By sending a direct message, you acknowledge that you have read and agreed to this policy. +By sending a direct message, you acknowledge that you have read and agreed to this Policy. -Remember, while we value direct communication, we encourage the use of our public channels whenever possible to foster community engagement and shared learning. +**IMPORTANT: While we value direct communication, we strongly encourage the use of our public channels whenever possible to foster community engagement and shared learning. Direct messages are the lowest priority communication channel and may experience significant response delays.** + +## 7. LIMITATION OF LIABILITY AND DISCLAIMERS + +### 7.1. Reference to Comprehensive Liability Framework + +**IMPORTANT: Comprehensive liability limitations, damage exclusions, and maximum liability caps are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference and governs all matters related to communications and contact with our organisation.** + +### 7.2. Communication-Specific Disclaimers + +**Additional Limitations:** +**(a)** We are not liable for delays, failures, or errors in communication delivery or processing; +**(b)** We do not guarantee response times or availability of any communication channel; +**(c)** We are not responsible for third-party platform failures or communication service interruptions; +**(d)** Our liability is limited to the maximum extent permitted by applicable law. + +## 8. CONTACT INFORMATION AND SUPPORT + +### 8.1. General Contact + +For general inquiries about this Policy or our communication channels: + +**Email:** contact@nhcarrigan.com + +**Discord Community:** https://chat.nhcarrigan.com + +**Response Time:** Within 48 hours for general inquiries + +### 8.2. Policy Questions + +For questions about this Contact Policy: + +**Email:** contact@nhcarrigan.com + +**Subject Line:** Contact Policy Inquiry - [Brief Description] + +--- + +*This Contact Policy establishes the terms and standards governing all communications with our organisation. By engaging in communication with us, you acknowledge that you have read, understood, and agree to comply with this Policy and all incorporated legal frameworks. For questions about this Policy, please contact us at contact@nhcarrigan.com.* diff --git a/src/content/docs/about/donate.md b/src/content/docs/about/donate.md index 289ab0f..7a4d7a2 100644 --- a/src/content/docs/about/donate.md +++ b/src/content/docs/about/donate.md @@ -1,55 +1,237 @@ --- -title: Support Our Work 💜 +title: Donation and Support Policy --- -:::tip -We have started tracking our organisation's income and expenses publicly, through our [OpenCollective](https://opencollective.com/nhcarrigan) account! +**SUPPORTING OUR MISSION THROUGH VOLUNTARY CONTRIBUTIONS** -You can also donate there directly. -::: +## 1. INTRODUCTION AND PURPOSE -We are passionate about creating and maintaining free-to-use projects and providing guidance in various programming communities. Your support helps us continue this mission and expand our efforts. +### 1.1. Policy Overview -## 1. Why Support Us? +This Donation and Support Policy ("Policy") establishes the terms, conditions, and procedures governing voluntary financial contributions and other forms of support to NHCarrigan ("we," "us," "our," or "the Company"). This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, and all applicable legal protections by reference. -- **Free Resources**: We offer numerous projects that are free for everyone to use and learn from. -- **Community Guidance**: We actively participate in programming communities, offering help and mentorship. -- **Open Source Contributions**: Your support enables us to dedicate more time to open source development. -- **Continuous Improvement**: Donations help us improve existing projects and create new ones. +### 1.2. Legal Framework Integration -## 2. How Your Support Helps +**IMPORTANT: All donations and support are voluntary contributions. This Policy does not create any contractual obligations, warranties, or guarantees regarding the use of donated funds or the provision of any services or benefits. Comprehensive disclaimers and liability limitations are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.** -- Covers hosting and infrastructure costs -- Allows us to dedicate more time to project development and community support -- Enables us to invest in better tools and resources -- Supports our ongoing education and skill development +### 1.3. Scope of Application -## 3. Ways to Support +This Policy applies to: +**(a)** All voluntary financial contributions made to NHCarrigan; +**(b)** All forms of non-financial support and contributions; +**(c)** All donation platforms and payment processors used for contributions; +**(d)** All benefits, recognition, or acknowledgements associated with contributions. -We offer a few options for donations! +## 2. DONATION PURPOSE AND USE -- You can donate on our [OpenCollective](https://opencollective.com/nhcarrigan) page -- You can donate via a monthly subscription in our [Discord community](https://chat.nhcarrigan.com) -- You can donate via a monthly membership on our [Patreon](https://patreon.com/nhcarrigan) -- You can make monthly or one-time donations on [Ko-Fi](https://ko-fi.com/nhcarrigan) -- You can suggest and purchase gifts for us on [Throne](https://throne.com/naomilgbt) -- You can subscribe to our [Twitch streams](https://twitch.tv/naomilgbt) -- You can send direct donations via [PayPal](https://paypal.me/nhcarrigan) or [CashApp](https://cash.app/$nhcarrigan) -- You can sponsor us directly through our [GitHub organisation](https://github.com/sponsors/nhcarrigan) or [Naomi's account](https://github.com/sponsors/naomi-lgbt) -- Want to keep it simple? Make [monthly](https://buy.stripe.com/cN24iTfqu1j6b3afZ2) or [one-time](https://donate.stripe.com/8wMcPp1zE8Ly2wEcMR) donations directly through Stripe! +### 2.1. Mission and Objectives -## 4. Other Ways to Help +We are committed to creating and maintaining free-to-use projects and providing guidance in various programming communities. Voluntary contributions support our mission to: -- **Spread the Word**: Share our projects and resources with others who might benefit. -- **Contribute**: If you have skills to offer, consider contributing to our open source projects. -- **Provide Feedback**: Your input helps us improve and refine our work. +**(a)** **Free Resource Development**: Create and maintain projects that are free for everyone to use and learn from; +**(b)** **Community Guidance**: Provide active participation in programming communities, offering help and mentorship; +**(c)** **Open Source Contributions**: Enable dedicated time to open source development and community support; +**(d)** **Continuous Improvement**: Improve existing projects and create new resources for the community. -## 5. Thank You! +### 2.2. Use of Donated Funds -Every contribution, no matter the size, makes a significant impact. We deeply appreciate your support and are committed to using it to benefit the wider programming community. +Donated funds may be used for: -For any questions about donations or to discuss other support options, please contact us at donors@nhcarrigan.com. +**(a)** **Infrastructure Costs**: Hosting, servers, and technical infrastructure necessary for service provision; +**(b)** **Development Resources**: Tools, software licences, and resources necessary for project development; +**(c)** **Community Support**: Time and resources dedicated to community support and mentorship activities; +**(d)** **Educational Development**: Ongoing education and skill development to enhance service quality; +**(e)** **Organisational Operations**: Reasonable operational expenses necessary for organisational functioning. -## 6. Perks +### 2.3. Financial Transparency -Once you have donated, make sure to join our [Discord](https://chat.nhcarrigan.com)! Once there, ping Naomi to request access to our special supporters channel and role! +We maintain transparency regarding our organisation's income and expenses through our publicly accessible [OpenCollective](https://opencollective.com/NHCarrigan) account, where donors may review financial information and contribute directly. + +**IMPORTANT DISCLAIMER:** +The ledger is updated as our workload allows. We make no guarantee of timely accuracy. + +### 2.4. No Guarantees or Obligations + +**IMPORTANT DISCLAIMER:** +**(a)** Donations do not create any contractual obligations or guarantees regarding specific project outcomes or service levels; +**(b)** We reserve the right to allocate donated funds at our sole discretion in furtherance of our mission; +**(c)** Donations do not entitle donors to any ownership interest, voting rights, or control over organisational decisions; +**(d)** We are not obligated to provide any specific services, features, or benefits in exchange for donations. + +## 3. DONATION METHODS AND PLATFORMS + +### 3.1. Available Donation Platforms + +We accept voluntary contributions through the following platforms: + +**(a)** **OpenCollective**: [https://opencollective.com/NHCarrigan](https://opencollective.com/NHCarrigan) - Primary platform for organisational donations and financial transparency; +**(b)** **Discord Community**: Monthly subscription options available within our [Discord community](https://chat.nhcarrigan.com); +**(c)** **Patreon**: Monthly membership options available at [https://patreon.com/NHCarrigan](https://patreon.com/NHCarrigan); +**(d)** **Ko-Fi**: Monthly or one-time donations available at [https://ko-fi.com/NHCarrigan](https://ko-fi.com/NHCarrigan); +**(e)** **Throne**: Gift suggestions and purchases available at [https://throne.com/naomilgbt](https://throne.com/naomilgbt); +**(f)** **Twitch**: Subscription options available through our [Twitch streams](https://twitch.tv/naomilgbt); +**(g)** **PayPal**: Direct donations via [https://paypal.me/NHCarrigan](https://paypal.me/NHCarrigan); +**(h)** **CashApp**: Direct donations via [https://cash.app/$NHCarrigan](https://cash.app/$NHCarrigan); +**(i)** **GitHub Sponsors**: Sponsorship options through our [GitHub organisation](https://github.com/sponsors/NHCarrigan) or [Naomi's account](https://github.com/sponsors/naomi-lgbt); +**(j)** **Stripe**: Direct [monthly](https://buy.stripe.com/cN24iTfqu1j6b3afZ2) or [one-time](https://donate.stripe.com/8wMcPp1zE8Ly2wEcMR) donations. + +### 3.2. Third-Party Platform Terms + +All donations processed through third-party platforms are subject to: +**(a)** The terms of service and privacy policies of the respective platform; +**(b)** Platform-specific fees, processing charges, and payment terms; +**(c)** Platform security measures and data handling practices; +**(d)** Our Privacy Policy regarding collection and processing of donor information. + +### 3.3. Payment Processing + +**(a)** All payment processing is handled by third-party payment processors; +**(b)** We do not directly process or store payment card information; +**(c)** Payment security is the responsibility of the respective payment platform; +**(d)** We are not liable for any issues arising from third-party payment processing. + +## 4. DONOR RECOGNITION AND BENEFITS + +### 4.1. Recognition Programmes + +We may provide recognition to donors through: +**(a)** Public acknowledgement in donor recognition lists (with explicit consent); +**(b)** Special roles or channels in our community platforms; +**(c)** Access to supporter-exclusive content or features; +**(d)** Other forms of recognition as determined at our sole discretion. + +### 4.2. Supporter Benefits + +Donors may be eligible for certain benefits, including: +**(a)** **Discord Community Access**: Access to special supporters channels and roles within our [Discord community](https://chat.nhcarrigan.com); +**(b)** **Early Access**: Early access to new features or content where applicable; +**(c)** **Recognition**: Public recognition in donor lists or supporter acknowledgements (with consent); +**(d)** **Community Engagement**: Enhanced engagement opportunities within our community platforms. + +### 4.3. Benefit Limitations + +**IMPORTANT:** +**(a)** Benefits are provided at our sole discretion and may be modified or discontinued at any time; +**(b)** Benefits do not create any contractual rights or obligations; +**(c)** We reserve the right to revoke benefits for violations of our Terms of Service or Community Code of Conduct; +**(d)** Benefits may vary based on donation amount, platform, or other factors determined by us. + +### 4.4. Benefit Activation + +To activate supporter benefits: +**(a)** Join our [Discord community](https://chat.nhcarrigan.com); +**(b)** Contact community leadership to request access to supporter channels and roles; +**(c)** Provide verification of donation if requested; +**(d)** Comply with all community standards and policies. + +## 5. ALTERNATIVE FORMS OF SUPPORT + +### 5.1. Non-Financial Contributions + +We value and appreciate various forms of non-financial support: + +**(a)** **Community Engagement**: Active participation in our community platforms and discussions; +**(b)** **Project Contributions**: Contributing code, documentation, or other resources to our open source projects; +**(c)** **Promotion and Advocacy**: Sharing our projects and resources with others who might benefit; +**(d)** **Feedback and Input**: Providing constructive feedback to help us improve and refine our work. + +### 5.2. Contribution Guidelines + +All non-financial contributions are subject to: +**(a)** Our Terms of Service and Acceptable Use Policy; +**(b)** Our Community Code of Conduct; +**(c)** Our Contributing Documentation for code and technical contributions; +**(d)** All applicable legal and policy frameworks. + +## 6. DONATION TERMS AND CONDITIONS + +### 6.1. Voluntary Nature + +**(a)** All donations are strictly voluntary and non-refundable; +**(b)** Donations do not create any employment, partnership, or business relationship; +**(c)** Donations are not investments and do not provide any financial return or equity interest; +**(d)** We are not obligated to accept any donation and may refuse donations at our sole discretion. + +### 6.2. Refund Policy + +**(a)** Donations are generally non-refundable; +**(b)** Refund requests will be considered on a case-by-case basis for exceptional circumstances; +**(c)** Refund requests must be submitted within thirty (30) days of the donation date; +**(d)** Processing fees charged by payment platforms are non-refundable. + +### 6.3. Tax Considerations + +**(a)** We are not a tax-exempt organisation and cannot provide tax deduction documentation; +**(b)** Donors are responsible for determining the tax implications of their contributions; +**(c)** We recommend consulting with a tax professional regarding donation tax treatment; +**(d)** We do not provide tax advice or tax-related documentation. + +### 6.4. Donation Modifications and Cancellations + +**(a)** Recurring donations may be cancelled through the respective payment platform; +**(b)** We are not responsible for cancellation processes managed by third-party platforms; +**(c)** Cancellation of recurring donations does not affect benefits already provided; +**(d)** We reserve the right to modify or discontinue donation programmes at any time. + +## 7. PRIVACY AND DATA PROTECTION + +### 7.1. Donor Information + +Donor information is handled in accordance with our Privacy Policy: +**(a)** We collect only information necessary for processing donations and providing benefits; +**(b)** Donor information is not sold or shared with third parties except as necessary for payment processing; +**(c)** Donors may request access to or deletion of their personal information; +**(d)** Public recognition requires explicit consent from donors. + +### 7.2. Payment Information + +**(a)** We do not directly process or store payment card information; +**(b)** Payment information is handled by third-party payment processors in accordance with their privacy policies; +**(c)** We are not responsible for data breaches or security incidents affecting third-party payment platforms; +**(d)** Donors should review payment platform privacy policies before making contributions. + +## 8. LIMITATION OF LIABILITY AND DISCLAIMERS + +### 8.1. Reference to Comprehensive Liability Framework + +**IMPORTANT: Comprehensive liability limitations, damage exclusions, and maximum liability caps are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference and governs all matters related to donations and support.** + +### 8.2. Donation-Specific Disclaimers + +In addition to comprehensive liability limitations: +**(a)** We are not liable for any issues arising from third-party payment platform failures or errors; +**(b)** We are not responsible for benefits or recognition that cannot be provided due to technical or operational limitations; +**(c)** We do not guarantee that donations will result in specific project outcomes or service improvements; +**(d)** We are not liable for any tax consequences or legal implications of donations. + +## 9. CONTACT INFORMATION + +### 9.1. Donation Inquiries + +For questions about donations or support options: + +**Email:** donors@nhcarrigan.com + +**Response Time:** Within 48 hours for donation-related inquiries + +### 9.2. General Contact + +For general inquiries about our organisation or services: + +**Email:** contact@nhcarrigan.com + +**Discord Community:** https://chat.nhcarrigan.com + +## 10. ACKNOWLEDGEMENT AND GRATITUDE + +### 10.1. Appreciation Statement + +We extend our sincere gratitude to all individuals and organisations who support our mission through voluntary contributions. Every contribution, regardless of size, makes a significant impact on our ability to serve the programming community and maintain free, accessible resources. + +### 10.2. Commitment to Mission + +We are committed to using all contributions responsibly and effectively to further our mission of creating inclusive, accessible technology resources and supporting programming communities worldwide. + +--- + +*This Donation and Support Policy establishes the terms governing voluntary contributions to our organisation. By making a donation, you acknowledge that you have read, understood, and agree to the terms set forth in this Policy. For questions about donations, please contact us at donors@nhcarrigan.com.* diff --git a/src/content/docs/about/hire.md b/src/content/docs/about/hire.md index 2b363f9..d2f56f1 100644 --- a/src/content/docs/about/hire.md +++ b/src/content/docs/about/hire.md @@ -1,55 +1,265 @@ --- -title: Hire us! +title: Professional Services and Commission Policy --- -We're excited about the opportunity to collaborate with you and contribute to the success of your goals. Our team brings a wealth of experience and a passion for delivering high-quality solutions tailored to your specific needs. +**PROFESSIONAL SERVICES, CONSULTING, AND COMMISSION ENGAGEMENTS** -!["If you knew I was so unstable, why'd you hire me?"](https://cdn.nhcarrigan.com/hire.jpeg) +## 1. INTRODUCTION AND SCOPE -## 1. Our Services +### 1.1. Policy Overview -- **Discord Bot Development**: Custom bots to enhance your server's functionality -- **Web Development**: From simple websites to complex web applications -- **Community Management**: Strategies to grow and maintain thriving online communities -- **Technical Consulting**: Expert advice on your tech-related projects and decisions +This Professional Services and Commission Policy ("Policy") establishes the terms, conditions, and procedures governing professional services, consulting engagements, and commission-based work provided by NHCarrigan ("we," "us," "our," or "the Company"). This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, and all applicable legal protections by reference. -## 2. Engagement Options +### 1.2. Legal Framework Integration -We offer flexible ways to work together, catering to projects of all sizes and complexities: +**IMPORTANT: This Policy does not create any binding service agreements. All professional services engagements require separate written agreements that supersede this Policy. Comprehensive disclaimers, warranty limitations, and liability protections are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.** -### 2.1. Quick Sync (15 minutes) +### 1.3. Scope of Application -For those with a well-defined product idea or seeking a quick review of their community plan, book a quick sync. +This Policy applies to: +**(a)** All professional services and consulting engagements; +**(b)** All commission-based development and technical work; +**(c)** All mentorship and training services; +**(d)** All initial consultations and project discussions. -- Ideal for: Initial project discussions, quick advice, or community plan reviews -- Duration: 15 minutes -- Outcome: Rapid insights and direction for your project +## 2. AVAILABLE SERVICES -### 2.2. In-Depth Consultation (30 minutes) +### 2.1. Service Categories -For more complex, long-term, or in-depth projects, we recommend booking an in-depth consultation. +We offer professional services in the following categories: -- Ideal for: Detailed project planning, technical strategy discussions, or exploring long-term collaborations -- Duration: 30 minutes -- Outcome: Comprehensive project assessment and tailored recommendations +**(a)** **Discord Bot Development**: Custom bot development to enhance server functionality, including feature implementation, integration services, and ongoing maintenance; +**(b)** **Web Development**: Website and web application development services, ranging from simple websites to complex web applications, including front-end and back-end development; +**(c)** **Community Management**: Strategic consulting and services for growing and maintaining thriving online communities, including moderation strategies, engagement programmes, and community growth planning; +**(d)** **Technical Consulting**: Expert technical advice and consultation on technology-related projects, decisions, and strategic planning. -### 2.3. Mentorship Session (60 minutes) +### 2.2. Service Limitations -For those seeking personalized guidance and skill development, we offer a full mentorship session. +**IMPORTANT DISCLAIMERS:** +**(a)** Services are provided subject to availability and our sole discretion to accept or decline engagements; +**(b)** Service scope, deliverables, and timelines are determined through separate written agreements; +**(c)** We reserve the right to refuse service for any reason, including conflicts of interest, resource constraints, or project incompatibility; +**(d)** All services are subject to our Terms of Service, Acceptable Use Policy, and applicable legal frameworks. -- Ideal for: Individuals looking to enhance their skills in development, community management, or related areas -- Duration: 60 minutes -- Outcome: Personalized learning path, hands-on projects, and ongoing support +## 3. ENGAGEMENT OPTIONS AND CONSULTATION SERVICES -## 3. Why Choose Us? +### 3.1. Initial Consultation Services -- **Expertise**: Years of experience in development and community management -- **Flexibility**: Multiple engagement options to suit your needs and preferences -- **Personalized Approach**: Tailored solutions for your unique challenges -- **Commitment to Quality**: Delivering high-value insights and solutions in every interaction +We offer structured consultation services to assess project needs and determine appropriate engagement approaches: -## 4. Ready to Get Started? +### 3.2. Quick Sync Consultation (15 Minutes) -Submit a [commission request](https://forms.nhcarrigan.com/form/XRlQjeu8CbMrTA-v0IPOxlUPEPitLKXTWg70UUCIORA)! +**Purpose and Scope:** +**(a)** **Intended Use**: Initial project discussions, quick advice, or community plan reviews for well-defined product ideas; +**(b)** **Duration**: Fifteen (15) minutes; +**(c)** **Outcome**: Rapid insights and directional guidance for project planning; +**(d)** **Limitations**: Quick sync consultations provide preliminary guidance only and do not constitute comprehensive project planning or binding service commitments. -Not sure which option is right for you? Feel free to contact us with any questions. We're excited to explore how we can help bring your ideas to life and contribute to your success! +### 3.3. In-Depth Consultation (30 Minutes) + +**Purpose and Scope:** +**(a)** **Intended Use**: Detailed project planning, technical strategy discussions, or exploration of long-term collaboration opportunities for complex, long-term, or in-depth projects; +**(b)** **Duration**: Thirty (30) minutes; +**(c)** **Outcome**: Comprehensive project assessment and tailored recommendations; +**(d)** **Limitations**: In-depth consultations provide strategic guidance but do not constitute binding service agreements or guarantee project acceptance. + +### 3.4. Mentorship Session (60 Minutes) + +**Purpose and Scope:** +**(a)** **Intended Use**: Personalized guidance and skill development for individuals seeking to enhance skills in development, community management, or related technical areas; +**(b)** **Duration**: Sixty (60) minutes; +**(c)** **Outcome**: Personalized learning path recommendations, hands-on project guidance, and ongoing support planning; +**(d)** **Limitations**: Mentorship sessions provide educational guidance and do not create ongoing mentorship relationships unless separately agreed. + +### 3.5. Consultation Terms and Conditions + +**IMPORTANT:** +**(a)** Consultation services are provided for informational and planning purposes only; +**(b)** Consultations do not create any binding service agreements or commitments; +**(c)** All consultation outcomes, recommendations, and advice are provided "as is" without warranties; +**(d)** Consultation fees, if applicable, are non-refundable and do not guarantee project acceptance or service provision. + +## 4. SERVICE ENGAGEMENT PROCESS + +### 4.1. Initial Inquiry and Assessment + +**Engagement Process:** +**(a)** **Commission Request Submission**: Submit initial inquiries through our [commission request form](https://forms.nhcarrigan.com/form/XRlQjeu8CbMrTA-v0IPOxlUPEPitLKXTWg70UUCIORA); +**(b)** **Initial Review**: We review all commission requests to assess project scope, compatibility, and resource availability; +**(c)** **Consultation Scheduling**: Appropriate consultation services may be scheduled to discuss project requirements and engagement options; +**(d)** **Project Assessment**: Comprehensive assessment of project feasibility, timeline, and resource requirements. + +### 4.2. Service Agreement Requirements + +**Formal Engagement:** +**(a)** All professional service engagements require separate written service agreements; +**(b)** Service agreements specify project scope, deliverables, timelines, compensation, and terms; +**(c)** No services are provided until a written service agreement is executed by both parties; +**(d)** Service agreements supersede this Policy and establish binding terms for specific engagements. + +### 4.3. Project Acceptance and Rejection + +**Engagement Decisions:** +**(a)** We reserve the right to accept or decline any project at our sole discretion; +**(b)** Project acceptance is subject to resource availability, project compatibility, and our assessment of project feasibility; +**(c)** We are not obligated to provide reasons for project rejection; +**(d)** Consultation fees, if paid, are non-refundable regardless of project acceptance or rejection. + +## 5. SERVICE QUALITY AND DELIVERABLES + +### 5.1. Service Standards + +We are committed to delivering high-quality professional services: +**(a)** **Expertise**: Years of experience in development, community management, and technical consulting; +**(b)** **Flexibility**: Multiple engagement options to accommodate diverse project needs and preferences; +**(c)** **Personalized Approach**: Tailored solutions addressing unique project challenges and requirements; +**(d)** **Quality Commitment**: Focus on delivering high-value insights and solutions in every engagement. + +### 5.2. Deliverable Specifications + +**Service Deliverables:** +**(a)** All deliverables are specified in individual service agreements; +**(b)** Deliverables are provided in accordance with agreed specifications and timelines; +**(c)** We reserve the right to modify deliverables with client consent and appropriate agreement amendments; +**(d)** Deliverable acceptance and approval processes are established in service agreements. + +### 5.3. Service Limitations and Disclaimers + +**IMPORTANT DISCLAIMERS:** +**(a)** Services are provided "as is" subject to the limitations and disclaimers in our Limitation of Liability and Indemnification Policy; +**(b)** We do not guarantee specific project outcomes, business results, or performance metrics; +**(c)** Service quality and outcomes may vary based on project complexity, client cooperation, and external factors; +**(d)** We are not responsible for client decisions made based on our services or recommendations. + +## 6. COMPENSATION AND PAYMENT TERMS + +### 6.1. Fee Structure + +**Compensation Arrangements:** +**(a)** Consultation fees, if applicable, are specified at the time of consultation scheduling; +**(b)** Professional service fees are established in individual service agreements; +**(c)** Payment terms, schedules, and methods are specified in service agreements; +**(d)** All fees are non-refundable except as specifically provided in service agreements. + +### 6.2. Payment Processing + +**Payment Methods:** +**(a)** Payments are processed through secure third-party payment processors; +**(b)** Payment processing is subject to third-party platform terms and conditions; +**(c)** We are not responsible for payment processing delays or issues caused by third-party platforms; +**(d)** Payment information is handled in accordance with our Privacy Policy and applicable data protection laws. + +### 6.3. Refund Policy + +**Refund Terms:** +**(a)** Consultation fees are non-refundable; +**(b)** Professional service refunds are governed by individual service agreements; +**(c)** Refund requests must be submitted in writing and are subject to our review and approval; +**(d)** We reserve the right to refuse refunds for services already provided or work already completed. + +## 7. INTELLECTUAL PROPERTY AND OWNERSHIP + +### 7.1. Work Product Ownership + +**Intellectual Property Rights:** +**(a)** Work product ownership is specified in individual service agreements; +**(b)** Unless otherwise agreed, we retain ownership of pre-existing intellectual property, tools, and methodologies; +**(c)** Client-specific work product ownership is determined by service agreement terms; +**(d)** All intellectual property terms are subject to applicable laws and our Terms of Service. + +### 7.2. License and Usage Rights + +**Usage Rights:** +**(a)** Usage rights for work product are established in service agreements; +**(b)** We may retain rights to use anonymised work product for portfolio and marketing purposes; +**(c)** Client usage rights are limited to the scope specified in service agreements; +**(d)** Unauthorised use of work product may constitute intellectual property infringement. + +## 8. CONFIDENTIALITY AND PRIVACY + +### 8.1. Confidential Information + +**Confidentiality Obligations:** +**(a)** Confidentiality terms are established in individual service agreements; +**(b)** We maintain confidentiality of client information in accordance with our Privacy Policy and service agreements; +**(c)** Client information is not shared with third parties except as necessary for service provision or as required by law; +**(d)** Confidentiality obligations survive termination of service agreements. + +### 8.2. Data Protection + +**Privacy and Data Security:** +**(a)** Client data is handled in accordance with our Privacy Policy and applicable data protection laws; +**(b)** We implement reasonable security measures to protect client information; +**(c)** We are not liable for data breaches caused by third-party systems or client security failures; +**(d)** Data retention and deletion policies are specified in service agreements. + +## 9. LIMITATION OF LIABILITY AND DISCLAIMERS + +### 9.1. Reference to Comprehensive Liability Framework + +**IMPORTANT: Comprehensive liability limitations, damage exclusions, maximum liability caps, and all related legal protections are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference and governs all matters related to professional services and consulting engagements.** + +### 9.2. Service-Specific Disclaimers + +**Additional Limitations:** +**(a)** We are not liable for business decisions, outcomes, or results based on our services or recommendations; +**(b)** We do not guarantee specific project outcomes, performance metrics, or business results; +**(c)** We are not responsible for third-party services, platforms, or tools used in connection with our services; +**(d)** Our liability is limited to the maximum extent permitted by applicable law and service agreements. + +## 10. TERMINATION AND CANCELLATION + +### 10.1. Service Termination + +**Termination Rights:** +**(a)** Termination rights and procedures are specified in individual service agreements; +**(b)** We reserve the right to terminate services for violations of our Terms of Service or service agreements; +**(c)** Clients may terminate services in accordance with service agreement terms; +**(d)** Termination does not affect accrued obligations or rights established prior to termination. + +### 10.2. Cancellation Policy + +**Cancellation Terms:** +**(a)** Consultation cancellations are subject to our cancellation policy specified at the time of scheduling; +**(b)** Service engagement cancellations are governed by individual service agreements; +**(c)** Cancellation fees may apply as specified in service agreements; +**(d)** We reserve the right to refuse future services following cancellation or termination. + +## 11. CONTACT INFORMATION AND INQUIRIES + +### 11.1. Commission and Service Inquiries + +For inquiries about professional services or to submit commission requests: + +**Commission Request Form:** [https://forms.nhcarrigan.com/form/xrlqjeu8cbmrta-v0ipoxlupepitlkxtwg70uuciora](https://forms.nhcarrigan.com/form/XRlQjeu8CbMrTA-v0IPOxlUPEPitLKXTWg70UUCIORA) + +**Email:** contact@nhcarrigan.com + +**Response Time:** Within 48 hours for service inquiries + +### 11.2. General Contact + +For general inquiries about our organisation or services: + +**Email:** contact@nhcarrigan.com + +**Discord Community:** https://chat.nhcarrigan.com + +## 12. ACKNOWLEDGEMENT AND AGREEMENT + +### 12.1. Policy Acceptance + +By engaging our professional services or submitting commission requests, you acknowledge that you have: +**(a)** Read, understood, and agree to comply with this Policy; +**(b)** Understood that this Policy does not create binding service agreements; +**(c)** Agreed that all professional services require separate written service agreements; +**(d)** Acknowledged all disclaimers, limitations, and legal protections incorporated by reference. + +### 12.2. Service Agreement Supremacy + +**IMPORTANT: This Policy provides general information about our professional services. All actual service engagements are governed by separate written service agreements that supersede this Policy and establish binding terms for specific projects.** + + +--- + +*This Professional Services and Commission Policy establishes general terms and information about our professional services offerings. This Policy does not create binding service agreements. All professional service engagements require separate written agreements. For questions about our services, please contact us through the commission request form or at contact@nhcarrigan.com.* diff --git a/src/content/docs/about/mentorship.md b/src/content/docs/about/mentorship.md index 7fa2105..101f1f2 100644 --- a/src/content/docs/about/mentorship.md +++ b/src/content/docs/about/mentorship.md @@ -2,48 +2,254 @@ title: Mentorship Programme Terms and Conditions --- -Here at NHCarrigan, we are dedicated to lowering the barriers of entry into tech and helping underprivileged/under-represented classes reach their goals. As part of this mission, we offer a mentorship programme ("Programme"). This Programme operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Community Policies, and all applicable legal protections by reference. +**COMPREHENSIVE TERMS AND CONDITIONS FOR MENTORSHIP PROGRAMME PARTICIPATION** -## 1. Introduction +## 1. INTRODUCTION AND SCOPE -These Terms and Conditions (“Terms”) outline the Programme provided by NHCarrigan (“Company”) and apply to all participants enrolled in the Programme. By enrolling, you (the "Mentee") agree to abide by these Terms. The Programme cost is $200 USD per month. +### 1.1. Policy Overview -### 1.1. Enrolment +This Mentorship Programme Terms and Conditions ("Terms" or "Agreement") establishes the terms, conditions, and procedures governing participation in the mentorship programme ("Programme") provided by NHCarrigan ("we," "us," "our," or "the Company"). This Agreement operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, and all applicable legal protections by reference. -To enrol in the Programme, [fill out the application](https://forms.nhcarrigan.com/form/gNv4NYZmdiMWpkUcnknII2yYCvnYNGAmabG5O5He9Mo). +### 1.2. Mission and Purpose -## 2. Programme Services +We are dedicated to lowering barriers of entry into technology and helping underprivileged and under-represented individuals reach their professional goals. The Programme is designed to provide structured mentorship, educational support, and career development opportunities to participants ("Mentees") who enrol in the Programme. -Upon successful enrolment, the Mentee receives the following benefits: +### 1.3. Legal Framework Integration -### 2.1 Dedicated Discord Channels +**IMPORTANT: Comprehensive warranty disclaimers, liability limitations, and all related legal protections are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference and governs all matters related to Programme participation. The Programme is provided "as is" without warranties of any kind.** -Participants will have access to private Discord channels exclusively for Mentees. These channels get priority response times from the NHCarrigan team. All participants must adhere to our [Code of Conduct](/community/coc). +### 1.4. Scope of Application -### 2.3 Flagship Project +This Agreement applies to: +**(a)** All Mentees enrolled in the Programme; +**(b)** All Programme services, benefits, and resources provided to Mentees; +**(c)** All interactions between Mentees and Programme staff, mentors, and resources; +**(d)** All Programme-related activities, projects, and collaborations. -Participants will gain maintainer-level access to a repository under our [Mentorship GitHub organisation](https://github.com/nhcarrigan-mentorship), which they will use to build their flagship project under the tutelage of our team. +## 2. ENROLMENT AND PARTICIPATION -### 2.4 Career Prep and Resume Building +### 2.1. Enrolment Requirements -Participants will have the opportunity to build their resumes through an internship with NHCarrigan. This includes eligibility for project contributions and collaboration with the NHCarrigan team. +**Enrolment Process:** +**(a)** Enrolment in the Programme requires completion of the official [mentorship application form](https://forms.nhcarrigan.com/form/gNv4NYZmdiMWpkUcnknII2yYCvnYNGAmabG5O5He9Mo); +**(b)** We reserve the right to accept or decline applications at our sole discretion; +**(c)** Enrolment is subject to Programme capacity, resource availability, and our assessment of applicant suitability; +**(d)** We are not obligated to provide reasons for application rejection. -### 2.5 Ongoing Support and Resources +### 2.2. Agreement Acceptance -Mentees will receive continuous resume reviews, personalized learning roadmaps, and dedicated guidance for the duration of their membership. Additional resources and Programme updates will be provided as part of this lifetime membership support. +By enrolling in the Programme, Mentees acknowledge and agree that they have: +**(a)** Read, understood, and agree to be bound by these Terms; +**(b)** Reviewed and agree to comply with our Community Code of Conduct and all applicable policies; +**(c)** Acknowledged all disclaimers, limitations, and legal protections incorporated by reference. -## 3. Code of Conduct +## 3. PROGRAMME SERVICES AND BENEFITS -Participants agree to uphold the Company's Code of Conduct and other policies, as outlined in the [NHCarrigan Documentation](https://docs.nhcarrigan.com/community/coc). +### 3.1. Dedicated Discord Channels -## 4 Programme Modifications +**Channel Access:** +**(a)** Mentees receive access to private Discord channels exclusively for Programme participants; +**(b)** These channels receive priority response times from our team; +**(c)** All participants must adhere to our [Community Code of Conduct](/community/coc) and Programme-specific guidelines; +**(d)** We reserve the right to restrict or revoke channel access for violations of community standards or Programme terms. -NHCarrigan reserves the right to modify Programme features, benefits, and terms at any time. Notification of such changes will be provided to participants with as much advance notice as possible. +### 3.2. Flagship Project Development -## 5. Termination and Cancellation +**Project Access and Support:** +**(a)** Mentees gain maintainer-level access to a repository under our [Mentorship GitHub organisation](https://github.com/NHCarrigan-mentorship); +**(b)** Mentees use this repository to build their flagship project under the guidance of our team; +**(c)** Project support and guidance are provided subject to mentor availability and Programme resources; +**(d)** We do not guarantee specific project outcomes, completion, or success. -Participants may cancel their membership at any time, by providing written notice to our team indicating their desire to drop-out and the reason for leaving. +### 3.3. Career Preparation and Resume Building -## 6. Contact Information +**Career Development Services:** +**(a)** Mentees have the opportunity to build their resumes through internship-style experiences with NHCarrigan; +**(b)** This includes eligibility for project contributions and collaboration with our team; +**(c)** Career preparation services are provided for educational and development purposes; +**(d)** We do not guarantee employment, job placement, or specific career outcomes. -For questions or further information, please contact the NHCarrigan team through the official support channels listed in the [documentation](/about/contact). +### 3.4. Ongoing Support and Resources + +**Continuous Support Services:** +**(a)** Mentees receive continuous resume reviews, personalised learning roadmaps, and dedicated guidance for the duration of their membership; +**(b)** Additional resources and Programme updates are provided as part of membership support; +**(c)** Support services are subject to mentor availability and Programme capacity; +**(d)** We reserve the right to modify or discontinue specific support services with reasonable notice. + +### 3.5. Service Limitations and Disclaimers + +**IMPORTANT DISCLAIMERS:** +**(a)** Programme services are provided "as is" without warranties of any kind; +**(b)** We do not guarantee specific learning outcomes, skill development, or career advancement; +**(c)** Programme benefits and services may vary based on mentor availability, resource constraints, and Programme capacity; +**(d)** We reserve the right to modify Programme features, benefits, and services at any time with reasonable notice. + +## 4. CODE OF CONDUCT AND PARTICIPATION STANDARDS + +### 4.1. Community Standards Compliance + +**Code of Conduct Requirements:** +**(a)** All Mentees must comply with our [Community Code of Conduct](/community/coc) and all applicable community policies; +**(b)** Violations of community standards may result in Programme suspension or termination; +**(c)** We reserve the right to take disciplinary action for conduct that violates community standards or Programme terms; +**(d)** Programme participation does not exempt Mentees from community standards or disciplinary procedures. + +### 4.2. Programme Participation Standards + +**Participation Requirements:** +**(a)** Mentees are expected to actively engage with Programme resources and activities; +**(b)** Mentees must maintain respectful and professional conduct in all Programme interactions; +**(c)** Mentees are responsible for their own learning and development progress; +**(d)** We reserve the right to terminate Programme participation for failure to meet participation standards. + +## 5. PROGRAMME MODIFICATIONS AND CHANGES + +### 5.1. Right to Modify Programme + +**Modification Authority:** +**(a)** We reserve the right to modify Programme features, benefits, terms, and services at any time; +**(b)** Significant modifications will be communicated to enrolled Mentees with as much advance notice as possible; +**(c)** Modifications may include changes to Programme structure, benefits, fees, or participation requirements; +**(d)** Continued Programme participation following modifications constitutes acceptance of modified terms. + +### 5.2. Programme Discontinuation + +**Discontinuation Rights:** +**(a)** We reserve the right to discontinue the Programme at any time with reasonable notice to enrolled Mentees; +**(b)** In the event of Programme discontinuation, we will provide prorated refunds for unused Programme fees; +**(c)** We are not liable for any consequences arising from Programme discontinuation beyond fee refunds; +**(d)** Programme discontinuation does not affect accrued obligations or rights established prior to discontinuation. + +## 6. TERMINATION AND CANCELLATION + +### 6.1. Mentee Cancellation Rights + +**Cancellation Process:** +**(a)** Mentees may cancel their Programme membership at any time by providing written notice to our team; +**(b)** Cancellation notices should indicate the Mentee's desire to withdraw and the reason for leaving; +**(c)** Cancellation becomes effective at the end of the current billing period; +**(d)** Fees paid for the current billing period are non-refundable upon cancellation. + +### 6.2. Company Termination Rights + +**Termination Authority:** +**(a)** We reserve the right to terminate Programme participation for violations of these Terms, Community Code of Conduct, or applicable policies; +**(b)** We may terminate Programme participation for non-payment of fees or failure to meet participation standards; +**(c)** Termination may be immediate for serious violations or with notice for other circumstances; +**(d)** We are not obligated to provide refunds for terminated Programme participation. + +### 6.3. Effect of Termination + +**Post-Termination:** +**(a)** Upon termination, Mentees lose access to Programme benefits, channels, and resources; +**(b)** Mentees retain ownership of work products created during Programme participation; +**(c)** Confidentiality and intellectual property obligations survive termination; +**(d)** We are not obligated to provide ongoing support or resources following termination. + +## 7. INTELLECTUAL PROPERTY AND WORK PRODUCT + +### 7.1. Mentee Work Product Ownership + +**Ownership Rights:** +**(a)** Mentees retain ownership of work products, projects, and contributions created during Programme participation; +**(b)** Work products created in Programme repositories are subject to repository licensing terms; +**(c)** We may request permission to showcase Mentee work for Programme promotion and portfolio purposes; +**(d)** Mentees grant us a non-exclusive license to use anonymised work products for Programme improvement and promotion. + +### 7.2. Programme Materials and Resources + +**Company Intellectual Property:** +**(a)** All Programme materials, resources, and content remain our intellectual property; +**(b)** Mentees may use Programme materials for personal learning and development purposes; +**(c)** Programme materials may not be redistributed, sold, or used for commercial purposes without permission; +**(d)** Unauthorised use of Programme materials may constitute intellectual property infringement. + +## 8. PRIVACY AND DATA PROTECTION + +### 8.1. Information Collection and Use + +**Data Handling:** +**(a)** Mentee information is collected and processed in accordance with our Privacy Policy; +**(b)** We collect information necessary for Programme administration, support, and improvement; +**(c)** Mentee information is not shared with third parties except as necessary for Programme provision or as required by law; +**(d)** Mentees may request access to or deletion of their personal information in accordance with our Privacy Policy. + +### 8.2. Programme Communications + +**Communication Practices:** +**(a)** Programme communications may include email, Discord messages, and other digital channels; +**(b)** Mentees consent to receive Programme-related communications; +**(c)** Communications are subject to our Privacy Policy and data protection practices; +**(d)** Mentees may opt out of non-essential communications while remaining enrolled in the Programme. + +## 9. LIMITATION OF LIABILITY AND DISCLAIMERS + +### 9.1. Reference to Comprehensive Liability Framework + +**IMPORTANT: Comprehensive liability limitations, damage exclusions, maximum liability caps, and all related legal protections are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference and governs all matters related to Programme participation.** + +### 9.2. Programme-Specific Disclaimers + +**Additional Limitations:** +**(a)** We are not liable for Mentee learning outcomes, career advancement, or professional success; +**(b)** We do not guarantee job placement, employment opportunities, or specific career outcomes; +**(c)** We are not responsible for Mentee decisions made based on Programme guidance or resources; +**(d)** Our liability is limited to the maximum extent permitted by applicable law and Programme fees paid. + +## 10. PAYMENT TERMS AND REFUND POLICY + +### 10.1. Payment Obligations + +**Payment Requirements:** +**(a)** Programme fees are due in advance on a monthly basis; +**(b)** Payments must be made through designated payment methods; +**(c)** Failure to pay fees may result in Programme suspension or termination; +**(d)** We reserve the right to modify payment terms with reasonable notice. + +### 10.2. Refund Policy + +**Refund Terms:** +**(a)** Programme fees are generally non-refundable; +**(b)** Refunds may be provided for Programme discontinuation or our failure to provide agreed services; +**(c)** Refund requests must be submitted in writing and are subject to our review and approval; +**(d)** Processing fees charged by payment platforms are non-refundable. + +## 11. CONTACT INFORMATION AND SUPPORT + +### 11.1. Programme Inquiries + +For questions about the Programme or to submit cancellation notices: + +**Email:** contact@nhcarrigan.com + +**Response Time:** Within 48 hours for Programme-related inquiries + +### 11.2. General Contact + +For general inquiries about our organisation or services: + +**Email:** contact@nhcarrigan.com + +**Discord Community:** https://chat.nhcarrigan.com + +**Support Channels:** As specified in our [Contact Policy](/about/contact) + +## 12. ACKNOWLEDGEMENT AND AGREEMENT + +### 12.1. Terms Acceptance + +By enrolling in the Programme, Mentees acknowledge that they have: +**(a)** Read, understood, and agree to be bound by these Terms; +**(b)** Reviewed and agree to comply with all applicable policies and community standards; +**(c)** Understood the Programme fees, payment obligations, and refund policy; +**(d)** Acknowledged all disclaimers, limitations, and legal protections incorporated by reference. + +### 12.2. Entire Agreement + +These Terms, together with all incorporated policies and agreements, constitute the entire agreement between Mentees and the Company regarding Programme participation and supersede all prior agreements and understandings. + + +--- + +*This Mentorship Programme Terms and Conditions establishes the terms governing participation in our mentorship programme. By enrolling in the Programme, you acknowledge that you have read, understood, and agree to be bound by these Terms. For questions about the Programme, please contact us at contact@nhcarrigan.com.* diff --git a/src/content/docs/about/mission.md b/src/content/docs/about/mission.md index 91a8904..52af06c 100644 --- a/src/content/docs/about/mission.md +++ b/src/content/docs/about/mission.md @@ -8,11 +8,11 @@ This Mission Statement ("Statement") articulates the core values and guiding pri ### 1.1. Commitment to Inclusivity -The Company shall actively work to dismantle barriers and promote diversity in all areas of its operations. We seek to create spaces where all individuals, particularly from marginalized communities, feel supported and valued. +The Company shall actively work to dismantle barriers and promote diversity in all areas of its operations. We seek to create spaces where all individuals, particularly from marginalised communities, feel supported and valued. ### 1.2. Sustainability as a Priority -Environmental sustainability is integral to the Company's mission. We shall consistently minimize our carbon footprint, use eco-friendly technologies, and ensure that every project aligns with our environmental goals. +Environmental sustainability is integral to the Company's mission. We shall consistently minimise our carbon footprint, use eco-friendly technologies, and ensure that every project aligns with our environmental goals. ### 1.3. Ethical Responsibility @@ -32,15 +32,15 @@ The Company is committed to tearing down the systemic and social barriers that e ### 1.7. Challenging Toxic Behaviors -We recognize that toxic behaviors and exclusionary practices harm communities. The Company shall take a proactive stance in challenging these behaviors within our industry and within the tech communities we interact with, fostering spaces where collaboration, respect, and growth thrive. +We recognise that toxic behaviours and exclusionary practices harm communities. The Company shall take a proactive stance in challenging these behaviours within our industry and within the tech communities we interact with, fostering spaces where collaboration, respect, and growth thrive. ### 1.8. Comprehensive Community Support and Member Welfare -The Company is dedicated to providing comprehensive support systems for community members, including mentorship for new developers, recognition and appreciation programs, and robust member welfare frameworks. Through guided mentorship, educational resources, crisis response systems, and hands-on support, we help individuals thrive within our communities and succeed in the tech industry, particularly focusing on support for underrepresented groups. +The Company is dedicated to providing comprehensive support systems for community members, including mentorship for new developers, recognition and appreciation programmes, and robust member welfare frameworks. Through guided mentorship, educational resources, crisis response systems, and hands-on support, we help individuals thrive within our communities and succeed in the tech industry, particularly focusing on support for underrepresented groups. ## 2. Strategic Goals -### 2.1. Elevating Marginalized Voices +### 2.1. Elevating Marginalised Voices The Company is committed to using its platform to elevate the voices and contributions of individuals from underrepresented communities in tech and beyond. @@ -64,7 +64,7 @@ We will continue to build and expand initiatives aimed at mentoring and supporti ### 3.1. Right to Amend -The Company reserves the right to amend this Statement as necessary to reflect evolving best practices and organizational goals. +The Company reserves the right to amend this Statement as necessary to reflect evolving best practices and organisational goals. ### 3.2. Notification of Changes diff --git a/src/content/docs/about/sustainability.md b/src/content/docs/about/sustainability.md index 4d16379..ebaa08f 100644 --- a/src/content/docs/about/sustainability.md +++ b/src/content/docs/about/sustainability.md @@ -2,7 +2,7 @@ title: Environmental Impact Commitment --- -This Environmental Impact Commitment ("Commitment") outlines the principles and obligations that NHCarrigan ("The Company") upholds to minimize its environmental impact and contribute to global sustainability efforts. This Commitment operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Mission Statement, and all applicable legal protections by reference. +This Environmental Impact Commitment ("Commitment") outlines the principles and obligations that NHCarrigan ("The Company") upholds to minimise its environmental impact and contribute to global sustainability efforts. This Commitment operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Mission Statement, and all applicable legal protections by reference. ## 1. Definitions @@ -26,7 +26,7 @@ A situation where the environmental harm caused by a project or activity exceeds ### 2.1. Commitment to Sustainability -The Company is committed to sustainability at all levels of its operations, actively seeking to minimize its environmental impact and promote long-term environmental health. +The Company is committed to sustainability at all levels of its operations, actively seeking to minimise its environmental impact and promote long-term environmental health. ### 2.2. Prioritization of Environmental Impact @@ -34,7 +34,7 @@ Environmental considerations, including carbon footprint and resource consumptio ### 2.3. Responsible Technology Use -The Company shall only utilize technologies that align with its environmental goals, ensuring minimal energy consumption and environmental degradation. +The Company shall only utilise technologies that align with its environmental goals, ensuring minimal energy consumption and environmental degradation. ## 3. Carbon Offsetting diff --git a/src/content/docs/community/appeal.md b/src/content/docs/community/appeal.md index 8cd95cc..0eedb45 100644 --- a/src/content/docs/community/appeal.md +++ b/src/content/docs/community/appeal.md @@ -4,11 +4,11 @@ title: Community Disciplinary Appeals Policy ## 1. Preamble and Purpose -### 1.1 Introduction +### 1.1. Introduction This Community Disciplinary Appeals Policy (hereinafter referred to as "the Policy") establishes the formal procedures and requirements for appealing disciplinary sanctions imposed by our moderation team. Whilst our Community Leaders exercise careful discretion and professional judgement when implementing disciplinary measures, we acknowledge that human error or misunderstandings may occasionally occur within any moderation system. -### 1.2 Purpose and Scope +### 1.2. Purpose and Scope This Policy serves to: - Provide a fair and transparent mechanism for reviewing disciplinary decisions @@ -16,13 +16,13 @@ This Policy serves to: - Maintain the integrity of our community standards whilst protecting individual rights - Establish clear procedures for both appellants and review panels -### 1.3 Right of Appeal +### 1.3. Right of Appeal Every community member who receives a disciplinary sanction has the fundamental right to appeal such decision through the procedures outlined herein, subject to the conditions and limitations specified in this Policy. ## 2. Definitions and Interpretation -### 2.1 Key Definitions +### 2.1. Key Definitions For the purposes of this Policy: - **"Appellant"** means any individual seeking to appeal a disciplinary sanction @@ -31,13 +31,13 @@ For the purposes of this Policy: - **"Original Decision"** means the initial disciplinary action being appealed - **"Community Leaders"** means moderators, administrators, and other authorised personnel -### 2.2 Interpretation +### 2.2. Interpretation This Policy shall be interpreted in accordance with principles of fairness, natural justice, and the overarching objectives of maintaining community safety and standards. ## 3. Grounds for Appeal -### 3.1 Acceptable Grounds +### 3.1. Acceptable Grounds Appeals may be submitted on the following grounds: 1. **Procedural Irregularity**: The disciplinary process was not followed correctly @@ -46,7 +46,7 @@ Appeals may be submitted on the following grounds: 4. **New Evidence**: Relevant evidence has become available that was not considered in the original decision 5. **Misinterpretation of Policy**: The community guidelines or terms of service were incorrectly applied -### 3.2 Inadmissible Appeals +### 3.2. Inadmissible Appeals Appeals will not be considered on the following grounds: 1. General disagreement with community policies or guidelines @@ -56,7 +56,7 @@ Appeals will not be considered on the following grounds: ## 4. Pre-Appeal Requirements -### 4.1 Mandatory Preparation +### 4.1. Mandatory Preparation Prior to submitting an appeal, appellants must complete the following preparatory steps: @@ -69,7 +69,7 @@ Prior to submitting an appeal, appellants must complete the following preparator 3. **Self-Assessment**: Complete a comprehensive self-assessment of the circumstances leading to the sanction -### 4.2 Required Documentation +### 4.2. Required Documentation Appeals must include the following information: 1. **Identity Verification**: Full account details and contact information @@ -81,11 +81,11 @@ Appeals must include the following information: ## 5. Appeal Submission Procedures -### 5.1 Formal Submission Process +### 5.1. Formal Submission Process Appeals must be submitted through our official appeals portal: [Community Appeals Form](https://forms.nhcarrigan.com/form/l3PC15yalSWjdZASTQvGo22q_uj_7OtXAhZdcW35ev8) -### 5.2 Submission Requirements +### 5.2. Submission Requirements All appeals must: - Be submitted within thirty (30) days of the original sanction @@ -93,7 +93,7 @@ All appeals must: - Be written in clear, professional language - Demonstrate good faith engagement with the appeals process -### 5.3 Multiple Appeal Prohibition +### 5.3. Multiple Appeal Prohibition :::caution[Critical Warning] Submitting multiple appeals for the same disciplinary sanction will result in automatic dismissal of all subsequent appeals and may constitute abuse of process, potentially leading to additional sanctions. @@ -101,7 +101,7 @@ Submitting multiple appeals for the same disciplinary sanction will result in au ## 6. Review Process and Procedures -### 6.1 Initial Review +### 6.1. Initial Review Upon receipt, all appeals undergo an initial administrative review to ensure: - Compliance with submission requirements @@ -109,7 +109,7 @@ Upon receipt, all appeals undergo an initial administrative review to ensure: - Completeness of documentation - Identification of appropriate grounds for appeal -### 6.2 Substantive Review +### 6.2. Substantive Review Appeals meeting initial requirements proceed to substantive review, wherein the Appeals Panel shall: 1. Examine all evidence and documentation @@ -117,13 +117,13 @@ Appeals meeting initial requirements proceed to substantive review, wherein the 3. Consider the appellant's submissions and arguments 4. Assess whether the appeal has merit under the established grounds -### 6.3 Review Timeline +### 6.3. Review Timeline The Appeals Panel endeavours to complete reviews within fourteen (14) business days of receipt, though complex cases may require additional time. ## 7. Possible Outcomes and Decisions -### 7.1 Appeal Outcomes +### 7.1. Appeal Outcomes Following review, the Appeals Panel may: 1. **Uphold the Appeal**: Overturn the original sanction entirely @@ -131,7 +131,7 @@ Following review, the Appeals Panel may: 3. **Dismiss the Appeal**: Confirm the original sanction remains in full effect 4. **Remit for Reconsideration**: Return the matter for fresh consideration with specific directions -### 7.2 Decision Communication +### 7.2. Decision Communication All appeal decisions shall be communicated in writing to the appellant, including: - The outcome of the appeal @@ -141,11 +141,11 @@ All appeal decisions shall be communicated in writing to the appellant, includin ## 8. Finality and Limitations -### 8.1 Decision Finality +### 8.1. Decision Finality Decisions of the Appeals Panel are final and binding. No further appeals or reviews are available through our internal processes. -### 8.2 Discretionary Rights Reserved +### 8.2. Discretionary Rights Reserved Notwithstanding this appeals process, we reserve the absolute right to: - Deny or revoke access to our services at any time @@ -153,7 +153,7 @@ Notwithstanding this appeals process, we reserve the absolute right to: - Take additional action based on new information or circumstances - Refuse service to any individual at our sole discretion -### 8.3 Abuse of Process +### 8.3. Abuse of Process Repeated abuse of the appeals process, including but not limited to: - Submitting frivolous or vexatious appeals @@ -165,7 +165,7 @@ May result in permanent ineligibility for future appeals and additional discipli ## 9. Compliance and Acknowledgement -### 9.1 Terms Acceptance +### 9.1. Terms Acceptance By submitting an appeal through this process, appellants explicitly acknowledge that they have: - Read and understood this Appeals Policy in its entirety @@ -173,7 +173,7 @@ By submitting an appeal through this process, appellants explicitly acknowledge - Agreed to accept the decision of the Appeals Panel as final and binding - Committed to full compliance with all community standards upon any reinstatement -### 9.2 Legal Framework Integration +### 9.2. Legal Framework Integration This appeals process operates within our comprehensive legal and policy framework, including: @@ -183,20 +183,20 @@ This appeals process operates within our comprehensive legal and policy framewor **(c)** **Content and Moderation Policy**: Enforcement procedures and standards; -**(d)** **All applicable policies**: Privacy, acceptable use, and specialized policies incorporated by reference. +**(d)** **All applicable policies**: Privacy, acceptable use, and specialised policies incorporated by reference. **IMPORTANT**: This appeals process is provided as an internal community service and does not create any legal rights or obligations beyond those established in our comprehensive legal policies. The availability of this process does not limit our right to take any action deemed necessary for community safety and integrity. ## 10. Policy Updates and Amendments -### 10.1 Amendment Rights +### 10.1. Amendment Rights This Policy may be updated, modified, or amended at any time without prior notice. Appellants are responsible for ensuring familiarity with the current version of this Policy. -### 10.2 Effective Date +### 10.2. Policy Implementation -This Policy is effective immediately upon publication and applies to all appeals submitted after its implementation. +This Policy applies to all appeals submitted after its implementation. --- -*This Community Disciplinary Appeals Policy was last updated on 15 September 2025 and supersedes all previous versions.* +*This Community Disciplinary Appeals Policy.* diff --git a/src/content/docs/community/coc.md b/src/content/docs/community/coc.md index b0036b1..209f353 100644 --- a/src/content/docs/community/coc.md +++ b/src/content/docs/community/coc.md @@ -4,11 +4,11 @@ title: Community Code of Conduct ## 1. Preamble and Foundational Principles -### 1.1 Introduction and Purpose +### 1.1. Introduction and Purpose This Community Code of Conduct (hereinafter referred to as "the Code") establishes the fundamental standards of behaviour and conduct expected from all individuals participating in our community ecosystem. This Code serves as the cornerstone of our commitment to fostering an inclusive, safe, and productive environment wherein all members can participate meaningfully and contribute positively to our collective objectives. -### 1.2 Fundamental Values +### 1.2. Fundamental Values Our community is built upon the following core principles: - **Respect and Dignity**: Every individual deserves to be treated with courtesy, respect, and human dignity @@ -17,7 +17,7 @@ Our community is built upon the following core principles: - **Constructive Collaboration**: We encourage productive dialogue, constructive criticism, and collaborative problem-solving - **Transparency and Accountability**: We operate with openness, honesty, and accept responsibility for our actions and decisions -### 1.3 Legal Framework and Policy Integration +### 1.3. Legal Framework and Policy Integration This Code operates within and supplements our comprehensive legal and policy framework, including: @@ -31,17 +31,17 @@ This Code operates within and supplements our comprehensive legal and policy fra **(e)** **Limitation of Liability and Indemnification Policy**: Legal protections and risk allocation; -**(f)** **All other applicable legal policies**: Export control, service level agreements, and specialized policies. +**(f)** **All other applicable legal policies**: Export control, service level agreements, and specialised policies. -**IMPORTANT**: Where this Code overlaps with our comprehensive legal policies, users are subject to both sets of requirements. For detailed enforcement procedures, content moderation standards, and legal protections, refer to the applicable specialized policies incorporated by reference. +**IMPORTANT**: Where this Code overlaps with our comprehensive legal policies, users are subject to both sets of requirements. For detailed enforcement procedures, content moderation standards, and legal protections, refer to the applicable specialised policies incorporated by reference. ## 2. Definitions and Scope of Application -### 2.1 Comprehensive Definitions +### 2.1. Comprehensive Definitions For the purposes of this Code, the following definitions shall apply: -#### 2.1.1 Community Ecosystem +#### 2.1.1. Community Ecosystem **"Our Community"** encompasses all platforms, spaces, and environments, whether digital, physical, or hybrid, where members interact under our organisation's auspices, including but not limited to: - Official Discord servers and communication platforms - Code repositories, version control systems, and development platforms @@ -52,7 +52,7 @@ For the purposes of this Code, the following definitions shall apply: - Virtual events, webinars, and online presentations - Any other platform officially endorsed, managed, or sponsored by our organisation -#### 2.1.2 Community Participants +#### 2.1.2. Community Participants **"Community Members"** refers to all individuals who participate in Our Community, regardless of their role, level of engagement, or duration of participation, including: - Casual users and occasional participants - Regular contributors and active members @@ -61,7 +61,7 @@ For the purposes of this Code, the following definitions shall apply: - Administrative staff and organisational representatives - Guest speakers, invited participants, and temporary contributors -#### 2.1.3 Leadership and Authority +#### 2.1.3. Leadership and Authority **"Community Leaders"** refers to individuals vested with official responsibilities, authority, and trust within Our Community, including: - Community moderators and content moderators - Technical administrators and system administrators @@ -70,38 +70,38 @@ For the purposes of this Code, the following definitions shall apply: - Event organisers and programme coordinators - Senior administrators and executive leadership -#### 2.1.4 Conduct and Violations +#### 2.1.4. Conduct and Violations **"Code of Conduct Violation"** means any behaviour, action, or communication that contravenes the guidelines, standards, and principles outlined in this Code or its associated policies. **"Reporting"** refers to the formal process of bringing potential Code of Conduct violations to the attention of Community Leaders through officially designated channels and procedures. **"Disciplinary Sanctions"** means the consequences, penalties, or corrective measures imposed upon community members who violate this Code, as determined by Community Leaders in accordance with established procedures. -### 2.2 Territorial and Temporal Scope +### 2.2. Territorial and Temporal Scope -#### 2.2.1 Primary Application +#### 2.2.1. Primary Application This Code applies directly and immediately to all interactions, communications, and behaviours occurring within Our Community spaces, including: - Public channels, forums, and discussion areas - Private channels, direct messages, and personal communications conducted through community platforms - Online and offline community-organised events and activities - Any communication using official community branding, accounts, or platforms -#### 2.2.2 Extended Application +#### 2.2.2. Extended Application This Code may also extend to interactions and behaviours occurring outside Our Community spaces when such conduct: - Involves multiple Community Members in a manner that affects community relationships or dynamics - Has a substantial, demonstrable impact on the well-being, safety, or participation of Community Members - Significantly affects the reputation, integrity, or safety of Our Community or its members - Constitutes harassment, threats, or other harmful behaviour directed at Community Members -#### 2.2.3 Temporal Considerations +#### 2.2.3. Temporal Considerations This Code applies to: - All current and ongoing interactions within Our Community - Past behaviour and conduct of Community Members, including actions that occurred prior to joining Our Community - Patterns of behaviour that may have commenced before participation in Our Community but continue to affect community dynamics -### 2.3 Reporting Framework +### 2.3. Reporting Framework -#### 2.3.1 Reporting Obligations and Encouragement +#### 2.3.1. Reporting Obligations and Encouragement We strongly encourage the reporting of any violations of this Code, including but not limited to: - Harassment, discrimination, or threats directed at Community Members - Violations committed by Community Leaders or individuals in positions of authority @@ -109,7 +109,7 @@ We strongly encourage the reporting of any violations of this Code, including bu - Historical incidents, regardless of when they occurred - Patterns of concerning behaviour that may not constitute individual violations but collectively create problems -#### 2.3.2 Community Leader Responsibilities +#### 2.3.2. Community Leader Responsibilities Community Leaders commit to the following standards in handling reports: - Treat all good-faith reports with seriousness, confidentiality, and respect - Protect the privacy, safety, and security of all report submitters @@ -120,35 +120,35 @@ Community Leaders commit to the following standards in handling reports: ## 3. Standards of Acceptable Conduct -### 3.1 Positive Behaviours and Expectations +### 3.1. Positive Behaviours and Expectations Community Members are expected to demonstrate the following positive behaviours: -#### 3.1.1 Respectful Communication +#### 3.1.1. Respectful Communication - Use welcoming, inclusive, and professional language in all interactions - Listen actively and engage constructively with diverse perspectives and viewpoints - Provide constructive feedback that focuses on ideas and contributions rather than individuals - Acknowledge mistakes promptly, apologise sincerely when appropriate, and learn from errors -#### 3.1.2 Collaborative Engagement +#### 3.1.2. Collaborative Engagement - Contribute positively to discussions and community activities - Support and mentor newcomers and less experienced community members - Share knowledge generously whilst respecting intellectual property rights - Participate in good faith and assume positive intent from others unless proven otherwise -#### 3.1.3 Professional Conduct +#### 3.1.3. Professional Conduct - Maintain appropriate boundaries between personal and professional interactions - Respect the time, effort, and contributions of all community members - Comply with all applicable laws, regulations, and platform-specific terms of service - Represent Our Community positively when acting in any official or semi-official capacity -### 3.2 Prohibited Conduct and Behaviours +### 3.2. Prohibited Conduct and Behaviours **Reference to Comprehensive Usage Policies**: Detailed prohibited activities, content restrictions, and usage guidelines are comprehensively covered in our Acceptable Use Policy and Content and Moderation Policy, which are incorporated herein by reference. -#### 3.2.1 Community-Specific Prohibited Conduct +#### 3.2.1. Community-Specific Prohibited Conduct -In addition to all prohibitions in our comprehensive policies, the following behaviors are specifically prohibited in community interactions: +In addition to all prohibitions in our comprehensive policies, the following behaviours are specifically prohibited in community interactions: **Identity and Discrimination:** - Deliberate misgendering, deadnaming, or use of rejected names or pronouns @@ -169,54 +169,54 @@ In addition to all prohibitions in our comprehensive policies, the following beh ## 4. Community Standards and Specific Policies -### 4.1 Neutrality and Social Justice +### 4.1. Neutrality and Social Justice -#### 4.1.1 Position on Oppression +#### 4.1.1. Position on Oppression :::caution[Community Position] Our Community explicitly rejects neutrality in the face of oppression. Remaining neutral when marginalised individuals share their experiences with discrimination, oppression, or harmful legislation constitutes support for oppressive systems and structures. ::: -#### 4.1.2 Educational Approach +#### 4.1.2. Educational Approach We recognise that not all community members may be fully aware of the challenges faced by marginalised communities. We encourage: - Asking respectful questions to educate oneself about social justice issues - Listening to the experiences of marginalised community members - Engaging constructively with discussions about equality and human rights - Taking responsibility for one's own education on social justice matters -#### 4.1.3 Prohibited Responses +#### 4.1.3. Prohibited Responses The following responses to discussions of oppression and marginalisation are considered violations of this Code: - Attempting to remain "neutral" or "bow out" of discussions about oppression - Claiming that discussions of discrimination or social justice are inappropriate or divisive - Dismissing or minimising the experiences of marginalised community members - Engaging in "whataboutism" or false equivalencies regarding discrimination -### 4.2 Intellectual Property and Privacy Rights +### 4.2. Intellectual Property and Privacy Rights -#### 4.2.1 Copyright and Attribution +#### 4.2.1. Copyright and Attribution Community Members must: - Respect all copyright and intellectual property rights - Provide appropriate attribution when sharing or referencing others' work - Obtain permission before sharing copyrighted material - Comply with fair use principles and applicable copyright laws -#### 4.2.2 Privacy Protection +#### 4.2.2. Privacy Protection Community Members must: - Respect the privacy of all community members - Obtain explicit consent before sharing personal information about others - Protect confidential information shared within community contexts - Report privacy violations to Community Leaders promptly -### 4.3 Content Standards and Community Guidelines +### 4.3. Content Standards and Community Guidelines -#### 4.3.1 Appropriate Content +#### 4.3.1. Appropriate Content All content shared within Our Community must: - Be relevant to community discussions and purposes - Comply with platform-specific content policies - Include appropriate content warnings when discussing potentially triggering topics - Respect community standards regarding language, imagery, and subject matter -#### 4.3.2 Content Warnings and Accessibility +#### 4.3.2. Content Warnings and Accessibility Community Members are required to: - Use content warnings when discussing potentially distressing topics - Provide alternative text for images and visual content when possible @@ -225,16 +225,16 @@ Community Members are required to: ## 5. Reporting Procedures and Incident Response -### 5.1 Reporting Mechanisms +### 5.1. Reporting Mechanisms -#### 5.1.1 Available Reporting Methods +#### 5.1.1. Available Reporting Methods Community Members can report Code of Conduct violations through the following channels: - **Discord Reporting**: Type `@Moderator` in any channel to alert Community Leaders - **Direct Communication**: Contact any Community Leader through private messages - **Email Contact**: Submit reports to contact@nhcarrigan.com - **Anonymous Reporting**: Use designated anonymous reporting forms where available -#### 5.1.2 Information to Include in Reports +#### 5.1.2. Information to Include in Reports Effective reports should include: - Contact information (unless reporting anonymously) - Names, usernames, or identifiable information for all individuals involved @@ -244,9 +244,9 @@ Effective reports should include: - Any previous related incidents or patterns of behaviour - Impact statement describing how the incident has affected you or others -### 5.2 Report Handling and Investigation Procedures +### 5.2. Report Handling and Investigation Procedures -#### 5.2.1 Initial Response Protocol +#### 5.2.1. Initial Response Protocol Upon receiving a report, Community Leaders will: - Acknowledge receipt within 24 hours when possible - Conduct an initial assessment of the report's severity and scope @@ -254,7 +254,7 @@ Upon receiving a report, Community Leaders will: - Recuse any Community Leaders who have conflicts of interest in the matter - Begin formal investigation procedures within 72 hours -#### 5.2.2 Investigation Standards +#### 5.2.2. Investigation Standards All investigations will adhere to the following standards: - **Thoroughness**: Complete examination of all evidence and witness statements - **Impartiality**: Fair consideration of all perspectives and evidence @@ -262,7 +262,7 @@ All investigations will adhere to the following standards: - **Timeliness**: Completion of investigations in a reasonable timeframe - **Documentation**: Proper record-keeping for accountability and consistency -#### 5.2.3 Confidentiality and Privacy Protection +#### 5.2.3. Confidentiality and Privacy Protection Community Leaders commit to: - Respecting confidentiality requests from reporters and witnesses - Limiting information sharing to those with legitimate need-to-know @@ -270,16 +270,16 @@ Community Leaders commit to: - Balancing transparency with privacy protection - Never revealing harassment victims' identities without explicit, affirmative consent -### 5.3 Response and Resolution Options +### 5.3. Response and Resolution Options -#### 5.3.1 Protective Measures +#### 5.3.1. Protective Measures Community Leaders may implement immediate protective measures including: - Temporary suspension of accused individuals pending investigation - Modification of access permissions or privileges - Implementation of no-contact orders between parties - Enhanced monitoring of specific community areas or interactions -#### 5.3.2 Public Statements and Warnings +#### 5.3.2. Public Statements and Warnings At Community Leaders' discretion, we may: - Issue public statements regarding individuals who pose community safety risks - Provide private warnings to third parties when necessary for community protection @@ -288,25 +288,25 @@ At Community Leaders' discretion, we may: ## 6. Disciplinary Framework and Enforcement -### 6.1 Reference to Comprehensive Enforcement Framework +### 6.1. Reference to Comprehensive Enforcement Framework **IMPORTANT: Comprehensive enforcement procedures, moderation standards, appeals processes, and disciplinary frameworks are set forth in our Content and Moderation Policy, which is incorporated herein by reference and governs all community enforcement matters.** -### 6.2 Community-Specific Enforcement Principles +### 6.2. Community-Specific Enforcement Principles -In addition to the comprehensive framework in our Moderation Policy, community enforcement emphasizes: +In addition to the comprehensive framework in our Moderation Policy, community enforcement emphasises: **(a)** **Restorative Justice**: Focus on repairing harm and restoring community relationships when possible; **(b)** **Community Safety**: Ultimate priority on protecting community members from harm and discrimination; -**(c)** **Educational Approach**: Emphasis on learning and behavior modification where appropriate; +**(c)** **Educational Approach**: Emphasis on learning and behaviour modification where appropriate; **(d)** **Community Values**: Enforcement that upholds our specific community values of inclusivity and respect. -### 6.2 Violation Assessment Criteria +### 6.2. Violation Assessment Criteria -#### 6.2.1 Sanctionable Conduct +#### 6.2.1. Sanctionable Conduct Disciplinary sanctions may be imposed for: - Direct violations of this Code of Conduct or associated community policies - Behaviour that violates the spirit of community standards even if not explicitly prohibited @@ -314,7 +314,7 @@ Disciplinary sanctions may be imposed for: - Attempts to circumvent or evade existing sanctions - Behaviour that demonstrates disregard for community values and member safety -#### 6.2.2 Aggravating and Mitigating Factors +#### 6.2.2. Aggravating and Mitigating Factors When determining appropriate sanctions, Community Leaders consider: **Aggravating Factors:** @@ -331,9 +331,9 @@ When determining appropriate sanctions, Community Leaders consider: - Acknowledgement of wrongdoing and commitment to improvement - Circumstances that may have contributed to the violation -### 6.3 Progressive Disciplinary System +### 6.3. Progressive Disciplinary System -#### 6.3.1 Level 1: Formal Reminder and Education +#### 6.3.1. Level 1: Formal Reminder and Education **Typical Application:** - First-time violations of community standards - Use of inappropriate language or unprofessional behaviour @@ -352,7 +352,7 @@ When determining appropriate sanctions, Community Leaders consider: - Engaging in behaviour that disrupts community discussions - Sharing content without appropriate warnings or context -#### 6.3.2 Level 2: Formal Warning and Monitoring +#### 6.3.2. Level 2: Formal Warning and Monitoring **Typical Application:** - Violations following previous reminders or educational interventions - Moderate violations of community standards @@ -371,7 +371,7 @@ When determining appropriate sanctions, Community Leaders consider: - Repeated disruption of community discussions despite warnings - Failure to respect others' boundaries after being asked to stop -#### 6.3.3 Level 3: Temporary Suspension and Mandatory Education +#### 6.3.3. Level 3: Temporary Suspension and Mandatory Education **Typical Application:** - Serious violations of community standards - Repeated violations despite previous warnings @@ -390,7 +390,7 @@ When determining appropriate sanctions, Community Leaders consider: - Violations that significantly disrupt community activities or discussions - Behaviour that makes other community members feel unsafe -#### 6.3.4 Level 4: Permanent Exclusion +#### 6.3.4. Level 4: Permanent Exclusion **Typical Application:** - Severe violations that pose significant risk to community safety - Patterns of repeated violations with no demonstrated improvement @@ -408,9 +408,9 @@ When determining appropriate sanctions, Community Leaders consider: - Sexual harassment or other forms of serious misconduct - Attempts to harm the community or its members through any means -### 6.4 Special Considerations and Additional Measures +### 6.4. Special Considerations and Additional Measures -#### 6.4.1 Enhanced Sanctions +#### 6.4.1. Enhanced Sanctions Community Leaders may impose additional requirements or restrictions including: - Public acknowledgement of wrongdoing and apology to affected parties - Completion of specific educational programmes or training @@ -418,7 +418,7 @@ Community Leaders may impose additional requirements or restrictions including: - Ongoing behavioural monitoring and reporting requirements - Restrictions on specific community privileges or leadership opportunities -#### 6.4.2 Immediate Protection Measures +#### 6.4.2. Immediate Protection Measures In cases where immediate action is necessary to protect community safety: - Temporary suspension may be implemented immediately pending investigation - Emergency removal from specific platforms or activities may occur @@ -427,9 +427,9 @@ In cases where immediate action is necessary to protect community safety: ## 7. Transparency and Accountability Systems -### 7.1 Documentation and Record-Keeping +### 7.1. Documentation and Record-Keeping -#### 7.1.1 Comprehensive Logging System +#### 7.1.1. Comprehensive Logging System All disciplinary actions are recorded in our public transparency system available at [https://hikari.nhcarrigan.com/sanctions](https://hikari.nhcarrigan.com/sanctions), including: - Date and time of each disciplinary action - Type and severity of sanction imposed @@ -439,39 +439,39 @@ All disciplinary actions are recorded in our public transparency system availabl - Community Leader responsible for implementing the sanction - Relevant evidence or documentation (with appropriate redaction) -#### 7.1.2 Privacy Protection in Documentation +#### 7.1.2. Privacy Protection in Documentation While maintaining transparency, we protect individual privacy by: - Anonymising personally identifiable information in public logs - Redacting sensitive details that could enable identification of victims - Balancing transparency with confidentiality requirements - Providing more detailed information only to authorised personnel -### 7.2 Appeals and Review Process +### 7.2. Appeals and Review Process -#### 7.2.1 Right to Appeal +#### 7.2.1. Right to Appeal Individuals subject to disciplinary sanctions have the right to appeal such decisions through our [formal appeals process](/community/appeal), which includes: - Review by Community Leaders not involved in the original decision - Consideration of new evidence or mitigating circumstances - Opportunity to present alternative perspectives or explanations - Fair and impartial review of the original decision and its basis -#### 7.2.2 Appeals Process Integrity +#### 7.2.2. Appeals Process Integrity During the appeals process: - Original sanctions remain in effect pending review - Appeals are reviewed by impartial Community Leaders - Decisions are based on evidence and established community standards - Final appeal decisions are communicated with detailed reasoning -### 7.3 Community Oversight and Continuous Improvement +### 7.3. Community Oversight and Continuous Improvement -#### 7.3.1 Regular Review and Assessment +#### 7.3.1. Regular Review and Assessment Our disciplinary system undergoes regular review including: - Annual assessment of consistency in sanction application - Community feedback collection on disciplinary processes - Review of appeals outcomes to identify systemic issues - Updates to policies and procedures based on community evolution -#### 7.3.2 Community Leader Accountability +#### 7.3.2. Community Leader Accountability Community Leaders are held accountable through: - Regular training on community standards and disciplinary procedures - Peer review of disciplinary decisions for consistency @@ -480,9 +480,9 @@ Community Leaders are held accountable through: ## 8. Advertising, Promotion, and Commercial Activity -### 8.1 General Prohibition on Commercial Activity +### 8.1. General Prohibition on Commercial Activity -#### 8.1.1 Scope of Prohibition +#### 8.1.1. Scope of Prohibition Commercial advertising and self-promotion are generally prohibited within Our Community spaces, including: - Unsolicited promotion of products, services, websites, or social media accounts - Commercial advertising or marketing communications @@ -490,38 +490,38 @@ Commercial advertising and self-promotion are generally prohibited within Our Co - Affiliate marketing or referral link sharing - Solicitation for commercial purposes or business development -#### 8.1.2 Rationale for Restrictions +#### 8.1.2. Rationale for Restrictions These restrictions exist to: - Maintain focus on community purposes and objectives - Prevent exploitation of community relationships for commercial gain - Ensure equal participation opportunities for all members - Protect community members from unwanted commercial solicitation -### 8.2 Authorised Exceptions and Permitted Activities +### 8.2. Authorised Exceptions and Permitted Activities -#### 8.2.1 Approved Commercial Activities +#### 8.2.1. Approved Commercial Activities The following activities are permitted when explicitly authorised: - Official announcements or promotions approved by Community Leaders - Sharing of resources directly relevant to ongoing discussions when done in good faith - Links or information specifically requested by Community Leaders for support or moderation purposes - Educational resources that provide value to the community without primary commercial purpose -#### 8.2.2 Context-Appropriate Sharing +#### 8.2.2. Context-Appropriate Sharing Limited sharing may be acceptable when: - Content is directly relevant to current discussions or community needs - Sharing is done transparently without hidden commercial motives - The primary purpose is education or community benefit rather than promotion - Appropriate disclosure of any commercial relationships or affiliations is provided -### 8.3 Compliance and Enforcement +### 8.3. Compliance and Enforcement -#### 8.3.1 Disclosure Requirements +#### 8.3.1. Disclosure Requirements When sharing any content with potential commercial implications, Community Members must: - Clearly disclose any personal, professional, or financial relationships with promoted entities - Identify themselves when sharing content from projects or organisations with which they are affiliated - Be transparent about any potential benefits they may receive from community members' engagement -#### 8.3.2 Violation Consequences +#### 8.3.2. Violation Consequences Violations of advertising and promotion restrictions will be addressed through: - Content removal and community member education for minor violations - Formal warnings for repeated or more serious promotional activities @@ -530,16 +530,16 @@ Violations of advertising and promotion restrictions will be addressed through: ## 9. Language Requirements and Communication Standards -### 9.1 Official Language Policy +### 9.1. Official Language Policy -#### 9.1.1 English as Primary Language +#### 9.1.1. English as Primary Language The official language of Our Community is English, and all community interactions, discussions, and contributions should be conducted in English to ensure: - Clear communication among all community members - Effective moderation and community management - Consistency across all community platforms and activities - Accessibility for the broadest range of community members -#### 9.1.2 Scope of Application +#### 9.1.2. Scope of Application The English language requirement applies to: - All public discussions and communications within community spaces - Documentation, contributions, and community-generated content @@ -547,32 +547,32 @@ The English language requirement applies to: - Support requests and community assistance interactions - Disciplinary and administrative communications -### 9.2 Support for Non-Native English Speakers +### 9.2. Support for Non-Native English Speakers -#### 9.2.1 Inclusive Approach +#### 9.2.1. Inclusive Approach We actively support non-native English speakers by: - Encouraging patience and understanding from all community members - Providing assistance with language barriers when appropriate - Focusing on the substance of contributions rather than perfect grammar or syntax - Offering clarification and rephrasing when communication difficulties arise -#### 9.2.2 Accommodation Measures +#### 9.2.2. Accommodation Measures Community Members are encouraged to: - Help clarify or rephrase messages when language barriers exist - Provide gentle correction or assistance when requested - Use clear, simple language to facilitate understanding - Be patient with translation delays or communication difficulties -### 9.3 Limited Exceptions and Special Circumstances +### 9.3. Limited Exceptions and Special Circumstances -#### 9.3.1 Permitted Exceptions +#### 9.3.1. Permitted Exceptions Limited use of languages other than English may be acceptable for: - Brief translations provided to assist community members, when immediately accompanied by English translation - Cultural sharing or educational content when clearly contextualised and explained in English - Emergency situations where immediate communication is necessary - Specific community events or activities explicitly designated as multilingual -#### 9.3.2 Translation and Accessibility Tools +#### 9.3.2. Translation and Accessibility Tools Community Members may: - Use translation tools to assist with participation, provided English content is also included - Request assistance with translation when needed for full participation @@ -580,56 +580,56 @@ Community Members may: ## 10. Implementation, Amendment, and Enforcement -### 10.1 Code Implementation and Effective Date +### 10.1. Code Implementation -#### 10.1.1 Immediate Effect +#### 10.1.1. Immediate Effect This Code of Conduct takes effect immediately upon publication and applies to all community interactions occurring after its implementation. Community Members are responsible for familiarising themselves with these standards and ensuring compliance in all community activities. -#### 10.1.2 Retroactive Considerations +#### 10.1.2. Retroactive Considerations While this Code primarily governs future conduct, Community Leaders reserve the right to consider past behaviour patterns when assessing current community participation and determining appropriate responses to new violations. -### 10.2 Amendment and Update Procedures +### 10.2. Amendment and Update Procedures -#### 10.2.1 Amendment Authority +#### 10.2.1. Amendment Authority This Code may be amended, updated, or modified at any time by Community Leaders to: - Address emerging community issues or challenges - Incorporate lessons learned from community experiences - Reflect changes in legal requirements or best practices - Respond to community feedback and suggestions for improvement -#### 10.2.2 Change Communication +#### 10.2.2. Change Communication Significant amendments to this Code will be communicated to the community through: - Announcements in primary community channels - Updates to community documentation and resources - Direct notification to Community Leaders and active participants - Clear indication of changes in publicly accessible versions -### 10.3 Enforcement Authority and Discretion +### 10.3. Enforcement Authority and Discretion -#### 10.3.1 Community Leader Authority +#### 10.3.1. Community Leader Authority Community Leaders possess both the authority and obligation to: - Interpret and apply this Code consistently and fairly - Take any action deemed necessary to protect community safety and integrity - Modify or expand enforcement procedures as community needs evolve - Collaborate with external authorities when violations involve illegal activity -#### 10.3.2 Discretionary Enforcement +#### 10.3.2. Discretionary Enforcement While this Code provides comprehensive guidance, Community Leaders retain discretion to: - Address situations not explicitly covered by written policies - Apply contextual judgement in complex or unusual circumstances - Implement innovative solutions to emerging community challenges - Prioritise community safety and well-being over rigid rule application -### 10.4 Legal and Operational Integration +### 10.4. Legal and Operational Integration -#### 10.4.1 Relationship to Other Policies +#### 10.4.1. Relationship to Other Policies This Code operates in conjunction with and supplements: - Terms of Service and User Agreements - Privacy Policies and Data Protection Measures - Platform-specific Terms of Use and Community Guidelines - Applicable laws and regulations governing online communities -#### 10.4.2 Conflict Resolution +#### 10.4.2. Conflict Resolution In the event of conflicts between this Code and other policies: - The provision that provides greater protection for community members shall take precedence - Community Leaders will interpret policies to maximise safety and inclusivity @@ -651,4 +651,4 @@ This Code represents our collective commitment to building and maintaining a com --- -*This Community Code of Conduct was last updated on 15 September 2025 and supersedes all previous versions. For questions regarding this Code or to report violations, please contact our Community Leaders through the designated reporting channels outlined above.* +*This Community Code of Conduct. For questions regarding this Code or to report violations, please contact our Community Leaders through the designated reporting channels outlined above.* diff --git a/src/content/docs/community/feedback.md b/src/content/docs/community/feedback.md index e0cf300..64c0e36 100644 --- a/src/content/docs/community/feedback.md +++ b/src/content/docs/community/feedback.md @@ -4,11 +4,11 @@ title: Community Feedback and Participation Policy ## 1. Foundation and Democratic Principles -### 1.1 Introduction and Purpose +### 1.1. Introduction and Purpose This Community Feedback and Participation Policy (hereinafter referred to as "the Policy") establishes our comprehensive framework for meaningful community member engagement in governance, policy development, and community improvement processes. This Policy embodies our commitment to participatory governance, ensuring that community members have multiple accessible pathways to influence decisions that affect their community experience and contribute to the continuous improvement of our shared environment. -### 1.2 Core Democratic Principles +### 1.2. Core Democratic Principles Our community feedback and participation approach is founded upon: @@ -24,7 +24,7 @@ Our community feedback and participation approach is founded upon: **(f)** **Democratic Accountability**: Mechanisms ensuring leadership remains accountable to the community they serve. -### 1.3 Participation Philosophy +### 1.3. Participation Philosophy We believe that community members are the ultimate experts on their own experience and needs, and our governance systems should reflect this expertise by: - Actively seeking diverse community perspectives on policies and decisions @@ -33,15 +33,15 @@ We believe that community members are the ultimate experts on their own experien - Building community ownership and investment in shared governance and improvement processes - Fostering a culture of collaborative decision-making and mutual responsibility -### 1.4 Legal Framework Integration +### 1.4. Legal Framework Integration This Policy operates within our comprehensive legal and policy framework, including our Terms of Service, Privacy Policy, Community Code of Conduct, and Community Leadership and Governance Policy, all of which are incorporated herein by reference. ## 2. Feedback Channels and Communication Systems -### 2.1 Regular Feedback Opportunities +### 2.1. Regular Feedback Opportunities -#### 2.1.1 Daily and Ongoing Feedback Channels +#### 2.1.1. Daily and Ongoing Feedback Channels **Open Communication Channels:** - Dedicated feedback channels accessible to all community members for ongoing input and suggestions @@ -60,7 +60,7 @@ This Policy operates within our comprehensive legal and policy framework, includ - Accessibility feedback channels specifically designed to identify and address inclusion barriers - `#accessibility` on Discord. -#### 2.1.2 Scheduled Feedback Collection +#### 2.1.2. Scheduled Feedback Collection **Monthly Community Input Sessions:** - Structured community meetings focused on specific policy areas or community improvements @@ -74,9 +74,9 @@ This Policy operates within our comprehensive legal and policy framework, includ - Community needs assessments identifying emerging priorities and improvement opportunities - Leadership performance evaluations providing community input on governance effectiveness -### 2.2 Accessible Participation Methods +### 2.2. Accessible Participation Methods -#### 2.2.1 Universal Design in Feedback Systems +#### 2.2.1. Universal Design in Feedback Systems **Multiple Communication Formats:** - Written feedback forms available in multiple languages and accessible formats @@ -90,7 +90,7 @@ This Policy operates within our comprehensive legal and policy framework, includ - Simple language versions of feedback requests and policy summaries for improved comprehension - Alternative format materials and documentation available upon request -#### 2.2.2 Cultural and Linguistic Inclusion +#### 2.2.2. Cultural and Linguistic Inclusion **Culturally Responsive Feedback Collection:** - Feedback systems designed with cultural sensitivity and diverse communication style accommodation @@ -106,9 +106,9 @@ This Policy operates within our comprehensive legal and policy framework, includ ## 3. Policy Development and Change Processes -### 3.1 Community Consultation Requirements +### 3.1. Community Consultation Requirements -#### 3.1.1 Mandatory Consultation Procedures +#### 3.1.1. Mandatory Consultation Procedures **Significant Policy Changes:** All significant policy changes must include: @@ -123,7 +123,7 @@ All significant policy changes must include: - **Stakeholder consultation** ensuring input from community members who would be most affected by new policies - **Implementation planning** involving community input on effective policy rollout and communication strategies -#### 3.1.2 Community Input Integration Process +#### 3.1.2. Community Input Integration Process **Systematic Input Analysis:** - **Comprehensive review** of all community feedback and input received during consultation periods @@ -137,9 +137,9 @@ All significant policy changes must include: - **Implementation timelines** and community preparation information for policy changes - **Ongoing evaluation commitments** outlining how policy effectiveness will be assessed with community input -### 3.2 Emergency and Urgent Change Procedures +### 3.2. Emergency and Urgent Change Procedures -#### 3.2.1 Emergency Policy Modifications +#### 3.2.1. Emergency Policy Modifications **Crisis Response Policy Changes:** When immediate policy changes are necessary for community safety: @@ -148,7 +148,7 @@ When immediate policy changes are necessary for community safety: - **Community input integration** for permanent policy changes following emergency measures - **Transparent review process** evaluating emergency decisions and incorporating community feedback for future improvements -#### 3.2.2 Urgent Community Need Response +#### 3.2.2. Urgent Community Need Response **Expedited Change Procedures:** - **Accelerated consultation timelines** with intensive community outreach and input collection @@ -158,9 +158,9 @@ When immediate policy changes are necessary for community safety: ## 4. Transparency and Decision-Making Communication -### 4.1 Open Governance Practices +### 4.1. Open Governance Practices -#### 4.1.1 Decision-Making Transparency +#### 4.1.1. Decision-Making Transparency **Public Decision Records:** - **Meeting minutes and records** available to all community members for transparency and accountability @@ -172,9 +172,9 @@ When immediate policy changes are necessary for community safety: - **Regular office hours** where community members can directly engage with leadership about governance and policy matters - **Public Q&A sessions** addressing community concerns and providing transparent answers about decision-making processes - **Leadership communication channels** accessible to all community members for ongoing dialogue and feedback -- **Community liaison programs** facilitating communication between leadership and diverse community groups +- **Community liaison programmes** facilitating communication between leadership and diverse community groups -#### 4.1.2 Information Accessibility and Sharing +#### 4.1.2. Information Accessibility and Sharing **Comprehensive Information Access:** - **Policy documentation** available in multiple formats and accessible language for broad community understanding @@ -188,9 +188,9 @@ When immediate policy changes are necessary for community safety: - **Multiple communication channels** ensuring information reaches community members through their preferred methods - **Follow-up communication** about decision outcomes and implementation progress -### 4.2 Community Accountability Mechanisms +### 4.2. Community Accountability Mechanisms -#### 4.2.1 Leadership Accountability Systems +#### 4.2.1. Leadership Accountability Systems **Performance Monitoring and Evaluation:** - **Regular community confidence surveys** assessing leadership effectiveness and community satisfaction @@ -204,7 +204,7 @@ When immediate policy changes are necessary for community safety: - **Community follow-up** ensuring leadership commitments are fulfilled and community concerns are adequately addressed - **Continuous improvement integration** incorporating accountability feedback into leadership development and governance enhancement -#### 4.2.2 Policy Effectiveness Assessment +#### 4.2.2. Policy Effectiveness Assessment **Community-Centred Evaluation:** - **Regular policy effectiveness surveys** gathering community input on how well policies are meeting their intended objectives @@ -214,13 +214,13 @@ When immediate policy changes are necessary for community safety: ## 5. Special Consultation and Participation Programs -### 5.1 Demographic and Identity-Based Consultation +### 5.1. Demographic and Identity-Based Consultation -#### 5.1.1 Targeted Community Outreach +#### 5.1.1. Targeted Community Outreach **Underrepresented Group Engagement:** -- **Specific consultation programs** ensuring input from community members who may not participate in general feedback processes -- **Identity-affirming participation opportunities** creating safe spaces for marginalized community members to provide honest feedback +- **Specific consultation programmes** ensuring input from community members who may not participate in general feedback processes +- **Identity-affirming participation opportunities** creating safe spaces for marginalised community members to provide honest feedback - **Cultural competency** in consultation design and facilitation to encourage authentic participation from diverse community members - **Language and accessibility support** removing barriers to participation for community members with diverse needs @@ -230,7 +230,7 @@ When immediate policy changes are necessary for community safety: - **Accessibility advisory groups** providing ongoing input on inclusion and accommodation needs and improvements - **Community youth and senior advisory panels** ensuring intergenerational perspectives in community governance -#### 5.1.2 Community-Driven Initiative Support +#### 5.1.2. Community-Driven Initiative Support **Grassroots Proposal Development:** - **Community member proposal processes** enabling members to suggest and develop new community initiatives and improvements @@ -239,22 +239,22 @@ When immediate policy changes are necessary for community safety: - **Implementation support** for community-approved initiatives including resource allocation and ongoing assistance **Community Organizing and Advocacy:** -- **Community organizing support** for members who want to advocate for specific changes or improvements +- **Community organising support** for members who want to advocate for specific changes or improvements - **Coalition building assistance** helping community members with shared interests collaborate effectively on improvement initiatives - **Advocacy training and resources** empowering community members to effectively participate in governance and change processes - **Community campaign support** for democratic initiatives that build broad community support for positive changes -### 5.2 Crisis and Emergency Community Consultation +### 5.2. Crisis and Emergency Community Consultation -#### 5.2.1 Emergency Response Input +#### 5.2.1. Emergency Response Input **Crisis Communication and Consultation:** - **Emergency communication protocols** ensuring community members receive timely information about crisis decisions affecting them - **Rapid consultation processes** gathering essential community input even during emergency situations -- **Community safety prioritization** balancing community input with immediate safety and security requirements +- **Community safety prioritisation** balancing community input with immediate safety and security requirements - **Post-crisis evaluation** involving comprehensive community consultation on emergency response effectiveness and improvements -#### 5.2.2 Community Healing and Recovery Participation +#### 5.2.2. Community Healing and Recovery Participation **Collective Recovery Planning:** - **Community-wide healing initiatives** developed with broad community input and participation @@ -264,9 +264,9 @@ When immediate policy changes are necessary for community safety: ## 6. Feedback Response and Follow-Up Systems -### 6.1 Comprehensive Response Protocols +### 6.1. Comprehensive Response Protocols -#### 6.1.1 Individual Feedback Acknowledgment +#### 6.1.1. Individual Feedback Acknowledgment **Personal Response Commitments:** - **Acknowledgment within 48 hours** for all individual feedback submissions and policy input @@ -280,7 +280,7 @@ When immediate policy changes are necessary for community safety: - **Outcome communication** sharing results and impacts of changes made in response to community feedback - **Satisfaction follow-up** ensuring community members are satisfied with how their feedback was handled and addressed -#### 6.1.2 Community-Wide Response Communication +#### 6.1.2. Community-Wide Response Communication **Public Feedback Summaries:** - **Monthly summary reports** highlighting community feedback themes, concerns, and suggestions received @@ -289,14 +289,14 @@ When immediate policy changes are necessary for community safety: - **Appreciation and recognition** of community members who provide valuable feedback and participate in governance processes **Community Learning and Improvement:** -- **Best practice sharing** about effective feedback integration and community input utilization +- **Best practice sharing** about effective feedback integration and community input utilisation - **Process improvement updates** showing how community feedback systems themselves are being enhanced based on member input - **Success story communication** celebrating positive changes that resulted from community feedback and participation - **Challenge identification** and collaborative problem-solving when feedback systems need improvement or enhancement -### 6.2 Continuous Feedback System Enhancement +### 6.2. Continuous Feedback System Enhancement -#### 6.2.1 Meta-Feedback and System Improvement +#### 6.2.1. Meta-Feedback and System Improvement **Feedback System Effectiveness Assessment:** - **Annual evaluation** of community feedback systems and their effectiveness in enabling meaningful participation @@ -312,9 +312,9 @@ When immediate policy changes are necessary for community safety: ## 7. Training and Support for Community Participation -### 7.1 Civic Engagement Education +### 7.1. Civic Engagement Education -#### 7.1.1 Participation Skills Development +#### 7.1.1. Participation Skills Development **Democratic Participation Training:** - **Civic engagement workshops** teaching community members effective advocacy, communication, and participation skills @@ -326,9 +326,9 @@ When immediate policy changes are necessary for community safety: - **Public speaking and presentation training** for community members interested in more active governance participation - **Written communication skills** development for effective policy feedback and proposal development - **Research and analysis training** helping community members gather information and develop evidence-based suggestions -- **Coalition building and organizing skills** for community members interested in leading community improvement initiatives +- **Coalition building and organising skills** for community members interested in leading community improvement initiatives -#### 7.1.2 Community Governance Education +#### 7.1.2. Community Governance Education **Governance Literacy Programs:** - **Community governance orientation** for new members explaining how community decision-making works and how to participate @@ -336,17 +336,17 @@ When immediate policy changes are necessary for community safety: - **Leadership and governance roles education** explaining different governance positions and how community members can become involved - **Community history and values education** helping members understand the context and principles guiding community governance -### 7.2 Participation Support and Mentorship +### 7.2. Participation Support and Mentorship -#### 7.2.1 New Member Integration +#### 7.2.1. New Member Integration -**Participation Mentorship Programs:** +**Participation Mentorship Programmes:** - **Governance mentorship** pairing experienced community members with newcomers interested in participation and feedback - **Peer support networks** connecting community members with similar interests in governance and community improvement - **Guided participation experiences** providing supported opportunities for new members to engage in feedback and governance processes - **Community leadership pipeline development** identifying and supporting community members interested in greater governance involvement -#### 7.2.2 Ongoing Participation Support +#### 7.2.2. Ongoing Participation Support **Sustained Engagement Assistance:** - **Resource libraries** providing ongoing access to materials, tools, and information supporting effective community participation @@ -356,9 +356,9 @@ When immediate policy changes are necessary for community safety: ## 8. Policy Implementation and Continuous Improvement -### 8.1 Policy Effectiveness Evaluation +### 8.1. Policy Effectiveness Evaluation -#### 8.1.1 Regular Assessment and Enhancement +#### 8.1.1. Regular Assessment and Enhancement **Quarterly System Review:** - **Participation metrics assessment** analysing community engagement levels and identifying areas for improvement @@ -372,13 +372,13 @@ When immediate policy changes are necessary for community safety: - **Community capacity building** evaluation assessing how participation systems support community member skill development and engagement - **System innovation and improvement** planning for enhanced feedback systems and participation opportunities -### 8.2 Community-Driven Policy Evolution +### 8.2. Community-Driven Policy Evolution -#### 8.2.1 Responsive Policy Development +#### 8.2.1. Responsive Policy Development **Community-Initiated Policy Changes:** - **Community proposal processes** enabling members to suggest policy modifications and improvements through structured democratic processes -- **Community prioritization systems** allowing members to identify which policy areas most need attention and improvement +- **Community prioritisation systems** allowing members to identify which policy areas most need attention and improvement - **Collaborative policy development** involving community members in drafting, reviewing, and refining policy changes - **Democratic approval processes** ensuring community input and consent for significant policy modifications and new policy development @@ -398,4 +398,4 @@ Through this Policy, we pledge to maintain transparent, accessible, and effectiv --- -*This Community Feedback and Participation Policy was created on 15 September 2025. For questions about community participation opportunities or to provide feedback on this Policy, please contact our Community Leaders through the designated channels outlined in our Community Code of Conduct.* +*This Community Feedback and Participation Policy provides comprehensive information about community participation opportunities. For questions about community participation opportunities or to provide feedback on this Policy, please contact our Community Leaders through the designated channels outlined in our Community Code of Conduct.* diff --git a/src/content/docs/community/guide.md b/src/content/docs/community/guide.md index cb772c3..abf4008 100644 --- a/src/content/docs/community/guide.md +++ b/src/content/docs/community/guide.md @@ -4,15 +4,15 @@ title: Community Guidelines and Best Practices ## 1. Introduction and Framework -### 1.1 Purpose and Scope +### 1.1. Purpose and Scope These Community Guidelines (hereinafter referred to as "the Guidelines") serve as a comprehensive framework for fostering positive, productive, and meaningful interactions within our community ecosystem. Whilst these Guidelines represent recommended best practices rather than mandatory requirements, adherence to these principles is strongly encouraged and contributes significantly to maintaining the high standards, integrity, and collaborative spirit that define our community. -### 1.2 Relationship to Mandatory Policies +### 1.2. Relationship to Mandatory Policies These Guidelines operate in conjunction with and supplement our mandatory Community Code of Conduct. Where any provision of these Guidelines conflicts with our Code of Conduct, the Code of Conduct shall take precedence as the binding standard. Nothing contained within these Guidelines shall supersede, modify, or diminish the requirements established by our Code of Conduct. -### 1.3 Community Objectives +### 1.3. Community Objectives The primary objectives of these Guidelines are to: 1. **Promote Excellence**: Encourage high-quality contributions and meaningful dialogue @@ -21,7 +21,7 @@ The primary objectives of these Guidelines are to: 4. **Maintain Standards**: Preserve the professional and collaborative atmosphere that characterises our community 5. **Encourage Participation**: Provide clear guidance for constructive engagement at all levels -### 1.4 Voluntary Nature and Benefits +### 1.4. Voluntary Nature and Benefits Whilst compliance with these Guidelines is voluntary, community members who consistently demonstrate these behaviours typically experience: - Enhanced reputation and standing within the community @@ -31,45 +31,45 @@ Whilst compliance with these Guidelines is voluntary, community members who cons ## 2. Staff Interaction and Professional Relationships -### 2.1 Recognition of Voluntary Service +### 2.1. Recognition of Voluntary Service Our community staff members, including moderators, administrators, and support personnel, generously volunteer their time, expertise, and energy to maintain safe, welcoming, and productive community environments. These individuals dedicate significant personal resources to ensure that our community remains accessible, secure, and beneficial for all participants. -### 2.2 Professional Courtesy and Respect +### 2.2. Professional Courtesy and Respect -#### 2.2.1 Fundamental Principles +#### 2.2.1. Fundamental Principles Community members are encouraged to demonstrate professional courtesy and respect in all interactions with staff by: - Acknowledging the challenges inherent in moderating online communities - Recognising that staff members are volunteers balancing community service with personal commitments - Approaching staff interactions with patience, understanding, and constructive intent - Expressing gratitude for staff efforts and contributions when appropriate -#### 2.2.2 Communication Standards +#### 2.2.2. Communication Standards Effective communication with staff members should demonstrate: - Clear, respectful, and professional language - Specific descriptions of issues or concerns rather than general complaints - Constructive suggestions for improvement when raising concerns - Recognition of resource constraints and competing priorities -### 2.3 Staff Authority and Decision-Making Process +### 2.3. Staff Authority and Decision-Making Process -#### 2.3.1 Scope of Authority +#### 2.3.1. Scope of Authority Staff members are vested with authority to make decisions necessary for maintaining community safety, order, and positive atmosphere. This authority includes, but is not limited to: - Interpreting and applying community policies and guidelines - Managing community resources and access permissions - Addressing conflicts and disciplinary matters - Implementing changes to improve community operations -#### 2.3.2 Recognition of Human Limitations +#### 2.3.2. Recognition of Human Limitations Community members should recognise that staff members, being human, may occasionally: - Make decisions that appear inconsistent or questionable - Experience variations in judgement due to personal circumstances - Require additional information to make fully informed decisions - Benefit from constructive feedback and alternative perspectives -### 2.4 Dispute Resolution and Appeals Process +### 2.4. Dispute Resolution and Appeals Process -#### 2.4.1 Constructive Approach to Disagreements +#### 2.4.1. Constructive Approach to Disagreements When community members disagree with staff decisions, the recommended approach includes: 1. **Pause and Reflect**: Allow time for emotional responses to subside before responding @@ -77,22 +77,22 @@ When community members disagree with staff decisions, the recommended approach i 3. **Consider Alternative Perspectives**: Attempt to understand the rationale behind staff decisions 4. **Document Concerns**: Prepare clear, factual descriptions of specific issues -#### 2.4.2 Inappropriate Response Patterns +#### 2.4.2. Inappropriate Response Patterns Community members should avoid the following counterproductive behaviours: - Direct confrontation or argumentative challenges to staff authority - Public criticism or undermining of staff decisions - Emotional outbursts or personal attacks directed at staff members - Demands for immediate resolution without allowing adequate consideration time -#### 2.4.3 Formal Appeals Process Reference +#### 2.4.3. Formal Appeals Process Reference **IMPORTANT: Comprehensive appeals procedures, including confidential review processes, impartial assessment protocols, and accessibility standards, are set forth in our dedicated [Appeals Process](/community/appeal) document.** For situations where informal resolution is insufficient, our formal appeals process provides independent, confidential review with fair consideration of all perspectives and transparent communication of outcomes. -### 2.6 Post-Sanction Conduct and Improvement +### 2.6. Post-Sanction Conduct and Improvement -#### 2.6.1 Constructive Response to Disciplinary Actions +#### 2.6.1. Constructive Response to Disciplinary Actions Community members who receive disciplinary sanctions are encouraged to: **Positive Actions:** @@ -103,7 +103,7 @@ Community members who receive disciplinary sanctions are encouraged to: - Maintain respectful, professional demeanour in all subsequent interactions - Focus on contributing positively to community discussions and activities -#### 2.6.2 Counterproductive Response Patterns +#### 2.6.2. Counterproductive Response Patterns Community members should avoid the following behaviours following disciplinary actions: - Continuing the sanctioned behaviour in modified or disguised forms - Attempting to circumvent policies through technical loopholes or creative interpretations @@ -111,7 +111,7 @@ Community members should avoid the following behaviours following disciplinary a - Engaging in comparative arguments about other members' conduct or perceived inconsistencies - Displaying resentment, hostility, or non-cooperation with staff or community standards -#### 2.6.3 Growth and Learning Opportunities +#### 2.6.3. Growth and Learning Opportunities Disciplinary situations, whilst challenging, offer opportunities for: - Personal growth and improved self-awareness - Enhanced understanding of community standards and expectations @@ -120,29 +120,29 @@ Disciplinary situations, whilst challenging, offer opportunities for: ## 3. Plural Systems Support and Inclusivity -### 3.1 Understanding and Recognition +### 3.1. Understanding and Recognition -#### 3.1.1 Definitions and Concepts +#### 3.1.1. Definitions and Concepts Plural systems refer to individuals who experience multiple distinct identities, personality states, or conscious entities sharing a single physical body. These identities, commonly referred to as "alters," "headmates," or "system members," may have different names, preferences, communication styles, and roles within the system's functioning. -#### 3.1.2 Community Commitment to Inclusion +#### 3.1.2. Community Commitment to Inclusion Our community explicitly recognises, values, and supports plural systems as full and equal members. We are committed to: - Creating safe, welcoming environments for all system members - Respecting the autonomy and validity of plural experiences - Supporting system members' right to self-identification and expression - Promoting understanding and acceptance throughout our community -### 3.2 Respectful Interaction Guidelines +### 3.2. Respectful Interaction Guidelines -#### 3.2.1 Privacy and Boundaries +#### 3.2.1. Privacy and Boundaries Community members should demonstrate respect for plural systems by: - **Respecting Privacy**: Never pressuring systems to disclose information about their plurality, individual alters, or system dynamics - **Honouring Boundaries**: Accepting the level of information systems choose to share without requesting additional details - **Avoiding Assumptions**: Not making judgements about system validity, formation, or functioning based on limited information - **Supporting Autonomy**: Recognising systems' right to manage their own disclosure and participation decisions -#### 3.2.2 Prohibited Behaviours -**Reference to Comprehensive Policies**: Detailed harassment definitions, prohibited behaviors, and enforcement procedures are comprehensively covered in our Acceptable Use Policy and Content and Moderation Policy, which are incorporated herein by reference. +#### 3.2.2. Prohibited Behaviours +**Reference to Comprehensive Policies**: Detailed harassment definitions, prohibited behaviours, and enforcement procedures are comprehensively covered in our Acceptable Use Policy and Content and Moderation Policy, which are incorporated herein by reference. Additional community-specific inappropriate behaviours include: - Attempting to identify which alter is "fronting" (actively controlling the body) without permission @@ -151,32 +151,32 @@ Additional community-specific inappropriate behaviours include: - Making unsolicited comments about the causes or origins of plurality - Offering unwanted advice about system management or integration -### 3.3 Communication Best Practices +### 3.3. Communication Best Practices -#### 3.3.1 Appropriate Addressing and Recognition +#### 3.3.1. Appropriate Addressing and Recognition When interacting with plural systems: - **Use Preferred Names and Pronouns**: Address individual alters by their chosen names and pronouns when known - **Ask for Clarification Respectfully**: If uncertain about how to address someone, politely request guidance - **Adapt to Communication Styles**: Recognise that different alters may have distinct communication preferences and styles - **Maintain Consistency**: Remember and apply individual preferences across interactions when possible -#### 3.3.2 Switching and Communication Changes +#### 3.3.2. Switching and Communication Changes Community members should understand that: - Different alters may participate in conversations at different times (switching) - Communication styles, interests, or responses may change when different alters are active - Systems may need time to communicate internally or may experience communication delays - Patience and flexibility enhance positive interactions with plural community members -### 3.4 Educational Approach and Community Development +### 3.4. Educational Approach and Community Development -#### 3.4.1 Promoting Understanding +#### 3.4.1. Promoting Understanding Our community encourages education about plurality through: - Sharing of appropriate educational resources and information - Respectful dialogue about plural experiences when welcomed by system members - Community-wide initiatives to increase awareness and acceptance - Training for staff members on inclusive practices for plural individuals -#### 3.4.2 Resource Direction and Support +#### 3.4.2. Resource Direction and Support Rather than placing educational burdens on individual systems: - Direct general questions about plurality to appropriate educational resources - Consult established literature, organisations, or informational websites @@ -185,9 +185,9 @@ Rather than placing educational burdens on individual systems: ## 4. Tone Tags and Communication Enhancement -### 4.1 Understanding Tone Tags and Their Purpose +### 4.1. Understanding Tone Tags and Their Purpose -#### 4.1.1 Communication Challenges in Text-Based Environments +#### 4.1.1. Communication Challenges in Text-Based Environments Text-based communication inherently lacks many contextual cues available in face-to-face interaction, including: - Vocal tone, inflection, and emphasis - Facial expressions and body language @@ -196,12 +196,12 @@ Text-based communication inherently lacks many contextual cues available in face These limitations frequently lead to misunderstandings, misinterpretations, and unnecessary conflicts within online communities. -#### 4.1.2 Solution: Tone Tags as Communication Tools +#### 4.1.2. Solution: Tone Tags as Communication Tools Tone tags represent a systematic approach to addressing these communication challenges by providing explicit contextual information about the intended tone, purpose, or emotional content of messages. These brief, standardised indicators help clarify intent and reduce misunderstandings. -### 4.2 Strategic Application of Tone Tags +### 4.2. Strategic Application of Tone Tags -#### 4.2.1 Optimal Usage Scenarios +#### 4.2.1. Optimal Usage Scenarios Consider implementing tone tags in the following circumstances: - **Ambiguous Content**: Messages that could reasonably be interpreted in multiple ways - **Humour and Sarcasm**: Content intended as humorous, sarcastic, or ironic that might not be immediately apparent @@ -209,23 +209,23 @@ Consider implementing tone tags in the following circumstances: - **Cross-Cultural Communication**: Interactions with individuals from different cultural or linguistic backgrounds - **Accessibility Needs**: Communication with individuals who have expressed difficulty interpreting textual tone -#### 4.2.2 Preventive Communication Strategy +#### 4.2.2. Preventive Communication Strategy Proactive use of tone tags can prevent: - Escalation of minor misunderstandings into significant conflicts - Emotional distress caused by misinterpretation of intent - Time-consuming clarification discussions - Damage to relationships and community trust -### 4.3 Implementation Guidelines and Best Practices +### 4.3. Implementation Guidelines and Best Practices -#### 4.3.1 Formatting and Placement Standards +#### 4.3.1. Formatting and Placement Standards Effective tone tag implementation involves: - **Location**: Place tone tags at the end of the relevant message or section - **Format**: Enclose tags in forward slashes, e.g., `/j` for joking - **Multiple Tags**: Use multiple tags when appropriate, e.g., `/s /lh` for sarcastic but lighthearted - **Consistency**: Apply tags consistently across similar communication contexts -#### 4.3.2 Comprehensive Tone Tag Reference +#### 4.3.2. Comprehensive Tone Tag Reference | Tag | Meaning | Usage Context | |------------------------|--------------------------------------|--------------------------------------------------| @@ -281,32 +281,32 @@ Effective tone tag implementation involves: | `/t` | Teasing | Engaging in playful, non-malicious mockery | | `/tc`, `/ti` or `/tic` | Typing a Tic | Indicating involuntary typing behaviour | -### 4.4 Community Etiquette and Respect +### 4.4. Community Etiquette and Respect -#### 4.4.1 Respectful Response to Tone Tags +#### 4.4.1. Respectful Response to Tone Tags Community members should demonstrate respect for tone tag usage by: - **Interpreting Appropriately**: Adjust message interpretation based on provided tone tags - **Seeking Clarification**: Politely request explanation for unfamiliar or unclear tags - **Avoiding Mockery**: Never belittle, mock, or criticise others for using tone tags - **Supporting Usage**: Encourage tone tag adoption when it would enhance communication -#### 4.4.2 Accessibility and Inclusion Benefits +#### 4.4.2. Accessibility and Inclusion Benefits Tone tags particularly benefit: - **Neurodivergent Individuals**: People who may experience difficulty interpreting social cues or implied meanings - **Non-Native Speakers**: Individuals for whom English cultural and linguistic nuances may be challenging - **Screen Reader Users**: People using assistive technology who can access tone tag information - **Anxiety-Prone Communicators**: Individuals who benefit from explicit clarification of intent -### 4.5 Limitations and Complementary Practices +### 4.5. Limitations and Complementary Practices -#### 4.5.1 Recognising Tool Limitations +#### 4.5.1. Recognising Tool Limitations Whilst tone tags enhance communication, they should not replace: - Clear, well-structured writing - Thoughtful consideration of audience and context - Direct communication when clarity is essential - Professional writing standards in formal contexts -#### 4.5.2 Community-Specific Adaptations +#### 4.5.2. Community-Specific Adaptations Our community may develop additional tone tags to address specific needs: - **Community Consensus**: New tags adopted through collective agreement and usage - **Documentation Updates**: Regular updates to tone tag references and guidelines @@ -314,28 +314,28 @@ Our community may develop additional tone tags to address specific needs: ## 5. Pronoun Usage and Gender Inclusivity -### 5.1 Importance of Accurate Pronoun Usage +### 5.1. Importance of Accurate Pronoun Usage -#### 5.1.1 Fundamental Principle of Respect +#### 5.1.1. Fundamental Principle of Respect Pronouns represent a fundamental aspect of personal identity and self-expression. Using individuals' correct pronouns demonstrates basic respect for their identity and contributes to creating inclusive environments where all community members can participate authentically and comfortably. -#### 5.1.2 Community Values and Commitment +#### 5.1.2. Community Values and Commitment Our community is committed to: - **Universal Respect**: Treating all gender identities with equal dignity and consideration - **Inclusive Practices**: Implementing systems and practices that accommodate diverse pronoun preferences - **Educational Support**: Providing resources and guidance to help community members learn inclusive practices - **Safe Expression**: Creating environments where individuals feel secure expressing their authentic identities -### 5.2 Pronoun Sharing and Display +### 5.2. Pronoun Sharing and Display -#### 5.2.1 Encouraging Universal Participation +#### 5.2.1. Encouraging Universal Participation We strongly encourage all community members to display their pronouns regardless of gender identity through: - **Profile Information**: Including pronouns in bio sections and profile descriptions - **Platform Features**: Utilising designated pronoun roles, badges, or comparable features when available - **Display Names**: Incorporating pronouns into usernames or display names when desired - **Signature Lines**: Adding pronouns to forum signatures or communication templates -#### 5.2.2 Benefits of Universal Pronoun Sharing +#### 5.2.2. Benefits of Universal Pronoun Sharing Universal pronoun sharing creates numerous community benefits: **Individual Benefits:** @@ -349,16 +349,16 @@ Universal pronoun sharing creates numerous community benefits: - **Education**: Raises awareness about gender diversity and respectful practices - **Safety**: Reduces the risk of inadvertent outing or identity disclosure -### 5.3 Respectful Pronoun Practices +### 5.3. Respectful Pronoun Practices -#### 5.3.1 Consistent Usage Standards +#### 5.3.1. Consistent Usage Standards Community members should consistently: - **Use Specified Pronouns**: Always employ the pronouns individuals have indicated for themselves - **Ask When Uncertain**: Politely request pronoun information when it is not readily available - **Correct Mistakes Promptly**: Acknowledge errors briefly, correct usage, and continue conversations - **Avoid Assumptions**: Never assume pronouns based on appearance, name, or other characteristics -#### 5.3.2 Error Correction Protocol +#### 5.3.2. Error Correction Protocol When pronoun mistakes occur: **For the Person Making the Error:** @@ -372,9 +372,9 @@ When pronoun mistakes occur: 2. **Support the Individual**: Check privately with misgendered individuals if they need support 3. **Avoid Public Scenes**: Don't create dramatic confrontations over honest mistakes -### 5.4 Diverse Pronoun Options and Recognition +### 5.4. Diverse Pronoun Options and Recognition -#### 5.4.1 Comprehensive Pronoun Spectrum +#### 5.4.1. Comprehensive Pronoun Spectrum Community members may use various pronoun sets including: **Traditional Pronouns:** @@ -393,39 +393,39 @@ Community members may use various pronoun sets including: - Name only: People who prefer their name used instead of pronouns - Multiple sets: Individuals who use different pronouns in different contexts -#### 5.4.2 Evolving and Changing Pronouns +#### 5.4.2. Evolving and Changing Pronouns Community members should understand that: - **Pronouns May Change**: Individuals have the right to modify their pronouns at any time - **Historical Accuracy**: Always use current pronouns, even when discussing past events - **No Explanation Required**: Pronoun changes do not require justification or detailed explanation - **Immediate Implementation**: Begin using new pronouns as soon as you become aware of changes -### 5.5 Community Support and Education +### 5.5. Community Support and Education -#### 5.5.1 Creating Learning Opportunities +#### 5.5.1. Creating Learning Opportunities Our community supports pronoun education through: - **Resource Sharing**: Providing educational materials about gender identity and pronoun usage - **Community Discussion**: Facilitating respectful conversations about inclusive practices -- **Mentorship Programs**: Connecting experienced community members with newcomers learning inclusive practices +- **Mentorship Programmes**: Connecting experienced community members with newcomers learning inclusive practices - **Regular Updates**: Sharing information about evolving best practices and community standards -#### 5.5.2 Addressing Challenges and Resistance +#### 5.5.2. Addressing Challenges and Resistance When community members experience difficulty with pronoun usage: - **Educational Approach**: Provide patient education and resources rather than immediate punishment - **Cultural Sensitivity**: Acknowledge different cultural backgrounds whilst maintaining community standards - **Progressive Improvement**: Recognise that learning takes time and celebrate progress over perfection - **Clear Boundaries**: Maintain firm standards whilst providing supportive learning environments -### 5.6 Privacy and Consent Considerations +### 5.6. Privacy and Consent Considerations -#### 5.6.1 Voluntary Disclosure +#### 5.6.1. Voluntary Disclosure Whilst pronoun sharing is strongly encouraged, community members should understand that: - **Personal Choice**: Pronoun sharing remains ultimately voluntary and personal - **No Pressure**: Never pressure individuals to disclose pronouns if they are uncomfortable doing so - **Privacy Respect**: Some individuals may have complex reasons for not sharing pronouns publicly - **Alternative Solutions**: Find respectful ways to communicate without pronouns when necessary -#### 5.6.2 Confidentiality and Safety +#### 5.6.2. Confidentiality and Safety In certain circumstances, pronoun information may require confidential handling: - **Safety Concerns**: Some individuals may face risk if their gender identity becomes widely known - **Professional Contexts**: Workplace or academic situations may require careful navigation @@ -434,21 +434,21 @@ In certain circumstances, pronoun information may require confidential handling: ## 6. Accessibility and Universal Design -### 6.1 Commitment to Accessibility +### 6.1. Commitment to Accessibility -#### 6.1.1 Foundational Principles +#### 6.1.1. Foundational Principles Our community is committed to ensuring that all members, regardless of disability status or access needs, can participate fully and meaningfully in all community activities, discussions, and opportunities. This commitment reflects our core values of inclusion, equality, and universal respect for human dignity. -#### 6.1.2 Universal Design Philosophy +#### 6.1.2. Universal Design Philosophy We embrace universal design principles that recognise accessibility benefits extend beyond individuals with specific disabilities: - **Broader Benefits**: Accessible content is easier for everyone to consume and understand - **Future-Proofing**: Accessible practices accommodate evolving technology and changing needs - **Inclusive Culture**: Accessibility awareness creates more thoughtful, inclusive community culture - **Innovation Driver**: Accessibility requirements often lead to creative solutions that benefit all users -### 6.2 Visual Content and Alternative Text +### 6.2. Visual Content and Alternative Text -#### 6.2.1 Alternative Text Requirements and Best Practices +#### 6.2.1. Alternative Text Requirements and Best Practices All visual content shared within our community should include descriptive alternative text to ensure accessibility for screen reader users and individuals who cannot view images directly. **Comprehensive Alt Text Guidelines:** @@ -472,15 +472,15 @@ All visual content shared within our community should include descriptive altern - Instead of: "meme" or "funny picture" - Use: "A photograph of a golden retriever wearing sunglasses sitting at a computer desk, with text reading 'When you finally understand the assignment' in bold white letters" -#### 6.2.2 Context-Appropriate Description +#### 6.2.2. Context-Appropriate Description Effective alternative text considers: - **Audience Needs**: What information do viewers need to understand the content's purpose? - **Context Relevance**: How does the image relate to the surrounding discussion or content? - **Essential Information**: Which visual elements are crucial for comprehension versus decorative? -### 6.3 Content Structure and Navigation +### 6.3. Content Structure and Navigation -#### 6.3.1 Hierarchical Organisation +#### 6.3.1. Hierarchical Organisation Well-structured content enhances accessibility and usability for all community members: **Heading Structure:** @@ -493,7 +493,7 @@ Well-structured content enhances accessibility and usability for all community m - Use bullet points, numbered lists, or other organisational tools for complex information - Group related information together under appropriate headings -#### 6.3.2 Link and Navigation Standards +#### 6.3.2. Link and Navigation Standards Accessible navigation requires: **Descriptive Link Text:** @@ -505,9 +505,9 @@ Accessible navigation requires: - Instead of: "Click here for more information" - Use: "View our upcoming community events and registration details" -### 6.4 Multimedia Content Accessibility +### 6.4. Multimedia Content Accessibility -#### 6.4.1 Video Content Requirements +#### 6.4.1. Video Content Requirements Video content shared within our community should include: **Captions and Subtitles:** @@ -521,61 +521,61 @@ Video content shared within our community should include: - Description of actions, settings, facial expressions, and visual information - Integration that doesn't interfere with original audio content -#### 6.4.2 Audio Content Support +#### 6.4.2. Audio Content Support Audio-only content benefits from: - **Complete Transcripts**: Full text versions of audio content - **Chapter Markers**: Time-stamped section indicators for easy navigation - **Content Summaries**: Brief descriptions of audio content for quick reference -### 6.5 Sensitive Content and Seizure Prevention +### 6.5. Sensitive Content and Seizure Prevention -#### 6.5.1 Flashing and Moving Content +#### 6.5.1. Flashing and Moving Content To protect individuals with photosensitive epilepsy and other conditions: - **Avoid Rapid Flashing**: Never share content that flashes more than three times per second - **Provide Warnings**: Include clear warnings before sharing potentially problematic content - **Alternative Formats**: Offer still images or descriptions as alternatives when possible -#### 6.5.2 Content Warnings and Preparation +#### 6.5.2. Content Warnings and Preparation Comprehensive content warnings help individuals prepare for or avoid potentially harmful content: - **Specific Descriptions**: Provide clear, specific information about content nature - **Placement**: Position warnings before the potentially problematic content - **Multiple Formats**: Use both text warnings and visual indicators when appropriate -### 6.6 Community Support and Continuous Improvement +### 6.6. Community Support and Continuous Improvement -#### 6.6.1 Feedback and Enhancement +#### 6.6.1. Feedback and Enhancement Our commitment to accessibility includes: - **Community Input**: Welcoming feedback on accessibility barriers and improvement opportunities - **Regular Assessment**: Periodic review of accessibility practices and their effectiveness - **Resource Sharing**: Providing tools, guides, and educational materials about accessibility - **Collaborative Improvement**: Working together to identify and address accessibility challenges -#### 6.6.2 Education and Awareness +#### 6.6.2. Education and Awareness Building accessibility awareness throughout our community involves: - **Training Opportunities**: Offering education about disability awareness and inclusive practices - **Resource Development**: Creating guides and tools to support accessible content creation - **Cultural Change**: Fostering community norms that prioritise accessibility and inclusion -- **Recognition Programs**: Celebrating community members who demonstrate exceptional commitment to accessibility +- **Recognition Programmes**: Celebrating community members who demonstrate exceptional commitment to accessibility ## 7. Content Warnings and Trauma-Informed Practices -### 7.1 Trauma-Informed Community Approach +### 7.1. Trauma-Informed Community Approach -#### 7.1.1 Understanding Trauma Impact +#### 7.1.1. Understanding Trauma Impact Our community recognises that many individuals have experienced various forms of trauma, and exposure to related content can cause significant distress, trigger harmful memories, or impact mental health. Content warnings represent our commitment to trauma-informed practices that prioritise community member safety and well-being. -#### 7.1.2 Community Safety Framework +#### 7.1.2. Community Safety Framework Content warnings contribute to community safety by: - **Informed Consent**: Enabling individuals to make educated decisions about content engagement - **Risk Reduction**: Minimising unintentional exposure to potentially harmful content - **Control and Agency**: Providing individuals with control over their content consumption - **Inclusive Environment**: Creating spaces where trauma survivors can participate safely -### 7.2 Content Warning Requirements Reference +### 7.2. Content Warning Requirements Reference **IMPORTANT: Comprehensive content warning requirements, including mandatory categories, enforcement procedures, and compliance standards, are set forth in our Content and Moderation Policy, which is incorporated herein by reference.** -#### 7.2.1 Community-Specific Guidance +#### 7.2.1. Community-Specific Guidance Content warnings are **mandatory** across all community spaces. Key community-specific considerations include: @@ -583,9 +583,9 @@ Content warnings are **mandatory** across all community spaces. Key community-sp - **Community Context**: Apply content warning standards thoughtfully within the context of community discussions and interactions - **Educational Support**: Community members are encouraged to support one another in learning and applying content warning practices -### 7.4 Effective Warning Implementation +### 7.4. Effective Warning Implementation -#### 7.4.1 Warning Format and Placement +#### 7.4.1. Warning Format and Placement Effective content warnings should: **Placement and Visibility:** @@ -603,33 +603,33 @@ Effective content warnings should: - "CW: Graphic descriptions of physical violence" - "Trigger Warning: References to sexual assault and trauma recovery" -#### 7.4.2 Spoiler Tags and Content Hiding +#### 7.4.2. Spoiler Tags and Content Hiding When platform features allow: - Use spoiler tags, content hiding, or "read more" cuts to conceal potentially triggering content - Combine warnings with hiding mechanisms for maximum protection - Ensure warnings remain visible even when content is hidden -### 7.5 Community Response and Support +### 7.5. Community Response and Support -#### 7.5.1 Respectful Responses to Warnings +#### 7.5.1. Respectful Responses to Warnings Community members should demonstrate respect for content warning practices by: - **Taking Warnings Seriously**: Never mock, dismiss, or minimise the importance of content warnings - **Individual Needs Recognition**: Understanding that warning needs vary among individuals - **Gracious Compliance**: Accepting requests for additional warnings without defensiveness - **Supportive Behaviour**: Encouraging and normalising content warning usage -#### 7.5.2 Appropriate Challenge and Discussion +#### 7.5.2. Appropriate Challenge and Discussion While respecting content warnings, community members may: - **Request Clarification**: Ask for more specific warnings when needed - **Suggest Improvements**: Offer constructive feedback about warning effectiveness - **Share Resources**: Provide educational materials about trauma-informed practices - **Model Best Practices**: Demonstrate excellent content warning usage for others to follow -### 7.6 Enforcement Reference +### 7.6. Enforcement Reference **IMPORTANT: Comprehensive enforcement procedures for content warning violations, including response protocols, disciplinary measures, and appeals processes, are set forth in our Content and Moderation Policy, which is incorporated herein by reference.** -#### 7.6.1 Community Education and Support +#### 7.6.1. Community Education and Support Our community commitment to content warning compliance includes: - **Peer Support**: Community members helping one another learn and apply content warning practices - **Educational Approach**: Emphasis on learning and improvement rather than punishment when possible @@ -637,12 +637,12 @@ Our community commitment to content warning compliance includes: ## 8. Conflict Resolution and Mediation -### 8.1 Philosophy of Constructive Conflict Management +### 8.1. Philosophy of Constructive Conflict Management -#### 8.1.1 Conflict as Natural Community Element +#### 8.1.1. Conflict as Natural Community Element Conflicts, disagreements, and differences of opinion represent natural and inevitable aspects of any vibrant, diverse community. Rather than viewing conflict as inherently negative or destructive, our community approaches disagreements as opportunities for growth, learning, and strengthened relationships when handled constructively. -#### 8.1.2 Restorative Justice Principles +#### 8.1.2. Restorative Justice Principles Our conflict resolution approach emphasises: - **Relationship Repair**: Focus on healing and strengthening community relationships - **Mutual Understanding**: Encouraging empathy and perspective-taking among conflicting parties @@ -650,9 +650,9 @@ Our conflict resolution approach emphasises: - **Collaborative Solutions**: Seeking win-win outcomes that address underlying needs and concerns - **Community Strengthening**: Leveraging conflict resolution to build more resilient community bonds -### 8.2 Foundational Principles for Constructive Engagement +### 8.2. Foundational Principles for Constructive Engagement -#### 8.2.1 Core Engagement Standards +#### 8.2.1. Core Engagement Standards All community members engaged in conflict resolution should demonstrate: **Respect and Human Dignity:** @@ -671,11 +671,11 @@ All community members engaged in conflict resolution should demonstrate: - Address specific behaviours, actions, or policies rather than personal character attacks - Concentrate on issues within the scope of community standards and values - Offer constructive suggestions and alternative approaches when raising concerns -- Avoid inflammatory language, generalizations, or escalatory rhetoric +- Avoid inflammatory language, generalisations, or escalatory rhetoric -### 8.3 Self-Directed Resolution Process +### 8.3. Self-Directed Resolution Process -#### 8.3.1 Direct Communication Framework +#### 8.3.1. Direct Communication Framework The preferred first step in conflict resolution involves direct communication between affected parties: **Preparation Phase:** @@ -695,7 +695,7 @@ The preferred first step in conflict resolution involves direct communication be - "I understand you might have intended [acknowledged intent], but the impact was [specific effect]" - "I would appreciate if we could [specific request for change] in future interactions" -#### 8.3.2 Cooling-Down Period Management +#### 8.3.2. Cooling-Down Period Management When emotions run high or productive communication becomes difficult: **Recognition Signs:** @@ -710,9 +710,9 @@ When emotions run high or productive communication becomes difficult: - **Perspective-Taking**: Consider the situation from other parties' viewpoints during the pause - **Solution Focus**: Return to discussions with renewed focus on collaborative problem-solving -### 8.4 Community-Supported Mediation +### 8.4. Community-Supported Mediation -#### 8.4.1 Third-Party Mediation Process +#### 8.4.1. Third-Party Mediation Process When direct communication fails to resolve conflicts, community-supported mediation offers structured assistance: **Mediator Selection:** @@ -728,7 +728,7 @@ When direct communication fails to resolve conflicts, community-supported mediat - **Solution Development**: Collaborative generation of potential solutions - **Agreement Formation**: Development of specific, actionable resolution agreements -#### 8.4.2 Mediator Responsibilities and Guidelines +#### 8.4.2. Mediator Responsibilities and Guidelines Community members serving as mediators should: - **Maintain Neutrality**: Avoid taking sides or advocating for specific outcomes - **Facilitate Communication**: Help parties express themselves clearly and listen effectively @@ -736,9 +736,9 @@ Community members serving as mediators should: - **Focus on Solutions**: Guide discussions toward constructive problem-solving - **Respect Confidentiality**: Maintain privacy about mediation discussions unless agreed otherwise -### 8.5 Staff Intervention and Escalation +### 8.5. Staff Intervention and Escalation -#### 8.5.1 Appropriate Escalation Triggers +#### 8.5.1. Appropriate Escalation Triggers Community members should involve staff moderators when conflicts involve: **Safety and Harassment Concerns:** @@ -759,7 +759,7 @@ Community members should involve staff moderators when conflicts involve: - Situations where parties refuse to engage constructively in resolution attempts - Complex issues requiring specialised knowledge or authority to resolve -#### 8.5.2 Staff Intervention Protocols +#### 8.5.2. Staff Intervention Protocols When staff intervention becomes necessary: **Assessment and Planning:** @@ -774,15 +774,15 @@ When staff intervention becomes necessary: - **Stakeholder Communication**: Clear, respectful communication with all involved parties - **Solution Development**: Collaborative development of sustainable, fair resolution approaches -### 8.6 Appeal and Review Processes +### 8.6. Appeal and Review Processes -#### 8.6.1 Dispute Resolution Appeals Reference +#### 8.6.1. Dispute Resolution Appeals Reference **IMPORTANT: Comprehensive appeals procedures, including appeal grounds, submission processes, and review standards, are set forth in our dedicated [Appeals Process](/community/appeal) document.** Community members who disagree with conflict resolution outcomes may access our formal appeals process, which provides independent review of procedural concerns, new evidence, and resolution appropriateness. -#### 8.6.2 Learning and Improvement Integration +#### 8.6.2. Learning and Improvement Integration Our conflict resolution system includes mechanisms for continuous improvement: - **Process Evaluation**: Regular assessment of resolution effectiveness and fairness - **Community Feedback**: Collection of input from parties who have used resolution processes @@ -791,12 +791,12 @@ Our conflict resolution system includes mechanisms for continuous improvement: ## 9. Community Enjoyment and Well-being -### 9.1 Fundamental Philosophy: Community as Enjoyable Experience +### 9.1. Fundamental Philosophy: Community as Enjoyable Experience -#### 9.1.1 Central Principle +#### 9.1.1. Central Principle Participation in our community should fundamentally be an enjoyable, fulfilling, and positive experience for all members. This principle underlies all other community policies, guidelines, and practices, serving as the ultimate measure of our community's success and health. -#### 9.1.2 Signs of Healthy Community Engagement +#### 9.1.2. Signs of Healthy Community Engagement Community members who are having positive experiences typically demonstrate: - **Enthusiasm**: Genuine excitement about participating in discussions and activities - **Curiosity**: Interest in learning from others and exploring new ideas or perspectives @@ -804,9 +804,9 @@ Community members who are having positive experiences typically demonstrate: - **Relaxation**: Ability to engage naturally without excessive stress or anxiety about community interactions - **Growth**: Development of new skills, knowledge, or relationships through community participation -### 9.2 Self-Care and Boundary Management +### 9.2. Self-Care and Boundary Management -#### 9.2.1 Recognising the Need for Breaks +#### 9.2.1. Recognising the Need for Breaks Community members are encouraged to recognise when they need distance from community activities: **Warning Signs for Break Consideration:** @@ -816,7 +816,7 @@ Community members are encouraged to recognise when they need distance from commu - Losing interest in previously enjoyable community activities or discussions - Noticing that community participation negatively impacts other areas of life -#### 9.2.2 Taking Healthy Breaks +#### 9.2.2. Taking Healthy Breaks When breaks become necessary: **Permission and Encouragement:** @@ -831,16 +831,16 @@ When breaks become necessary: - **Read-Only Mode**: Consuming community content without feeling pressure to contribute actively - **Selective Participation**: Engaging only with specific community areas or topics that remain enjoyable -#### 9.2.3 Return and Re-engagement +#### 9.2.3. Return and Re-engagement When community members feel ready to return: - **Gradual Re-engagement**: No pressure to immediately return to previous participation levels - **Continued Boundary Management**: Ongoing permission to adjust participation as needed - **Community Support**: Assistance from other members in finding comfortable re-engagement approaches - **Learning Integration**: Application of insights gained during breaks to enhance future community experience -### 9.3 Engagement Style Assessment and Adjustment +### 9.3. Engagement Style Assessment and Adjustment -#### 9.3.1 Self-Reflection on Interaction Patterns +#### 9.3.1. Self-Reflection on Interaction Patterns Community members experiencing consistent dissatisfaction should consider: **Interaction Style Evaluation:** @@ -855,7 +855,7 @@ Community members experiencing consistent dissatisfaction should consider: - Are your expectations for community interaction realistic and appropriate? - Do you find meaning and satisfaction in the types of activities and discussions the community offers? -#### 9.3.2 Adjustment and Improvement Strategies +#### 9.3.2. Adjustment and Improvement Strategies When reflection reveals opportunities for improvement: **Communication Style Modifications:** @@ -870,9 +870,9 @@ When reflection reveals opportunities for improvement: - Appreciate the volunteer nature of community leadership and support systems - Celebrate small positive interactions rather than expecting dramatic community changes -### 9.4 Staff-Supported Temporary Restrictions +### 9.4. Staff-Supported Temporary Restrictions -#### 9.4.1 Voluntary Temporary Exclusion +#### 9.4.1. Voluntary Temporary Exclusion For community members who struggle with self-regulated breaks, our staff team offers supportive temporary restrictions: **Service Description:** @@ -887,7 +887,7 @@ For community members who struggle with self-regulated breaks, our staff team of - Need for external structure to support personal well-being goals - Temporary life circumstances that require reduced digital engagement -#### 9.4.2 Request Process and Implementation +#### 9.4.2. Request Process and Implementation Members seeking voluntary temporary restrictions can: **Request Procedure:** @@ -902,9 +902,9 @@ Members seeking voluntary temporary restrictions can: - Check-in communications at agreed intervals to assess continued need - Collaborative planning for gradual re-engagement when restrictions end -### 9.5 Community Culture and Atmosphere Maintenance +### 9.5. Community Culture and Atmosphere Maintenance -#### 9.5.1 Collective Responsibility for Positive Environment +#### 9.5.1. Collective Responsibility for Positive Environment Creating and maintaining an enjoyable community experience requires collective effort from all members: **Individual Contributions:** @@ -920,7 +920,7 @@ Creating and maintaining an enjoyable community experience requires collective e - Constructive handling of challenges and conflicts that arise - Ongoing evolution of community practices to better serve member needs -#### 9.5.2 Identifying and Addressing Systemic Issues +#### 9.5.2. Identifying and Addressing Systemic Issues When community enjoyment becomes consistently problematic: **Issue Recognition:** @@ -937,17 +937,17 @@ When community enjoyment becomes consistently problematic: ## 10. Mini-Moderation and Peer Support -### 10.1 Understanding Mini-Moderation +### 10.1. Understanding Mini-Moderation -#### 10.1.1 Definition and Scope +#### 10.1.1. Definition and Scope "Mini-moderation" refers to activities where non-staff community members provide guidance, correction, or support to other members regarding community standards, practices, or norms. This behaviour occupies a middle ground between passive observation and formal moderation authority. -#### 10.1.2 Community Position on Mini-Moderation +#### 10.1.2. Community Position on Mini-Moderation Our community adopts a permissive approach to mini-moderation, recognising its value in creating self-regulating, mutually supportive community environments. However, this permission comes with specific guidelines and limitations to prevent abuse or overreach. -### 10.2 Acceptable Mini-Moderation Practices +### 10.2. Acceptable Mini-Moderation Practices -#### 10.2.1 Constructive Guidance and Support +#### 10.2.1. Constructive Guidance and Support Appropriate mini-moderation includes: **Welcoming and Integration Support:** @@ -968,7 +968,7 @@ Appropriate mini-moderation includes: - Offering constructive feedback on content or communication style - Sharing resources that help community members understand expectations -#### 10.2.2 Appropriate Communication Methods +#### 10.2.2. Appropriate Communication Methods Effective mini-moderation employs: **Respectful Language and Tone:** @@ -983,9 +983,9 @@ Effective mini-moderation employs: - Encourage questions and discussion rather than demanding compliance - Focus on community benefit rather than personal authority -### 10.3 Prohibited Mini-Moderation Behaviours +### 10.3. Prohibited Mini-Moderation Behaviours -#### 10.3.1 Authority Misrepresentation +#### 10.3.1. Authority Misrepresentation Community members engaged in mini-moderation must never: **False Authority Claims:** @@ -1000,7 +1000,7 @@ Community members engaged in mini-moderation must never: - Claim to speak on behalf of the community leadership - Misrepresent the scope or nature of their community role -#### 10.3.2 Harmful or Counterproductive Approaches +#### 10.3.2. Harmful or Counterproductive Approaches Inappropriate mini-moderation includes: **Public Confrontation and Embarrassment:** @@ -1015,9 +1015,9 @@ Inappropriate mini-moderation includes: - Escalating situations through argumentative or confrontational responses - Demonstrating impatience or frustration with members who are learning -### 10.4 Effective Mini-Moderation Strategies +### 10.4. Effective Mini-Moderation Strategies -#### 10.4.1 Leading by Example +#### 10.4.1. Leading by Example The most effective mini-moderation approach involves: **Consistent Positive Behaviour:** @@ -1032,7 +1032,7 @@ The most effective mini-moderation approach involves: - Create welcoming environments for newcomers and less experienced participants - Celebrate community successes and positive developments -#### 10.4.2 Supportive Intervention Techniques +#### 10.4.2. Supportive Intervention Techniques When mini-moderation becomes necessary: **Private Communication:** @@ -1047,9 +1047,9 @@ When mini-moderation becomes necessary: - Ask clarifying questions that encourage reflection rather than making direct accusations - Provide positive alternatives that naturally guide discussions in better directions -### 10.5 Escalation and Staff Involvement +### 10.5. Escalation and Staff Involvement -#### 10.5.1 Recognising Limits of Mini-Moderation +#### 10.5.1. Recognising Limits of Mini-Moderation Community members should recognise when situations require professional staff intervention: **Escalation Triggers:** @@ -1059,7 +1059,7 @@ Community members should recognise when situations require professional staff in - Complex conflicts that require formal mediation or resolution processes - Issues beyond the scope of peer education and support -#### 10.5.2 Appropriate Escalation Procedures +#### 10.5.2. Appropriate Escalation Procedures When mini-moderation reaches its limits: **Discontinue Personal Intervention:** @@ -1074,9 +1074,9 @@ When mini-moderation reaches its limits: - Offer to provide additional information or context if staff request it - Trust staff to handle situations according to their training and authority -### 10.6 Community Benefits and Culture Building +### 10.6. Community Benefits and Culture Building -#### 10.6.1 Positive Impact of Effective Mini-Moderation +#### 10.6.1. Positive Impact of Effective Mini-Moderation When conducted appropriately, mini-moderation contributes to: **Self-Regulating Community Culture:** @@ -1091,7 +1091,7 @@ When conducted appropriately, mini-moderation contributes to: - Continuous improvement in community knowledge and practices - Stronger relationships between community members -#### 10.6.2 Cultural Reinforcement and Development +#### 10.6.2. Cultural Reinforcement and Development Effective mini-moderation helps establish: - **Norm Reinforcement**: Clear, consistent messaging about community expectations - **Inclusive Practices**: Support for members learning to participate effectively @@ -1108,4 +1108,4 @@ Our community's strength lies not in rigid rule enforcement, but in the voluntar --- -*These Community Guidelines were last updated on 15 September 2025 and represent the collective wisdom and values of our community. For questions about these guidelines or suggestions for improvement, please contact our community staff through the designated channels outlined in our Community Code of Conduct.* +*These Community Guidelines represent the collective wisdom and values of our community. For questions about these guidelines or suggestions for improvement, please contact our community staff through the designated channels outlined in our Community Code of Conduct.* diff --git a/src/content/docs/community/leadership.md b/src/content/docs/community/leadership.md index 8307149..e927eef 100644 --- a/src/content/docs/community/leadership.md +++ b/src/content/docs/community/leadership.md @@ -4,11 +4,11 @@ title: Community Leadership and Governance Policy ## 1. Foundation and Purpose -### 1.1 Introduction +### 1.1. Introduction This Community Leadership and Governance Policy (hereinafter referred to as "the Policy") establishes the framework for transparent, accountable, and effective leadership within our community ecosystem. This Policy ensures that community leadership operates with integrity, serves the best interests of all community members, and maintains the highest standards of conduct whilst fostering a safe, welcoming, and inclusive environment. -### 1.2 Core Principles +### 1.2. Core Principles Our community leadership operates on the following foundational principles: @@ -22,30 +22,30 @@ Our community leadership operates on the following foundational principles: **(e)** **Collaborative Governance**: Community input is actively sought and valued in decision-making processes. -### 1.3 Legal Framework Integration +### 1.3. Legal Framework Integration This Policy operates within our comprehensive legal and policy framework, including our Terms of Service, Community Code of Conduct, Content and Moderation Policy, and Limitation of Liability and Indemnification Policy, all of which are incorporated herein by reference. ## 2. Leadership Structure and Roles -### 2.1 Leadership Hierarchy +### 2.1. Leadership Hierarchy Our community leadership operates through a structured hierarchy designed to ensure effective governance whilst maintaining accessibility and accountability: -#### 2.1.1 Executive Leadership +#### 2.1.1. Executive Leadership - **Community Director**: Overall strategic direction and final decision-making authority - **Deputy Director**: Support for Community Director and succession planning - **Legal and Policy Advisor**: Oversight of legal compliance and policy development -#### 2.1.2 Operational Leadership +#### 2.1.2. Operational Leadership - **Head Moderator**: Oversight of moderation team and enforcement consistency - **Community Managers**: Day-to-day community operations and member engagement - **Technical Manager**: Day-to-day technical operations, code reviews, and technical contributor coordination - **Technical Administrators**: Platform infrastructure management and strategic technical planning -#### 2.1.3 Specialist Leadership +#### 2.1.3. Specialist Leadership - **Accessibility Coordinator**: Ensuring inclusive design and accommodation - **Crisis Response Coordinator**: Mental health and emergency situation management @@ -56,7 +56,7 @@ Our community leadership operates through a structured hierarchy designed to ens - **Support Team Leader**: Oversight and coordination of community support operations - **Community Growth Specialist**: Member recruitment, retention, and community expansion initiatives -#### 2.1.4 Volunteer Leadership +#### 2.1.4. Volunteer Leadership - **Moderators**: Front-line community moderation and member support - **Mentors**: New member guidance and peer support programmes @@ -67,7 +67,7 @@ Our community leadership operates through a structured hierarchy designed to ens - **Quality Assurance Coordinator**: Testing and quality control for community platforms and resources - **Data and Analytics Coordinator**: Community metrics analysis and reporting -#### 2.1.5 Support Team +#### 2.1.5. Support Team - **Community Support Specialists**: General member assistance and issue resolution - **Technical Support Representatives**: Platform and technical assistance for community members @@ -75,9 +75,9 @@ Our community leadership operates through a structured hierarchy designed to ens - **Member Relations Specialists**: Member onboarding and relationship management - **Documentation Support Technicians**: Maintenance and improvement of community documentation -### 2.2 Role Responsibilities +### 2.2. Role Responsibilities -#### 2.2.1 Executive Leadership Responsibilities +#### 2.2.1. Executive Leadership Responsibilities **Community Director:** @@ -102,7 +102,7 @@ Our community leadership operates through a structured hierarchy designed to ens - Coordinate with external legal counsel when necessary - Maintain awareness of relevant laws and regulations affecting community operations -#### 2.2.2 Operational Leadership Responsibilities +#### 2.2.2. Operational Leadership Responsibilities **Head Moderator:** @@ -135,10 +135,10 @@ Our community leadership operates through a structured hierarchy designed to ens - Implement security protocols and system monitoring - Coordinate strategic technical planning and architecture decisions - Oversee system upgrades, maintenance, and disaster recovery procedures -- Collaborate with Technical Manager on technical project prioritization -- Ensure platform scalability and performance optimization +- Collaborate with Technical Manager on technical project prioritisation +- Ensure platform scalability and performance optimisation -#### 2.2.3 Specialist Leadership Responsibilities +#### 2.2.3. Specialist Leadership Responsibilities **Accessibility Coordinator:** @@ -159,7 +159,7 @@ Our community leadership operates through a structured hierarchy designed to ens **Events Coordinator:** -- Plan and organize community activities, events, and engagement programmes +- Plan and organise community activities, events, and engagement programmes - Coordinate with other leadership roles to ensure event alignment with community goals - Manage event logistics, scheduling, and resource allocation - Develop community engagement strategies to increase participation @@ -179,18 +179,18 @@ Our community leadership operates through a structured hierarchy designed to ens **Training and Development Coordinator:** - Develop and maintain comprehensive training curricula for all leadership roles -- Coordinate onboarding programs for new leaders and community members -- Manage mentorship program structure, matching, and effectiveness monitoring +- Coordinate onboarding programmes for new leaders and community members +- Manage mentorship programme structure, matching, and effectiveness monitoring - Oversee professional development opportunities and educational resources -- Ensure consistent training standards and quality across all programs +- Ensure consistent training standards and quality across all programmes - Coordinate with external training providers and professional development opportunities - Evaluate training effectiveness and implement continuous improvements **Partnership and Collaboration Coordinator:** -- Manage relationships with other communities, organizations, and external partners +- Manage relationships with other communities, organisations, and external partners - Coordinate collaborative projects and cross-community initiatives -- Oversee guest speaker programs and external educational opportunities +- Oversee guest speaker programmes and external educational opportunities - Manage sponsorship agreements and partnership development - Facilitate inter-community events and collaborative activities - Develop and maintain partnership agreements and memoranda of understanding @@ -205,7 +205,7 @@ Our community leadership operates through a structured hierarchy designed to ens - Handle escalated support issues and complex member concerns requiring leadership intervention - Coordinate support team scheduling and coverage to ensure consistent availability - Collaborate with other leadership roles to identify support needs and resource requirements -- Implement support team improvements and process optimizations based on feedback and analytics +- Implement support team improvements and process optimisations based on feedback and analytics - Serve as primary liaison between support team and executive/operational leadership - Manage support team knowledge base and ensure consistent information sharing @@ -215,15 +215,15 @@ Our community leadership operates through a structured hierarchy designed to ens - Analyse community growth metrics, member acquisition trends, and retention patterns - Design and execute outreach campaigns to attract new members from target demographics - Coordinate with Communications and Outreach Coordinator on growth-focused messaging and content -- Implement member retention programs and initiatives to reduce community churn +- Implement member retention programmes and initiatives to reduce community churn - Identify and develop community growth opportunities through partnerships and collaborations -- Monitor and optimize member onboarding processes to improve new member experience and retention +- Monitor and optimise member onboarding processes to improve new member experience and retention - Conduct market research and competitive analysis to identify growth opportunities -- Create and manage referral programs and member advocacy initiatives +- Create and manage referral programmes and member advocacy initiatives - Track and report on key growth metrics including member acquisition, retention, and lifetime value -- Collaborate with Events Coordinator to design growth-focused community activities and engagement programs +- Collaborate with Events Coordinator to design growth-focused community activities and engagement programmes -#### 2.2.4 Volunteer Leadership Responsibilities +#### 2.2.4. Volunteer Leadership Responsibilities **Moderators:** @@ -245,12 +245,12 @@ Our community leadership operates through a structured hierarchy designed to ens **Subject Matter Experts:** -- Provide specialized knowledge and expertise in designated areas +- Provide specialised knowledge and expertise in designated areas - Create educational content and resources for community members - Offer technical support and guidance within their areas of expertise - Lead workshops, discussions, and educational initiatives -- Serve as consultants to leadership team on specialized topics -- Mentor other community members in developing specialized skills +- Serve as consultants to leadership team on specialised topics +- Mentor other community members in developing specialised skills **Technical Contributors:** @@ -298,10 +298,10 @@ Our community leadership operates through a structured hierarchy designed to ens - Manage community surveys and feedback analysis for leadership decision-making - Support leadership team with data insights and trend identification - Maintain privacy-compliant data collection and analysis practices -- Develop dashboards and visualization tools for community metrics monitoring +- Develop dashboards and visualisation tools for community metrics monitoring - Coordinate with other leadership roles to identify key performance indicators and success metrics -#### 2.2.5 Support Team Responsibilities +#### 2.2.5. Support Team Responsibilities **Community Support Specialists:** @@ -327,7 +327,7 @@ Our community leadership operates through a structured hierarchy designed to ens - Assist community members with content creation, formatting, and publishing - Provide guidance on community content guidelines and best practices -- Help members optimize their contributions for accessibility and engagement +- Help members optimise their contributions for accessibility and engagement - Coordinate with Subject Matter Experts to ensure content accuracy and quality - Manage content creation resources, templates, and style guides - Support community content initiatives and collaborative projects @@ -337,7 +337,7 @@ Our community leadership operates through a structured hierarchy designed to ens - Facilitate new member onboarding and integration into community culture - Serve as primary point of contact for member concerns and relationship issues -- Coordinate welcome programs and new member orientation activities +- Coordinate welcome programmes and new member orientation activities - Monitor member satisfaction and engagement levels across the community - Mediate minor conflicts and facilitate communication between members - Collect member feedback and suggestions for community improvements @@ -355,11 +355,11 @@ Our community leadership operates through a structured hierarchy designed to ens ## 3. Selection and Appointment Processes -### 3.1 Leadership Selection Criteria +### 3.1. Leadership Selection Criteria All community leaders must demonstrate: -#### 3.1.1 Essential Qualifications +#### 3.1.1. Essential Qualifications - **Community Standing**: Minimum six (6) months of positive community participation - **Conduct Record**: Clean disciplinary record with no serious violations @@ -367,16 +367,16 @@ All community leaders must demonstrate: - **Commitment Availability**: Adequate time and energy to fulfil role responsibilities - **Values Alignment**: Strong commitment to community principles and inclusive practices -#### 3.1.2 Preferred Qualifications +#### 3.1.2. Preferred Qualifications - **Prior Leadership Experience**: Previous volunteer or professional leadership roles - **Specialised Knowledge**: Relevant expertise in moderation, community management, or technical areas - **Mentorship Capability**: Demonstrated ability to guide and support other community members - **Crisis Management Experience**: Skills in conflict resolution and emergency response -### 3.2 Selection Processes +### 3.2. Selection Processes -#### 3.2.1 Application and Nomination Process +#### 3.2.1. Application and Nomination Process **Open Applications:** @@ -392,13 +392,13 @@ All community leaders must demonstrate: - Existing leadership team provides assessments of candidate suitability - Transparent scoring rubrics ensure fair and consistent evaluation -#### 3.2.2 Interview and Assessment Process +#### 3.2.2. Interview and Assessment Process **Structured Interviews:** - All candidates participate in structured interviews with existing leadership - Scenario-based questions assess decision-making capabilities and values alignment -- Technical competency assessments for roles requiring specialized skills +- Technical competency assessments for roles requiring specialised skills - Cultural fit evaluation ensures compatibility with community values and practices **Community Engagement Assessment:** @@ -408,9 +408,9 @@ All community leaders must demonstrate: - Ethical decision-making assessments ensure integrity and sound judgement - Commitment verification confirms availability and dedication to the role -### 3.3 Appointment and Transition +### 3.3. Appointment and Transition -#### 3.3.1 Final Selection and Announcement +#### 3.3.1. Final Selection and Announcement **Decision Making:** @@ -428,9 +428,9 @@ All community leaders must demonstrate: ## 4. Leadership Accountability and Oversight -### 4.1 Performance Standards and Expectations +### 4.1. Performance Standards and Expectations -#### 4.1.1 Ongoing Performance Metrics +#### 4.1.1. Ongoing Performance Metrics All community leaders are evaluated on: @@ -448,7 +448,7 @@ All community leaders are evaluated on: - Professional development and skills enhancement - Collaboration effectiveness with other leadership team members -#### 4.1.2 Regular Review Processes +#### 4.1.2. Regular Review Processes **Quarterly Performance Reviews:** @@ -464,9 +464,9 @@ All community leaders are evaluated on: - Leadership development planning and career progression discussions - Reappointment decisions based on performance and community needs -### 4.2 Community Feedback and Input Mechanisms +### 4.2. Community Feedback and Input Mechanisms -#### 4.2.1 Regular Feedback Channels +#### 4.2.1. Regular Feedback Channels **Monthly Community Forums:** @@ -482,7 +482,7 @@ All community leaders are evaluated on: - Community liaison positions to facilitate communication between members and leadership - Transparent communication about leadership decisions and their rationales -#### 4.2.2 Formal Accountability Processes +#### 4.2.2. Formal Accountability Processes **Community Confidence Measures:** @@ -491,9 +491,9 @@ All community leaders are evaluated on: - Transparent reporting of community feedback themes and leadership responses - Regular town hall meetings for community-wide discussion of governance issues -### 4.3 Leadership Standards Enforcement +### 4.3. Leadership Standards Enforcement -#### 4.3.1 Misconduct Investigation Procedures +#### 4.3.1. Misconduct Investigation Procedures When concerns about leadership conduct arise: @@ -511,7 +511,7 @@ When concerns about leadership conduct arise: - Independent review panels including community member representation - Clear standards of evidence and burden of proof requirements -#### 4.3.2 Disciplinary Measures and Consequences +#### 4.3.2. Disciplinary Measures and Consequences **Progressive Disciplinary System:** @@ -529,9 +529,9 @@ When concerns about leadership conduct arise: ## 5. Leadership Development and Support -### 5.1 Training and Professional Development +### 5.1. Training and Professional Development -#### 5.1.1 Mandatory Training Programs +#### 5.1.1. Mandatory Training Programs All community leaders must complete: @@ -551,13 +551,13 @@ All community leaders must complete: - Technical administration and security for technical leadership - Event planning and community engagement for activities coordinators -#### 5.1.2 Ongoing Development Opportunities +#### 5.1.2. Ongoing Development Opportunities **Skill Enhancement Programs:** - Leadership coaching and mentorship opportunities - External training and conference attendance support -- Cross-functional experience and role shadowing programs +- Cross-functional experience and role shadowing programmes - Community management and governance best practices workshops **Personal Development Support:** @@ -567,15 +567,15 @@ All community leaders must complete: - Cultural competency and diversity, equity, inclusion education - Technology skills and platform administration training -### 5.2 Leadership Support Systems +### 5.2. Leadership Support Systems -#### 5.2.1 Peer Support Networks +#### 5.2.1. Peer Support Networks **Leadership Team Collaboration:** - Regular leadership team meetings for coordination and mutual support - Peer mentoring partnerships for experience sharing and guidance -- Cross-training programs to ensure coverage and capability development +- Cross-training programmes to ensure coverage and capability development - Team-building activities and relationship-strengthening initiatives **External Professional Networks:** @@ -585,14 +585,14 @@ All community leaders must complete: - Industry conference attendance and professional development events - Access to external coaching and consultation resources -#### 5.2.2 Wellness and Burnout Prevention +#### 5.2.2. Wellness and Burnout Prevention **Workload Management:** - Clear role boundaries and expectation setting to prevent overextension - Regular workload assessment and redistribution when necessary - Mandatory rest periods and vacation time for volunteer leaders -- Recognition and appreciation programs to maintain motivation and satisfaction +- Recognition and appreciation programmes to maintain motivation and satisfaction **Mental Health Support:** @@ -602,15 +602,15 @@ All community leaders must complete: ## 6. Succession Planning and Continuity -### 6.1 Leadership Succession Framework +### 6.1. Leadership Succession Framework -#### 6.1.1 Planned Succession Processes +#### 6.1.1. Planned Succession Processes **Leadership Pipeline Development:** - Identification and mentorship of potential future leaders - Progressive responsibility assignments to prepare succession candidates -- Cross-training programs to ensure multiple qualified candidates for key roles +- Cross-training programmes to ensure multiple qualified candidates for key roles - Regular succession planning reviews and candidate development assessment **Transition Management:** @@ -620,7 +620,7 @@ All community leaders must complete: - Interim leadership arrangements during transition periods - Community communication strategies for leadership changes -#### 6.1.2 Emergency Succession Procedures +#### 6.1.2. Emergency Succession Procedures **Crisis Leadership Arrangements:** @@ -629,9 +629,9 @@ All community leaders must complete: - Rapid response team formation for crisis management - Community communication protocols for emergency leadership changes -### 6.2 Knowledge Management and Institutional Memory +### 6.2. Knowledge Management and Institutional Memory -#### 6.2.1 Documentation and Record-Keeping +#### 6.2.1. Documentation and Record-Keeping **Leadership Knowledge Base:** @@ -649,9 +649,9 @@ All community leaders must complete: ## 7. Community Transparency and Communication -### 7.1 Transparency Requirements +### 7.1. Transparency Requirements -#### 7.1.1 Public Reporting and Disclosure +#### 7.1.1. Public Reporting and Disclosure **Regular Community Updates:** @@ -667,7 +667,7 @@ All community leaders must complete: - Open meeting minutes and records for community leadership discussions - Clear communication of appeals processes and outcomes -#### 7.1.2 Community Engagement and Input +#### 7.1.2. Community Engagement and Input **Participatory Governance:** @@ -678,9 +678,9 @@ All community leaders must complete: ## 8. Policy Implementation and Review -### 8.2 Regular Review and Updates +### 8.2. Regular Review and Updates -#### 8.2.1 Policy Review Schedule +#### 8.2.1. Policy Review Schedule **Annual Reviews:** @@ -696,9 +696,9 @@ All community leaders must complete: - Regular benchmarking against community management best practices - Ongoing legal and regulatory compliance verification -### 8.2 Amendment Procedures +### 8.2. Amendment Procedures -#### 8.2.1 Policy Change Process +#### 8.2.1. Policy Change Process **Community Input Requirements:** @@ -709,9 +709,9 @@ All community leaders must complete: **Implementation and Communication:** -- Clear communication of policy changes and effective dates +- Clear communication of policy changes - Training updates for all leadership team members -- Community education and awareness programs for new requirements +- Community education and awareness programmes for new requirements - Regular monitoring of policy effectiveness and community impact --- @@ -724,4 +724,4 @@ This Policy represents our collective commitment to maintaining excellent leader --- -_This Community Leadership and Governance Policy was created on 15 September 2025. For questions about this Policy or to provide feedback on leadership performance, please contact our Community Leaders through the designated channels outlined in our Community Code of Conduct._ +_This Community Leadership and Governance Policy provides comprehensive information about leadership and governance. For questions about this Policy or to provide feedback on leadership performance, please contact our Community Leaders through the designated channels outlined in our Community Code of Conduct._ diff --git a/src/content/docs/community/recognition.md b/src/content/docs/community/recognition.md index 5a0f9b8..7af77ab 100644 --- a/src/content/docs/community/recognition.md +++ b/src/content/docs/community/recognition.md @@ -4,11 +4,11 @@ title: Community Recognition and Appreciation Policy ## 1. Foundation and Philosophy -### 1.1 Introduction and Purpose +### 1.1. Introduction and Purpose This Community Recognition and Appreciation Policy (hereinafter referred to as "the Policy") establishes our comprehensive framework for acknowledging, celebrating, and appreciating the diverse contributions of community members. This Policy recognises that fostering a truly welcoming and inclusive environment requires intentional appreciation of member efforts, celebration of diverse talents and contributions, and creation of meaningful recognition systems that motivate continued positive engagement. -### 1.2 Core Principles +### 1.2. Core Principles Our recognition and appreciation approach is founded upon: @@ -20,11 +20,11 @@ Our recognition and appreciation approach is founded upon: **(d)** **Cultural Sensitivity**: Recognition practices that respect diverse cultural approaches to appreciation and celebration; -**(e)** **Sustainable Systems**: Long-term recognition programs that maintain motivation and community engagement; +**(e)** **Sustainable Systems**: Long-term recognition programmes that maintain motivation and community engagement; **(f)** **Community-Driven Values**: Recognition that reinforces positive community culture and shared values. -### 1.3 Recognition Philosophy +### 1.3. Recognition Philosophy We believe that every community member contributes value in unique ways, and our recognition systems are designed to: - Acknowledge contributions both large and small @@ -33,15 +33,15 @@ We believe that every community member contributes value in unique ways, and our - Build community connections and mutual appreciation - Encourage continued positive contribution and community involvement -### 1.4 Legal Framework Integration +### 1.4. Legal Framework Integration This Policy operates within our comprehensive legal and policy framework, including our Terms of Service, Privacy Policy, Community Code of Conduct, and Community Leadership and Governance Policy, all of which are incorporated herein by reference. ## 2. Recognition Categories and Programs -### 2.1 Regular Recognition Programs +### 2.1. Regular Recognition Programmes -#### 2.1.1 Daily Appreciation Initiatives +#### 2.1.1. Daily Appreciation Initiatives **Community Gratitude Practices:** - Daily appreciation messages highlighting specific member contributions @@ -55,7 +55,7 @@ This Policy operates within our comprehensive legal and policy framework, includ - Recognition of members who provide assistance, answer questions, or offer guidance - Acknowledgement of members who demonstrate inclusive and welcoming behaviour -#### 2.1.2 Monthly Recognition Programs +#### 2.1.2. Monthly Recognition Programmes **Member of the Month Awards:** - Recognition for outstanding community contribution and positive impact @@ -69,9 +69,9 @@ This Policy operates within our comprehensive legal and policy framework, includ - **Innovator of the Month**: Members who bring creative ideas, solutions, or new perspectives - **Inclusivity Champion**: Members who actively promote inclusive practices and welcoming environments -### 2.2 Special Recognition Programs +### 2.2. Special Recognition Programmes -#### 2.2.1 Annual Achievement Awards +#### 2.2.1. Annual Achievement Awards **Excellence in Community Building:** - Outstanding Community Leader Award for members who demonstrate exceptional leadership qualities @@ -85,7 +85,7 @@ This Policy operates within our comprehensive legal and policy framework, includ - **Behind-the-Scenes Hero**: Members who contribute significantly in less visible but essential ways - **Community Bridge Builder**: Members who facilitate connections and resolve conflicts constructively -#### 2.2.2 Milestone Celebration Programs +#### 2.2.2. Milestone Celebration Programs **Participation Milestone Recognition:** - Anniversary celebrations for community membership milestones (1 year, 2 years, 5 years) @@ -104,9 +104,9 @@ This Policy operates within our comprehensive legal and policy framework, includ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuovSixbXFEnkYq-3Gp-bZMH-n__PNRKw ::: -### 3.1 Community-Driven Nomination Systems +### 3.1. Community-Driven Nomination Systems -#### 3.1.1 Peer Nomination Processes +#### 3.1.1. Peer Nomination Processes **Open Nomination Periods:** - Monthly nomination windows allowing any community member to nominate others @@ -120,7 +120,7 @@ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuov - Focus on effort, growth, and positive community impact rather than just results - Consideration of diverse contribution types and varying participation styles -#### 3.1.2 Selection and Review Processes +#### 3.1.2. Selection and Review Processes **Diverse Selection Committees:** - Rotating committee membership ensuring diverse perspectives and fair evaluation @@ -134,9 +134,9 @@ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuov - Multiple reviewer assessment system for important recognition decisions - Regular review of selection processes to ensure equity and effectiveness -### 3.2 Recognition Frequency and Distribution +### 3.2. Recognition Frequency and Distribution -#### 3.2.1 Balanced Recognition Distribution +#### 3.2.1. Balanced Recognition Distribution **Inclusive Recognition Practices:** - Ensure recognition reaches members from all community areas and participation styles @@ -152,9 +152,9 @@ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuov ## 4. Types of Contributions Valued -### 4.1 Direct Community Contributions +### 4.1. Direct Community Contributions -#### 4.1.1 Active Participation and Engagement +#### 4.1.1. Active Participation and Engagement **Discussion and Content Contributions:** - Thoughtful questions that promote community learning and engagement @@ -168,7 +168,7 @@ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuov - Mentoring and guidance for less experienced community members - Conflict resolution assistance and constructive mediation efforts -#### 4.1.2 Leadership and Initiative +#### 4.1.2. Leadership and Initiative **Volunteer Leadership Roles:** - Moderation activities and community standards enforcement @@ -178,13 +178,13 @@ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuov **Innovation and Problem-Solving:** - Creative solutions to community challenges and improvement opportunities -- New program or initiative development and implementation +- New programme or initiative development and implementation - Technology improvements and platform enhancement contributions - Process improvements that enhance community experience and accessibility -### 4.2 Indirect and Supporting Contributions +### 4.2. Indirect and Supporting Contributions -#### 4.2.1 Community Culture Building +#### 4.2.1. Community Culture Building **Positive Environment Creation:** - Consistent demonstration of inclusive and welcoming behaviour @@ -193,12 +193,12 @@ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuov - Celebration of other members' achievements and positive contribution acknowledgement **Values Demonstration and Modeling:** -- Exemplary adherence to community standards and positive behaviour modeling +- Exemplary adherence to community standards and positive behaviour modelling - Advocacy for inclusive practices and accessibility improvements - Support for marginalised community members and inclusive representation - Constructive engagement with community policies and improvement processes -#### 4.2.2 Behind-the-Scenes Contributions +#### 4.2.2. Behind-the-Scenes Contributions **Administrative and Organisational Support:** - Documentation improvement and resource organisation activities @@ -214,9 +214,9 @@ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuov ## 5. Recognition Methods and Formats -### 5.1 Public Recognition and Celebration +### 5.1. Public Recognition and Celebration -#### 5.1.1 Community Announcements and Features +#### 5.1.1. Community Announcements and Features **Regular Recognition Announcements:** - Weekly appreciation announcements highlighting specific member contributions @@ -230,7 +230,7 @@ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuov - "Wall of Fame" or recognition gallery featuring outstanding contributors - Newsletter features and external communication highlighting member achievements -#### 5.1.2 Community Events and Celebrations +#### 5.1.2. Community Events and Celebrations **Recognition Ceremony Events:** - Annual awards ceremony with community-wide attendance and celebration @@ -244,14 +244,14 @@ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuov - Peer appreciation sessions where members can acknowledge each other's contributions - Storytelling events where members share impact stories and appreciation experiences -### 5.2 Private and Personal Recognition +### 5.2. Private and Personal Recognition -#### 5.2.1 Individual Appreciation Communications +#### 5.2.1. Individual Appreciation Communications **Personal Recognition Messages:** - Direct appreciation messages from community leadership acknowledging specific contributions - Personalized thank-you notes for exceptional community service and positive impact -- One-on-one appreciation conversations recognizing member efforts and growth +- One-on-one appreciation conversations recognising member efforts and growth - Private acknowledgement of sensitive contributions that require confidential appreciation **Tailored Recognition Approaches:** @@ -262,9 +262,9 @@ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuov ## 6. Accessibility and Inclusion in Recognition -### 6.1 Universal Design Recognition Systems +### 6.1. Universal Design Recognition Systems -#### 6.1.1 Accessible Recognition Participation +#### 6.1.1. Accessible Recognition Participation **Inclusive Nomination Processes:** - Multiple nomination methods accommodating different communication preferences and abilities @@ -278,7 +278,7 @@ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuov - Clear communication about accessibility features and accommodation availability - Alternative participation methods for members unable to attend live recognition events -#### 6.1.2 Diverse Recognition Styles +#### 6.1.2. Diverse Recognition Styles **Cultural Sensitivity in Recognition:** - Recognition practices that respect diverse cultural approaches to appreciation and celebration @@ -292,9 +292,9 @@ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuov - Clear communication about recognition expectations and optional participation levels - Flexible recognition formats that allow members to engage in ways that work best for them -### 6.2 Equity in Recognition Distribution +### 6.2. Equity in Recognition Distribution -#### 6.2.1 Bias Awareness and Prevention +#### 6.2.1. Bias Awareness and Prevention **Systematic Bias Prevention:** - Regular analysis of recognition distribution patterns to identify and address potential bias @@ -308,7 +308,7 @@ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuov - Recognition of contributions that may be less visible but equally valuable to community health - Consideration of different life circumstances and availability levels in recognition evaluation -#### 6.2.2 Representative Recognition Outcomes +#### 6.2.2. Representative Recognition Outcomes **Demographic Equity Monitoring:** - Regular assessment of recognition distribution across different community demographic groups @@ -318,9 +318,9 @@ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuov ## 7. Volunteer Appreciation and Support -### 7.1 Leadership and Staff Recognition +### 7.1. Leadership and Staff Recognition -#### 7.1.1 Volunteer Appreciation Programs +#### 7.1.1. Volunteer Appreciation Programs **Regular Volunteer Recognition:** - Monthly volunteer appreciation events with special recognition for leadership contributions @@ -330,11 +330,11 @@ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuov **Professional Development and Growth Support:** - Training and skill development opportunities for volunteers as appreciation for their service -- Leadership development programs and advancement opportunities within community structure +- Leadership development programmes and advancement opportunities within community structure - Professional reference and recommendation support for volunteers seeking career opportunities - Networking opportunities and community connections that benefit volunteer development -#### 7.1.2 Volunteer Wellness and Burnout Prevention +#### 7.1.2. Volunteer Wellness and Burnout Prevention **Volunteer Support Systems:** - Regular check-ins with volunteers to assess satisfaction, challenges, and support needs @@ -350,25 +350,25 @@ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuov ## 8. Community Feedback and Recognition Evolution -### 8.1 Community Input on Recognition Programs +### 8.1. Community Input on Recognition Programmes -#### 8.1.1 Regular Feedback Collection +#### 8.1.1. Regular Feedback Collection -**Recognition Program Evaluation:** -- Annual surveys collecting community feedback on recognition program effectiveness and satisfaction -- Focus groups with community members who have received recognition to assess program impact +**Recognition Programme Evaluation:** +- Annual surveys collecting community feedback on recognition programme effectiveness and satisfaction +- Focus groups with community members who have received recognition to assess programme impact - Input collection from community members who have not received recognition to identify barriers and improvements -- Regular assessment of recognition program accessibility and inclusive representation +- Regular assessment of recognition programme accessibility and inclusive representation **Continuous Improvement Integration:** -- Community suggestion processes for recognition program enhancement and new recognition categories -- Responsive program modification based on community feedback and changing needs -- Transparent communication about recognition program changes and improvement rationales -- Community involvement in recognition program planning and development processes +- Community suggestion processes for recognition programme enhancement and new recognition categories +- Responsive programme modification based on community feedback and changing needs +- Transparent communication about recognition programme changes and improvement rationales +- Community involvement in recognition programme planning and development processes -### 8.2 Recognition Program Evolution and Innovation +### 8.2. Recognition Programme Evolution and Innovation -#### 8.2.1 Adaptive Recognition Systems +#### 8.2.1. Adaptive Recognition Systems **Emerging Recognition Opportunities:** - Regular evaluation of community needs and new types of contributions that merit recognition @@ -377,43 +377,43 @@ Nomination form can be found at https://forms.nhcarrigan.com/form/wksk-NuR3HBuov - Partnership development with external organisations to expand recognition opportunities and resources **Long-Term Program Sustainability:** -- Planning for recognition program continuity during leadership transitions and community growth +- Planning for recognition programme continuity during leadership transitions and community growth - Resource allocation and volunteer development to support ongoing recognition activities -- Documentation and knowledge preservation to maintain recognition program quality and consistency -- Strategic planning for recognition program expansion and enhancement as community evolves +- Documentation and knowledge preservation to maintain recognition programme quality and consistency +- Strategic planning for recognition programme expansion and enhancement as community evolves ## 9. Policy Implementation and Review -### 9.1 Regular Review and Enhancement +### 9.1. Regular Review and Enhancement -#### 9.1.1 Continuous Improvement Process +#### 9.1.1. Continuous Improvement Process **Monthly Program Assessment:** -- Recognition program effectiveness evaluation and participant satisfaction assessment +- Recognition programme effectiveness evaluation and participant satisfaction assessment - Recognition distribution analysis to ensure equity and inclusive representation -- Community feedback integration and program adjustment based on member input -- Volunteer appreciation program evaluation and enhancement planning +- Community feedback integration and programme adjustment based on member input +- Volunteer appreciation programme evaluation and enhancement planning **Annual Comprehensive Review:** -- Community-wide recognition program impact assessment and satisfaction evaluation +- Community-wide recognition programme impact assessment and satisfaction evaluation - Recognition criteria and selection process review for effectiveness and fairness - Accessibility and inclusion evaluation with improvement planning and implementation -- Strategic planning for recognition program expansion and innovation +- Strategic planning for recognition programme expansion and innovation -### 9.2 Community Celebration and Recognition Culture +### 9.2. Community Celebration and Recognition Culture -#### 9.2.1 Culture Development and Reinforcement +#### 9.2.1. Culture Development and Reinforcement **Recognition Culture Promotion:** - Community education about the importance and impact of appreciation and recognition - Peer-to-peer recognition encouragement and facilitation -- Leadership modeling of appreciation and recognition practices +- Leadership modelling of appreciation and recognition practices - Integration of recognition and appreciation into regular community activities and interactions **Long-Term Community Impact:** -- Recognition program contribution to overall community health and member satisfaction +- Recognition programme contribution to overall community health and member satisfaction - Appreciation culture development and maintenance as community grows and evolves -- Recognition program role in member retention and continued positive community engagement +- Recognition programme role in member retention and continued positive community engagement - Community reputation enhancement through recognition of excellence and positive contribution --- @@ -426,4 +426,4 @@ Through this Policy, we pledge to maintain systems that celebrate diverse contri --- -*This Community Recognition and Appreciation Policy was created on 15 September 2025. For questions about recognition programs or to nominate community members for appreciation, please contact our Community Leaders through the designated channels outlined in our Community Code of Conduct.* +*This Community Recognition and Appreciation Policy provides comprehensive information about recognition programmes. For questions about recognition programmes or to nominate community members for appreciation, please contact our Community Leaders through the designated channels outlined in our Community Code of Conduct.* diff --git a/src/content/docs/dev/contributing.md b/src/content/docs/dev/contributing.md index 4d19d84..ed41645 100644 --- a/src/content/docs/dev/contributing.md +++ b/src/content/docs/dev/contributing.md @@ -2,13 +2,21 @@ title: Contributing Documentation --- -## 1. Scope and General Contribution Guidelines +**ESTABLISHING CONTRIBUTION GUIDELINES AND REQUIREMENTS FOR ALL PROJECTS** -### 1.1 Overview +## 1. INTRODUCTION AND LEGAL FRAMEWORK -This document outlines the general guidelines for contributing to our projects. It serves as a high-level framework for all contributors, whether you're submitting code, documentation, or other forms of contribution. +### 1.1. Policy Overview -### 1.2 Project-Specific Instructions +This Contributing Documentation (hereinafter referred to as "the Guidelines") establishes mandatory guidelines, procedures, and requirements for all contributions to projects maintained by our organisation. These Guidelines operate within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Contributor Covenant, and all applicable legal protections by reference. + +### 1.2. Scope and Applicability + +These Guidelines apply to all forms of contribution, including but not limited to code, documentation, artwork, design, and other materials submitted to any project maintained by our organisation. All contributors, regardless of status or experience level, are required to comply with these Guidelines. + +**IMPORTANT: Failure to comply with these Guidelines may result in rejection of contributions, requests for modification, or other appropriate actions as determined by project maintainers.** + +### 1.3. Project-Specific Instructions While these guidelines apply broadly, individual projects may have unique requirements or processes. Always refer to the specific project's documentation for: @@ -20,151 +28,118 @@ While these guidelines apply broadly, individual projects may have unique requir In case of any discrepancy between this document and project-specific guidelines, the project-specific instructions take precedence. -### 1.3 Commit Signing Requirements +### 1.4. Commit Signing Requirements All commits must be cryptographically signed using either GPG or SSH. This requirement serves to verify the authenticity and integrity of your contributions. -- For GPG signing, ensure your GPG key is associated with your GitHub or Codeberg account. -- For SSH signing, use a key linked to your GitHub or Codeberg account. +- For GPG signing, ensure your GPG key is associated with your Github or NHCarrigan Git account. +- For SSH signing, use a key linked to your Github or NHCarrigan Git account. By signing your commit, you are certifying that: -- The commit adheres to our [Contributor Covenant](/covenant.md) +- The commit adheres to our [Contributor Covenant](/dev/covenant) - You have the right to submit the contribution under our project license. - You understand and agree to our contribution terms. -### 1.4 Contributor Covenant +### 1.5. Contributor Covenant -All contributors are expected to adhere to our Contributor Covenant. The full text of the Contributor Covenant can be found in [its own document](/covenant.md). +All contributors are expected to adhere to our Contributor Covenant. The full text of the Contributor Covenant can be found in [its own document](/dev/covenant). -### 1.5 Licensing of Contributions +### 1.6. Licensing of Contributions -All contributions to our projects, including but not limited to code, documentation, artwork, and other materials, will be licensed under our global software license. By submitting a contribution, you are agreeing to license your work under the terms of this license. +All contributions to our projects, including but not limited to code, documentation, artwork, and other materials, will be licensed under our global software licence. By submitting a contribution, you are agreeing to license your work under the terms of this license. -- Our global software license: Naomi's Public License +- Our global software licence: Naomi's Public Licence - Full text of the license: [License Page](/legal/license) -### 1.6 Intellectual Property +### 1.7. Intellectual Property By contributing to our projects, you affirm that: -- You own the copyright to your contribution or have authorization from the copyright owner to submit it under our license. +- You own the copyright to your contribution or have authorisation from the copyright owner to submit it under our license. - Your contribution does not infringe on any third-party intellectual property rights. - You grant us a perpetual, worldwide, non-exclusive, royalty-free license to use, modify, and distribute your contribution. -### 1.7 Legal Compliance +### 1.8. Legal Compliance Ensure all contributions comply with relevant laws and regulations, including export controls and data protection laws. -### 1.8 Acceptance of Contributions +### 1.9. Acceptance of Contributions While we appreciate all contributions, we reserve the right to reject any contribution that doesn't meet our standards or align with our project goals. The project maintainers have final say on the inclusion of any contribution. -## 2. Secrets Management +## 2. SECRETS MANAGEMENT -### 2.1 Overview +### 2.1. Overview -Proper management of secrets is crucial for maintaining the security and integrity of our projects. We use 1Password as our centralized secrets management solution. This section outlines our policies and procedures for handling secrets. +Proper management of secrets is crucial for maintaining the security and integrity of our projects. We use 1Password as our centralised secrets management solution. This section outlines our policies and procedures for handling secrets. -### 2.2 General Policy +### 2.2. General Policy - Plain-text secrets should never be stored on personal machines, development environments, or our servers. - All secrets should be stored and managed through 1Password. -### 2.3 1Password Setup and Usage +### 2.3. 1Password Setup and Usage To work with secrets locally, you must set up the 1Password CLI (Command Line Interface) and integrate it with your 1Password desktop application. -#### 2.3.1 Setup Instructions +#### 2.3.1. Setup Instructions - Install the 1Password desktop application if you haven't already. - Install the 1Password CLI. Instructions can be found at: https://developer.1password.com/docs/cli/get-started/ - Authenticate the CLI with your 1Password account. - Configure your development environment to use the 1Password CLI for secret retrieval. https://developer.1password.com/docs/cli/secrets-environment-variables/ -#### 2.3.2 Best Practices +#### 2.3.2. Best Practices - Use environment variables to store secrets retrieved from 1Password during runtime. - Never log or display secrets in any form. - Rotate secrets regularly. -### 2.4 Handling Secrets in Code +### 2.4. Handling Secrets in Code - Development environment variables should be set in `dev.env` - changes to this file should generally be excluded from your contributions. - Use 1Password references instead of actual secret values in configuration files. -## 3. Setting Up Your Development Environment +## 3. SETTING UP YOUR DEVELOPMENT ENVIRONMENT -### 3.1 Forking the Repository +### 3.1. Gaining a Contributor Account -1. Navigate to the original repository on Codeberg. -2. Click the "Fork" button in the upper right corner of the page. -3. Select your account as the destination for the fork. -4. Wait for Codeberg to create a copy of the repository in your account. +Contributor accounts are provided only to members of our team. If you wish to join our volunteer team, please [apply](https://forms.nhcarrigan.com/form/PEpB3gA79gxP8wmfEf4zou96opkpUTjssTcaeYjhoi8) for our Technical Contributor position. -### 3.2 Cloning Your Fork +Once accepted, you will be granted credentials as part of your onboarding. -1. Go to your forked repository on Codeberg. -2. Click the "Code" button and copy the URL (HTTPS or SSH, depending on your setup). +### 3.2. Cloning A Project + +1. Go to repository on NHCarrigan's Git instance. +2. Click the "Code" button and copy the HTTPS URL. 3. Open your terminal or command prompt. 4. Navigate to the directory where you want to store the project. 5. Run the following command, replacing `` with the URL you copied: - ``` + ```bash git clone ``` -6. Enter your GitHub credentials if prompted. +6. Enter your Git credentials if prompted. -### 3.3 Setting Up the Upstream Remote +### 3.3. Keeping Your Clone Up-to-Date -Adding the original repository as an upstream remote allows you to easily keep your fork up-to-date. +Regularly update your clone to incorporate changes from the upstream repository: -1. Change into the project directory: +1. Check out the main branch: - ``` - cd - ``` - -2. Add the upstream remote: - - ``` - git remote add upstream - ``` - - Replace `` with the **git** URL of the original repository. - -3. Verify the new remote: - - ``` - git remote -v - ``` - - You should see entries for both `origin` (your fork) and `upstream`. - -### 3.4 Keeping Your Fork Up-to-Date - -Regularly update your fork to incorporate changes from the upstream repository: - -1. Fetch the branches and commits from the upstream repository: - - ``` - git fetch upstream - ``` - -2. Check out your fork's local main branch: - - ``` + ```bash git checkout main ``` -3. Merge changes from upstream/main into your local main branch: +2. Pull changes from upstream to your local clone: - ``` - git merge upstream/main + ```bash + git pull ``` -### 3.5 Troubleshooting +### 3.4. Troubleshooting If you encounter any issues during setup: @@ -172,28 +147,28 @@ If you encounter any issues during setup: 2. Search for similar issues in the project's issue tracker. 3. If the problem persists, open a new issue with detailed information about the problem and steps to reproduce it. -You can also reach out to us on our forum: https://forum.nhcarrigan.com +You can also reach out to us in our Discord community: https://chat.nhcarrigan.com -## 4. Claiming an Issue +## 4. CLAIMING AN ISSUE -### 4.1 Finding an Issue +### 4.1. Finding an Issue 1. Navigate to the project's issue tracker. 2. Browse open issues or use filters to find tasks that interest you. 3. Read the issue description thoroughly to understand the requirements and context. -### 4.2 Expressing Interest +### 4.2. Expressing Interest 1. If you find an issue you'd like to work on, comment on the issue expressing your interest. 2. Example comment: "I'm interested in working on this issue. May I be assigned to it?" 3. Wait for a project maintainer to respond and potentially assign the issue to you. -### 4.3 Issue Assignment +### 4.3. Issue Assignment - Project maintainers will assign issues based on the order of interest and the contributor's experience level. - Once assigned, you'll see your username in the "Assignees" section of the issue. -### 4.4 Already Assigned Issues +### 4.4. Already Assigned Issues If an issue is already assigned: @@ -204,32 +179,32 @@ If an issue is already assigned: We encourage collaboration and pair programming on complex issues! -### 4.5 Working on the Issue +### 4.5. Working on the Issue -1. Once assigned, create a new branch in your fork for this specific issue. +1. Once assigned, create a new branch in the project for this specific issue. 2. Use a descriptive branch name, e.g., `fix/issue-123-button-alignment`. 3. Make your changes, committing regularly with clear, concise commit messages. -4. Push your changes to your fork. +4. Push your changes to your branch. 5. Open a pull request when ready for review (see Pull Request Guidelines in section [X]). -### 4.6 Keeping the Community Updated +### 4.6. Keeping the Community Updated 1. Provide regular updates on your progress in the issue comments. 2. If you encounter obstacles, don't hesitate to ask for help in the issue thread. 3. If you need to step away from an issue, please let us know so it can be reassigned if necessary. -### 4.7 Time Management +### 4.7. Time Management - Try to start working on the issue within a few days of assignment. - If you haven't made progress within a week, the issue may be unassigned to keep the project moving forward. - If you need more time, communicate this in the issue comments. -### 4.8 Multiple Issues +### 4.8. Multiple Issues - We encourage focusing on one issue at a time to ensure quality and timely completion. - If you want to work on multiple issues, please complete one before requesting assignment to another. -### 4.9 Issue Labels +### 4.9. Issue Labels Pay attention to issue labels for additional context: @@ -237,27 +212,27 @@ Pay attention to issue labels for additional context: - `help wanted`: Issues where we're actively seeking community help. - `staff only`: Issue that will require staff attention. -### 4.10 Respectful Communication +### 4.10. Respectful Communication - Always be courteous and professional in issue discussions. - Respect the decisions of project maintainers regarding issue assignments and priorities. - If you disagree with something, express your thoughts constructively and be open to feedback. -## 5. Working on Your Issue +## 5. WORKING ON YOUR ISSUE -### 5.1 Updating Your Fork +### 5.1. Updating Your Clone -Before starting work, ensure your forked version is up to date with the original repository. If you've set up the `upstream` remote as mentioned in Section 3, follow these steps: +Before starting work, ensure your clone is up to date with the original repository. 1. Open your terminal and navigate to your project's root directory. 2. Run the following commands: ```bash - git fetch upstream - git merge upstream/main + git checkout main + git pull ``` -### 5.2 Creating a New Branch +### 5.2. Creating a New Branch Always create a new branch for your work: @@ -278,17 +253,17 @@ Always create a new branch for your work: - `fix/resolve-memory-leak` - `docs/update-api-endpoints` -### 5.3 Making Changes +### 5.3. Making Changes 1. Make your code changes, following the project's coding standards and guidelines. 2. Regularly commit your changes with clear, concise messages. -3. Push your changes to your fork periodically: +3. Push your changes to your branch periodically: ```bash git push origin ``` -### 5.4 Committing Changes +### 5.4. Committing Changes When you're ready to commit your changes: @@ -310,7 +285,7 @@ When you're ready to commit your changes: git commit ``` -### 5.5 Commit Message Guidelines +### 5.5. Commit Message Guidelines - Follow Conventional Commit standards: `type(scope): description` such as `docs: update contributing guidelines`. - Use the present tense ("Add feature" not "Added feature") @@ -327,7 +302,7 @@ feat: add user authentication system Implement JWT-based authentication for API endpoints. ``` -### 5.7 Testing Your Changes +### 5.7. Testing Your Changes - Run the linter to ensure your code complies with [our style guidelines](/dev/style). @@ -343,12 +318,12 @@ Implement JWT-based authentication for API endpoints. - Add new tests for your changes if applicable. -### 5.8 Documentation +### 5.8. Documentation - Update relevant documentation to reflect your changes. - If you've added new features, include appropriate documentation. -### 5.9 Preparing for Pull Request +### 5.9. Preparing for Pull Request Before submitting a pull request: @@ -357,32 +332,32 @@ Before submitting a pull request: 1. Ensure all tests pass. 1. Review your changes and commit history. -If you're unsure about any part of the process or need help, don't hesitate to ask in our [forum](https://forum.nhcarrigan.com). Our community is here to support you! +If you're unsure about any part of the process or need help, don't hesitate to ask in our [Discord community](https://chat.nhcarrigan.com). Our community is here to support you! -## 6. Submitting a Pull Request +## 6. SUBMITTING A PULL REQUEST -### 6.1 Pushing Your Changes +### 6.1. Pushing Your Changes -1. Push your changes to your forked repository: +1. Push your changes to the repository: ```bash git push -u origin ``` - `-u` sets the upstream, linking your local branch to the remote branch -- `origin` specifies your forked repository as the destination +- `origin` specifies the project repository as the destination - `` is the name of your local branch -2. Ensure the push is successful and your changes appear in your forked repository on Codeberg. +2. Ensure the push is successful and your changes appear in the repository on NHCarrigan's Git instance. -### 6.2 Creating the Pull Request +### 6.2. Creating the Pull Request -1. Navigate to your forked repository on Codeberg. +1. Navigate to the repository on NHCarrigan's Git instance. 2. You should see a prompt to create a pull request for your recently pushed branch. If not, click on the "Pull requests" tab and then the "New pull request" button. 3. Ensure the base repository is the original project repository and the base branch is `main`. -4. Select your fork as the head repository and your recently pushed branch as the compare branch. +4. Select the project as the head repository and your recently pushed branch as the compare branch. -### 6.3 Filling Out the Pull Request +### 6.3. Filling Out the Pull Request 1. Change the title of your pull request to be a conventional commit message summarising all changes in that PR 2. Fill out the pull request description with as much information as possible. This typically includes: @@ -392,24 +367,24 @@ git push -u origin 3. Fill out the rest of the pull request form *completely*. 4. If your changes include visual elements, consider adding screenshots or GIFs to illustrate the modifications. -### 6.4 Pull Request Best Practices +### 6.4. Pull Request Best Practices - Ensure your PR addresses only one issue or adds one feature. If you have made multiple unrelated changes, consider breaking them into separate pull requests. - Double-check that all tests pass and there are no conflicts with the base branch. - If your PR is a work in progress, mark it as a draft pull request. -### 6.5 After Submitting +### 6.5. After Submitting - Keep an eye on your pull request for any comments, requests for changes, or approval. - Be prepared to make additional commits to your branch if changes are requested. -### 6.6 Updating Your Pull Request +### 6.6. Updating Your Pull Request If you need to make changes to your pull request: 1. Make the required changes in your local branch. 2. Commit the changes. -3. Push the new commits to your fork: +3. Push the new commits to your branch: ```bash git push origin @@ -417,28 +392,28 @@ If you need to make changes to your pull request: 4. The pull request will automatically update with your new commits. -### 6.7 Pull Request Etiquette +### 6.7. Pull Request Etiquette - Be patient. Maintainers are often managing multiple priorities. - Be open to feedback and willing to make changes. - Respond promptly to any questions or requests from reviewers. - If there's a delay in your ability to respond or make requested changes, leave a comment explaining the situation. -### 6.8 Merging and Closing +### 6.8. Merging and Closing - Once your pull request is approved, a maintainer will merge it into the main project. -- After merging, you can delete your branch from your fork if you won't be using it anymore. +- After merging, you can delete your branch from the repository if you won't be using it anymore. - Celebrate your contribution to the project! -## 7. Pull Request Reviews +## 7. PULL REQUEST REVIEWS -### 7.1 Review Process Overview +### 7.1. Review Process Overview - All pull requests require at least one approved review before merging. - Reviews are primarily conducted by Naomi, but some projects may have additional reviewers. - The review process helps maintain code quality, consistency, and project standards. -### 7.2 What Reviewers Look For +### 7.2. What Reviewers Look For Reviewers typically assess the following aspects: @@ -449,13 +424,13 @@ Reviewers typically assess the following aspects: 5. Adherence to project-specific guidelines 6. Potential impact on existing features or performance -### 7.3 Types of Review Outcomes +### 7.3. Types of Review Outcomes 1. **Approved**: Your pull request is ready to be merged. 2. **Changes Requested**: Modifications or additional information is needed before approval. 3. **Commented**: The reviewer has provided feedback but hasn't explicitly approved or requested changes. -### 7.4 Responding to Review Feedback +### 7.4. Responding to Review Feedback If changes are requested: @@ -465,31 +440,31 @@ If changes are requested: 4. Commit and push the changes to update your pull request. 5. Respond to each comment, explaining how you addressed the feedback or why you chose a different approach. -### 7.5 Best Practices for Handling Reviews +### 7.5. Best Practices for Handling Reviews - Respond promptly to review comments (ideally within a few days). - Be open to constructive criticism and willing to make changes. - If you disagree with a suggestion, explain your reasoning politely and be open to discussion. - Use the review process as a learning opportunity to improve your coding skills. -### 7.6 Timelines and Expectations +### 7.6. Timelines and Expectations - We strive to review pull requests as quickly as possible, typically within a week. - If your pull request requires changes, please address them promptly. - Pull requests with outstanding change requests and no activity for a week may be closed as stale. - If you need more time to address changes, communicate this in the pull request comments to prevent your contribution from being closed. -### 7.7 Multiple Iterations +### 7.7. Multiple Iterations - Complex changes may require multiple rounds of reviews and revisions. - Stay engaged throughout the process and be patient if additional iterations are needed. -### 7.8 Learning from the Review Process +### 7.8. Learning from the Review Process - Take note of common feedback to improve future contributions. - Consider reviewing other pull requests to gain insights into the project's standards and practices. -### 7.9 After Approval +### 7.9. After Approval Once your pull request is approved: @@ -498,11 +473,11 @@ Once your pull request is approved: Thank you for providing that section. I'll expand and improve it to make it more comprehensive and encourage a wider range of contributions. Here's an enhanced version: -## 8. Other Contributions +## 8. OTHER CONTRIBUTIONS We value all types of contributions, not just code. There are many ways to contribute to our project, regardless of your technical experience or comfort level with the codebase. Here are several ways you can make a meaningful impact: -### 8.1 Documentation Updates +### 8.1. Documentation Updates Clear and accurate documentation is crucial for any project. You can help by: @@ -511,7 +486,7 @@ Clear and accurate documentation is crucial for any project. You can help by: - Creating new documentation for undocumented features - Improving README files, API documentation, or user guides -### 8.2 Feature Requests +### 8.2. Feature Requests Your ideas can help shape the future of the project. To suggest a new feature: @@ -523,17 +498,17 @@ Your ideas can help shape the future of the project. To suggest a new feature: Consider discussing your idea in our community chat before creating an issue to gather initial feedback. ::: -### 8.3 Bug Reports +### 8.3. Bug Reports Identifying and reporting bugs is a valuable contribution. When reporting a bug: 1. Search existing issues to avoid duplicates 1. Provide a clear, concise description of the problem 1. Include steps to reproduce the bug -1. Describe the expected behavior and what actually happened +1. Describe the expected behaviour and what actually happened 1. If possible, include screenshots, error messages, or code samples -### 8.4 User Support +### 8.4. User Support Helping other users is a great way to contribute to the community: @@ -542,7 +517,7 @@ Helping other users is a great way to contribute to the community: - Guide new users through common issues or setup processes - Create tutorials or blog posts about using the project -### 8.5 Design Contributions +### 8.5. Design Contributions If you have design skills, you can contribute by: @@ -551,7 +526,7 @@ If you have design skills, you can contribute by: - Improving the overall user experience and accessibility - Creating infographics or visual aids for documentation -### 8.6 Testing and Quality Assurance +### 8.6. Testing and Quality Assurance Help improve the project's stability by: @@ -560,7 +535,7 @@ Help improve the project's stability by: - Writing or improving automated tests - Identifying edge cases or potential security issues -### 8.7 Community Building +### 8.7. Community Building Foster a welcoming and inclusive community by: @@ -569,7 +544,7 @@ Foster a welcoming and inclusive community by: - Promoting the project on social media or relevant forums - Helping to moderate community discussions -### 8.8 Internationalization and Localization +### 8.8. Internationalization and Localization Make the project accessible to a global audience: @@ -577,7 +552,7 @@ Make the project accessible to a global audience: - Provide localized documentation - Ensure the project supports multiple languages and cultures -### 8.9 Code Reviews +### 8.9. Code Reviews Even if you're not comfortable making code changes, you can: @@ -585,7 +560,7 @@ Even if you're not comfortable making code changes, you can: - Provide feedback on proposed features or bug fixes - Help ensure code style and convention consistency -### 8.10 Fundraising and Sponsorship +### 8.10. Fundraising and Sponsorship If you have connections or experience in this area: @@ -595,12 +570,46 @@ If you have connections or experience in this area: Or even make a donation yourself! -### 8.11 Mentoring +### 8.11. Mentoring Share your knowledge and experience: - Mentor new contributors - Create learning resources for the project -- Participate in or organize coding workshops related to the project +- Participate in or organise coding workshops related to the project Remember, all contributions, big or small, are valuable to the project. Don't hesitate to get involved in any way you feel comfortable. If you have any questions about how to contribute or need help getting started, please reach out to us in our Discord server or through the project's communication channels. + +## 9. LIMITATION OF LIABILITY AND DISCLAIMERS + +### 9.1. Reference to Comprehensive Liability Framework + +**IMPORTANT: Comprehensive liability limitations, damage exclusions, and maximum liability caps are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.** + +### 9.2. Contribution Guidelines Disclaimer + +These Guidelines establish mandatory requirements for contributions. However, compliance with these Guidelines does not guarantee acceptance of contributions. Project maintainers reserve the right to: + +- Reject contributions that comply with these Guidelines for other valid reasons +- Request modifications beyond the scope of these Guidelines +- Modify or update these Guidelines at any time without prior notice +- Interpret Guideline requirements in specific contexts as necessary + +### 9.3. Technical Accuracy Disclaimer + +While we strive to maintain accurate and current information in these Guidelines, technical standards, tooling, and best practices evolve continuously. Contributors are responsible for: + +- Verifying current tool versions and compatibility +- Ensuring their development environment matches project requirements +- Adapting to updates in these Guidelines as they are published +- Consulting project-specific documentation for additional requirements + +## 10. CONCLUSION + +These Contributing Guidelines represent our commitment to maintaining high-quality, consistent, and legally compliant contributions across all projects. By adhering to these standards, contributors help ensure that our projects remain accessible, professional, and aligned with our organisational values and legal obligations. + +All contributors are expected to familiarise themselves with and comply with the requirements set forth in these Guidelines. Questions about specific requirements or requests for clarification should be directed to project maintainers through appropriate communication channels. + +--- + +*For questions about contribution requirements or to suggest improvements, please contact project maintainers through the designated channels outlined in our Contributor Covenant.* diff --git a/src/content/docs/dev/covenant.md b/src/content/docs/dev/covenant.md index 3394320..3f17fe3 100644 --- a/src/content/docs/dev/covenant.md +++ b/src/content/docs/dev/covenant.md @@ -2,12 +2,12 @@ title: Contributor Covenant --- -Copyright (C) 2024 nhcarrigan and its contributors. +Copyright (C) 2024 NHCarrigan and its contributors. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. -## nhcarrigan Contributor Covenant 1.0 +## NHCarrigan Contributor Covenant 1.0 By making a contribution to this project I certify that: @@ -22,7 +22,7 @@ By making a contribution to this project I certify that: I have the right to submit any code, documentation, or other content under the project's designated license.
  • - If my contribution is based on previous work covered under an open source license, I have the right to submit that work with modifications under the project's license. + If my contribution is based on previous work covered under an open source licence, I have the right to submit that work with modifications under the project's license.
  • Any contribution provided to me by another person for submission to this project has been done so with certification of points a through d, and I have not modified it. @@ -31,12 +31,12 @@ By making a contribution to this project I certify that: I understand that my contributions may be logged publicly, and that moderation actions taken in response to Code of Conduct violations may be recorded in the community's public moderation log.
  • - I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved. + I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it) is maintained indefinitely and may be redistributed consistent with this project or the open source licence(s) involved.
  • I acknowledge that community leaders have the right and responsibility to remove, edit, or reject my contributions if they do not align with this certificate or the project's Code of Conduct.
  • - I agree to release my contribution to nhcarrigan pursuant to the Terms of Service. + I agree to release my contribution to NHCarrigan pursuant to the Terms of Service.
    • diff --git a/src/content/docs/dev/environment.md b/src/content/docs/dev/environment.md index 95b2834..1748a41 100644 --- a/src/content/docs/dev/environment.md +++ b/src/content/docs/dev/environment.md @@ -2,13 +2,34 @@ title: Development Environment --- -This page documents Naomi's local development environment. The information here is provided to allow contributors to mirror the environment as closely as possible, ensuring the smoothest developer experience. +**DOCUMENTING DEVELOPMENT ENVIRONMENT SPECIFICATIONS AND CONFIGURATION REQUIREMENTS** -## 1. System Information +## 1. INTRODUCTION AND LEGAL FRAMEWORK -Naomi's local environment runs on the Arch Linux kernel. +### 1.1. Policy Overview -### 1.1. `hyfetch` +This Development Environment Documentation (hereinafter referred to as "the Documentation") provides technical specifications, configuration details, and environment setup information for development work on projects maintained by our organisation. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Contributor Covenant, and all applicable legal protections by reference. + +### 1.2. Purpose and Scope + +This Documentation describes the primary development environment used by our organisation's lead developer. While contributors are not required to replicate this exact environment, this information is provided to facilitate: + +- Understanding of the development context and tooling preferences +- Troubleshooting compatibility issues +- Achieving similar development experiences +- Ensuring consistency in development practices + +**IMPORTANT: This Documentation is provided for informational purposes. Contributors may use any development environment that meets project requirements. Our organisation does not endorse or require specific tools, operating systems, or configurations beyond those necessary for project functionality.** + +### 1.3. Disclaimer + +The information contained in this Documentation reflects the personal preferences and configurations of individual developers. These configurations are not mandatory requirements for contributions. Our organisation does not guarantee that replicating these configurations will result in identical development experiences. + +## 2. SYSTEM INFORMATION + +The primary development environment runs on the Arch Linux kernel. + +### 2.1. Hyfetch Diagnostic Report This is the current diagnostic report from `hyfetch`. @@ -75,11 +96,11 @@ Editor: Emacs 30.2 └─Nano: 8.5 ``` -## 2. Packages +## 3. PACKAGES Naomi uses the following packages. -### 2.1. Foreign Packages +### 3.1. Foreign Packages These packages come from unofficial repositories, such as the AUR. This list is generated with `yay -Qm`. @@ -151,7 +172,7 @@ yay-debug 12.5.0-1 -### 2.2. Explicit Installations +### 3.2. Explicit Installations These are all of the packages Naomi has specifically installed. This list is generated with `yay -Qe`. @@ -345,7 +366,7 @@ zram-generator 1.2.1-1 -### 2.3. Pinned Packages +### 3.3. Pinned Packages These packages have updates ignored, due to incompatibility issues. This list is generated with `grep "^IgnorePkg" /etc/pacman.conf`. @@ -353,7 +374,7 @@ These packages have updates ignored, due to incompatibility issues. This list is IgnorePkg = sway ``` -### 2.4. All Packages +### 3.4. All Packages This is a complete list of all packages on the machine. This list is generated with `yay -Q`. @@ -1857,11 +1878,11 @@ zziplib 0.13.80-1 -## 3. Configuration +## 4. CONFIGURATION Naomi's specific application configurations are noted here for posterity. -### 3.1. `git` +### 4.1. Git Configuration The most important thing to note is that Naomi signs her commits with her SSH key, not a GPG key. @@ -1886,7 +1907,7 @@ The most important thing to note is that Naomi signs her commits with her SSH ke helper = store ``` -### 3.2. `zsh` +### 4.2. Zsh Configuration Naomi uses Oh My ZSH instead of bash. @@ -1997,7 +2018,7 @@ eval "$(starship init zsh)" source <(ng completion script) ``` -#### 3.2.1. `starship` +#### 4.2.1. Starship Configuration Naomi uses `starship` to manage her customised shell prompt. @@ -2106,7 +2127,7 @@ command = "mommy -1 -s $status" when = true ``` -### 3.3. `pacman` +### 4.3. Pacman Configuration Naomi's package manager configuration. @@ -2135,7 +2156,7 @@ Include = /etc/pacman.d/chaotic-mirrorlist Include = /etc/pacman.d/mirrorlist ``` -### 3.4 `sway` +### 4.4. Sway Configuration ```ini frame="code" title="~/.config/sway/config" set $mod Mod4 @@ -2280,7 +2301,7 @@ bar { } ``` -#### 3.4.1. `swaylock` +#### 4.4.1. Swaylock Configuration ```ini frame="code" title="~/.config/swaylock/config" # Background image @@ -2296,7 +2317,7 @@ fade-in=0.2 effect-blur=8x2 effect-vignette=0.5:0.5 -# Ring customization +# Ring customisation indicator-radius=120 indicator-thickness=20 indicator-idle-visible @@ -2332,12 +2353,12 @@ text-clear-color=abfcec text-ver-color=abfcec text-wrong-color=abfcec -# Text customization +# Text customisation font=OpenDyslexicMono font-size=24 ``` -### 3.5 Waybar +### 4.5. Waybar Configuration These manage Naomi's waybar instance. @@ -2714,7 +2735,7 @@ echo "{\"text\":\"${text}\", \"tooltip\":\"${tooltip}\"}"; #!/usr/bin/env sh model=$(cat /proc/cpuinfo | grep 'model name' | head -n 1 | awk -F ': ' '{print $2}') -utilization=$(top -bn1 | awk '/^%Cpu/ {print 100 - $8}') +utilisation=$(top -bn1 | awk '/^%Cpu/ {print 100 - $8}') freqlist=$(cat /proc/cpuinfo | grep "cpu MHz" | awk '{ print $4 }') maxfreq=$(cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq | sed 's/...$//') frequency=$(echo $freqlist | tr ' ' '\n' | awk "{ sum+=\$1 } END {printf \"%.0f/$maxfreq MHz\", sum/NR}") @@ -2731,8 +2752,8 @@ eval_ico() { echo "${set_ico}" | jq -r --arg aky "$1" --arg avl "$map_ico" '.[$aky] | .[$avl]' } thermo=$(eval_ico thermo $temp) -speedo=$(eval_ico util $utilization) -echo "{\"text\":\"${thermo} ${temp}°C\", \"tooltip\":\"${model}\n${thermo} Temperature: ${temp}°C\n${speedo} Utilization: ${utilization}%\n󰘚 Clock Speed: ${frequency}\"}" +speedo=$(eval_ico util $utilisation) +echo "{\"text\":\"${thermo} ${temp}°C\", \"tooltip\":\"${model}\n${thermo} Temperature: ${temp}°C\n${speedo} Utilization: ${utilisation}%\n󰘚 Clock Speed: ${frequency}\"}" ``` @@ -2886,7 +2907,7 @@ echo "{\"text\": \"${icon} ${ssid}\", \"tooltip\": \"${tooltip}\"}" -### 3.6 Ghostty +### 4.6. Ghostty Configuration ```ini frame="code" title="~/.config/ghostty/config" font-family="OpenDyslexicM Nerd Font" @@ -2922,7 +2943,7 @@ cursor-color = #ff3b6f cursor-text = #ffe6ee ``` -### 3.7 Discord +### 4.7. Discord Configuration ```json frame="code" title="~/.config/discord/settings.json" { @@ -2941,7 +2962,7 @@ cursor-text = #ffe6ee } ``` -### 3.8 Hyfetch +### 4.8. Hyfetch Configuration There are two config files here. @@ -3093,7 +3114,7 @@ background_color= stdout="off" ``` -### 3.9 Wofi +### 4.9. Wofi Configuration ```css frame="code" title="~/.config/wofi/style.css" #window { @@ -3146,7 +3167,7 @@ stdout="off" } ``` -### 3.10 Dunst +### 4.10. Dunst Configuration `dunst` manages Naomi's system notifications, and (like many other aspects of her environment) has been highly customised. @@ -3177,15 +3198,15 @@ stdout="off" frame_color="#ffefef" ``` -## 4. Code Editors +## 5. CODE EDITORS These are the code editors Naomi uses. -### 4.1. Emacs +### 5.1. Emacs Configuration Naomi uses `emacs` for her main editor. -#### 4.1.1. Config +#### 5.1.1. Emacs Configuration File ```lisp frame="code" title="~/.emacs" (setq inhibit-startup-message t ; Don't show the splash screen @@ -3243,7 +3264,7 @@ Naomi uses `emacs` for her main editor. (set-face-background 'line-number-current-line nil) (set-face-foreground 'line-number-current-line "yellow") -;; Optional: Customize line number format +;; Optional: Customise line number format (setq display-line-numbers-width 4) ; Reserve space for line numbers (setq display-line-numbers-widen t) ; Expand line number space as needed @@ -3394,3 +3415,46 @@ Naomi uses `emacs` for her main editor. ;; If there is more than one, they won't work right. ) ``` + +## 6. LIMITATION OF LIABILITY AND DISCLAIMERS + +### 6.1. Reference to Comprehensive Liability Framework + +**IMPORTANT: Comprehensive liability limitations, damage exclusions, and maximum liability caps are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.** + +### 6.2. Development Environment Disclaimer + +This Documentation is provided for informational purposes only. Our organisation: + +- Does not require contributors to replicate this exact development environment +- Does not guarantee that replicating these configurations will result in identical development experiences +- Does not provide technical support for setting up or maintaining these configurations +- Reserves the right to modify or update this Documentation at any time without prior notice + +### 6.3. Technical Accuracy Disclaimer + +While we strive to maintain accurate and current information in this Documentation, technical specifications, software versions, and configuration details change frequently. Contributors are responsible for: + +- Verifying current software versions and compatibility +- Adapting configurations to their specific system requirements +- Ensuring their development environment meets project requirements +- Consulting project-specific documentation for additional requirements + +### 6.4. Third-Party Tools and Services + +This Documentation references various third-party tools, services, and software packages. Our organisation: + +- Does not endorse or guarantee the functionality, security, or availability of third-party tools +- Is not responsible for issues arising from the use of third-party tools or services +- Does not provide support for third-party tools beyond what is necessary for project functionality +- Recommends that contributors review third-party licenses, terms of service, and privacy policies + +## 7. CONCLUSION + +This Development Environment Documentation provides comprehensive information about the primary development environment used within our organisation. While contributors are not required to replicate this exact environment, this information serves as a valuable reference for understanding our development context, tooling preferences, and configuration standards. + +All contributors are encouraged to use development environments that meet project requirements and align with their personal preferences and constraints. Questions about development environment setup or compatibility should be directed to project maintainers through appropriate communication channels. + +--- + +*For questions about development environment requirements or to suggest improvements, please contact project maintainers through the designated channels outlined in our Contributor Covenant.* diff --git a/src/content/docs/dev/labels.md b/src/content/docs/dev/labels.md index d8a58c8..4880c69 100644 --- a/src/content/docs/dev/labels.md +++ b/src/content/docs/dev/labels.md @@ -50,7 +50,7 @@ Requires access to production infrastructure for proper testing and implementati Staff members working on these issues must adhere to all relevant confidentiality agreements, data protection policies, and internal security protocols. -### 1.4 Disclaimer +### 1.4. Disclaimer Labels are assigned based on the project maintainers' best judgement but may not guarantee the exact level of difficulty or access requirements for every contributor. Contributors should use their discretion and communicate with project maintainers if they have any doubts about their ability to address an issue or comply with any associated legal requirements. @@ -114,7 +114,7 @@ Typically does not require code changes. Proficiency in technical writing is a m Contributors must ensure the accuracy of the information provided in documentation updates. Documentation changes should adhere to any applicable style guides and licensing terms. -### 2.5 Disclaimer +### 2.5. Disclaimer Aspect labels are assigned based on the primary focus of the issue but may not encompass all potential areas of impact. Contributors are encouraged to consider potential cross-aspect effects of their work and discuss these with project maintainers when in doubt. The project maintainers reserve the right to reassign aspect labels or request additional changes if the submitted work does not align with the intended scope of the issue. @@ -212,7 +212,7 @@ Important for project improvement but not critical for current functionality. Sh #### 4.3.3. Expectations -May involve improvements to user experience or accessibility, which could have legal implications if neglected long-term. Could relate to optimizations that affect performance guarantees or service level agreements. +May involve improvements to user experience or accessibility, which could have legal implications if neglected long-term. Could relate to optimisations that affect performance guarantees or service level agreements. ### 4.4. `priority: low` @@ -240,9 +240,9 @@ Not critical enough to dedicate maintainer time for resolution. Often left for c #### 4.5.3. Expectations -While not prioritized, maintainers should periodically review these issues to ensure they haven't become more significant over time, potentially accruing legal or compliance risks. +While not prioritised, maintainers should periodically review these issues to ensure they haven't become more significant over time, potentially accruing legal or compliance risks. -### 4.6 Disclaimer +### 4.6. Disclaimer Priority labels reflect the project maintainers' current assessment and may be subject to change. The presence of a lower-priority label does not diminish the importance of the issue or the value of contributions addressing it. Contributors should communicate with maintainers if they believe an issue's priority should be reassessed due to new information or changing circumstances. @@ -310,7 +310,7 @@ Clearly communicate the project's maintenance status to manage user expectations #### 5.5.1. Purpose -Indicates issues that need proper labeling and categorization. +Indicates issues that need proper labelling and categorisation. #### 5.5.2. Characteristics @@ -318,7 +318,7 @@ May have ongoing discussions but lack appropriate classification. #### 5.5.3. Expectations -Proper labeling is crucial for efficient project management and may have implications for compliance tracking and reporting. Establish clear guidelines for labeling to ensure consistency and avoid potential misunderstandings. +Proper labelling is crucial for efficient project management and may have implications for compliance tracking and reporting. Establish clear guidelines for labelling to ensure consistency and avoid potential misunderstandings. ### 5.6. `status: ready for dev` @@ -414,7 +414,7 @@ Signifies that the pull request is not in draft mode and is awaiting maintainer #### 7.2.2. Characteristics -PR has been submitted as complete and ready for evaluation. Maintainers should prioritize reviewing these PRs. +PR has been submitted as complete and ready for evaluation. Maintainers should prioritise reviewing these PRs. #### 7.2.3. Expectations @@ -440,7 +440,7 @@ The presence of these labels does not guarantee that a pull request will be merg ## 8. Continuous Improvement -We encourage all project participants to provide feedback on our labeling system. If you have suggestions for improvements or notice any inconsistencies, please reach out to us in our [forums](https://forum.nhcarrigan.com). +We encourage all project participants to provide feedback on our labelling system. If you have suggestions for improvements or notice any inconsistencies, please reach out to us in our [Discord community](https://chat.nhcarrigan.com). ## 9. Legal Notice diff --git a/src/content/docs/dev/servers.md b/src/content/docs/dev/servers.md index 395410f..d496d10 100644 --- a/src/content/docs/dev/servers.md +++ b/src/content/docs/dev/servers.md @@ -2,17 +2,37 @@ title: Server Setup --- -This document outlines how we set up our remote servers for running projects. +**ESTABLISHING SERVER CONFIGURATION STANDARDS AND SECURITY REQUIREMENTS** -## 1. Provision a Server +## 1. INTRODUCTION AND LEGAL FRAMEWORK + +### 1.1. Policy Overview + +This Server Setup Documentation (hereinafter referred to as "the Documentation") establishes mandatory standards, procedures, and security requirements for configuring remote servers used to host projects maintained by our organisation. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Security Policy, and all applicable legal protections by reference. + +### 1.2. Scope and Applicability + +This Documentation applies to all remote servers used to host projects, services, or infrastructure maintained by our organisation. All personnel responsible for server configuration, deployment, or maintenance must comply with the standards set forth in this Documentation. + +**IMPORTANT: Non-compliance with server security and configuration standards set forth in this Documentation may result in security vulnerabilities, service disruptions, or other serious consequences. All server administrators must strictly adhere to these requirements.** + +### 1.3. Security and Compliance Requirements + +Server configuration must comply with: +- Our Security Policy and security standards +- Applicable data protection and privacy regulations +- Industry best practices for server security +- All relevant legal and regulatory requirements + +## 2. PROVISIONING A SERVER We use DigitalOcean as our provider. Regardless of your choice, provision a new VPS using the **latest Ubuntu LTS version**. Add your `ssh` key AND Naomi's `ssh` key in the setup process. -## 2. Set Up User +## 3. SETTING UP USER ACCOUNTS You should never run applications on root. SSH into the new VPS to prepare your user. -### 2.1. Creating the User +### 3.1. Creating the User Account You'll need to set a password for the `root` account first. @@ -22,10 +42,10 @@ passwd Once you have set a password, ensure that you have provided it to Naomi to store in the vault. -Create an `nhcarrigan` user for our organisation. +Create an `NHCarrigan` user for our organisation. ```bash -adduser nhcarrigan +adduser NHCarrigan ``` Set a **different** password, and provide that to Naomi as well. For all of the user information, use the default blank values. @@ -33,13 +53,13 @@ Set a **different** password, and provide that to Naomi as well. For all of the Add the new user to the sudoers file. ```bash -usermod -aG sudo nhcarrigan +usermod -aG sudo NHCarrigan ``` Then sync the SSH keys so we can authenticate as that user. ```bash -rsync --archive --chown=nhcarrigan:nhcarrigan ~/.ssh /home/nhcarrigan +rsync --archive --chown=NHCarrigan:NHCarrigan ~/.ssh /home/NHCarrigan ``` While you are there, set the timezone for the server to our business' local timezone. @@ -48,11 +68,11 @@ While you are there, set the timezone for the server to our business' local time sudo timedatectl set-timezone America/Los_Angeles ``` -## 3. Preparing For Web Requests +## 4. PREPARING FOR WEB REQUESTS To prepare the server to receive web requests, you'll need to follow a few steps. -### 3.1. SSL Certificate +### 4.1. SSL Certificate Configuration :::note If the Firewall has been set up, you'll need to temporarily allow port 80 for the certificate to generate. @@ -88,7 +108,7 @@ When you need to renew the certificate: sudo certbot renew ``` -### 3.2. NGINX +### 4.2. NGINX Configuration All requests should be routed through NGINX. At no point should an application run directly on ports 80 or 443. @@ -133,11 +153,11 @@ If so, restart NGINX to apply the changes: sudo systemctl restart nginx ``` -## 4. Securing the Server +## 5. SECURING THE SERVER We have a minimum level of security that is required on ALL of our servers. This section should not be treated as the best effort, but as the minimal requirements to comply with our policies. -### 4.1. Firewall +### 5.1. Firewall Configuration We use `ufw` as our firewall. First, enable the SSH port. @@ -158,7 +178,7 @@ Enable the firewall. You may get dropped from the SSH connection. sudo ufw enable ``` -### 4.2. Fail2Ban +### 5.2. Fail2Ban Configuration We also use Fail2Ban to block IP addresses which fail to make requests too often. @@ -289,7 +309,7 @@ And to unban them: sudo fail2ban-client set nginx-auth unbanip ``` -## 5. Uploading a Project +## 6. UPLOADING PROJECTS To upload a project, you should **not** use `git` to clone the project to the machine. Instead, start by cloning the project to your local environment and navigating to the directory: @@ -301,14 +321,14 @@ cd /path/to/project Then sync the project up to the machine, ignoring any installed packages. ```bash -rsync -av --exclude='node_modules' ./ :/home/nhcarrigan/ +rsync -av --exclude='node_modules' ./ :/home/NHCarrigan/ ``` -## 6. Running a Project +## 7. RUNNING PROJECTS Now you are ready to start running the project. -### 6.1. Node.js +### 7.1. Node.js Setup Most of our projects will run on Node. For a new machine, you'll need to set that up. @@ -338,7 +358,7 @@ Finally, install `pnpm` as the package manager. npm i -g pnpm ``` -### 6.2. PM2 +### 7.2. PM2 Process Management All of our processes run with PM2 to allow for monitoring and auto-restarts. You'll need to install it. @@ -353,3 +373,56 @@ pm2 start '