-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' of https://github.com/hyperledger/indy-besu into …
…feat/revert-reason # Conflicts: # LICENSE
- Loading branch information
Showing
162 changed files
with
14,407 additions
and
20,264 deletions.
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| ## How to contribute | ||
|
|
||
| You are encouraged to contribute to the repository by **forking and submitting a pull request**. | ||
|
|
||
| For significant changes, please open an issue first to discuss the proposed changes to avoid re-work. | ||
|
|
||
| (If you are new to GitHub, you might start with a [basic tutorial](https://help.github.com/articles/set-up-git) and check out a more detailed guide to [pull requests](https://help.github.com/articles/using-pull-requests/).) | ||
|
|
||
| Pull requests will be evaluated by the repository guardians on a schedule and if deemed beneficial will be committed to the master. Pull requests should have a descriptive name and include an summary of all changes made in the pull request description. | ||
|
|
||
| If you would like to propose a significant change, please open an issue first to discuss the work with the community. | ||
|
|
||
| All contributors retain the original copyright to their stuff, but by contributing to this project, you grant a world-wide, royalty-free, perpetual, irrevocable, non-exclusive, transferable license to all users **under the terms of the license under which this project is distributed.** |
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,99 @@ | ||
| # Maintainers | ||
|
|
||
| <!-- Please keep all lists sorted alphabetically by github --> | ||
|
|
||
| ## Active Maintainers | ||
|
|
||
| | Name | Github | LFID | | ||
| |---------------------|--------------------|------| | ||
| | Artem Ivanov | Artemkaaas | | | ||
| | Renata Toktar | Toktar | | | ||
| | Alexander Sherbakov | ashcherbakov | | | ||
| | Wade Barnes | WadeBarnes | | | ||
|
|
||
| ## Becoming a Maintainer | ||
|
|
||
| Indy-Besu welcomes community contribution. | ||
| Each community member may progress to become a maintainer. | ||
|
|
||
| How to become a maintainer: | ||
|
|
||
| - Contribute significantly to the code in this repository. | ||
|
|
||
| ### Maintainers contribution requirement | ||
|
|
||
| The requirement to be able to be proposed as a maintainer is: | ||
|
|
||
| - 5 significant changes on code have been authored in this repos by the proposed maintainer and accepted (merged PRs). | ||
|
|
||
| ### Maintainers approval process | ||
|
|
||
| The following steps must occur for a contributor to be "upgraded" as a maintainer: | ||
|
|
||
| - The proposed maintainer has the sponsorship of at least one other maintainer. | ||
| - This sponsoring maintainer will create a proposal PR modifying the list of | ||
| maintainers. (see [proposal PR template](#proposal-pr-template).) | ||
| - The proposed maintainer accepts the nomination and expresses a willingness | ||
| to be a long-term (more than 6 month) committer by adding a comment in the proposal PR. | ||
| - The PR will be communicated in all appropriate communication channels | ||
| including at least [indy-contributors channel on Hyperledger Discord](https://discord.gg/hyperledger), | ||
| the [mailing list](https://lists.hyperledger.org/g/indy) | ||
| and any maintainer/community call. | ||
| - Approval by at least 3 current maintainers within two weeks of the proposal or | ||
| an absolute majority (half the total + 1) of current maintainers. | ||
| - Maintainers will vote by approving the proposal PR. | ||
| - No veto raised by another maintainer within the voting timeframe. | ||
| - All vetoes must be accompanied by a public explanation as a comment in the | ||
| proposal PR. | ||
| - A veto can be retracted, in that case the voting timeframe is reset and all approvals are removed. | ||
| - It is bad form to veto, retract, and veto again. | ||
|
|
||
| The proposed maintainer becomes a maintainer either: | ||
|
|
||
| - when two weeks have passed without veto since the third approval of the proposal PR, | ||
| - or an absolute majority of maintainers approved the proposal PR. | ||
|
|
||
| In either case, no maintainer raised and stood by a veto. | ||
|
|
||
| ## Removing Maintainers | ||
|
|
||
| Being a maintainer is not a status symbol or a title to be maintained indefinitely. | ||
|
|
||
| It will occasionally be necessary and appropriate to move a maintainer to emeritus status. | ||
|
|
||
| This can occur in the following situations: | ||
|
|
||
| - Resignation of a maintainer. | ||
| - Violation of the Code of Conduct warranting removal. | ||
| - Inactivity. | ||
| - A general measure of inactivity will be no commits or code review comments | ||
| for two reporting quarters, although this will not be strictly enforced if | ||
| the maintainer expresses a reasonable intent to continue contributing. | ||
| - Reasonable exceptions to inactivity will be granted for known long term | ||
| leave such as parental leave and medical leave. | ||
| - Other unspecified circumstances. | ||
|
|
||
| As for adding a maintainer, the record and governance process for moving a | ||
| maintainer to emeritus status is recorded using review approval in the PR making that change. | ||
|
|
||
| Returning to active status from emeritus status uses the same steps as adding a | ||
| new maintainer. | ||
|
|
||
| Note that the emeritus maintainer always already has the required significant contributions. | ||
| There is no contribution prescription delay. | ||
|
|
||
| ## Proposal PR template | ||
|
|
||
| ```markdown | ||
| I propose to add [maintainer github handle] as a Indy-Besu project maintainer. | ||
|
|
||
| [maintainer github handle] contributed with many high quality commits: | ||
|
|
||
| - [list significant achievements] | ||
|
|
||
| Here are [their past contributions on Indy-Besu project](https://github.com/hyperledger/indy-besu/commits?author=[user github handle]). | ||
|
|
||
| Voting ends two weeks from today. | ||
|
|
||
| For more information on this process see the Becoming a Maintainer section in the MAINTAINERS.md file. | ||
| ``` |
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| # Hyperledger Security Policy | ||
|
|
||
| ## Reporting a Security Bug | ||
|
|
||
| If you think you have discovered a security issue in any of the Hyperledger projects, we'd love to hear from you. We will take all security bugs seriously and if confirmed upon investigation we will patch it within a reasonable amount of time and release a public security bulletin discussing the impact and credit the discoverer. | ||
|
|
||
| There are two ways to report a security bug. The easiest is to email a description of the flaw and any related information (e.g. reproduction steps, version) to [security at hyperledger dot org](mailto:[email protected]). | ||
|
|
||
| The other way is to file a confidential security bug in our [JIRA bug tracking system](https://jira.hyperledger.org). Be sure to set the “Security Level” to “Security issue”. | ||
|
|
||
| The process by which the Hyperledger Security Team handles security bugs is documented further in our [Defect Response page](https://wiki.hyperledger.org/display/HYP/Defect+Response) on our [wiki](https://wiki.hyperledger.org). |
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
Oops, something went wrong.