[Docs] Community Health#12
Draft
shorodilov wants to merge 5 commits into
Draft
Conversation
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.
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.
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.
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.
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request updates the core community health documents to reflect the organization's rebranding from "DevsForge" to "OpenRoost," and introduces a new
CONTRIBUTING.mdguide. It also standardizes document metadata, status badges, and attribution across all docs, and improves changelog formatting and clarity.Key changes:
Organization Rebranding and Consistency:
CODE_OF_CONDUCT.md,SUPPORT.md, andSECURITY.mdto ensure consistent branding and community identity. [1] [2] [3] [4] [5] [6] [7] [8] F15caa95L15R19, [9] [10] [11] [12]Documentation Structure and Metadata:
status,owner, and standardized status badges ([draft],[final]) to all community health documents for improved discoverability and clarity. [1] [2] [3] [4]Changelog and Attribution Improvements:
New Contributor Guide:
CONTRIBUTING.mdthat outlines how to participate, report bugs, suggest enhancements, submit pull requests, and follow style guides, with a focus on inclusivity and bilingual communication.Minor Content and Process Updates:
These updates help ensure all documentation is up-to-date, welcoming, and aligned with the OpenRoost community's values and processes.