This repository has been archived by the owner on Feb 15, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 181
Define next steps and responsibilities for Devops mutualization #124
Comments
👀 👍 |
@mcleo-d @toshaellison tried to frame the expectation a little more. Would be good to discuss next steps by end of this week / early next. |
The meeting happened with @mindthegab and @toshaellison and @mcleo-d is actioning step 1 below ... Actions
The work is being done in the Google Sheet below ... |
The following items are done Completed Actions
Next Steps
|
The agreed date for the DevOps Multualization project call with FINOS team is Thursday 18th June @ 4pm BST / 11am ET. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In February we convened an initial roundtable on "DevOps mutualization for regulated industries", after initial interest from Morgan Stanley and Capital One and considering the natural interest many of our dev toolchain and services vendors (github, gitlab, cloudbees, red hat, nearform, wipro, etc.) would have in the topic.
Now this project has been made a 20Q2 formation focus project for FINOS by the Board and so we need to define the strategy to:
@mcleo-d collected notes from the Feb 24th call which can be used as a starting point.
The text was updated successfully, but these errors were encountered: