Thanks @weichiu. Makes sense to have a separate repo for ozone tools.
+1 for ozone-contrib as the name. Sent from Gmail Mobile On Wed, 21 Jan 2026 at 10:18 PM, Wei-Chiu Chuang <[email protected]> wrote: > I am helping Soumitra to set up a repo ozone-installer for the installer > project https://issues.apache.org/jira/browse/HDDS-13870 > > https://github.com/apache/ozone-installer > > We are creating this repo for the installer outside of the main ozine repo, > because the ozone installer can be used to install different versions of > Ozone. It doesn't need to be versioned. This installer is a small tool > right now, but there's a plan to expand it and support upgrade/tls/tde in > the future, which is why we call for a repo of its own. > > In the meantime, I want to propose having a separate ozone repo for tools. > Call it ozone-tools or ozone-contrib, for example. The idea is to have a > separate repo for tools or things that are contributed by people outside of > Ozone core developers. For example, tools for repairing corrupt metadata, > sample docker compose files for third party integration like Flink or > Trino, Kubernetes Operators... etc. These contributions can have a > low-touch merge process, we don't have to hold the bar high for them, and > they can be merged sooner and released in a different cadence. >
