finos
DevOps Automation SIG Meeting - Jan 16 2025
Date
Thursday, Jan 16 2025 - 12pm ET; 5pm UK
Untracked attendees
| Name | Firm | Comment |
|---|
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
- [x] Convene, roll call, welcome new people
- [x] Approve previous meeting minutes - note this is for the Nov 2024 meeting; there was no meeting in Dec 2024.
- [x] Code Modernization & Evolution at Scale working group to be launched in February within DevOps SIG
- [ ] OSS AI/ML model onboarding approaches, gotchas, and mutualization opportunities
- [ ] AOB, Q&A & Adjourn (5mins)
Decisions Made
- [ ] Decision 1
- [ ] Decision 2
- [ ] ...
Action Items
- [ ] Action 1
- [ ] Action 2
- [ ] ...
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/devops-automation/
Project Board: https://github.com/orgs/finos/projects/33
Mailing List: Email [email protected] to subscribe to our mailing list
Meeting minutes
- @rocketstack-matt suggested raising interest for Code Modernization & Evolution at Scale to be launched as working group vs project within DevOps SIG while it is in in the formation stage at the next ToC meeting on January 22. @DovOps please note
- Brian Warner summarized key points in Fidelity's talk at OSFF - https://www.youtube.com/watch?v=PutO8IZV3xw (separate license evaluation from model evaluation, tooling to build a model tree similar to SCA tool generated dependency trees, tooling to onboard models so developers/strats don't ever need to read a license). this is a lot of work
- question on how much of this can be shared; documentation on process used to establish dependency tree for models would be valuable, as would the dependency tree of OSS models itself (because many of the self declared licenses on hugging face are incorrect, for example). deciding what licenses are considered permissible is an org specific decision
- question on whether approach used to evaluate licenses and other criteria used to onboard OSS model could be shared a this would be valuable
- @karlmoll mentioned knowledge sharing on some license types that are considered problematic would also be useful; also enquired whether they have been discussions on LF AI or Opia. Brian mentioned he has had these discussions. Reiterated the dependency tree of models is lot more useful.
- Brian will discuss internally whether some of the learnings and model dependency tree metadata at Fidelity can be shared through FINOS
- Discussion on whether OSS AIML model onboarding has been automated (after checking for licensing, security vulnerabilities, operational risk etc.). Would be interesting to have the knowledge base or even tooling (e.g., allowlist) of OSS AIML models available as an open source
- Discussion on inventory and usage tracking of models. These appears to be in formative stages at most of the orgs
- @karlmoll notified Backstage reference instance setup (along with Backstage plugins) will be presented at the ToC by @cnygardtw