├── resources └── social-media-template.png ├── CODE_OF_CONDUCT.md ├── PULL_REQUEST_TEMPLATE.md ├── .github ├── ISSUE_TEMPLATE │ ├── feature.yml │ ├── bug.yml │ └── good-first-issue-candidate.yaml └── DISCUSSION_TEMPLATE │ └── app-requests.yaml ├── README_TEMPLATE.md ├── MAINTAINERS.md ├── README.md ├── GLOBAL-MAINTAINERS.md ├── SECURITY.md ├── CONTRIBUTING.md ├── LICENSE.md ├── profile └── README.md ├── .gitvote.yml └── .gitignore /resources/social-media-template.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/hiero-ledger/.github/main/resources/social-media-template.png -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | Code of Conduct Guidelines 2 | ========================== 3 | 4 | Please review the Linux Foundation Decentralized Trust [Code of 5 | Conduct](https://www.lfdecentralizedtrust.org/code-of-conduct) 6 | before participating. It is important that we keep things civil. 7 | 8 | Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License. 9 | -------------------------------------------------------------------------------- /PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | **Description**: 2 | 12 | 13 | **Related issue(s)**: 14 | 15 | Fixes # 16 | 17 | **Notes for reviewer**: 18 | 19 | 20 | **Checklist** 21 | 22 | - [ ] Documented (Code comments, README, etc.) 23 | - [ ] Tested (unit, integration, etc.) 24 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature.yml: -------------------------------------------------------------------------------- 1 | name: Feature 2 | description: Suggest an idea for this project 3 | labels: [ enhancement ] 4 | type: Feature 5 | body: 6 | - type: markdown 7 | attributes: 8 | value: | 9 | ## Thanks for submitting a feature request! 10 | 11 | Before submitting: 12 | * Try searching the existing issues and discussions to see if something similar has been discussed previously 13 | * Try opening a GitHub discussion first to gather feedback and reach consensus 14 | * If this is a major enhancement, please open a [Hiero Improvement Proposal](https://github.com/hiero-ledger/hiero-improvement-proposals) 15 | - type: textarea 16 | id: problem 17 | attributes: 18 | label: Problem 19 | description: What is the problem you are trying to solve? 20 | placeholder: I'm always frustrated when ... 21 | validations: 22 | required: true 23 | - type: textarea 24 | id: solution 25 | attributes: 26 | label: Solution 27 | description: What solution do you propose to solve the problem? 28 | placeholder: | 29 | - Add a config property 30 | - Change the schema 31 | - ... 32 | validations: 33 | required: true 34 | - type: textarea 35 | id: alternatives 36 | attributes: 37 | label: Alternatives 38 | description: What alternative solutions have you considered? 39 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug.yml: -------------------------------------------------------------------------------- 1 | name: Bug report 2 | description: Create a report to help us improve 3 | labels: [ bug ] 4 | type: Bug 5 | body: 6 | - type: markdown 7 | attributes: 8 | value: | 9 | ## Thanks for submitting a bug report! 10 | 11 | Before submitting: 12 | 1. Try searching the existing issues and discussions to see if your issue has already been reported 13 | 2. Try asking on [Discord's hiero-general channel](discord.hiero.org) 14 | 3. If you're reporting a security vulnerability, please disclose responsibly via our [bug bounty program](https://hedera.com/bounty) 15 | - type: textarea 16 | id: description 17 | attributes: 18 | label: Description 19 | description: What happened and what you did you expect to happen? 20 | validations: 21 | required: true 22 | - type: textarea 23 | id: steps 24 | attributes: 25 | label: Steps to reproduce 26 | description: Steps to reproduce the behavior 27 | placeholder: | 28 | 1. Run the program 29 | 2. Click on '...' 30 | 3. Scroll down to '...' 31 | validations: 32 | required: true 33 | - type: textarea 34 | id: context 35 | attributes: 36 | label: Additional context 37 | description: Attach any logs or screenshots relevent to the problem. 38 | placeholder: | 39 | ![Screenshot](bug.png) 40 | 41 | ```bash 42 | 2021-06-29T13:50:45.008-0600 INFO thread-1 Some logs 43 | ``` 44 | - type: dropdown 45 | id: network 46 | attributes: 47 | description: Which network(s) did the issue occur on? 48 | label: Hedera network 49 | multiple: true 50 | options: 51 | - mainnet 52 | - testnet 53 | - previewnet 54 | - other 55 | - type: input 56 | id: version 57 | attributes: 58 | description: What version of the software are you using? 59 | label: Version 60 | placeholder: v0.1.0 61 | validations: 62 | required: true 63 | - type: dropdown 64 | id: os 65 | attributes: 66 | description: Which OS did the issue occur on? 67 | label: Operating system 68 | options: 69 | - Linux 70 | - macOS 71 | - Windows 72 | - Other 73 | -------------------------------------------------------------------------------- /.github/DISCUSSION_TEMPLATE/app-requests.yaml: -------------------------------------------------------------------------------- 1 | # Template metadata 2 | title: "GitHub App Integration Request" 3 | labels: ["app-request"] 4 | 5 | # Template body 6 | body: 7 | - type: input 8 | id: app_name 9 | attributes: 10 | label: "GitHub App Name" 11 | description: "Enter the exact name of the GitHub App you’d like integrated." 12 | placeholder: "Example: Dependabot, Snyk, or Custom Internal App" 13 | validations: 14 | required: true 15 | 16 | - type: textarea 17 | id: affected_repos 18 | attributes: 19 | label: "Affected Repositories" 20 | description: | 21 | Specify where this integration should be applied. 22 | You can choose: 23 | - `All` (for all repositories) 24 | - A list of specific repository names (one per line) 25 | placeholder: | 26 | All 27 | OR 28 | repo-one 29 | repo-two 30 | validations: 31 | required: true 32 | 33 | - type: textarea 34 | id: justification 35 | attributes: 36 | label: "Justification" 37 | description: "Explain why this integration is needed and what value it provides." 38 | placeholder: "Describe the motivation, compliance, or business reason for this integration." 39 | validations: 40 | required: true 41 | 42 | - type: markdown 43 | attributes: 44 | value: | 45 | **Default Included Teams:** 46 | @hiero-ledger/security-maintainers 47 | @hiero-ledger/prod-security 48 | @hiero-ledger/sec-ops 49 | @hiero-ledger/github-maintainers 50 | 51 | - type: textarea 52 | id: additional_teams 53 | attributes: 54 | label: "Additional Teams to Include (optional)" 55 | description: "Add any other organization teams to notify about this request. Separate multiple teams with spaces." 56 | placeholder: | 57 | Please include the following teams: 58 | - @hiero-ledger/security-maintainers 59 | - @hiero-ledger/prod-security 60 | - @hiero-ledger/sec-ops 61 | - @hiero-ledger/github-maintainers 62 | value: | 63 | @hiero-ledger/security-maintainers 64 | @hiero-ledger/prod-security 65 | @hiero-ledger/sec-ops 66 | @hiero-ledger/github-maintainers 67 | validations: 68 | required: false 69 | -------------------------------------------------------------------------------- /README_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | # Project Name 2 | 3 | 8 | [CI Link][Documentation Link][OpenSSF Score Card][CII Best Practices][Security Scan Links][Global or Repo Security File Link][License Link] 9 | 10 | 13 | ## Releases 14 | 15 | [Current Releases Link] 16 | 17 | [Historic Releases Links] 18 | 19 | 22 | ## Useful References 23 | 24 | - Reference1 25 | - Reference2 26 | - Reference3 27 | 28 | 31 | ## About Project 32 | - History/backround of how the project came to be and/or need that is addressing. 33 | - What the project does? 34 | - Why is the project useful? 35 | 36 | 39 | ## Getting Started 40 | 41 | - How users can get started with the project? 42 | 43 | 48 | ## Contribute 49 | 50 | - To contribute, please refer to the **[Hiero-Ledger's contribution guidelines](https://github.com/hiero-ledger/.github/blob/main/CONTRIBUTING.md)** 51 | 52 | 56 | ## Help/Community 57 | 58 | - Where users can get help with your project 59 | 60 | 65 | ## About Users and Maintainers 66 | 67 | - Users and Maintainers guidelies are located in **[Hiero-Ledger's roles and groups guidelines](https://github.com/hiero-ledger/governance/blob/main/roles-and-groups.md#maintainers).** 68 | 69 | 72 | ## Acknowledgements 73 | 74 | - Special thanks and recognition. 75 | 76 | 79 | ## License 80 | 81 | - License information. 82 | -------------------------------------------------------------------------------- /MAINTAINERS.md: -------------------------------------------------------------------------------- 1 | # Maintainers 2 | 3 | The general handling of Maintainer rights and all groups in this GitHub org is done in the https://github.com/hiero-ledger/governance repository. 4 | 5 | ## Maintainer Scopes, GitHub Roles and GitHub Teams 6 | 7 | Maintainers are assigned the following scopes in this repository: 8 | 9 | | Scope | Definition | GitHub Role | GitHub Team | 10 | | ------------------- | --------------------------------- | ----------- | -------------------------- | 11 | | project-maintainers | The Maintainers of the project | Maintain | `hiero-github-maintainers` | 12 | | tsc | The Hiero TSC | Maintain | `tsc` | 13 | | github-maintainers | The Maintainers of the github org | Maintain | `github-maintainers` | 14 | 15 | ## Active Maintainers 16 | 17 | | Name | GitHub ID | Scope | LFID | Discord ID | Email | Company Affiliation | 18 | |----------------------- | ------------- | ------------------ | ---- | ---------- | ----- | -------------------- | 19 | | Lenin Mehedy | leninmehedy | github-maintainers | | | | Hashgraph | 20 | | Jeromy Cannon | jeromy-cannon | github-maintainers | | | | Hashgraph | 21 | | Nathan Klick | nathanklick | github-maintainers | | | | Hashgraph | 22 | | Pavel Borisov | PavelSBorisov | github-maintainers | | | | LimeChain | 23 | | Roger Barker | rbarker-dev | github-maintainers | | | | Hashgraph | 24 | | Andrew Brandt | andrewb1269hg | github-maintainers | | | | Hashgraph | 25 | | Richard Bair | rbair23 | tsc | | | | Hashgraph | 26 | | Leemon Baird | lbaird | tsc | | | | Hashgraph | 27 | | George Spasov | Perseverance | tsc | | | | LimeChain | 28 | | Hendrik Ebbers | hendrikebbers | tsc | | | | Hashgraph | 29 | | Alex Popowycz | popowycz | tsc | | | | Hedera | 30 | | Stoyan Panayotov | stoqnkpL | tsc | | | | LimeChain | 31 | | Milan Wiercx Van Rhijn | MilanWR | tsc | | | | MilanWR.com (8BEES) | 32 | | Michael Kantor | kantorcodes | tsc | | | | Hashgraph Online | 33 | 34 | ## Emeritus Maintainers 35 | 36 | | Name | GitHub ID | Scope | LFID | Discord ID | Email | Company Affiliation | 37 | |----- | --------- | ----- | ---- | ---------- | ----- | ------------------- | 38 | | | | | | | | | 39 | 40 | ## The Duties of a Maintainer 41 | 42 | Maintainers are expected to perform duties in alignment with **[Hiero-Ledger's defined maintainer guidelines](https://github.com/hiero-ledger/governance/blob/main/roles-and-groups.md#maintainers).** 43 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # .github 2 | 3 | 8 | [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/10697/badge)](https://bestpractices.coreinfrastructure.org/projects/10697) 9 | [![License](https://img.shields.io/badge/license-apache2-blue.svg)](LICENSE.md) 10 | 13 | ## Useful References 14 | 15 | - [Hiero Website](https://hiero.org) 16 | 17 | 20 | ## About Project 21 | 22 | This repository holds organization-wide configurations, templates, and guidelines for contributing to our projects on GitHub. 23 | 24 | 27 | ## Getting Started 28 | 29 | - For a comprehensive and detailed overview of Hiero, please refer to the technical documentation and related resources available on our [website](https://hiero.org). 30 | 31 | 36 | ## Contribute 37 | 38 | - To contribute, please refer to the **[Hiero-Ledger's contribution guidelines](https://github.com/hiero-ledger/.github/blob/main/CONTRIBUTING.md)** 39 | 40 | 44 | ## Help/Community 45 | 46 | - Engage with the Hyperledger community: 47 | - **[hiero-general Discord channel](https://discord.lfdecentralizedtrust.org/)** 48 | - **[Public Calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week)** 49 | 50 | 55 | ## About Users and Maintainers 56 | 57 | - Users and Maintainers guidelines are located in **[Hiero-Ledger's roles and groups guidelines](https://github.com/hiero-ledger/governance/blob/main/roles-and-groups.md#maintainers).** 58 | 59 | 62 | 63 | ## License 64 | 65 | - Hiero's source code is available under the **Apache License, Version 2.0 (Apache-2.0)**[Apache License 2.0](LICENSE.md) 66 | -------------------------------------------------------------------------------- /GLOBAL-MAINTAINERS.md: -------------------------------------------------------------------------------- 1 | # Global Maintainers 2 | 3 | This file defines the global maintainers of the hiero-ledger org that have maintainer rights to all projects within Hiero. 4 | The general handling of Maintainer rights and all groups in this GitHub org is done in the https://github.com/hiero-ledger/governance repository. 5 | 6 | ## Maintainer Scopes, GitHub Roles and GitHub Teams 7 | 8 | Global maintainers are assigned the following scopes in this repository: 9 | 10 | | Scope | Definition | GitHub Role | GitHub Team | 11 | | ------------------ | ----------------------------------------- | ----------- | ---------------------------------- | 12 | | github-maintainers | The Maintainers of the GitHub org | Maintain | `github-maintainers` | 13 | | tsc | The Technical Steering Committee of Hiero | Maintain | `tsc` | 14 | 15 | ## Active Maintainers 16 | 17 | | Name | GitHub ID | Scope | LFID | Discord ID | Email | Company Affiliation | 18 | |----------------------- | ------------- | ------------------ | ---- | ---------- | ----- | -------------------- | 19 | | Lenin Mehedy | leninmehedy | github-maintainers | | | | Hashgraph | 20 | | Jeromy Cannon | jeromy-cannon | github-maintainers | | | | Hashgraph | 21 | | Nathan Klick | nathanklick | github-maintainers | | | | Hashgraph | 22 | | Pavel Borisov | PavelSBorisov | github-maintainers | | | | LimeChain | 23 | | Roger Barker | rbarker-dev | github-maintainers | | | | Hashgraph | 24 | | Andrew Brandt | andrewb1269 | github-maintainers | | | | Hashgraph | 25 | | Ry Jones | ryjones | github-maintainers | | | | The Linux Foundation | 26 | | Jessica Gonzalez | jwagantall | github-maintainers | | | | The Linux Foundation | 27 | | Richard Bair | rbair23 | tsc | | | | Hashgraph | 28 | | Leemon Baird | lbaird | tsc | | | | Hashgraph | 29 | | George Spasov | Perseverance | tsc | | | | LimeChain | 30 | | Hendrik Ebbers | hendrikebbers | tsc | | | | Hashgraph | 31 | | Alex Popowycz | popowycz | tsc | | | | Hedera | 32 | | Stoyan Panayotov | stoqnkpL | tsc | | | | LimeChain | 33 | | Milan Wiercx Van Rhijn | MilanWR | tsc | | | | 8Bees | 34 | | Michael Kantor | kantorcodes | tsc | | | | Hashgraph Online | 35 | 36 | ## Emeritus Maintainers 37 | 38 | | Name | GitHub ID | Scope | LFID | Discord ID | Email | Company Affiliation | 39 | |----- | --------- | ----- | ---- | ---------- | ----- | ------------------- | 40 | | | | | | | | | 41 | 42 | ## The Duties of a Maintainer 43 | 44 | Maintainers are expected to perform duties in alignment with **[Hiero-Ledger's defined maintainer guidelines](https://github.com/hiero-ledger/governance/blob/main/roles-and-groups.md#maintainers).** 45 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/good-first-issue-candidate.yaml: -------------------------------------------------------------------------------- 1 | name: Good First Issue Candidate 2 | description: Suggest an idea for this project 3 | labels: [ "Good First Issue Candidate" ] 4 | type: Feature 5 | body: 6 | - type: markdown 7 | attributes: 8 | value: | 9 | ## Thanks for submitting a Good First Issue! 10 | This issue targets first time contributors to [Hiero](https://hiero.org). 11 | We know that creating a pull request (PR) is a major barrier for new contributors. 12 | 13 | Before submitting: 14 | * Try searching the existing issues and discussions to see if something similar has been discussed previously. 15 | * Check if this issue is likely to be a Good First Issue [Good First Issue Guidelines](https://github.com/hiero-ledger/governance/blob/main/guidelines/good-first-issues.md). 16 | 17 | ------ 18 | - type: textarea 19 | id: intro 20 | attributes: 21 | label: 🆕🐥 First Timers Only 22 | description: Who is this issue for? 23 | value: | 24 | This issue is reserved for people who have never contributed or have made minimal contributions to [Hiero](https://hiero.org). 25 | We know that creating a pull request (PR) is a major barrier for new contributors. 26 | The goal of this issue and all other issues in [**find a good first issue**](https://github.com/issues?q=is%3Aopen+is%3Aissue+org%3Ahiero-ledger+archived%3Afalse+label%3A%22good+first+issue%22+) is to help you make your first contribution to the Hiero. 27 | validations: 28 | required: false 29 | 30 | - type: textarea 31 | id: issue 32 | attributes: 33 | label: 👾 Description of the issue 34 | description: | 35 | DESCRIBE THE ISSUE IN A WAY THAT IS UNDERSTANDABLE TO NEW CONTRIBUTORS. 36 | YOU MUST NOT ASSUME THAT SUCH CONTRIBUTORS HAVE ANY KNOWLEDGE ABOUT THE CODEBASE OR HIERO. 37 | IT IS HELPFUL TO ADD LINKS TO THE RELEVANT DOCUMENTATION AND/OR CODE SECTIONS. 38 | value: | 39 | Edit here. 40 | validations: 41 | required: true 42 | 43 | - type: textarea 44 | id: solution 45 | attributes: 46 | label: 💡 Proposed Solution 47 | description: | 48 | AT THIS SECTION YOU NEED TO DESCRIBE THE STEPS NEEDED TO SOLVE THE ISSUE. 49 | PLEASE BREAK DOWN THE STEPS AS MUCH AS POSSIBLE AND MAKE SURE THAT THEY 50 | ARE EASY TO FOLLOW. IF POSSIBLE, ADD LINKS TO THE RELEVANT 51 | DOCUMENTATION AND/OR CODE SECTIONS. 52 | value: | 53 | Edit here. 54 | validations: 55 | required: true 56 | 57 | - type: textarea 58 | id: implementation 59 | attributes: 60 | label: 👩‍💻 Implementation Steps 61 | description: | 62 | AT THIS SECTION YOU NEED TO DESCRIBE THE TECHNICAL STEPS NEEDED TO SOLVE THE ISSUE. 63 | PLEASE BREAK DOWN THE STEPS AS MUCH AS POSSIBLE AND MAKE SURE THAT THEY ARE EASY TO FOLLOW. 64 | IF POSSIBLE, ADD LINKS TO THE RELEVANT DOCUMENTATION AND/OR CODE. 65 | value: | 66 | Edit here. Example provided below. 67 | validations: 68 | required: true 69 | 70 | - type: textarea 71 | id: acceptance-criteria 72 | attributes: 73 | label: ✅ Acceptance Criteria 74 | description: | 75 | EDIT OR EXPAND THE CHECKLIST ON WHAT IS REQUIRED TO BE ABLE TO MERGE A PULL REQUEST FOR THIS ISSUE 76 | value: | 77 | To be able to merge a pull request for this issue, we need: 78 | - [ ] **Changelog Entry:** Correct changelog entry 79 | - [ ] **Signed commits:** commits must be DCO and GPG key signed 80 | - [ ] **All Tests Pass:** our workflow checks like unit and integration tests must pass 81 | - [ ] **Issue is Solved:** The implementation fully addresses the issue requirements as described above 82 | - [ ] **No Further Changes are Made:** Code review feedback has been addressed and no further changes are requested 83 | validations: 84 | required: true 85 | 86 | - type: textarea 87 | id: workflow 88 | attributes: 89 | label: 📋 Step-by-Step Contribution Guide 90 | description: Instructions for new contributors 91 | value: | 92 | If you have never contributed to an open source project at GitHub, the following step-by-step guide will introduce you to the workflow. 93 | More information and concrete samples for shell commands for each step can be found in our [CONTRIBUTING.md](https://github.com/hiero-ledger/.github/blob/main/CONTRIBUTING.md) file. 94 | A more detailed general documentation of the GitHub PR workflow can be found [here](https://github.com/firstcontributions/first-contributions/blob/master/README.md). 95 | 96 | - [ ] **Claim this issue:** Comment below that you are interested in working on the issue 97 | - [ ] **Wait for assignment:** A community member with the given rights will add you as an assignee of the issue 98 | - [ ] **Work on the issue:** Follow the detailed description in our [CONTRIBUTING.md](https://github.com/hiero-ledger/.github/blob/main/CONTRIBUTING.md) file. 99 | - [ ] **You did it 🎉:** We will merge the fix in the main branch. Thanks for being part of the Hiero community as an open-source contributor! 100 | 101 | ***IMPORTANT*** Your pull request CANNOT BE MERGED until your commits are each with `git commit -S -s -m "chore: your commit message"` with a GPG key setup. 102 | 103 | - type: textarea 104 | id: additional_questions 105 | attributes: 106 | label: 🤔 Additional Information 107 | description: Provide any extra resources or context for contributors to solve this good first issue 108 | value: | 109 | If you have any questions about the topic of this issue, please ask us directly by adding a comment below. 110 | Additionally, we invite you to join our community on our [Discord](https://discord.gg/hyperledger) server or attend our [public community calls](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week). 111 | 112 | A general manual about open-source contributions can be found [here](https://github.com/firstcontributions/first-contributions/blob/master/README.md). 113 | 114 | ------ 115 | 116 | - type: markdown 117 | attributes: 118 | value: | 119 | ## :jack_o_lantern: Hacktoberfest :jack_o_lantern: 120 | 121 | At the time of the [Hacktoberfest](https://hacktoberfest.digitalocean.com) event we try to mark all PRs that solve any good first issue with the `hacktoberfest-accepted` label. 122 | If you want to resolve this issue as part of Hacktoberfest and we missed adding the label, simply add a comment to the issue or PR, and we will add it. 123 | 124 | ------ -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | # Hiero, an LF Decentralized Trust Project Security Policy 2 | 3 | ## About this document 4 | 5 | This document defines how security vulnerability reporting is handled in Hiero, an [LF Decentralized Trust Project](https://www.lfdecentralizedtrust.org/). The approach aligns with the [LF Decentralized Trust Security Policy](https://lf-decentralized-trust.github.io/governance/governing-documents/SECURITY-POLICY). Please review that document to understand the basis of the security reporting for Hiero. 6 | 7 | This vulnerability policy borrows heavily from the recommendations of the OpenSSF Vulnerability Disclosure working group. For up-to-date information on the latest recommendations related to vulnerability disclosures, please visit the [GitHub of that working group](https://github.com/ossf). 8 | 9 | If you are already familiar with the security policies of Hiero, and ready to report a vulnerability, please jump to [Report Intakes](#report-intakes). 10 | 11 | ## Outline 12 | 13 | This document has the following sections: 14 | 15 | - [About this document](#about-this-document) 16 | - [Outline](#outline) 17 | - [What Is a Vulnerability Disclosure Policy?](#what-is-a-vulnerability-disclosure-policy) 18 | - [Security Team](#security-team) 19 | - [Report Intakes](#report-intakes) 20 | - [CNA/CVE Reporting](#cnacve-reporting) 21 | - [Embargo List](#embargo-list) 22 | - [GitHub Security Advisories](#github-security-advisories) 23 | - [Private Patch Deployment Infrastructure](#private-patch-deployment-infrastructure) 24 | 25 | ## What Is a Vulnerability Disclosure Policy? 26 | 27 | No piece of software is perfect. All software (at least, all software of a certain size and complexity) has bugs. In open source development, members of the community or the public find bugs and report them to the project. A vulnerability disclosure policy explains how this process functions from the perspective of the project. 28 | 29 | This vulnerability disclosure policy explains the rules and guidelines for Hiero. It is intended to act as both a reference for outsiders–including both bug reporters and those looking for information on the project’s security practices–as well as a set of rules that maintainers and contributors have agreed to follow. 30 | 31 | ## Security Team 32 | 33 | The current Hiero security team is: 34 | 35 | | Name | Email ID | Discord ID | Area/Specialty | 36 | |--------------------------|------------------------|------------|---------------------------| 37 | | Hart Mongomery (LFDT) | <> | <> | Temp Security Advisor | 38 | | Jessica Gonzalez (LFDT) | <> | <> | Community Architect | 39 | | Alex Popowycz | <> | <> | Security Advisor | 40 | | Roger Barker | <> | <> | Project Maintainer | 41 | | Richard Bair | <> | <> | Project Maintainer | 42 | | Nathan Klick | <> | <> | Security Advisor | 43 | | Deepak Rathore | <> | <> | Security Advisor | 44 | 45 | The security team for Hiero must include at least three project Maintainers that agree to carry out the following duties and responsibilities. Members are added and removed from the team via approved Pull Requests to this repository. For additional background into the role of the security team, see the [People Infrastructure](https://lf-decentralized-trust.github.io/governance/governing-documents/SECURITY-POLICY#people-infrastructure) section of the LF Decentralized Trust Security Policy. 46 | 47 | ### Responsibilities: 48 | 49 | 1. Acknowledge the receipt of vulnerability reports to the reporter within 2 business days. 50 | 2. Assess the issue. Engage with the reporter to ask any outstanding questions about the report and how to reproduce it. If the report was received by email and may be a security vulnerability, open a GitHub Security Advisory on the repository to manage the report. If the report is not considered a vulnerability, then the reporter should be informed and this process can be halted. If the report is a regular bug (but not a security vulnerability), the reporter should be informed (if necessary) of the regular process for reporting issues. 51 | 3. Some issues may require more time and resources to correct. If a particular report is complex, discuss an embargo period with the reporter during which time the report will not be publicly disclosed. The embargo period should be negotiated with the reporter. 52 | 4. If necessary, create a private patch development infrastructure for the issue by emailing the [LF Decentralized Trust Community Architects](mailto:community-architects@lfdecentralizedtrust.org). 53 | 5. Request a CVE for the issue (see the [CNA/CVE Reporting](#cnacve-reporting) section). 54 | 6. Decide a date for the public release of the vulnerability report, the date the embargo period ends. 55 | 7. If applicable, notify members of the embargo list of the vulnerability, upcoming patch and release, as described above. 56 | 8. Publish a new (software) release in which the vulnerability is addressed. 57 | 9. Publicly disclose the issue within 48 hours after the release via a GitHub security advisory (see the [(GitHub) Security Advisories](#github-security-advisories) section for details). 58 | 59 | ## Report Intakes 60 | 61 | Do not publicly disclose vulnerablities. 62 | 63 | For LFDT or Community Projects 64 | 65 | Hiero has the following ways to submit security vulnerabilities. While the security team members will do their best to respond to bugs disclosed in all possible ways, it is encouraged for bug finders to report through the following approved channels: 66 | 67 | Open a GitHub security vulnerability report: Open a draft security advisory on the “Security” tab of this GitHub repository. See [GitHub Security Advisories](https://docs.github.com/en/code-security/security-advisories) to learn more about the security infrastructure in GitHub. 68 | 69 | For Hedera repositories details on the bug bounty program can be found at: [Hedera Bug Bounty Program](https://hedera.com/bounty). 70 | 71 | For general questions, excluding security reports, please email the [Hiero Security Team](mailto:hiero@lists.lfdecentralizedtrust.org). 72 | 73 | ## CNA/CVE Reporting 74 | 75 | Hiero maintains a list of Common Vulnerabilities and Exposures (CVE) and uses GitHub as its CVE numbering authority (CNA) for issuing CVEs. 76 | 77 | ## Embargo List 78 | 79 | Hiero maintains a private embargo list. If you wish to be added to the embargo list, please email the [Hiero Security Team](mailto:hiero@lists.lfdecentralizedtrust.org), including the project name (Hiero) and reason for being added to the embargo list. Requests will be assessed by the Hiero security team in conjunction with the appropriate LF Decentralized Trust Staff, and a decision will be made to accommodate or not the request. 80 | 81 | For more information about the embargo list, please see the Embargo List section of the [LF Decentralized Trust Security Policy](https://lf-decentralized-trust.github.io/governance/governing-documents/security.html#embargo-list). 82 | 83 | ## GitHub Security Advisories 84 | 85 | Hiero uses [GitHub Security Advisories](https://docs.github.com/en/code-security/security-advisories) to manage the public disclosure of security vulnerabilities. 86 | 87 | ## Private Patch Deployment Infrastructure 88 | 89 | In creating patches and new releases that address security vulnerabilities, Hiero uses the private development features of GitHub for security vulnerabilities. [GitHub](https://docs.github.com/en/code-security) has extensive documentation about these features. 90 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to Hiero 2 | 3 | First off, thanks for taking the time to contribute! ❤️ 4 | 5 | All types of contributions are encouraged and valued. 6 | Please make sure to read the relevant section before making your contribution. 7 | It will make it a lot easier for us maintainers and smooth out the experience for all involved. 8 | The community looks forward to your contributions. 🎉 9 | 10 | > And if you like the project, but just don't have time to contribute, that's fine. 11 | > There are other easy ways to support the project and show your appreciation, which we would also be very happy about: 12 | > - Star the project 13 | > - Tweet about it 14 | > - Refer this project in your project's readme 15 | > - Mention the project at local meetups and tell your friends/colleagues 16 | 17 | ## Code of Conduct 18 | 19 | This project and everyone participating in it is governed by the 20 | [Linux Foundation Decentralized Trust Code of Conduct](https://www.lfdecentralizedtrust.org/code-of-conduct). 21 | By participating, you are expected to uphold this code. 22 | Please report unacceptable behavior to Mike Dolan (mdolan@linuxfoundation.org) or Angela Brown (angela@linuxfoundation.org). 23 | 24 | ## Pull Requests 25 | Like most open source projects, we use 26 | [pull requests](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) ( 27 | PRs) to track code changes. 28 | 29 | ### Forking 30 | 31 | 1. [Fork](https://guides.github.com/activities/forking/) the repository. Go to the project page then hit the `Fork` 32 | button to fork your own copy of the repository to your GitHub account. 33 | 34 | 2. Clone the forked repository to your local working directory. 35 | 36 | ```sh 37 | $ git clone https://github.com/${owner}/${repo}.git 38 | ``` 39 | 40 | 3. Add an `upstream` remote to keep your fork in sync with the main repo. 41 | 42 | ```sh 43 | $ git remote add upstream https://github.com/hiero-ledger/${repo}.git 44 | ``` 45 | 46 | 4. Sync your local `main` branch. 47 | 48 | ```sh 49 | $ git pull upstream main 50 | ``` 51 | 52 | 5. Create a branch to add a new feature or fix issues. 53 | 54 | ```sh 55 | $ git checkout -b new-feature 56 | ``` 57 | 58 | 6. Make any change on the branch `new-feature` then build and test your code locally. 59 | 60 | 7. Add files that you want to be committed. 61 | 62 | ```sh 63 | $ git add 64 | ``` 65 | 66 | We do not have a hard definition for commit messages but it is best practice to use the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification. 67 | 68 | 8. Enable [GPG signing](https://docs.github.com/en/github/authenticating-to-github/managing-commit-signature-verification/signing-commits) of your commits within the repo. 69 | Signing all your commits with your public key allows the community to verify it's really you. If you forgot to sign some 70 | commits that are part of the contribution, you can 71 | ask [git to rewrite your commit history](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History). 72 | 73 | ```sh 74 | $ git config commit.gpgsign true 75 | ``` 76 | 77 | 9. Use [sign-off](#sign-off) when making each of your commits. Additionally, 78 | [GPG sign](https://docs.github.com/en/github/authenticating-to-github/managing-commit-signature-verification/signing-commits) of 79 | all your commits is a must. 80 | 81 | ```sh 82 | $ git commit --signoff -S -m "Your commit message" 83 | ``` 84 | 85 | 10. [Submit](#pr-lifecycle) a pull request. 86 | 87 | ### Sign Off 88 | 89 | The sign-off is a simple line at the end of a commit message. All commits need to be signed. Your signature certifies 90 | that you wrote the code or otherwise have the right to contribute the material. First, read the 91 | [Developer Certificate of Origin](https://developercertificate.org/) (DCO) to fully understand its terms. 92 | 93 | Contributors sign-off that they adhere to these requirements by adding a `Signed-off-by` line to commit messages (as 94 | seen via `git log`): 95 | 96 | ``` 97 | Author: Joe Smith 98 | Date: Thu Feb 2 11:41:15 2018 -0800 99 | 100 | Update README 101 | 102 | Signed-off-by: Joe Smith 103 | ``` 104 | 105 | Use your real name and email (sorry, no pseudonyms or anonymous contributions). Notice the `Author` and `Signed-off-by` 106 | lines match. If they don't your PR will be rejected by the automated DCO check. 107 | 108 | If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `-s` 109 | or `--sign-off` command line option: 110 | 111 | ```sh 112 | $ git config --global user.name "Joe Smith" 113 | $ git config --global user.email "joe.smith@example.com" 114 | $ git commit -s -S -m 'Update README' 115 | ``` 116 | 117 | ### PR Lifecycle 118 | 119 | Now that you've got your [forked](#forking) branch, you can proceed to submit it. 120 | 121 | #### Submitting 122 | 123 | - It is preferred, but not required, to have a PR tied to a specific issue. There can be circumstances where if it is a 124 | quick fix then an issue might be overkill. The details provided in the PR description would suffice in this case. 125 | - The PR description or commit message should contain 126 | a [keyword](https://help.github.com/en/articles/closing-issues-using-keywords) 127 | to automatically close the related issue. 128 | - Commits should be as small as possible, while ensuring that each commit is correct independently 129 | (i.e., each commit should compile and pass tests). 130 | - Add tests and documentation relevant to the fixed bug or new feature. Code coverage should stay the same or increase 131 | for the PR to be approved. 132 | - We more than welcome PRs that are currently in progress. If a PR is a work in progress, it should be opened as 133 | a [Draft PR](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests). Once the PR is ready for 134 | review, mark it as ready to convert it to a regular PR. 135 | - After submitting, ensure all GitHub checks pass before requesting a review. Also double-check all static analysis and 136 | coverage tools show a sufficient coverage and quality level. 137 | - When creating a pull request the name of the PR must follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification. 138 | - Several GitHub Actions will be triggered automatically for each PR. 139 | If a GitHub Action fails and you do not understand the cause of that error do not hesitate to add a comment to the PR and ask the Hiero developer community for support. 140 | 141 | #### Triage 142 | 143 | - The maintainer in charge of triaging will apply the proper labels for the PR. 144 | - The maintainer can assign a reviewer, or a reviewer can assign themselves. 145 | 146 | #### Reviewing 147 | 148 | - All reviews will be completed using the GitHub review tool. 149 | - A "Comment" review should be used when there are questions about the code that should be answered, but that don't 150 | involve code changes. This type of review does not count as approval. 151 | - A "Changes Requested" review indicates that changes to the code need to be made before they will be merged. 152 | - For documentation, special attention will be paid to spelling, grammar, and clarity 153 | (whereas those things don't matter *as* much for comments in code). 154 | - Reviews are also welcome from others in the community. In the code review, a message can be added, as well as `LGTM` 155 | if the PR is good to merge. It’s also possible to add comments to specific lines in a file, for giving context to the 156 | comment. 157 | - PR owner should try to be responsive to comments by answering questions or changing code. If the owner is unsure of 158 | any comment, please ask for clarification in the PR comments. 159 | - Once all comments have been addressed and all reviewers have approved, the PR is ready to be merged. 160 | 161 | #### Merge or Close 162 | 163 | - PRs should stay open until they are merged or closed. The issue may be closed if the submitter has not been responsive 164 | for more than 30 days. This will help keep the PR queue to a manageable size and reduce noise. 165 | 166 | ## I Have a Question 167 | 168 | Before you ask a question, it is best to search for existing Issues that might help you. 169 | In case you have found a suitable issue and still need clarification, you can write your question in this issue. 170 | It is also advisable to search the internet for answers first. 171 | 172 | If you then still feel the need to ask a question and need clarification, we recommend the following: 173 | 174 | - Open an Issue. 175 | - Provide as much context as you can about what you're running into. 176 | 177 | We will then take care of the issue as soon as possible. 178 | 179 | ## Reporting Bugs Or Suggesting Enhancements 180 | 181 | If you found a bug in our code or want to suggest a new feature or improvement please create a new Issue. 182 | 183 | ## Your First Code Contribution 184 | 185 | We reserve issues for people who have never contributed to this project or any open source project in general. 186 | We know that creating a pull request (PR) is a major barrier for new contributors. 187 | The goal of issues labeled by **'good first issue'** is to help you make your first contribution. 188 | You can read about or workflows for **'good first issue'** handling [here](https://github.com/hiero-ledger/governance/blob/main/guidelines/good-first-issues.md). 189 | 190 | This does not mean that contribution is only welcome for those issues. 191 | We are happy with any contribution. 192 | The most important point is that an issue exists for the contribution. 193 | If that is not the case please create an issue for a bug or enhancement. 194 | Please comment on the given issue that you want to work on it. 195 | Once a member of the team has assigned you to the issue you can start working on it. 196 | 197 | ## Attribution 198 | This guide is based on the **contributing-gen**. [Make your own](https://github.com/bttger/contributing-gen)! 199 | -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /profile/README.md: -------------------------------------------------------------------------------- 1 | # Hiero @ Github 2 | 3 | Welcome to Hiero, the Open Source Distributed Ledger Technology of the [Linux Foundation Decentralized Trust](https://www.lfdecentralizedtrust.org). 4 | Hiero is an open-source, vendor-neutral distributed ledger technology. Hiero is used to build the [Hedera](https://hedera.com) public ledger. 5 | You can find more information at our [website](https://hiero.org). 6 | 7 | ![repository-open-graph-template-2](https://github.com/user-attachments/assets/c0a1df9c-2a13-42ec-82ba-5e0df044750e) 8 | 9 | ## Resources 10 | 11 | The following documents will help you to understand our vision, workflows and community. More documents will be added in the near future. 12 | 13 | - Our [Code of Conduct](https://www.lfdecentralizedtrust.org/code-of-conduct). 14 | - Our [CONTRIBUTING.md](https://github.com/hiero-ledger/.github/blob/main/CONTRIBUTING.md) is a good starting point if you want to contribute to Hiero. 15 | - All global maintainers of the GitHub can be found at [GLOBAL-MAINTAINERS.md](https://github.com/hiero-ledger/.github/blob/main/GLOBAL-MAINTAINERS.md). 16 | - For security related issues, please refer to our [SECURITY Policy](https://github.com/hiero-ledger/.github/blob/main/SECURITY.md). Do not post security related content, issues or discussions publicly in any repository. 17 | - All our projects are licensed under the [Apache 2.0 license](https://github.com/hiero-ledger/.github/blob/main/LICENSE.md). 18 | - Our [technical charter](https://github.com/hiero-ledger/governance/blob/main/hiero-technical-charter.md) gives an overview about our official workflows, processes and the work of the technical steering committee (TSC). 19 | - Our [project roles and groups](https://github.com/hiero-ledger/governance/blob/main/roles-and-groups.md) gives an overview of responsibilities and roles within any given project. 20 | - We provide a [transfer document](https://github.com/hiero-ledger/hiero/blob/main/transition.md) that shows the current state of the transition of Hedera projects to Hiero. 21 | - We track a [transfer document for community driven projects](https://github.com/hiero-ledger/hiero/blob/main/community-transition.md) that shows the current state of the transition of community projects to Hiero. 22 | - Our [public calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week) contains the open TSC and community meetings. 23 | 24 | ## Discord communication channels 25 | 26 | Discord is a popular, free communication platform used by many communities, including open-source projects. 27 | 28 | ### How to Join and Find the Hiero Python SDK Channel 29 | 30 | Follow these essential steps: 31 | 32 | 1. **Join the Linux Foundation Decentralized Trust (LFDT) Server:** 33 | * Click the official invite link: **[LFDT Discord](https://discord.gg/hyperledger)** 34 | * If you're new to Discord, create a free account when prompted. 35 | * Follow Discord's instructions to enter the server. 36 | 37 | 2. **Agree to Server Rules:** 38 | * Upon joining, you will likely land in a `#welcome` or `#rules` channel. 39 | * Read the server rules carefully. You **must agree** to these rules (usually via a button or emoji reaction ✅ at the bottom) to gain full access to the server channels. 40 | * Once you agree, other channels should become visible. 41 | 42 | 3. **Access any of our available channels:** 43 | 44 | | Channel Name / Join Link | Channel Purpose | 45 | | ------------------------------------------------------------------------------------------------- |-------------------------------------------------------------------------------------------------------------------------------------- | 46 | | **[#hiero-general](https://discord.com/channels/905194001349627914/1289954446712770600)** | General questions, conversations and discussions not necesarily related to a specific component. | 47 | | **[#hiero-announcements](https://discord.com/channels/905194001349627914/1283487046484234270)** | Announcements on agenda, meetings happening, blog posts, events and participation opportunities. | 48 | | **[#hiero-did-sdk-python](https://discord.com/channels/905194001349627914/1339549374782378027)** | Conversations/questions/issues/updates in https://github.com/hiero-ledger/hiero-did-sdk-python. | 49 | | **[#hiero-did-sdk-js](https://discord.com/channels/905194001349627914/1403132892007366806)** | Conversations/questions/issues/updates in https://github.com/hiero-ledger/hiero-did-sdk-js. | 50 | | **[#hiero-enterprise-java](https://discord.com/channels/905194001349627914/1370373361942663178)** | Conversations on future transfer of [hiero-enterprise-java](https://github.com/OpenElements/hiero-enterprise-java/issues/172). | 51 | | **[#hiero-hips](https://discord.com/channels/905194001349627914/1354514446898430032)** | Conversations/questions/issues/updates in [hiero-improvement-proposals](https://github.com/hiero-ledger/hiero-improvement-proposals). | 52 | | **[#hiero-maintainers](https://discord.com/channels/905194001349627914/1283487103006543952)** | Conversations, taskforce events, issues and related topic for maintainers | 53 | | **[#hiero-consensus-node](https://discord.com/channels/905194001349627914/1380936805897080862)** | Conversations/questions/issues/updates in [hiero-consensus-node](https://github.com/hiero-ledger/hiero-consensus-node). | 54 | | **[#hiero-mirror-node](https://discord.com/channels/905194001349627914/1374414879334596739)** | Conversations/questions/issues/updates in [hiero-mirror-node](https://github.com/hiero-ledger/hiero-mirror-node). | 55 | | **[#hiero-sdk-cpp](https://discord.com/channels/905194001349627914/1337424839761465364)** | Conversations/questions/issues/updates in [hiero-sdk-cpp](https://github.com/hiero-ledger/hiero-sdk-cpp). | 56 | | **[#hiero-sdk-go](https://discord.com/channels/905194001349627914/1337424630289404015)** | Conversations/questions/issues/updates in [hiero-sdk-go](https://github.com/hiero-ledger/hiero-sdk-go). | 57 | | **[#hiero-sdk-java](https://discord.com/channels/905194001349627914/1337424581652381696)** | Conversations/questions/issues/updates in [hiero-sdk-java](https://github.com/hiero-ledger/hiero-sdk-java). | 58 | | **[#hiero-sdk-js](https://discord.com/channels/905194001349627914/1337424656138899537)** | Conversations/questions/issues/updates in [hiero-sdk-js](https://github.com/hiero-ledger/hiero-sdk-js). | 59 | | **[#hiero-sdk-python](https://discord.com/channels/905194001349627914/1336494517544681563)** | Conversations/questions/issues/updates in [hiero-sdk-python](https://github.com/hiero-ledger/hiero-sdk-python). | 60 | | **[#hiero-sdk-rust](https://discord.com/channels/905194001349627914/1400196736244518982)** | Conversations/questions/issues/updates in [hiero-sdk-rust](https://github.com/hiero-ledger/hiero-sdk-rust). | 61 | | **[#hiero-sdk-swift](https://discord.com/channels/905194001349627914/1337424716238946344)** | Conversations/questions/issues/updates in [hiero-sdk-swift](https://github.com/hiero-ledger/hiero-sdk-swift). | 62 | | **[#hiero-sdk-tck](https://discord.com/channels/905194001349627914/1336034637310464031)** | Conversations/questions/issues/updates in [hiero-sdk-tck](https://github.com/hiero-ledger/hiero-sdk-tck). | 63 | | **[#hiero-solo-action](https://discord.com/channels/905194001349627914/1337046798472052776)** | Conversations/questions/issues/updates in [hiero-solo-action](https://github.com/hiero-ledger/hiero-solo-action). | 64 | | **[#solo](https://discord.com/channels/905194001349627914/1364886813017247775)** | Conversations/questions/issues/updates in [solo](https://github.com/hiero-ledger/solo). | 65 | 66 | You can also select specific channels under the "hiero" category so these channels will appear in your left navigation panel 67 | 68 | ## Open Community Meetings and TSC schedules 69 | 70 | | Community Meeting | Meeting occurrence link | Registration link | 71 | | -------------------- |-------------------------------------------------------------------------------------------------------------------| --------------------------------------------------------------------------------------------------------------------------------------- | 72 | | TSC meeting | [LFX Calendar link](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week&occurrence=1758031200) | [Register](https://zoom-lfx.platform.linuxfoundation.org/meeting/95775743341?password=c07443bf-b0e6-4a68-93f1-5c7ce9bb49ab&invite=true) | 73 | | Community Call | [LFX Calendar link](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week&occurrence=1758207600) | [Register](https://zoom-lfx.platform.linuxfoundation.org/meeting/97122675754?password=7eaa865a-2f17-4a7c-97b0-aff51933991c&invite=true) | 74 | | Python SDK | [LFX Calendar link](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week&occurrence=1758117600) | [Register](https://zoom-lfx.platform.linuxfoundation.org/meeting/92041330205?password=2f345bee-0c14-4dd5-9883-06fbc9c60581&invite=true) | 75 | | Docs | [LFX Calendar link](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week&occurrence=1757516400) | [Register](https://zoom-lfx.platform.linuxfoundation.org/meeting/96247351493?password=54a04164-8618-458d-8176-4ca21b346291&invite=true) | 76 | | Solo | [LFX Calendar link](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week&occurrence=1757433600) | [Register](https://zoom-lfx.platform.linuxfoundation.org/meeting/94695703550?password=e8819002-3f6e-4905-9916-b049f501e866&invite=true) | 77 | | Solo Action | [LFX Calendar link](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week&occurrence=1757944800) | [Register](https://zoom-lfx.platform.linuxfoundation.org/meeting/92576669768?password=8dab94bb-7315-4d37-a944-b1fa0e924741&invite=true) | 78 | | SDK | [LFX Calendar link](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week&occurrence=1757340000) | [Register](https://zoom-lfx.platform.linuxfoundation.org/meeting/94709702244?password=bcba4892-928c-47e0-9a21-e1abca95f7d3&invite=true) | 79 | | Hiero Website | [LFX Calendar link](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week&occurrence=1755529200) | [Register](https://zoom-lfx.platform.linuxfoundation.org/meeting/94831465670?password=50e11cd2-6450-4a97-b9ae-7a7585c4409b&invite=true) | 80 | | Hiero Marketing | [LFX Calendar link](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week&occurrence=1761663600) | [Register](https://zoom-lfx.platform.linuxfoundation.org/meeting/91725705912?password=57115f71-9576-46dc-90f7-98be38aade2d&invite=true) | 81 | | Monthly Maintainers | [LFX Calendar link](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week&occurrence=1761750000) | [Register](https://zoom-lfx.platform.linuxfoundation.org/meeting/99574473075?password=deff3fc9-0e80-4877-80de-91499b5480e9&invite=true) | 82 | | Hiero/Hedera Identity| [LFX Calendar link](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week&occurrence=1763049600) | [Register](https://zoom-lfx.platform.linuxfoundation.org/meeting/99097542854?password=3ee2d9c9-32de-4758-8a23-417c751bd7ab&invite=true) | 83 | | Hiero Mirror Node | [LFX Calendar link](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week&occurrence=1763053200) | [Register](https://zoom-lfx.platform.linuxfoundation.org/meeting/94618152832?password=3b037576-2aab-4f7e-ab24-acf9ca2c3734&invite=true) | 84 | 85 | ## Meeting Recordings 86 | 87 | There are two ways to access past meeting recordings: 88 | 89 | 1. Via [LFX Individual Dashboard](https://openprofile.dev/) - Create and complete your profile. Look for past meeting recordings under [My Meetings](https://openprofile.dev/my-meetings) section. 90 | Recordings of meetings you are registered to will appear in the list. If you need to be registered to a specific meeting series, register using the button above or let LF Staff know via [Discord](https://discord.lfdecentralizedtrust.org/). 91 | 2. Via [Hiero Calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week) - Browse meeting recordings in the calendar. Recordings appear aprox an hour after the meeting has ended. 92 | 93 | ## LFX Tooling 94 | 95 | LFX is Linux Foundation’s comprehensive, free-to-use open source project collaboration platform designed to help developers, maintainers, organizations, and contributors streamline and scale open source initiatives. 96 | Linux Foundation hosted projects gain valuable support from these tools for streamlined project monitoring and administration. 97 | [Learn more about LFX](https://lfx.linuxfoundation.org/). 98 | 99 | - [LFX Individual Dashboard](https://openprofile.dev/) - Is a self-service hub for all of your open source activity and great tool to easily access past meeting recordings. [Read More](https://docs.linuxfoundation.org/lfx/my-profile). 100 | - [LFX Insights](https://insights.linuxfoundation.org/) - This tool helps developers and their organizations make smarter decisions about the open source projects by tracking their project's health.[Read More](https://insights.linuxfoundation.org/docs/introduction/what-is-insights/) [Contribute!](https://github.com/linuxfoundation/insights). 101 | -------------------------------------------------------------------------------- /.gitvote.yml: -------------------------------------------------------------------------------- 1 | # The audit page lists all the votes recorded for the repository. It can be 2 | # useful to provide transparency on the voting history of a repository. By 3 | # default, the audit page is disabled. To enable it, the audit section must be 4 | # included in the configuration file, with the `enabled` field set to true. 5 | # 6 | # Please note that this page is publicly accessible, so anyone will be able 7 | # to see all votes recorded for the repository. 8 | # 9 | # Once you have enabled it, the audit page will be available at: 10 | # 11 | # https://gitvote.com/audit/OWNER/REPO 12 | audit: 13 | enabled: true 14 | 15 | # Automation (optional) 16 | # 17 | # Create votes automatically on PRs when any of the files affected by the PR 18 | # match any of the patterns provided. Patterns must follow the gitignore 19 | # format (https://git-scm.com/docs/gitignore#_pattern_format). 20 | # 21 | # Each automation rule must include a list of patterns and the profile to use 22 | # when creating the vote. This allows creating votes automatically using the 23 | # desired configuration based on the patterns matched. Rules are processed in 24 | # the order provided, and the first match wins. 25 | # 26 | # automation: 27 | # enabled: true 28 | # rules: 29 | # - patterns: 30 | # - "README.md" 31 | # - "*.txt" 32 | # profile: default 33 | # 34 | automation: 35 | enabled: false 36 | rules: 37 | - patterns: [] 38 | profile: default 39 | 40 | # Configuration profiles (required) 41 | # 42 | # A configuration profile defines some properties of a vote, like its duration, 43 | # the pass threshold or the users who have a binding vote. It's possible to 44 | # define multiple configuration profiles, each with a different set of settings. 45 | # 46 | profiles: 47 | # Default configuration profile 48 | # 49 | # This profile will be used with votes created with the /vote command 50 | default: 51 | # Voting duration (required) 52 | # 53 | # How long the vote will be open 54 | # 55 | # Units supported (can be combined as in 1hour 30mins): 56 | # 57 | # minutes | minute | mins | min | m 58 | # hours | hour | hrs | hrs | h 59 | # days | day | d 60 | # weeks | week | w 61 | # 62 | duration: 1w 63 | 64 | # Pass threshold (required) 65 | # 66 | # Percentage of votes in favor required to pass the vote 67 | # 68 | # The percentage is calculated based on the number of votes in favor and the 69 | # number of allowed voters (see allowed_voters field below for more details). 70 | pass_threshold: 66.66 71 | 72 | # Allowed voters (optional) 73 | # 74 | # List of GitHub teams and users who have binding votes 75 | # 76 | # If no teams or users are provided, all repository collaborators will be 77 | # allowed to vote. For organization-owned repositories, the list of 78 | # collaborators includes outside collaborators, organization members that 79 | # are direct collaborators, organization members with access through team 80 | # memberships, organization members with access through default organization 81 | # permissions, and organization owners. 82 | # 83 | # By default, teams' members with the maintainer role are allowed to vote 84 | # as well. By using the `exclude_team_maintainers` option, it's possible to 85 | # modify this behavior so that only teams' members with the member role are 86 | # considered allowed voters. Please note that this option only applies to 87 | # the teams explicitly listed in `allowed_voters/teams`. 88 | # 89 | # Teams names must be provided without the organization prefix. 90 | # 91 | # allowed_voters: 92 | # teams: 93 | # - team1 94 | # users: 95 | # - cynthia-sg 96 | # - tegioz 97 | # exclude_team_maintainers: false 98 | # 99 | allowed_voters: 100 | teams: 101 | - github-maintainers 102 | - tsc 103 | - lf-staff 104 | 105 | # Periodic status check 106 | # 107 | # GitVote allows checking the status of a vote in progress manually by 108 | # calling the /check-vote command. The periodic status check option makes 109 | # it possible to automate the execution of status checks periodically. The 110 | # vote status will be published to the corresponding issue or pull request, 111 | # the same way as if the /check-vote command would have been called 112 | # manually. 113 | # 114 | # When this option is enabled, while the vote is open, a status check will 115 | # be run automatically using the frequency configured. Please note that the 116 | # hard limit of one status check per day still applies, so if the command 117 | # has been called manually the automatic periodic run may be delayed. 118 | # Automatic status checks won't be run if the vote will be closed within 119 | # the next hour. 120 | # 121 | # Units supported: 122 | # 123 | # - day / days 124 | # - week / weeks 125 | # 126 | # As an example, using a value of "5 days" would mean that 5 days after the 127 | # vote was created, and every 5 days after that, an automatic status check 128 | # will be run. 129 | # 130 | # periodic_status_check: "5 days" 131 | # 132 | periodic_status_check: "1 day" 133 | 134 | # Close on passing 135 | # 136 | # By default, votes remain open for the configured duration. Sometimes, 137 | # specially on votes that stay open for a long time, it may be preferable 138 | # to close a vote automatically once the passing threshold has been met. 139 | # The close on passing feature makes this possible. Open votes where this 140 | # feature has been enabled will be checked once daily and, if GitVote 141 | # detects that the vote has passed, it will automatically close it. 142 | # 143 | # close_on_passing: true 144 | # 145 | close_on_passing: false 146 | 147 | # Close on passing minimum wait 148 | # 149 | # When the close on passing feature is activated, voting will conclude once 150 | # the pass threshold is met. However, there may be instances where it is 151 | # preferable to implement a minimum wait time, even if the vote would 152 | # already pass. This allows participants sufficient opportunity to engage 153 | # and reflect before the vote is automatically finalized. 154 | # 155 | # Units supported: 156 | # 157 | # - day / days 158 | # - week / weeks 159 | # 160 | # close_on_passing_min_wait: "1 week" 161 | # 162 | close_on_passing_min_wait: null 163 | 164 | # Announcements 165 | # 166 | # GitVote can announce the results of a vote when it is closed on GitHub 167 | # discussions. This feature won't be enabled if this configuration section 168 | # is not provided. The slug of the category where the announcement will be 169 | # posted to must be specified (i.e. announcements). 170 | # 171 | # announcements: 172 | # discussions: 173 | # category: announcements 174 | # 175 | # announcements: 176 | # discussions: 177 | # category: null 178 | 179 | allMembers: 180 | duration: 1w 181 | pass_threshold: 66.66 182 | close_on_passing: true 183 | close_on_passing_min_wait: "3 days" 184 | periodic_status_check: "1 day" 185 | 186 | allMaintainers: 187 | duration: 2w 188 | pass_threshold: 66.66 189 | periodic_status_check: "2 days" 190 | close_on_passing: false 191 | allowed_voters: 192 | teams: 193 | - github-maintainers 194 | - hiero-mirror-node-maintainers 195 | - hiero-local-node-maintainers 196 | - hiero-sdk-swift-maintainers 197 | - hiero-sdk-python-maintainers 198 | - hiero-did-sdk-js-maintainers 199 | - hiero-did-sdk-python-maintainers 200 | - hiero-sdk-rust-maintainers 201 | - hiero-sdk-java-maintainers 202 | - hiero-sdk-js-maintainers 203 | - hiero-sdk-cpp-maintainers 204 | - hiero-sdk-tck-maintainers 205 | - hiero-sdk-go-maintainers 206 | - hiero-solo-action-maintainers 207 | - hiero-gradle-conventions-maintainers 208 | - hiero-block-node-maintainers 209 | - hiero-consensus-node-maintainers 210 | - hiero-protobufs-maintainers 211 | - hiero-cli-maintainers 212 | - hiero-docs-maintainers 213 | - hiero-mirror-node-explorer-maintainers 214 | - hiero-json-rpc-relay-maintainers 215 | - hiero-hederium-maintainers 216 | - hiero-identity-standards-maintainers 217 | - hiero-improvement-proposals-maintainers 218 | - hiero-website-maintainers 219 | - homebrew-tools-maintainers 220 | - security-maintainers 221 | - sdk-collaboration-hub-maintainers 222 | - solo-maintainers 223 | - tsc-eligibility-check-maintainers 224 | - hashgraph-online-standards-sdk-js-maintainers 225 | 226 | githubMaintainers: 227 | duration: 2w 228 | pass_threshold: 66.66 229 | periodic_status_check: "2 days" 230 | close_on_passing: false 231 | allowed_voters: 232 | teams: 233 | - github-maintainers 234 | 235 | hieroMirrorNodeMaintainers: 236 | duration: 2w 237 | pass_threshold: 66.66 238 | periodic_status_check: "2 days" 239 | close_on_passing: false 240 | allowed_voters: 241 | teams: 242 | - hiero-mirror-node-maintainers 243 | 244 | hieroLocalNodeMaintainers: 245 | duration: 2w 246 | pass_threshold: 66.66 247 | periodic_status_check: "2 days" 248 | close_on_passing: false 249 | allowed_voters: 250 | teams: 251 | - hiero-local-node-maintainers 252 | 253 | hieroSdkPythonMaintainers: 254 | duration: 2w 255 | pass_threshold: 66.66 256 | periodic_status_check: "2 days" 257 | close_on_passing: false 258 | allowed_voters: 259 | teams: 260 | - hiero-sdk-python-maintainers 261 | 262 | hieroSdkSwiftMaintainers: 263 | duration: 2w 264 | pass_threshold: 66.66 265 | periodic_status_check: "2 days" 266 | close_on_passing: false 267 | allowed_voters: 268 | teams: 269 | - hiero-sdk-swift-maintainers 270 | 271 | hieroDidSdkPythonMaintainers: 272 | duration: 2w 273 | pass_threshold: 66.66 274 | periodic_status_check: "2 days" 275 | close_on_passing: false 276 | allowed_voters: 277 | teams: 278 | - hiero-did-sdk-python-maintainers 279 | 280 | hieroSdkRustMaintainers: 281 | duration: 2w 282 | pass_threshold: 66.66 283 | periodic_status_check: "2 days" 284 | close_on_passing: false 285 | allowed_voters: 286 | teams: 287 | - hiero-sdk-rust-maintainers 288 | 289 | hieroSdkJavaMaintainers: 290 | duration: 2w 291 | pass_threshold: 66.66 292 | periodic_status_check: "2 days" 293 | close_on_passing: false 294 | allowed_voters: 295 | teams: 296 | - hiero-sdk-java-maintainers 297 | 298 | hieroSdkJsMaintainers: 299 | duration: 2w 300 | pass_threshold: 66.66 301 | periodic_status_check: "2 days" 302 | close_on_passing: false 303 | allowed_voters: 304 | teams: 305 | - hiero-sdk-js-maintainers 306 | 307 | hieroSdkCppMaintainers: 308 | duration: 2w 309 | pass_threshold: 66.66 310 | periodic_status_check: "2 days" 311 | close_on_passing: false 312 | allowed_voters: 313 | teams: 314 | - hiero-sdk-cpp-maintainers 315 | 316 | hieroSdkTckMaintainers: 317 | duration: 2w 318 | pass_threshold: 66.66 319 | periodic_status_check: "2 days" 320 | close_on_passing: false 321 | allowed_voters: 322 | teams: 323 | - hiero-sdk-tck-maintainers 324 | 325 | hieroSdkGoMaintainers: 326 | duration: 2w 327 | pass_threshold: 66.66 328 | periodic_status_check: "2 days" 329 | close_on_passing: false 330 | allowed_voters: 331 | teams: 332 | - hiero-sdk-go-maintainers 333 | 334 | hieroSoloActionMaintainers: 335 | duration: 2w 336 | pass_threshold: 66.66 337 | periodic_status_check: "2 days" 338 | close_on_passing: false 339 | allowed_voters: 340 | teams: 341 | - hiero-solo-action-maintainers 342 | 343 | hieroGradleConventionsMaintainers: 344 | duration: 2w 345 | pass_threshold: 66.66 346 | periodic_status_check: "2 days" 347 | close_on_passing: false 348 | allowed_voters: 349 | teams: 350 | - hiero-gradle-conventions-maintainers 351 | 352 | hieroBlockNodeMaintainers: 353 | duration: 2w 354 | pass_threshold: 66.66 355 | periodic_status_check: "2 days" 356 | close_on_passing: false 357 | allowed_voters: 358 | teams: 359 | - hiero-block-node-maintainers 360 | 361 | hieroConsensusNodeMaintainers: 362 | duration: 2w 363 | pass_threshold: 66.66 364 | periodic_status_check: "2 days" 365 | close_on_passing: false 366 | allowed_voters: 367 | teams: 368 | - hiero-consensus-node-maintainers 369 | 370 | hieroProtobufsMaintainers: 371 | duration: 2w 372 | pass_threshold: 66.66 373 | periodic_status_check: "2 days" 374 | close_on_passing: false 375 | allowed_voters: 376 | teams: 377 | - hiero-protobufs-maintainers 378 | 379 | hieroCliMaintainers: 380 | duration: 2w 381 | pass_threshold: 66.66 382 | periodic_status_check: "2 days" 383 | close_on_passing: false 384 | allowed_voters: 385 | teams: 386 | - hiero-cli-maintainers 387 | 388 | hieroDocsMaintainers: 389 | duration: 2w 390 | pass_threshold: 66.66 391 | periodic_status_check: "2 days" 392 | close_on_passing: false 393 | allowed_voters: 394 | teams: 395 | - hiero-docs-maintainers 396 | 397 | hieroMirrorNodeExplorerMaintainers: 398 | duration: 2w 399 | pass_threshold: 66.66 400 | periodic_status_check: "2 days" 401 | close_on_passing: false 402 | allowed_voters: 403 | teams: 404 | - hiero-mirror-node-explorer-maintainers 405 | 406 | hieroJsonRpcRelayMaintainers: 407 | duration: 2w 408 | pass_threshold: 66.66 409 | periodic_status_check: "2 days" 410 | close_on_passing: false 411 | allowed_voters: 412 | teams: 413 | - hiero-json-rpc-relay-maintainers 414 | 415 | hieroHederiumMaintainers: 416 | duration: 2w 417 | pass_threshold: 66.66 418 | periodic_status_check: "2 days" 419 | close_on_passing: false 420 | allowed_voters: 421 | teams: 422 | - hiero-hederium-maintainers 423 | 424 | hieroIdentityStandardsMaintainers: 425 | duration: 2w 426 | pass_threshold: 66.66 427 | periodic_status_check: "2 days" 428 | close_on_passing: false 429 | allowed_voters: 430 | teams: 431 | - hiero-identity-standards-maintainers 432 | 433 | hieroImprovementProposalsMaintainers: 434 | duration: 2w 435 | pass_threshold: 66.66 436 | periodic_status_check: "2 days" 437 | close_on_passing: false 438 | allowed_voters: 439 | teams: 440 | - hiero-improvement-proposals-maintainers 441 | 442 | hieroWebsiteMaintainers: 443 | duration: 2w 444 | pass_threshold: 66.66 445 | periodic_status_check: "2 days" 446 | close_on_passing: false 447 | allowed_voters: 448 | teams: 449 | - hiero-website-maintainers 450 | 451 | homebrewToolsMaintainers: 452 | duration: 2w 453 | pass_threshold: 66.66 454 | periodic_status_check: "2 days" 455 | close_on_passing: false 456 | allowed_voters: 457 | teams: 458 | - homebrew-tools-maintainers 459 | 460 | securityMaintainers: 461 | duration: 2w 462 | pass_threshold: 66.66 463 | periodic_status_check: "2 days" 464 | close_on_passing: false 465 | allowed_voters: 466 | teams: 467 | - security-maintainers 468 | 469 | sdkCollaborationHubMaintainers: 470 | duration: 2w 471 | pass_threshold: 66.66 472 | periodic_status_check: "2 days" 473 | close_on_passing: false 474 | allowed_voters: 475 | teams: 476 | - sdk-collaboration-hub-maintainers 477 | 478 | soloMaintainers: 479 | duration: 2w 480 | pass_threshold: 66.66 481 | periodic_status_check: "2 days" 482 | close_on_passing: false 483 | allowed_voters: 484 | teams: 485 | - solo-maintainers 486 | 487 | tscEligibilityCheckMaintainers: 488 | duration: 2w 489 | pass_threshold: 66.66 490 | periodic_status_check: "2 days" 491 | close_on_passing: false 492 | allowed_voters: 493 | teams: 494 | - tsc-eligibility-check-maintainers 495 | 496 | hashgraphOnlineStandardsSdkJsMaintainers: 497 | duration: 2w 498 | pass_threshold: 66.66 499 | periodic_status_check: "2 days" 500 | close_on_passing: false 501 | allowed_voters: 502 | teams: 503 | - hashgraph-online-standards-sdk-js-maintainers 504 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | ######################################################################################################################## 2 | ## Autogenerated Definitions - DO NOT EDIT THIS SECTION. Instead, edit the section below named "Custom Definitions". ## 3 | ######################################################################################################################## 4 | 5 | ### Maven template 6 | target/ 7 | pom.xml.tag 8 | pom.xml.releaseBackup 9 | pom.xml.versionsBackup 10 | pom.xml.next 11 | release.properties 12 | dependency-reduced-pom.xml 13 | buildNumber.properties 14 | .mvn/timing.properties 15 | # https://github.com/takari/maven-wrapper#usage-without-binary-jar 16 | .mvn/wrapper/maven-wrapper.jar 17 | 18 | # Eclipse m2e generated files 19 | # Eclipse Core 20 | .project 21 | # JDT-specific (Eclipse Java Development Tools) 22 | .classpath 23 | 24 | ### MonoDevelop template 25 | #User Specific 26 | *.userprefs 27 | *.usertasks 28 | 29 | #Mono Project Files 30 | *.pidb 31 | *.resources 32 | test-results/ 33 | 34 | ### NotepadPP template 35 | # Notepad++ backups # 36 | *.bak 37 | 38 | ### VisualStudioCode template 39 | .vscode/* 40 | !.vscode/settings.json 41 | !.vscode/tasks.json 42 | !.vscode/launch.json 43 | !.vscode/extensions.json 44 | !.vscode/*.code-snippets 45 | 46 | # Local History for Visual Studio Code 47 | .history/ 48 | 49 | # Built Visual Studio Code Extensions 50 | *.vsix 51 | 52 | ### Kate template 53 | # Swap Files # 54 | .*.kate-swp 55 | .swp.* 56 | 57 | ### Diff template 58 | *.patch 59 | *.diff 60 | 61 | ### Eclipse template 62 | .metadata 63 | bin/ 64 | tmp/ 65 | *.tmp 66 | *.swp 67 | *~.nib 68 | local.properties 69 | .settings/ 70 | .loadpath 71 | .recommenders 72 | 73 | # External tool builders 74 | .externalToolBuilders/ 75 | 76 | # Locally stored "Eclipse launch configurations" 77 | *.launch 78 | 79 | # PyDev specific (Python IDE for Eclipse) 80 | *.pydevproject 81 | 82 | # CDT-specific (C/C++ Development Tooling) 83 | .cproject 84 | 85 | # CDT- autotools 86 | .autotools 87 | 88 | # Java annotation processor (APT) 89 | .factorypath 90 | 91 | # PDT-specific (PHP Development Tools) 92 | .buildpath 93 | 94 | # sbteclipse plugin 95 | .target 96 | 97 | # Tern plugin 98 | .tern-project 99 | 100 | # TeXlipse plugin 101 | .texlipse 102 | 103 | # STS (Spring Tool Suite) 104 | .springBeans 105 | 106 | # Code Recommenders 107 | .recommenders/ 108 | 109 | # Annotation Processing 110 | .apt_generated/ 111 | .apt_generated_test/ 112 | 113 | # Scala IDE specific (Scala & Java development for Eclipse) 114 | .cache-main 115 | .scala_dependencies 116 | .worksheet 117 | 118 | # Uncomment this line if you wish to ignore the project description file. 119 | # Typically, this file would be tracked if it contains build/dependency configurations: 120 | #.project 121 | 122 | ### Node template 123 | # Logs 124 | logs 125 | *.log 126 | npm-debug.log* 127 | yarn-debug.log* 128 | yarn-error.log* 129 | lerna-debug.log* 130 | .pnpm-debug.log* 131 | 132 | # Diagnostic reports (https://nodejs.org/api/report.html) 133 | report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json 134 | 135 | # Runtime data 136 | pids 137 | *.pid 138 | *.seed 139 | *.pid.lock 140 | 141 | # Directory for instrumented libs generated by jscoverage/JSCover 142 | lib-cov 143 | 144 | # Coverage directory used by tools like istanbul 145 | coverage 146 | *.lcov 147 | 148 | # nyc test coverage 149 | .nyc_output 150 | 151 | # Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files) 152 | .grunt 153 | 154 | # Bower dependency directory (https://bower.io/) 155 | bower_components 156 | 157 | # node-waf configuration 158 | .lock-wscript 159 | 160 | # Compiled binary addons (https://nodejs.org/api/addons.html) 161 | build/Release 162 | 163 | # Dependency directories 164 | node_modules/ 165 | jspm_packages/ 166 | 167 | # Snowpack dependency directory (https://snowpack.dev/) 168 | web_modules/ 169 | 170 | # TypeScript cache 171 | *.tsbuildinfo 172 | 173 | # Optional npm cache directory 174 | .npm 175 | 176 | # Optional eslint cache 177 | .eslintcache 178 | 179 | # Optional stylelint cache 180 | .stylelintcache 181 | 182 | # Microbundle cache 183 | .rpt2_cache/ 184 | .rts2_cache_cjs/ 185 | .rts2_cache_es/ 186 | .rts2_cache_umd/ 187 | 188 | # Optional REPL history 189 | .node_repl_history 190 | 191 | # Output of 'npm pack' 192 | *.tgz 193 | 194 | # Yarn Integrity file 195 | .yarn-integrity 196 | 197 | # dotenv environment variable files 198 | .env 199 | .env.development.local 200 | .env.test.local 201 | .env.production.local 202 | .env.local 203 | 204 | # parcel-bundler cache (https://parceljs.org/) 205 | .cache 206 | .parcel-cache 207 | 208 | # Next.js build output 209 | .next 210 | out 211 | 212 | # Nuxt.js build / generate output 213 | .nuxt 214 | dist 215 | 216 | # Gatsby files 217 | .cache/ 218 | # Comment in the public line in if your project uses Gatsby and not Next.js 219 | # https://nextjs.org/blog/next-9-1#public-directory-support 220 | # public 221 | 222 | # vuepress build output 223 | .vuepress/dist 224 | 225 | # vuepress v2.x temp and cache directory 226 | .temp 227 | 228 | # Docusaurus cache and generated files 229 | .docusaurus 230 | 231 | # Serverless directories 232 | .serverless/ 233 | 234 | # FuseBox cache 235 | .fusebox/ 236 | 237 | # DynamoDB Local files 238 | .dynamodb/ 239 | 240 | # TernJS port file 241 | .tern-port 242 | 243 | # Stores VSCode versions used for testing VSCode extensions 244 | .vscode-test 245 | 246 | # yarn v2 247 | .yarn/cache 248 | .yarn/unplugged 249 | .yarn/build-state.yml 250 | .yarn/install-state.gz 251 | .pnp.* 252 | 253 | ### Backup template 254 | *.gho 255 | *.ori 256 | *.orig 257 | 258 | ### PuTTY template 259 | # Private key 260 | *.ppk 261 | 262 | ### Windows template 263 | # Windows thumbnail cache files 264 | Thumbs.db 265 | Thumbs.db:encryptable 266 | ehthumbs.db 267 | ehthumbs_vista.db 268 | 269 | # Dump file 270 | *.stackdump 271 | 272 | # Folder config file 273 | [Dd]esktop.ini 274 | 275 | # Recycle Bin used on file shares 276 | $RECYCLE.BIN/ 277 | 278 | # Windows Installer files 279 | *.cab 280 | *.msi 281 | *.msix 282 | *.msm 283 | *.msp 284 | 285 | # Windows shortcuts 286 | *.lnk 287 | 288 | ### SublimeText template 289 | # Cache files for Sublime Text 290 | *.tmlanguage.cache 291 | *.tmPreferences.cache 292 | *.stTheme.cache 293 | 294 | # Workspace files are user-specific 295 | *.sublime-workspace 296 | 297 | # Project files should be checked into the repository, unless a significant 298 | # proportion of contributors will probably not be using Sublime Text 299 | # *.sublime-project 300 | 301 | # SFTP configuration file 302 | sftp-config.json 303 | sftp-config-alt*.json 304 | 305 | # Package control specific files 306 | Package Control.last-run 307 | Package Control.ca-list 308 | Package Control.ca-bundle 309 | Package Control.system-ca-bundle 310 | Package Control.cache/ 311 | Package Control.ca-certs/ 312 | Package Control.merged-ca-bundle 313 | Package Control.user-ca-bundle 314 | oscrypto-ca-bundle.crt 315 | bh_unicode_properties.cache 316 | 317 | # Sublime-github package stores a github token in this file 318 | # https://packagecontrol.io/packages/sublime-github 319 | GitHub.sublime-settings 320 | 321 | ### MicrosoftOffice template 322 | 323 | # Word temporary 324 | ~$*.doc* 325 | 326 | # Word Auto Backup File 327 | Backup of *.doc* 328 | 329 | # Excel temporary 330 | ~$*.xls* 331 | 332 | # Excel Backup File 333 | *.xlk 334 | 335 | # PowerPoint temporary 336 | ~$*.ppt* 337 | 338 | # Visio autosave temporary files 339 | *.~vsd* 340 | 341 | ### JetBrains template 342 | # Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio, WebStorm and Rider 343 | # Reference: https://intellij-support.jetbrains.com/hc/en-us/articles/206544839 344 | 345 | # User-specific stuff 346 | .idea/**/workspace.xml 347 | .idea/**/tasks.xml 348 | .idea/**/usage.statistics.xml 349 | .idea/**/dictionaries 350 | .idea/**/shelf 351 | 352 | # AWS User-specific 353 | .idea/**/aws.xml 354 | 355 | # Generated files 356 | .idea/**/contentModel.xml 357 | 358 | # Sensitive or high-churn files 359 | .idea/**/dataSources/ 360 | .idea/**/dataSources.ids 361 | .idea/**/dataSources.local.xml 362 | .idea/**/sqlDataSources.xml 363 | .idea/**/dynamic.xml 364 | .idea/**/uiDesigner.xml 365 | .idea/**/dbnavigator.xml 366 | 367 | # Gradle 368 | .idea/**/gradle.xml 369 | .idea/**/libraries 370 | 371 | # Gradle and Maven with auto-import 372 | # When using Gradle or Maven with auto-import, you should exclude module files, 373 | # since they will be recreated, and may cause churn. Uncomment if using 374 | # auto-import. 375 | .idea/artifacts 376 | .idea/compiler.xml 377 | .idea/jarRepositories.xml 378 | .idea/modules.xml 379 | .idea/*.iml 380 | .idea/modules 381 | *.iml 382 | *.ipr 383 | 384 | # CMake 385 | cmake-build-*/ 386 | 387 | # Mongo Explorer plugin 388 | .idea/**/mongoSettings.xml 389 | 390 | # File-based project format 391 | *.iws 392 | 393 | # IntelliJ 394 | out/ 395 | 396 | # mpeltonen/sbt-idea plugin 397 | .idea_modules/ 398 | 399 | # JIRA plugin 400 | atlassian-ide-plugin.xml 401 | 402 | # Cursive Clojure plugin 403 | .idea/replstate.xml 404 | 405 | # SonarLint plugin 406 | .idea/sonarlint/ 407 | 408 | # Crashlytics plugin (for Android Studio and IntelliJ) 409 | com_crashlytics_export_strings.xml 410 | crashlytics.properties 411 | crashlytics-build.properties 412 | fabric.properties 413 | 414 | # Editor-based Rest Client 415 | .idea/httpRequests 416 | 417 | # Android studio 3.1+ serialized cache file 418 | .idea/caches/build_file_checksums.ser 419 | 420 | ### LibreOffice template 421 | # LibreOffice locks 422 | .~lock.*# 423 | 424 | ### Archives template 425 | # It's better to unpack these files and commit the raw source because 426 | # git has its own built in compression methods. 427 | *.7z 428 | *.jar 429 | *.rar 430 | *.zip 431 | *.gz 432 | *.gzip 433 | *.bzip 434 | *.bzip2 435 | *.bz2 436 | *.xz 437 | *.lzma 438 | *.xar 439 | 440 | # Packing-only formats 441 | *.iso 442 | *.tar 443 | 444 | # Package management formats 445 | *.dmg 446 | *.xpi 447 | *.gem 448 | *.egg 449 | *.deb 450 | *.rpm 451 | *.txz 452 | 453 | ### Dropbox template 454 | # Dropbox settings and caches 455 | .dropbox 456 | .dropbox.attr 457 | .dropbox.cache 458 | 459 | ### macOS template 460 | # General 461 | .DS_Store 462 | .AppleDouble 463 | .LSOverride 464 | 465 | # Icon must end with two \r 466 | Icon 467 | 468 | # Thumbnails 469 | ._* 470 | 471 | # Files that might appear in the root of a volume 472 | .DocumentRevisions-V100 473 | .fseventsd 474 | .Spotlight-V100 475 | .TemporaryItems 476 | .Trashes 477 | .VolumeIcon.icns 478 | .com.apple.timemachine.donotpresent 479 | 480 | # Directories potentially created on remote AFP share 481 | .AppleDB 482 | .AppleDesktop 483 | Network Trash Folder 484 | Temporary Items 485 | .apdisk 486 | 487 | ### Java template 488 | # Compiled class file 489 | *.class 490 | 491 | # Log file 492 | 493 | # BlueJ files 494 | *.ctxt 495 | 496 | # Mobile Tools for Java (J2ME) 497 | .mtj.tmp/ 498 | 499 | # Package Files # 500 | *.war 501 | *.nar 502 | *.ear 503 | *.tar.gz 504 | 505 | # virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml 506 | hs_err_pid* 507 | replay_pid* 508 | 509 | ### Kotlin template 510 | # Compiled class file 511 | 512 | # Log file 513 | 514 | # BlueJ files 515 | 516 | # Mobile Tools for Java (J2ME) 517 | 518 | # Package Files # 519 | 520 | # virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml 521 | 522 | ### OpenSSL template 523 | # OpenSSL-related files best not committed 524 | 525 | ## Certificate Authority 526 | *.ca 527 | 528 | ## Certificate 529 | *.crt 530 | 531 | ## Certificate Sign Request 532 | *.csr 533 | 534 | ## Certificate 535 | *.der 536 | 537 | ## Key database file 538 | *.kdb 539 | 540 | ## OSCP request data 541 | *.org 542 | 543 | ## PKCS #12 544 | *.p12 545 | 546 | ## PEM-encoded certificate data 547 | *.pem 548 | 549 | ## Random number seed 550 | *.rnd 551 | 552 | ## SSLeay data 553 | *.ssleay 554 | 555 | ## S/MIME message 556 | *.smime 557 | 558 | ### NetBeans template 559 | **/nbproject/private/ 560 | **/nbproject/Makefile-*.mk 561 | **/nbproject/Package-*.bash 562 | build/ 563 | nbbuild/ 564 | dist/ 565 | nbdist/ 566 | .nb-gradle/ 567 | 568 | ### Linux template 569 | *~ 570 | 571 | # temporary files which can be created if a process still has a handle open of a deleted file 572 | .fuse_hidden* 573 | 574 | # KDE directory preferences 575 | .directory 576 | 577 | # Linux trash folder which might appear on any partition or disk 578 | .Trash-* 579 | 580 | # .nfs files are created when an open file is removed but is still being accessed 581 | .nfs* 582 | 583 | ### TextMate template 584 | *.tmproj 585 | *.tmproject 586 | tmtags 587 | 588 | ### VisualStudio template 589 | ## Ignore Visual Studio temporary files, build results, and 590 | ## files generated by popular Visual Studio add-ons. 591 | ## 592 | ## Get latest from https://github.com/github/gitignore/blob/main/VisualStudio.gitignore 593 | 594 | # User-specific files 595 | *.rsuser 596 | *.suo 597 | *.user 598 | *.userosscache 599 | *.sln.docstates 600 | 601 | # User-specific files (MonoDevelop/Xamarin Studio) 602 | 603 | # Mono auto generated files 604 | mono_crash.* 605 | 606 | # Build results 607 | [Dd]ebug/ 608 | [Dd]ebugPublic/ 609 | [Rr]elease/ 610 | [Rr]eleases/ 611 | x64/ 612 | x86/ 613 | [Ww][Ii][Nn]32/ 614 | [Aa][Rr][Mm]/ 615 | [Aa][Rr][Mm]64/ 616 | bld/ 617 | [Bb]in/ 618 | [Oo]bj/ 619 | [Ll]og/ 620 | [Ll]ogs/ 621 | 622 | # Visual Studio 2015/2017 cache/options directory 623 | .vs/ 624 | # Uncomment if you have tasks that create the project's static files in wwwroot 625 | #wwwroot/ 626 | 627 | # Visual Studio 2017 auto generated files 628 | Generated\ Files/ 629 | 630 | # MSTest test Results 631 | [Tt]est[Rr]esult*/ 632 | [Bb]uild[Ll]og.* 633 | 634 | # NUnit 635 | *.VisualState.xml 636 | TestResult.xml 637 | nunit-*.xml 638 | 639 | # Build Results of an ATL Project 640 | [Dd]ebugPS/ 641 | [Rr]eleasePS/ 642 | dlldata.c 643 | 644 | # Benchmark Results 645 | BenchmarkDotNet.Artifacts/ 646 | 647 | # .NET Core 648 | project.lock.json 649 | project.fragment.lock.json 650 | artifacts/ 651 | 652 | # ASP.NET Scaffolding 653 | ScaffoldingReadMe.txt 654 | 655 | # StyleCop 656 | StyleCopReport.xml 657 | 658 | # Files built by Visual Studio 659 | *_i.c 660 | *_p.c 661 | *_h.h 662 | *.ilk 663 | *.meta 664 | *.obj 665 | *.iobj 666 | *.pch 667 | *.pdb 668 | *.ipdb 669 | *.pgc 670 | *.pgd 671 | *.rsp 672 | *.sbr 673 | *.tlb 674 | *.tli 675 | *.tlh 676 | *.tmp_proj 677 | *_wpftmp.csproj 678 | *.tlog 679 | *.vspscc 680 | *.vssscc 681 | .builds 682 | *.svclog 683 | *.scc 684 | 685 | # Chutzpah Test files 686 | _Chutzpah* 687 | 688 | # Visual C++ cache files 689 | ipch/ 690 | *.aps 691 | *.ncb 692 | *.opendb 693 | *.opensdf 694 | *.sdf 695 | *.cachefile 696 | *.VC.db 697 | *.VC.VC.opendb 698 | 699 | # Visual Studio profiler 700 | *.psess 701 | *.vsp 702 | *.vspx 703 | *.sap 704 | 705 | # Visual Studio Trace Files 706 | *.e2e 707 | 708 | # TFS 2012 Local Workspace 709 | $tf/ 710 | 711 | # Guidance Automation Toolkit 712 | *.gpState 713 | 714 | # ReSharper is a .NET coding add-in 715 | _ReSharper*/ 716 | *.[Rr]e[Ss]harper 717 | *.DotSettings.user 718 | 719 | # TeamCity is a build add-in 720 | _TeamCity* 721 | 722 | # DotCover is a Code Coverage Tool 723 | *.dotCover 724 | 725 | # AxoCover is a Code Coverage Tool 726 | .axoCover/* 727 | !.axoCover/settings.json 728 | 729 | # Coverlet is a free, cross platform Code Coverage Tool 730 | coverage*.json 731 | coverage*.xml 732 | coverage*.info 733 | 734 | # Visual Studio code coverage results 735 | *.coverage 736 | *.coveragexml 737 | 738 | # NCrunch 739 | _NCrunch_* 740 | .*crunch*.local.xml 741 | nCrunchTemp_* 742 | 743 | # MightyMoose 744 | *.mm.* 745 | AutoTest.Net/ 746 | 747 | # Web workbench (sass) 748 | .sass-cache/ 749 | 750 | # Installshield output folder 751 | [Ee]xpress/ 752 | 753 | # DocProject is a documentation generator add-in 754 | DocProject/buildhelp/ 755 | DocProject/Help/*.HxT 756 | DocProject/Help/*.HxC 757 | DocProject/Help/*.hhc 758 | DocProject/Help/*.hhk 759 | DocProject/Help/*.hhp 760 | DocProject/Help/Html2 761 | DocProject/Help/html 762 | 763 | # Click-Once directory 764 | publish/ 765 | 766 | # Publish Web Output 767 | *.[Pp]ublish.xml 768 | *.azurePubxml 769 | # Note: Comment the next line if you want to checkin your web deploy settings, 770 | # but database connection strings (with potential passwords) will be unencrypted 771 | *.pubxml 772 | *.publishproj 773 | 774 | # Microsoft Azure Web App publish settings. Comment the next line if you want to 775 | # checkin your Azure Web App publish settings, but sensitive information contained 776 | # in these scripts will be unencrypted 777 | PublishScripts/ 778 | 779 | # NuGet Packages 780 | *.nupkg 781 | # NuGet Symbol Packages 782 | *.snupkg 783 | # The packages folder can be ignored because of Package Restore 784 | **/[Pp]ackages/* 785 | # except build/, which is used as an MSBuild target. 786 | !**/[Pp]ackages/build/ 787 | # Uncomment if necessary however generally it will be regenerated when needed 788 | #!**/[Pp]ackages/repositories.config 789 | # NuGet v3's project.json files produces more ignorable files 790 | *.nuget.props 791 | *.nuget.targets 792 | 793 | # Microsoft Azure Build Output 794 | csx/ 795 | *.build.csdef 796 | 797 | # Microsoft Azure Emulator 798 | ecf/ 799 | rcf/ 800 | 801 | # Windows Store app package directories and files 802 | AppPackages/ 803 | BundleArtifacts/ 804 | Package.StoreAssociation.xml 805 | _pkginfo.txt 806 | *.appx 807 | *.appxbundle 808 | *.appxupload 809 | 810 | # Visual Studio cache files 811 | # files ending in .cache can be ignored 812 | *.[Cc]ache 813 | # but keep track of directories ending in .cache 814 | !?*.[Cc]ache/ 815 | 816 | # Others 817 | ClientBin/ 818 | ~$* 819 | *.dbmdl 820 | *.dbproj.schemaview 821 | *.jfm 822 | *.pfx 823 | *.publishsettings 824 | orleans.codegen.cs 825 | 826 | # Including strong name files can present a security risk 827 | # (https://github.com/github/gitignore/pull/2483#issue-259490424) 828 | #*.snk 829 | 830 | # Since there are multiple workflows, uncomment next line to ignore bower_components 831 | # (https://github.com/github/gitignore/pull/1529#issuecomment-104372622) 832 | #bower_components/ 833 | 834 | # RIA/Silverlight projects 835 | Generated_Code/ 836 | 837 | # Backup & report files from converting an old project file 838 | # to a newer Visual Studio version. Backup files are not needed, 839 | # because we have git ;-) 840 | _UpgradeReport_Files/ 841 | Backup*/ 842 | UpgradeLog*.XML 843 | UpgradeLog*.htm 844 | ServiceFabricBackup/ 845 | *.rptproj.bak 846 | 847 | # SQL Server files 848 | *.mdf 849 | *.ldf 850 | *.ndf 851 | 852 | # Business Intelligence projects 853 | *.rdl.data 854 | *.bim.layout 855 | *.bim_*.settings 856 | *.rptproj.rsuser 857 | *- [Bb]ackup.rdl 858 | *- [Bb]ackup ([0-9]).rdl 859 | *- [Bb]ackup ([0-9][0-9]).rdl 860 | 861 | # Microsoft Fakes 862 | FakesAssemblies/ 863 | 864 | # GhostDoc plugin setting file 865 | *.GhostDoc.xml 866 | 867 | # Node.js Tools for Visual Studio 868 | .ntvs_analysis.dat 869 | 870 | # Visual Studio 6 build log 871 | *.plg 872 | 873 | # Visual Studio 6 workspace options file 874 | *.opt 875 | 876 | # Visual Studio 6 auto-generated workspace file (contains which files were open etc.) 877 | *.vbw 878 | 879 | # Visual Studio 6 auto-generated project file (contains which files were open etc.) 880 | *.vbp 881 | 882 | # Visual Studio 6 workspace and project file (working project files containing files to include in project) 883 | *.dsw 884 | *.dsp 885 | 886 | # Visual Studio 6 technical files 887 | 888 | # Visual Studio LightSwitch build output 889 | **/*.HTMLClient/GeneratedArtifacts 890 | **/*.DesktopClient/GeneratedArtifacts 891 | **/*.DesktopClient/ModelManifest.xml 892 | **/*.Server/GeneratedArtifacts 893 | **/*.Server/ModelManifest.xml 894 | _Pvt_Extensions 895 | 896 | # Paket dependency manager 897 | .paket/paket.exe 898 | paket-files/ 899 | 900 | # FAKE - F# Make 901 | .fake/ 902 | 903 | # CodeRush personal settings 904 | .cr/personal 905 | 906 | # Python Tools for Visual Studio (PTVS) 907 | __pycache__/ 908 | *.pyc 909 | 910 | # Cake - Uncomment if you are using it 911 | # tools/** 912 | # !tools/packages.config 913 | 914 | # Tabs Studio 915 | *.tss 916 | 917 | # Telerik's JustMock configuration file 918 | *.jmconfig 919 | 920 | # BizTalk build output 921 | *.btp.cs 922 | *.btm.cs 923 | *.odx.cs 924 | *.xsd.cs 925 | 926 | # OpenCover UI analysis results 927 | OpenCover/ 928 | 929 | # Azure Stream Analytics local run output 930 | ASALocalRun/ 931 | 932 | # MSBuild Binary and Structured Log 933 | *.binlog 934 | 935 | # NVidia Nsight GPU debugger configuration file 936 | *.nvuser 937 | 938 | # MFractors (Xamarin productivity tool) working folder 939 | .mfractor/ 940 | 941 | # Local History for Visual Studio 942 | .localhistory/ 943 | 944 | # Visual Studio History (VSHistory) files 945 | .vshistory/ 946 | 947 | # BeatPulse healthcheck temp database 948 | healthchecksdb 949 | 950 | # Backup folder for Package Reference Convert tool in Visual Studio 2017 951 | MigrationBackup/ 952 | 953 | # Ionide (cross platform F# VS Code tools) working folder 954 | .ionide/ 955 | 956 | # Fody - auto-generated XML schema 957 | FodyWeavers.xsd 958 | 959 | # VS Code files for those working on multiple tools 960 | *.code-workspace 961 | 962 | # Local History for Visual Studio Code 963 | 964 | # Windows Installer files from build outputs 965 | 966 | # JetBrains Rider 967 | *.sln.iml 968 | 969 | ### Gradle template 970 | .gradle 971 | **/build/ 972 | !src/**/build/ 973 | 974 | # Ignore Gradle GUI config 975 | gradle-app.setting 976 | 977 | # Avoid ignoring Gradle wrapper jar file (.jar files are usually ignored) 978 | !gradle-wrapper.jar 979 | 980 | # Avoid ignore Gradle wrappper properties 981 | !gradle-wrapper.properties 982 | 983 | # Cache of project 984 | .gradletasknamecache 985 | 986 | # Eclipse Gradle plugin generated files 987 | # Eclipse Core 988 | # JDT-specific (Eclipse Java Development Tools) 989 | 990 | ### Vim template 991 | # Swap 992 | [._]*.s[a-v][a-z] 993 | !*.svg # comment out if you don't need vector files 994 | [._]*.sw[a-p] 995 | [._]s[a-rt-v][a-z] 996 | [._]ss[a-gi-z] 997 | [._]sw[a-p] 998 | 999 | # Session 1000 | Session.vim 1001 | Sessionx.vim 1002 | 1003 | # Temporary 1004 | .netrwhist 1005 | 1006 | # Persistent undo 1007 | [._]*.un~ 1008 | 1009 | ### Patch template 1010 | *.rej 1011 | 1012 | ### GPG template 1013 | secring.* 1014 | 1015 | ######################################################################################################################## 1016 | ## Custom Definitions ## 1017 | ######################################################################################################################## 1018 | 1019 | ### Ignore all Jetbrains IDE files 1020 | .idea/ 1021 | 1022 | ### CI Pipeline Created Files 1023 | gha-creds-*.json 1024 | 1025 | ### Snyk Files 1026 | .dccache 1027 | snyk-code.html 1028 | snyk-code.json 1029 | snyk/ 1030 | --------------------------------------------------------------------------------