open-next / losh-okh-tool Goto Github PK

As of now, there is only one sub-set defined: the required properties.
It would be useful though, if we have more such sets defined (e.g. recommended and optimal) within OKH or the tooling,
but also to allow external entities to define such sets and publish them in a way compatible with our tooling.

Given a project repository (local checkout),
we would generate an okh.toml manifest file,
with as much data as we manage to gather automatically.
The remaining fields may be:

1. omitted,
2. added with placeholder values
   (like "TODO" or "https://TODO.com/YOUR_ORG/YOUR_REPO/")
3. same as 2., but commented out

Previous issue: https://gitlab.com/OSEGermany/osh-tool/-/issues/4

NOTE:

• Use projvar to gather lots of the required info
• Use this suggestion
  to figure out [[part]]s of the project