From 322ca87960487f7e287511c3d208e9686d37e43f Mon Sep 17 00:00:00 2001 From: Serhii Horodilov Date: Tue, 20 Jan 2026 00:06:22 +0200 Subject: [PATCH 1/5] docs(coc): Remove outdated reporting option for clarity Remove reference to the confidential issue reporting option in the Code of Conduct as this repository does not currently support such functionality. This simplifies the document and avoids confusion regarding the available reporting methods. This update ensures the reporting section remains accurate and aligned with current community practices. --- docs/CODE_OF_CONDUCT.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/CODE_OF_CONDUCT.md b/docs/CODE_OF_CONDUCT.md index 72cf5bf..98eb24c 100644 --- a/docs/CODE_OF_CONDUCT.md +++ b/docs/CODE_OF_CONDUCT.md @@ -281,8 +281,6 @@ please report it as soon as possible. You can report violations by: - Contacting the community manager directly at: [todo: add email] -- Opening a confidential issue in our dedicated reporting repository (if - available) **What to Include in Your Report:** From 60fac1cd8950fe30f15b9b48da94412e9a15ba30 Mon Sep 17 00:00:00 2001 From: Serhii Horodilov Date: Tue, 20 Jan 2026 22:36:01 +0200 Subject: [PATCH 2/5] docs: Update organization references to OpenRoost Replace all references to "DevsForge" with "OpenRoost" across the Code of Conduct, Security Policy, and Support Guidelines documentation. This change ensures consistency with the project's updated branding and reinforces accurate representation across community-facing documents. --- docs/CODE_OF_CONDUCT.md | 20 ++++++++++---------- docs/SECURITY.md | 6 +++--- docs/SUPPORT.md | 12 ++++++------ 3 files changed, 19 insertions(+), 19 deletions(-) diff --git a/docs/CODE_OF_CONDUCT.md b/docs/CODE_OF_CONDUCT.md index 98eb24c..57147bb 100644 --- a/docs/CODE_OF_CONDUCT.md +++ b/docs/CODE_OF_CONDUCT.md @@ -19,7 +19,7 @@ owner: /orgs/devsforge/teams/community @community ## Our Stance on the War in :ukraine:Ukraine -DevsForge stands with Ukraine and the Ukrainian people in the ongoing war of +OpenRoost stands with Ukraine and the Ukrainian people in the ongoing war of aggression by the Russian Federation. We condemn this illegal invasion and the humanitarian crisis it has caused. @@ -42,7 +42,7 @@ humanitarian efforts: ## Our Pledge -We, the members, contributors, and maintainers of DevsForge, pledge to make +We, the members, contributors, and maintainers of OpenRoost, pledge to make participation in our community a welcoming, respectful, and harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, @@ -59,7 +59,7 @@ transparent, and engaged community. ## Our Values -At DevsForge, our community is guided by these core values: +At OpenRoost, our community is guided by these core values: **:earth_africa: Inclusivity** We believe in creating opportunities for everyone. Our community welcomes @@ -95,15 +95,15 @@ work while remaining humble and open to improvement. ## Scope -This Code of Conduct applies to all DevsForge community spaces, including but +This Code of Conduct applies to all OpenRoost community spaces, including but not limited to: - GitHub repositories (issues, pull requests, discussions, code reviews) - Official communication channels (if applicable: Discord, Slack, mailing lists, forums) - Community events (online and in-person meetups, conferences, workshops) -- Social media interactions where you represent DevsForge -- Any other spaces where you act as a representative of the DevsForge community +- Social media interactions where you represent OpenRoost +- Any other spaces where you act as a representative of the OpenRoost community This Code of Conduct also applies when an individual is officially representing the community in public spaces. Examples of representing our community include @@ -116,7 +116,7 @@ or acting as an appointed representative at an online or offline event. - Contributors - Maintainers - Partners -- Anyone interacting with DevsForge projects and community spaces +- Anyone interacting with OpenRoost projects and community spaces This Code of Conduct applies equally to all community members, regardless of their level of contribution or standing within the community. @@ -166,7 +166,7 @@ We encourage all community members to: - Promote inclusivity and accessibility in everything you do - Respect our stance on Ukraine and human rights - Contribute to a positive, transparent community environment -- Help make DevsForge a welcoming place for everyone +- Help make OpenRoost a welcoming place for everyone ## Unacceptable Behavior @@ -216,7 +216,7 @@ in our community: **Scope of Enforcement** -- These standards apply to all community spaces and when representing DevsForge +- These standards apply to all community spaces and when representing OpenRoost - Violations may result in consequences even if they occur in public spaces outside our direct control, if they negatively impact community safety @@ -344,6 +344,6 @@ This Code of Conduct is licensed under the [Creative Commons Attribution 4.0 International License][CC-BY-4.0]. You are free to adapt and use this Code of Conduct for your own community, with -attribution to DevsForge. +attribution to OpenRoost. [CC-BY-4.0]: https://creativecommons.org/licenses/by/4.0/ diff --git a/docs/SECURITY.md b/docs/SECURITY.md index 0605c5a..0f63073 100644 --- a/docs/SECURITY.md +++ b/docs/SECURITY.md @@ -82,12 +82,12 @@ discovery (unless you prefer to remain anonymous). ## Scope -This security policy applies to all repositories within the DevsForge +This security policy applies to all repositories within the OpenRoost organization, including both public and private repositories. ### In Scope -- Security vulnerabilities in DevsForge-maintained code +- Security vulnerabilities in OpenRoost-maintained code - Configuration issues that could lead to security exposure - Authentication and authorization flaws - Data exposure risks @@ -141,6 +141,6 @@ This Security Policy is licensed under the [Creative Commons Attribution 4.0 International License][CC-BY-4.0]. You are free to adapt and use this Security Policy for your own community, with -attribution to DevsForge. +attribution to OpenRoost. [CC-BY-4.0]: https://creativecommons.org/licenses/by/4.0/ diff --git a/docs/SUPPORT.md b/docs/SUPPORT.md index aaf893b..2b0b8dd 100644 --- a/docs/SUPPORT.md +++ b/docs/SUPPORT.md @@ -13,7 +13,7 @@ owner: /orgs/devsforge/teams/support @support | 0.2 | 2025-01-19 | Serhii Horodilov | Update Attribution section | | 0.1 | 2025-01-19 | Serhii Horodilov | Initial draft | -Welcome to DevsForge! This document outlines how to get help, ask questions, +Welcome to OpenRoost! This document outlines how to get help, ask questions, and connect with our community. We communicate in both English and Ukrainian. @@ -31,7 +31,7 @@ For general questions, ideas, and community conversations, please use This is our primary support channel and the best place to: -- Ask questions about DevsForge projects +- Ask questions about OpenRoost projects - Share ideas and suggestions - Connect with other community members - Seek guidance on developer growth and learning @@ -60,7 +60,7 @@ Instead, follow the process outlined in our [Security Policy](SECURITY.md). ### Technical Support -For technical questions related to DevsForge projects, tools, and +For technical questions related to OpenRoost projects, tools, and implementations, our support team is here to help. Responsible team: @support @@ -77,8 +77,8 @@ Responsible team: @community While we want to be as helpful as possible, some topics fall outside our support scope: -- Support for third-party tools or services not maintained by DevsForge -- General programming questions unrelated to DevsForge projects +- Support for third-party tools or services not maintained by OpenRoost +- General programming questions unrelated to OpenRoost projects - Requests that violate our [Code of Conduct](CODE_OF_CONDUCT.md) ## Resources @@ -98,6 +98,6 @@ This Support document is licensed under the [Creative Commons Attribution 4.0 International License][CC-BY-4.0]. You are free to adapt and use this document for your own community, with -attribution to DevsForge. +attribution to OpenRoost. [CC-BY-4.0]: https://creativecommons.org/licenses/by/4.0/ From 9eea464095635d1bc6adf34fed4886b6a7500c77 Mon Sep 17 00:00:00 2001 From: Serhii Horodilov Date: Tue, 20 Jan 2026 23:17:28 +0200 Subject: [PATCH 3/5] docs: Unify document metadata and streamline licenses Update badge references in CODE_OF_CONDUCT.md, SUPPORT.md, and SECURITY.md to utilize shared metadata variables for document status. Refactor attribution sections to consistently use the term "document" instead of individual file names. This change enhances consistency across documentation, simplifies badge management, and standardizes terminology in licensing details. --- docs/CODE_OF_CONDUCT.md | 16 +++++++++++----- docs/SECURITY.md | 18 ++++++++++++------ docs/SUPPORT.md | 10 ++++++++-- 3 files changed, 31 insertions(+), 13 deletions(-) diff --git a/docs/CODE_OF_CONDUCT.md b/docs/CODE_OF_CONDUCT.md index 57147bb..d394bb4 100644 --- a/docs/CODE_OF_CONDUCT.md +++ b/docs/CODE_OF_CONDUCT.md @@ -3,9 +3,13 @@ status: draft owner: /orgs/devsforge/teams/community @community --- +[draft]: https://img.shields.io/badge/document_status-draft-orange +[ready]: https://img.shields.io/badge/document_status-ready-cyan +[final]: https://img.shields.io/badge/document_status-final-blue + # Code of Conduct -![doc_status:draft](https://img.shields.io/badge/document_status-draft-red) +![document status][draft]
Document Changelog @@ -333,17 +337,19 @@ While we prefer to have contact information to follow up, you may submit anonymous reports. Please note that our ability to investigate and respond may be limited without the ability to ask follow-up questions. +--- + ## Attribution -This Code of Conduct is inspired by community best practices and open source +This Support document is inspired by community best practices and open source community standards. **License:** -This Code of Conduct is licensed under -the [Creative Commons Attribution 4.0 International License][CC-BY-4.0]. +This Support document is licensed under +[Creative Commons Attribution 4.0 International License][CC-BY-4.0]. -You are free to adapt and use this Code of Conduct for your own community, with +You are free to adapt and use this document for your own community, with attribution to OpenRoost. [CC-BY-4.0]: https://creativecommons.org/licenses/by/4.0/ diff --git a/docs/SECURITY.md b/docs/SECURITY.md index 0f63073..efe5952 100644 --- a/docs/SECURITY.md +++ b/docs/SECURITY.md @@ -3,9 +3,13 @@ status: draft owner: /orgs/devsforge/teams/security @security --- +[draft]: https://img.shields.io/badge/document_status-draft-orange +[ready]: https://img.shields.io/badge/document_status-ready-cyan +[final]: https://img.shields.io/badge/document_status-final-blue + # Security Policy -![status: draft](https://img.shields.io/badge/status-draft-red) +![document status][draft]
Document Changelog @@ -130,17 +134,19 @@ introduce: Security reports and incidents are handled by our dedicated security team. For general security inquiries, please use the channels listed above. +--- + ## Attribution -This Security Policy is inspired by community best practices and open source -security standards. +This Support document is inspired by community best practices and open source +community standards. **License:** -This Security Policy is licensed under -the [Creative Commons Attribution 4.0 International License][CC-BY-4.0]. +This Support document is licensed under +[Creative Commons Attribution 4.0 International License][CC-BY-4.0]. -You are free to adapt and use this Security Policy for your own community, with +You are free to adapt and use this document for your own community, with attribution to OpenRoost. [CC-BY-4.0]: https://creativecommons.org/licenses/by/4.0/ diff --git a/docs/SUPPORT.md b/docs/SUPPORT.md index 2b0b8dd..80ca299 100644 --- a/docs/SUPPORT.md +++ b/docs/SUPPORT.md @@ -3,9 +3,13 @@ status: draft owner: /orgs/devsforge/teams/support @support --- +[draft]: https://img.shields.io/badge/document_status-draft-orange +[ready]: https://img.shields.io/badge/document_status-ready-cyan +[final]: https://img.shields.io/badge/document_status-final-blue + # Support -![status: draft](https://img.shields.io/badge/status-draft-red) +![document status][draft] | Ver. | Date | Author | Change description | |------|------------|------------------|----------------------------| @@ -87,6 +91,8 @@ support scope: _Coming soon._ +--- + ## Attribution This Support document is inspired by community best practices and open source @@ -95,7 +101,7 @@ community standards. **License:** This Support document is licensed under -the [Creative Commons Attribution 4.0 International License][CC-BY-4.0]. +[Creative Commons Attribution 4.0 International License][CC-BY-4.0]. You are free to adapt and use this document for your own community, with attribution to OpenRoost. From 0379040b0e9622189cccd1e52b3598414d49b3b3 Mon Sep 17 00:00:00 2001 From: Serhii Horodilov Date: Tue, 20 Jan 2026 23:28:35 +0200 Subject: [PATCH 4/5] [Docs] Contributing Guide (v0.1) (#10) Introduce a draft version of the contributing guide to provide clear guidelines for community contributions. This document includes sections on reporting bugs, suggesting enhancements, creating pull requests, and adhering to the project's development process. Key additions: - Code of Conduct acknowledgment requirement for contributors. - Style guides for commit messages and documentation. - Bilingual communication guidelines (English and Ukrainian). This draft enhances contributor onboarding, fosters collaboration, and aligns with community best practices. --- docs/CONTRIBUTING.md | 132 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 132 insertions(+) create mode 100644 docs/CONTRIBUTING.md diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md new file mode 100644 index 0000000..1d1ce48 --- /dev/null +++ b/docs/CONTRIBUTING.md @@ -0,0 +1,132 @@ +--- +status: draft +owner: /orgs/devsforge/teams/maintainers @maintainers +--- + +# Contributing Guide + +![status: draft](https://img.shields.io/badge/status-draft-red) + +
+Document Changelog + +| Ver. | Date | Author | Change description | +|------|------------|------------------|--------------------| +| 0.1 | 2026-01-20 | Serhii Horodilov | Initial draft | + +
+ +## Welcome + +Thank you for your interest in contributing to OpenRoost! We welcome +contributions from everyone and appreciate your help in making our community +and software better. + +As a Ukrainian-based organization, we are committed to fostering growth and +showcasing talent within the Ukrainian tech community, while remaining open and +inclusive to contributors from all over the world. + +We communicate in both English and Ukrainian. Feel free to use either language +for your contributions, issues, and discussions. + +## Code of Conduct + +By participating in this project, you agree to abide by our +[Code of Conduct](CODE_OF_CONDUCT.md). Please read it to understand our values +and expectations for behavior within our community. + +## How Can I Contribute? + +### Reporting Bugs + +If you find a bug, please report it by opening an issue in the relevant +repository. Before reporting, please: + +- Search existing issues to see if the bug has already been reported. +- Use a clear and descriptive title. +- Follow the provided issue template, including steps to reproduce, expected + behavior, and actual behavior. + +### Suggesting Enhancements + +We welcome ideas for new features or improvements. To suggest an enhancement: + +- Check if the idea has already been proposed in issues or discussions. +- Open a new issue using the "Feature Request" template. +- Explain why this enhancement would be useful and how it should work. + +### Your First Code Contribution + +Not sure where to start? Look for issues labeled `good first issue` or +`help wanted`. These are specifically chosen for newcomers to the project. + +### Pull Requests + +To contribute code or documentation changes: + +1. **Fork** the repository and create your branch from `main`. +2. **Setup** your development environment according to the project's README. +3. **Commit** your changes using descriptive commit messages + (see Style Guides). +4. **Push** to your fork and submit a **Pull Request**. +5. **Wait** for a maintainer to review your PR. We may suggest changes or + improvements. + +All Pull Requests must include an acknowledgment of our Code of Conduct. + +## Development Process + +We follow a transparent development process. All work is tracked via GitHub +Issues and Project boards. + +- **Main Branch**: The `main` branch is the primary branch for development. +- **Code Reviews**: All PRs require at least one approval from a maintainer + before merging. +- **Testing**: Ensure that your changes do not break existing functionality. + Add new tests where appropriate. + +## Style Guides + +### Git Commit Messages + +- Use the present tense ("Add feature" not "Added feature"). +- Use the imperative mood ("Fix bug" not "Fixes bug"). +- Keep the subject line short (under 50 characters). +- Provide more detail in the body if necessary. + +### Documentation Style + +- Use clear, concise language. +- Follow Markdown best practices. +- For organization-wide documentation, we prefer a professional yet welcoming + tone. +- Where appropriate, use bilingual labels for clarity (e.g., ":gb: English / + :ukraine: Українська"). + +## Community + +Join our community to discuss projects, seek help, or share your growth +journey: + +- [GitHub Discussions](https://github.com/orgs/devsforge/discussions) +- [Support Guide](SUPPORT.md) + +## Recognition + +We value and recognize all contributions. Contributors will be credited in the +repository's README or a dedicated CONTRIBUTORS file. + +## Attribution + +This Contributing Guide is inspired by community best practices and open source +community standards. + +**License:** + +This Contributing Guide is licensed under the [Creative Commons Attribution 4.0 +International License][CC-BY-4.0]. + +You are free to adapt and use this guide for your own community, with +attribution to OpenRoost. + +[CC-BY-4.0]: https://creativecommons.org/licenses/by/4.0/ From 8e140b93152dd2a49f693db2f642cae590a11bd1 Mon Sep 17 00:00:00 2001 From: Serhii Horodilov Date: Tue, 20 Jan 2026 23:54:53 +0200 Subject: [PATCH 5/5] docs: Update document changelogs and streamline metadata Update changelogs in CODE_OF_CONDUCT.md, CONTRIBUTING.md, SUPPORT.md, and SECURITY.md to reflect versioning updates and history corrections. Unify badge references by adopting consistent metadata variables for document statuses, removing unused "ready" badge. This change ensures chronological accuracy, improves readability, and maintains consistency across documentation versions and metadata. --- docs/CODE_OF_CONDUCT.md | 10 +++++----- docs/CONTRIBUTING.md | 23 +++++++++++++++-------- docs/SECURITY.md | 12 ++++++------ docs/SUPPORT.md | 12 ++++++------ 4 files changed, 32 insertions(+), 25 deletions(-) diff --git a/docs/CODE_OF_CONDUCT.md b/docs/CODE_OF_CONDUCT.md index d394bb4..9c2e2c6 100644 --- a/docs/CODE_OF_CONDUCT.md +++ b/docs/CODE_OF_CONDUCT.md @@ -4,7 +4,6 @@ owner: /orgs/devsforge/teams/community @community --- [draft]: https://img.shields.io/badge/document_status-draft-orange -[ready]: https://img.shields.io/badge/document_status-ready-cyan [final]: https://img.shields.io/badge/document_status-final-blue # Code of Conduct @@ -14,10 +13,11 @@ owner: /orgs/devsforge/teams/community @community
Document Changelog -| Ver. | Date | Author | Change description | -|------|------------|------------------|--------------------| -| 0.9 | 2025-01-19 | Serhii Horodilov | Final draft | -| 0.1 | 2025-01-10 | Serhii Horodilov | Initial draft | +| ver. | Date | Author | Change description | +|------|------------|------------------|-------------------------------| +| 0.9 | 2025-01-20 | Serhii Horodilov | Final draft | +| 0.2 | 2026-01-20 | Serhii Horodilov | Utilize community health docs | +| 0.1 | 2025-01-10 | Serhii Horodilov | Initial draft |
diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md index 1d1ce48..7521cdc 100644 --- a/docs/CONTRIBUTING.md +++ b/docs/CONTRIBUTING.md @@ -3,16 +3,21 @@ status: draft owner: /orgs/devsforge/teams/maintainers @maintainers --- +[draft]: https://img.shields.io/badge/document_status-draft-orange +[final]: https://img.shields.io/badge/document_status-final-blue + # Contributing Guide -![status: draft](https://img.shields.io/badge/status-draft-red) +![document status][draft]
Document Changelog -| Ver. | Date | Author | Change description | -|------|------------|------------------|--------------------| -| 0.1 | 2026-01-20 | Serhii Horodilov | Initial draft | +| ver. | Date | Author | Change description | +|------|------------|------------------|-------------------------------| +| 0.9 | 2025-01-20 | Serhii Horodilov | Final draft | +| 0.2 | 2026-01-20 | Serhii Horodilov | Utilize community health docs | +| 0.1 | 2026-01-20 | Serhii Horodilov | Initial draft |
@@ -116,17 +121,19 @@ journey: We value and recognize all contributions. Contributors will be credited in the repository's README or a dedicated CONTRIBUTORS file. +--- + ## Attribution -This Contributing Guide is inspired by community best practices and open source +This Support document is inspired by community best practices and open source community standards. **License:** -This Contributing Guide is licensed under the [Creative Commons Attribution 4.0 -International License][CC-BY-4.0]. +This Support document is licensed under +[Creative Commons Attribution 4.0 International License][CC-BY-4.0]. -You are free to adapt and use this guide for your own community, with +You are free to adapt and use this document for your own community, with attribution to OpenRoost. [CC-BY-4.0]: https://creativecommons.org/licenses/by/4.0/ diff --git a/docs/SECURITY.md b/docs/SECURITY.md index efe5952..623dacf 100644 --- a/docs/SECURITY.md +++ b/docs/SECURITY.md @@ -4,7 +4,6 @@ owner: /orgs/devsforge/teams/security @security --- [draft]: https://img.shields.io/badge/document_status-draft-orange -[ready]: https://img.shields.io/badge/document_status-ready-cyan [final]: https://img.shields.io/badge/document_status-final-blue # Security Policy @@ -14,11 +13,12 @@ owner: /orgs/devsforge/teams/security @security
Document Changelog -| Ver. | Date | Author | Change description | -|------|------------|------------------|----------------------------| -| 0.9 | 2025-01-20 | Serhii Horodilov | Final draft | -| 0.2 | 2025-01-19 | Serhii Horodilov | Update Attribution section | -| 0.1 | 2025-01-19 | Serhii Horodilov | Initial draft | +| ver. | Date | Author | Change description | +|------|------------|------------------|-------------------------------| +| 0.9 | 2025-01-20 | Serhii Horodilov | Final draft | +| 0.3 | 2026-01-20 | Serhii Horodilov | Utilize community health docs | +| 0.2 | 2025-01-19 | Serhii Horodilov | Update Attribution section | +| 0.1 | 2025-01-19 | Serhii Horodilov | Initial draft |
diff --git a/docs/SUPPORT.md b/docs/SUPPORT.md index 80ca299..15caa95 100644 --- a/docs/SUPPORT.md +++ b/docs/SUPPORT.md @@ -4,18 +4,18 @@ owner: /orgs/devsforge/teams/support @support --- [draft]: https://img.shields.io/badge/document_status-draft-orange -[ready]: https://img.shields.io/badge/document_status-ready-cyan [final]: https://img.shields.io/badge/document_status-final-blue # Support ![document status][draft] -| Ver. | Date | Author | Change description | -|------|------------|------------------|----------------------------| -| 0.9 | 2025-01-20 | Serhii Horodilov | Final draft | -| 0.2 | 2025-01-19 | Serhii Horodilov | Update Attribution section | -| 0.1 | 2025-01-19 | Serhii Horodilov | Initial draft | +| ver. | Date | Author | Change description | +|------|------------|------------------|-------------------------------| +| 0.9 | 2025-01-20 | Serhii Horodilov | Final draft | +| 0.3 | 2026-01-20 | Serhii Horodilov | Utilize community health docs | +| 0.2 | 2025-01-19 | Serhii Horodilov | Update Attribution section | +| 0.1 | 2025-01-19 | Serhii Horodilov | Initial draft | Welcome to OpenRoost! This document outlines how to get help, ask questions, and connect with our community.