We are interested in adding native STACKIT platform support to HyperShift.
While looking into the implementation, we came across the platform onboarding guide:
https://hypershift-docs.netlify.app/contribute/onboard-a-platform/
Before getting started, we wanted to check whether the documented process is still the
recommended approach. Is it fine to simply work through the onboarding guide and open the
respective PRs as we progress, or would you prefer an enhancement proposal or design document
before implementation begins?
Additionally, is there anything that is not currently covered by the onboarding documentation
that we should be aware of before starting? For example, architectural considerations, the
expected review process, or other repositories that also require changes.
Our intention is to contribute native STACKIT platform support upstream, and we're happy to
drive the implementation ourselves. We just want to make sure we're following the preferred
process from the beginning.
We are interested in adding native STACKIT platform support to HyperShift.
While looking into the implementation, we came across the platform onboarding guide:
https://hypershift-docs.netlify.app/contribute/onboard-a-platform/
Before getting started, we wanted to check whether the documented process is still the
recommended approach. Is it fine to simply work through the onboarding guide and open the
respective PRs as we progress, or would you prefer an enhancement proposal or design document
before implementation begins?
Additionally, is there anything that is not currently covered by the onboarding documentation
that we should be aware of before starting? For example, architectural considerations, the
expected review process, or other repositories that also require changes.
Our intention is to contribute native STACKIT platform support upstream, and we're happy to
drive the implementation ourselves. We just want to make sure we're following the preferred
process from the beginning.