DevOps Automation SIG Meeting - March 21, 2024
ashukla13 opened this issue · comments
Date
Thursday, March 21 2024 - 12pm ET; 4pm 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 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
- Convene, roll call, welcome new people
- Approve previous meeting minutes
- Working Group updates
- #181
- Approaches on Deprecation of Programming Languages and Tech Stacks - NatWest
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 devops-mutualization+subscribe@finos.org to subscribe to our mailing list
Ragha Vema | Fannie Mae
amol shukla/morgan stanley
Karl Moll / FINOS
James McLeod / NatWest
Wilson Sinclair / NatWest
Alvin Shih / Morgan Stanley
Attended:
Frank Schawillie - RBC
Minutes
- Updates from working group
- @rvema raised question on raising surveys on specific topics like change mgmt approach at members. @mcleo-d raised prior surveys including OSS readiness and also the annual surveys; also brought up getting information through informal demos and knowledge sharing through meeting. Discussion on potentially merging the Software supply chain and automated change deployment working group perspective - since the software supply chain seems to have traction
- @ashukla13 provided a summary of #183
- @karlmoll summarized Arch as code working group meetings - lots of demos and lively discussion; see also #185
- @karlmoll summarzied Backstage working group meeting - including RedHat led discussion and reinforced interest in Backstage in FSI. @mcleo-d reiterated strategic importance of Backstage. Discussion on whether SIG should developer portal broadly - not just Backstage. @ashukla13 to raise this with @cnygardtw at the next meeting
- For #181 - see minutes here
- Wilson Sinclair/NatWest provided an overview of lifecycle management of programming languages - including how to introduce new ones and decommission legacy ones; @mcleo-d brought up many organizations are doing tech radars and lifecycle mgmt based on just internal information; would be great to consider an industry radar (like thoughtworks tech radar) or even get an external/industry view on where member banks are; would also help to benchmark where your org is vs. the industry. This discussion will continue in April
Matthew Bain / Morgan Stanley
Code Generation Indemnity Further Reading referenced on today's call
Existing policies:
https://blogs.microsoft.com/on-the-issues/2023/09/07/copilot-copyright-commitment-ai-legal-concerns/
https://cloud.google.com/blog/products/ai-machine-learning/protecting-customers-with-generative-ai-indemnification
Reporting coverage:
https://www.runtime.news/ai-vendors-promised-indemnification-against-copyright-lawsuits-the-details-are-messy/
https://learn.g2.com/ai-code-generators-legal-considerations