Office Hours - 2024-10-24

[Thels]

Date

Thursday, 24th Oct 2024 - 15:30 BST

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

Office Hours is a meeting for maintainers to get together to discuss active development and upcoming priorities.

Zoom info

Join Zoom Meeting

• https://zoom.us/j/94904595244
• Meeting ID: 949 0459 5244
• Passcode: 545224
• Find your local number: https://zoom.us/u/aesEqmNODb

Github Repo: https://github.com/finos/architecture-as-code/

Project Board: https://github.com/orgs/finos/projects/98

Mailing List: Email [email protected] to subscribe to our mailing list

[Thels]

Ross Maden - Morgan Stanley

[willosborne]

Will Osborne - Morgan Stanley

[aidanm3341]

Aidan McPhelim / Morgan Stanley

[karlmoll]

Karl Moll / FINOS

[slvonmars]

Srinivas Lakhanigam / Morgan Stanley

[dc-ms]

Denis Coffaro / Morgan Stanley

[yt-ms]

Yan Tordoff / Morgan Stanley

[Adwoa-Konadu-Appiah]

Konadu Appiah / Turntabl

[Thels]

Minutes

• Discussed Programmatic Derivation of CALM File Type #490 - finding is that we're going to introduce some sort of file-naming convention. Although it wouldn't be required for Control Requirement or Control Evidence files for now. @Thels to update the issue to reflect this discussion and proposed change. @yt-ms also had input around the naming convention that he will put onto the issue.
• Update from @willosborne - he's looking into reducing code duplication in the generate space.
• @willosborne discussed CALM at a non-financial forum and there was interest - asked the best way to introduce folks to the project. @dc-ms suggested using the docs website for documentation and talks on the project.
• Discussed open PR for validate VSCode Extension VSCode Extension for CALM Validation #442 - going to be split into two PR's given the other changes on-going to the CLI space.

Actions

• @karlmoll to raise an issue for investigating how CALM could fit into other on-going FINOS projects.
• Issue to be raised relating to adding a GitHub action that pulls down the latest CLI and validates it against "good" files to validate that the CLI isn't broken on merge. Suggested files to use are this for the instantiation and this for the pattern.
• @Thels to update PR into two different PR's.

[Elisha-Veve]

Elisha Amenuveve | Turntabl