Office Hours - 2024-10-17

[rocketstack-matt]

Date

Thursday, 17th 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 legal@finos.org 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/95349776375

• Meeting ID: 953 4977 6375

• Passcode: 373428

• Find your local number: https://zoom.us/u/acIxq5va8m

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

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

Mailing List: Email devops-automation+subscribe@finos.org to subscribe to our mailing list

[willosborne]

Will Osborne / Morgan Stanley

[rocketstack-matt]

Matthew Bain / Morgan Stanley

[Thels]

Ross Maden / Morgan Stanley

[aidanm3341]

Aidan McPhelim / Morgan Stanley

[karlmoll]

Karl Moll / FINOS

[slvonmars]

Srinivas Lakhanigam / Morgan Stanley

[dc-ms]

Denis Coffaro / Morgan Stanley

[rocketstack-matt]

Minutes

• Round of introductions

• @jpgough-ms Gave detail of the purpose of the new Office Hours meeting: intended for maintainers and active contributors to touch base once a week, set priorities.

Priorities
Artefact Store

• Issue pending @rocketstack-matt

• Top priority @jpgough-ms for building an artefact store that firms will be able to publish patterns / instantiations / control-requirements, etc.
• @karlmoll asked are these things we wouldn't host in the main repo?
• @jpgough-ms explained that this is for hosting the documents pertinent to each user of CALM
• @rocketstack-matt gave additional colour that it would be required for some of our tools to function, such as a visualiser being able to navigate between nodes and the detailed-architecture elements, for being able to reference reusable artefacts like control-requirements, etc.
• @dc-ms added that this is related to what some vendors are asking for about what needs to be contributed
• @karlmoll mentioned that RedHat have contributed a public / private vault - perhaps something we could reuse? Karl to add link to the comments.

Bundling

• CALM Bundle #449
• @jpgough-ms also raised the ability to "bundle" artefacts together
• @Thels thinks there are a few angles to this, keen to pick up this issue once done with vs code plugin he's working on

Identifying CALM documents

• How to tell that you're working with a CALM file #482
• @Thels raised this discussion on whether we should introduce a naming convention to be able to enable the plugin to recognise file types without interning and looking at the schema tag, e.g. *.pattern.json
• @rocketstack-matt has concerns that we have to look at the schema anyway as we support multiple disparate schemas that combined make up CALM
• @willosborne / @Thels / @jpgough-ms think having a convention makes things easier
• All the files are JSON, what we're talking about is adding a 'helper' to the tools to point them in the right direction.
• @Thels to raise an issue showing where he sees the value
• @rocketstack-matt highlighted that we're still going to have to do the error checks to confirm the files really are what the file names claim they are, but fine for this to go ahead if folks think it makes life easier.

• @Thels to raise an issue showing the value here and we will go ahead and implement.

CLI Small Tasks

• @willosborne highlighted there are a number of small issues in the CLI that make the development experience jarring and wants to get some of these fixed.
• @rocketstack-matt asked @willosborne to post the items in the comments to this issue and to add the "Good first issue" tag.

Top Priorities

• @rocketstack-matt : enhance visualiser / artefact store foundation / documentation generator from flows
• @jpgough-ms : need to get the existing tooling up to date with the schema (we're currently still working against 2024-04 for most tooling)
• @rocketstack-matt : agreed we need to focus on getting tooling to up date with schema; would like to jump all the way to 2024-10 even if we have priority order of which features we enable through the tools (e.g. do control-requirement then flows)
• @rocketstack-matt also raised that we need to enhance the documentation

• Add a "definition of done" into the DEVELOPER.md
• Build project board to show the items we want to get done to agree a v1 release @jpgough-ms / @rocketstack-matt / @Thels

[karlmoll]

https://github.com/os-climate/OS-Climate-Community-Hub/blob/main/FAQ.md#what-data-is-in-the-data-commons

[Adwoa-Konadu-Appiah]

Konadu Appiah/ Turntabl

[Thels]

Raised an issue as promised - #490 - input would be massively appreciated.

[Elisha-Veve]

Elisha Amenuveve | Turntabl