These meetings were initiated in response to ongoing discussions in the TSC and PTL meetings about dealing with with dependencies on unmaintained projects, as well as documentation.
...
- Scope:
- Documentation
- Software dependencies (incl. uses cases)
- Understand what repos are actually part of a release - not just the projects in a release.
- Increased transparency on software modules included in an ONAP release
- Need an x-project dependency tree from the PTLs of all active projects
- repos with no dependencies should be locked
- repos with dependencies where unmaintained need to have the conversation
- end state needs to be an awareness of unmaintained dependencies.
- Release notes should document any use of or dependency on unmaintained projects/repos
- Amy: goal should be no dependency on unmaintained projects. However, we will still have exceptions
- Suggestion that we look at ESR/Logging and Portal as the litmus test for Jakarta
- Doc team will not include non-branched / unmaintained content going forward.
- Need an automated way for identifying the dependencies. SBOM?
- Should the arch subcommittee be tasked with determining whether a use case has a dependency on an unmaintained project?
- Example: Cannot pass arch review if there is a dependency on an unmaintained project without an exception from the TSC.