Added the required Docs for issue #12 (governance) #89
Conversation
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
Signed-off-by: YATIN JAMWAL <yatinjamwal07@gmail.com>
YATIN072007
force-pushed
the
issue-12-add-governance
branch
from
b73a21d to
04813f9
Compare
Contributor
Author
|
@AkarshSahlot |
Contributor
|
@HritikRaj2 have a look , try it locally if it build successfully than ping |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
his PR adds the
GOVERNANCE.md
file to the repository to clearly define the project's governance model, roles, and decision-making processes. This document is based on standard open-source best practices (CNCF/LF-style) and is designed to transparently guide the project's growth and management.
Related Issue
Closes #12
Changes
Created
GOVERNANCE.md
with the following comprehensive sections:
Overview and Scope: Aligning with Hyphae and LF Energy standards.
Roles and Responsibilities: Defining Users, Contributors, Maintainers, and the Project Steering Committee (PSC).
Decision-Making Process: Outlining consensus seeking, lazy consensus, and voting procedures.
Committer Lifecycle: Processes for nominating new maintainers and handling retirement.
Release Governance: Roadmap planning and release approval workflow.
Security: Instructions for responsible disclosure.
Notes
Placeholders (e.g., ) have been used where specific contact details were not yet available. These should be updated by the maintainers upon merging.