You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

These meetings were initiated in response to ongoing discussions in the TSC and PTL meetings about dealing with dependencies on unmaintained projects, as well as documentation.

Meeting Minutes

Jan 24, 2022

Attendees: David, Muddasar, Amy, Thomas, Tony, Kenny

Dec 13, 2021

Attendees:  David, Pawel, Tony, Chaker, Thomas, Kenny

  • David McBride asks Chaker Al-Hakim to describe how the Arch Subcommittee works with project dependencies
  • Chaker says that dependencies are tracked at the project level, not the repo level.
  • Need to map dependencies to the repo level
    • Example:  DMAAP archived a repo, but the project is still active.  What if active projects have a dependency on the repo that was archived?
  • Chaker shares the review template with a new section that asks about dependencies.
    • Thomas Kulik suggests that "critical dependencies" should be replaced by "dependencies".
  • Chaker believes that mapping dependencies between projects at the repo level is outside of the scope of the architectural review.
  • Need to understand both build dependencies and functional dependencies.
  • Kenny:  Force updates by removing unmaintained projects from OOM.  
    • Build failures and test failures will highlight dependencies.

Dec 6, 2021

Attendees:  David, Kenny, Amy, Andreas, Muddasar, Pawel, Tony, Cedric

  • Andreas:  how are unmaintained projects represented in the arch diagram
    • Chaker says that the diagram includes unmaintained projects for one release past when they were moved to unmaintained
  • Unmaintained Project Dependencies.pdf
  • Audit (propose to TSC on Thursday)
    • Develop a map of dependencies between components
    • David to present to the TSC
  • Unmaintained => Archived should happen when there are no longer any dependencies on the unmaintained project
    • Already documented?  Kenny will check.

Actions:

  • David McBride ask Chaker to attend next week's meeting to discuss arch subcommittee and unmaintained project dependencies

Nov 29, 2021

Attendees:  David, Kenny, Amy, Cedric, Thomas

  • 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.
  • No labels