Skip to content

Latest commit

 

History

History
53 lines (40 loc) · 8.73 KB

transition.md

File metadata and controls

53 lines (40 loc) · 8.73 KB

Transition of Hedera projects to Hiero

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.

A step-by-step guide for doing the transition of a repository can be found here.

Initial steps

The following table contains an overview of the initial steps that need to be done for each project before the actual transition can start.

Hedera Repo Hiero Repo automatic DCO check DCO remediation automatic License check License remediation user rights transfered
hedera-sdk-go hiero-sdk-go 🎉
hedera-sdk-tck hiero-sdk-tck 🎉
hedera-sdk-cpp hiero-sdk-cpp 🎉
hedera-sdk-swift hiero-sdk-swift 🎉
hedera-sdk-js hiero-sdk-js 🎉
hedera-sdk-java hiero-sdk-java 🎉
hedera-sdk-rust hiero-sdk-rust 🔴*
solo solo 🚧*
hedera-local-node hiero-local-node 🎉
hedera-json-rpc-relay hiero-json-rpc-relay 🚧*
hedera-mirror-node hiero-mirror-node 🔴* 🔴*
hedera-mirror-node-explorer hiero-mirror-node-explorer 🔴* 🔴* 🚧*
hedera-block-node hiero-block-node 🔴*
hedera-services hiero-consensus-node 🚧 🚧*
hedera-docs hiero-docs 🔴* 🚧*
did-method 🔴* 🚧*
did-sdk-js 🚧*
did-sdk-java 🔴* 🚧 🚧 🚧*
hedera-protobufs hiero-protobufs 🚧*
hedera-improvement-proposal hiero-improvement-proposals 🔴* 🚧*

Defintions of columns

Hedera Repo - Name and maybe link to old Hedera repo

Hiero Repo - Name and maybe link to new Hiero repo

automatic DCO check - Check if all commits in the repo are automatically checked for DCO signing

DCO remediation - We need to ensure that all commits on the main branch are DCO signed. This can be accomplished by retroactively signing commits through an empty signed commit on the repository.

automatic License check - Check if the repo is automatically checked for licensing issues

License remediation - Check if the repo license and the licenses of all transitive dependencies are compatible with 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.