charter #8114
Draft
charter #8114
+117
−0
Conversation
This file contains 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: Sally MacFarlane <[email protected]>
siladu
requested changes
Jan 14, 2025
macfarla
commented
Jan 14, 2025
|
|
||
| 2. **Technical Steering Committee** | ||
|
|
||
| 1. The Technical Steering Committee (the “TSC”) will be responsible for all technical oversight of the open source Project. |
There was a problem hiding this comment.
If this is intended to be a Besu-specific TSC (as opposed to a LFDT-level body), I think this needs to be clarified
|
|
||
| 2. Maintainers are Contributors who have earned the ability to modify (“commit”) source code, documentation or other technical artifacts in a project’s repository; and | ||
|
|
||
| 3. A Contributor may become a Maintainer by a majority approval of the existing Maintainers. A Maintainer may be removed by a majority approval of the other existing Maintainers. |
There was a problem hiding this comment.
this process is described in more detail already in the MAINTAINERS.md
|
|
||
| 1. While the Project aims to operate as a consensus-based community, if any TSC decision requires a vote to move the Project forward, the voting members of the TSC will vote on a one vote per voting member basis. | ||
|
|
||
| 2. Quorum for TSC meetings requires at least fifty percent of all voting members of the TSC to be present. The TSC may continue to meet if quorum is not met but will be prevented from making any decisions at the meeting. |
There was a problem hiding this comment.
Besu decision making is generally conducted async
|
|
||
| **Technical** **Charter (the “Charter”)** | ||
| **for** | ||
| **Besu a Series of LF Projects, LLC** |
There was a problem hiding this comment.
Is this just boilerplate or is this charter intended to cover multiple repositories?
|
|
||
| 6. establishing community norms, workflows, issuing releases, and security issue reporting policies; | ||
|
|
||
| 7. approving and implementing policies and processes for contributing (to be published in the CONTRIBUTING file) and coordinating with the series manager of the Project (as provided for in the Series Agreement, the “Series Manager”) to resolve matters or concerns that may arise as set forth in Section 7 of this Charter; |
There was a problem hiding this comment.
who is the Series Manager, where is the Series Agreement?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR description
This PR proposes the addition of a Besu charter. Please add your feedback, questions etc in the form of comments on this PR.
Charter text originates from https://github.com/besu-eth/governance/blob/main/Besu%20Technical%20Charter.md however that charter is proposed for removal in this PR besu-eth/governance#7 since it was added without consultation with Besu maintainers.
Note this is a re-draft of #7128
This has come up again for discussion as part of move from Hyperledger to LFDT, and the relocation of this repo from hyperledger github org.
For context, as a LFDT project, Besu is already subject to the LFDT charter https://www.lfdecentralizedtrust.org/about/charter
Fixed Issue(s)
Thanks for sending a pull request! Have you done the following?
doc-change-requiredlabel to this PR if updates are required.Locally, you can run these tests to catch failures early:
./gradlew build./gradlew acceptanceTest./gradlew integrationTest./gradlew ethereum:referenceTests:referenceTests