This document contains an overview of the state of the project transition from Hedera to Hiero. We will do the transition in phases and several different tasks need to be done and checked for each and every project. Therefore, we created a matrix that shows the state of all projects for that the transition has been started or is planned for the near future. Next to the matrix that is shown in this document we create issues for each repo that should be transfered. The issues might contain more detailed information about the transition state as shown in the matrix. A list of all issues can be found here.
| Hedera Repo | Hiero Repo | DCO check | License check | README and others updated | user rights | vendor neutral code | GitHub Actions | deployments |
|---|---|---|---|---|---|---|---|---|
| hedera-sdk-go | hiero-sdk-go | 🚧 | ❌ | 🚧 | 🚧 | 🚧 | ➖ | |
| hedera-sdk-swift | hiero-sdk-swift | ✅ | ❌ | 🚧 | 🚧 | 🚧 | ➖ | |
| hedera-sdk-tck | hiero-sdk-tck | ✅ | ||||||
| hedera-sdk-js | hiero-sdk-js | 🚧 | ||||||
| hedera-sdk-cpp | hiero-sdk-cpp | ✅ | ❌ | |||||
| hedera-sdk-java | hiero-sdk-java | 🚧 | ||||||
| hedera-sdk-rust | hiero-sdk-rust | 🚧 | ||||||
| solo | 🚧 | ✅ | ||||||
| hedera-local-node | 🚧 | |||||||
| hedera-json-rpc-relay | 🚧 | |||||||
| hedera-mirror-node | 🚧 | |||||||
| hedera-mirror-node-explorer | ✅ | 🚧 | ||||||
| hedera-block-node | 🚧 | |||||||
| hedera-services | 🚧 | |||||||
| hedera-docs | 🚧 | |||||||
| did-method | 🚧 | |||||||
| did-sdk-js | ✅ | 🚧 | ||||||
| did-sdk-java | 🚧 | |||||||
| hedera-protobufs | ✅ | ✅ | ||||||
| hedera-improvement-proposal | hiero-improvement-proposals | 🚧 | 🚧 | 🚧 | 🚧 | 🚧 | ➖ |
❌ - Problem with given tasks
✅ - Task sucessfull
🚧 - In progress
➖ - not needed (for example a repo without deployments)
Hedera Repo - Name and maybe link to old Hedera repo
Hiero Repo - Name and maybe link to new Hiero repo
DCO check - Check if all commits in the repo are signed the DCO
License check - Check if the repo license and the licenses of all transitive dependencies are compatible with the LFDT guidelines. All open issues regarding license problems can be found here.
README and others updated - Files like README.md, MAINTAINERS.md and others must exist and be up to date. More information can be found in the LFDT guidelines
user rights - Users, groups and rights are managed by the config.yaml file in the https://github.com/LFDT-Hiero/governance repo. We will create custom groups for each repo. That groups must be created and added to the specific repos in the config.yaml.
vendor neutral code - Names like "Hedera" and or "Hashgraph" are removed from the code (and other ressources) of the repository.
GitHub Actions - GitHub Actions must work for Hiero repositories. This can include the creation of possible tokens, service accounts or custom GitHub action runners.
deployments - Deployments can be published webpages (like for HIPs or docs) or release artifacts (like a jar) that is deployed to a registry. All that need to be reconfigured for Hiero.