common-cloud-controls
common-cloud-controls copied to clipboard
08/15/2024 Common Cloud Controls Meeting Minutes - Communications Working Group
August 15 2024
08/15/2024 - 12:00 ET / 17:00 UK
- Join Zoom Meeting
- Meeting ID: 944 1616 8360
- Passcode: 042805
- Find your local number
- Copy this meeting to your calendar
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
- [ ] ...
- [ ] AOB, Q&A & Adjourn (5mins)
Untracked attendees
- Fullname, Affiliation, (optional) GitHub username
- ...
Rob / FINOS 🏹
:wave: :shipit: Eddie Knight / Sonatype
Sonali Mendis / Scott Logic
Rudra Gupta / Krumware
Euthyme Ziogas / Scott Logic / Observer
Jared Lambert / Microsoft
Minutes
- No updates on Community Structure (@sshiells-scottlogic OOO), Security (@mlysaght2017 is OOO).
Issues Update
- #267 Update from @damienjburks: @mlysaght2017 has reviewed, @jared-lambert needs to also approve. @eddie-knight investigated why this was necessary given the settings in the CODEOWNERS and then it was merged
- #300 YAML to Markdown generator from @eddie-knight.
- #305 in flight for security working group, creating controls
Duplication Reduction Update
- @jared-lambert on the call - slow steady progress but nothing major to report. Needs more helpers
Taxonomy
- @smendis-scottlogic finding it hard to get the resources she needs to make fast progress. Working on internal participation. Will look into @eddie-knight's new format for controls.
Delivery
- @damienjburks have agreed the approach for versioning / releases. Some automation needs to be built to handle releases. Asking for help for this within own network - looking at defence contractors.
Milestone Discussion
- @damienjburks gave an update on milestones, drafted https://github.com/finos/common-cloud-controls/milestone/6
- Details work to be done over the next 6 weeks (until 30th September)
- LSEG and Marsh McLennan both happy to use pilot CCC/CFI materials.
Release Candidate for RAG LLM
-
Need to do a gap analysis of the available services against the ones defined in the architecture. @smendis-scottlogic and @jared-lambert tried to figure this out on the call. Approximately 15 services from Jared:
- App Service (App Service Plan) 🔗
- Application Insights 🔗
- Azure AI Services 🔗
- Azure Cosmos DB 🔗
- Bing Search Service 🔗
- Azure AI Document Intelligence 🔗
- Azure Function(App Service Plan) 🔗
- Azure Key Vault 🔗
- Log Analytics workspace 🔗
- Azure Logic App 🔗
- Azure AI Search 🔗
- Azure OpenAI 🔗
- Storage account 🔗
- Azure Active Directory 🔗
-
Key Services that we should focus on might be:
- Azure Open AI
- Storage Account
- Azure Key Vault
- Log Analytics
ACTION: @Alexstpierrework, @smendis-scottlogic and @jared-lambert to work on prioritisation, genericising the names and removing items that we've already done (e.g. Azure Cosmos DB is an RDBMS, which is defined already).
- #314
Alex St. Pierre / METRO
This issue will be closed as stale in 7 days. Please update this issue if it is still needed.
Closed as stale. An update may reopen this issue.