08/15/2024 Delivery Meeting Minutes

[damienjburks]

Date

08/15/2024 - 11:30 ET / 16:30 UK

• Join Zoom Meeting
• Meeting ID: 930 1013 8669
• Passcode: 432980
• Copy this meeting to your calendar
• Find your local number

Meeting notices

• FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.
• All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.
• FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact [email protected] with any questions.
• FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

• [ ] Convene & roll call (5mins)
• [ ] Display FINOS Antitrust Policy summary slide
• [ ] Review Meeting Notices (see above)
• [ ] Approve past meeting minutes
• [ ] Project board walkthrough
• [x] https://github.com/finos/common-cloud-controls/issues/299
  • [ ] Discuss the impact of this project and see how this conflicts with the current open tickets (below) for the Delivery WG.
    • [ ] Does this change our releasing strategy moving forward?
• [ ] https://github.com/finos/common-cloud-controls/discussions/268
  • [ ] Highlight or summarize the results of this discussion
• [x] https://github.com/finos/common-cloud-controls/issues/213
  • [ ] This is now in progress, @damienjburks is working on writing up the documentation to define the versioning criteria based on the discussion
• [ ] AOB, Q&A & Adjourn (5mins)

Untracked attendees

• Fullname, Affiliation, (optional) GitHub username
• ...

[eddie-knight]

:wave: :shipit: Eddie Knight / Sonatype

[smendis-scottlogic]

Sonali Mendis / Scott Logic

[robmoffat]

Rob Moffat / FINOS 🏄

[psmulovics]

Peter Smulovics / Morgan Stanley

[robmoffat]

Minutes

Pilot Users

• Marsh McLennan and Tier 1 both interested in using whatever initial releases the CCC project pilots
• Paul Stevenson handing over CCC SteerCo ownership to Vlad Robotka. (?) We should ask
• @mlysaght2017 quite keen from Citi, but not on the call today.

Release Structure / Format

• #312 Adds versioning guidelines (CalVer)
• Releases will be in the form of zip files one for each service category (e.g. Object Storage), containing a taxonomy element, controls and gherkin test definitions.

YAML Format

• In order that we can build different releases, we need to have a more structured (i.e. YAML) format that can be processed into the different releases.
• #301 Addresses This
• @psmulovics asked about extra metadata in the YAML.
• Also should we add version-tracking metadata in there so that we can generate release notes (as per FDC3)
• @robmoffat asked whether this couldn't be done from OSCAL format, but @eddie-knight said there are various transforms that we can build from this (e.g. CFI) and various bits of data that OSCAL doesn't support.

[github-actions[bot]]

This issue will be closed as stale in 7 days. Please update this issue if it is still needed.

[github-actions[bot]]

Closed as stale. An update may reopen this issue.