25 Oct 2024 - Trader X Meeting Minutes

[karlmoll]

Date

2024/10/25 - 8am ET

Untracked attendees

• Fullname, Affiliation, (optional) GitHub username
• ...

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
• Agenda item 1
• Agenda item 2
• ...
• AOB, Q&A & Adjourn (5mins)

Decisions Made

• Decision 1
• Decision 2
• ...

Action Items

• Action 1
• Action 2
• ...

Zoom info

https://zoom.us/j/96264933811
Meeting ID: 962 6493 3811
Passcode: 532953

Find your local number: https://zoom.us/u/aHHeTieyi

[sammoorhouse]

Sam Moorhouse / turntabl

[karlmoll]

Karl Moll / FINOS

[psmulovics]

Peter Smulovics / Morgan Stanley

[janfernandosmoothstack]

Janet Fernando / Smoothstack

[DovOps]

Dov Katz / Morgan Stanley

[DovOps]

Rough Ideas around the 'knowledge graph' as discussed in the meeting

0. Optimized Monorepo
1. Add containerization support
   1.1 Multi-container support (docker-compose, k8s/minikub,etc)
   1.1.1 Local dev GitOps support (e.g. tilt.dev)
   1.1.2 Radius Support for multi container environments
2. CALM documentation of architecture/IaC/State Changes
3. Add more robust messaging
   3.1. Add pricing support
   3.1.1. Add orders/matching support, and partial fills in the trade Processor

etc ... etc..

[DovOps]

Ideas around the knowledge graph

1. We should have published norms around what constitutes a 'node-worthy' change, versus a 'fix/tweak' which should be contributed to an existing node and fast forwarded to its children. (e.g. is this a bug fix/incomplete impl, etc-- or is this a new 'learning'?)
2. All graph 'nodes' are branches in the codebase
3. We select a specific 'naming convention' for these... (e.g. 'graph/$XXXX')
4. All nodes must follow a specific set of norms, e.g. (node-specific documentation file , some sort of CI jobs, etc.)
5. Branches should have the core maintainers defined (Similar to MAINTAINERS file, etc..., and a collection of tags/features to help searching)
6. We use our regular calls for vetting new nodes for 'inclusion' on the graph
7. Main documentation branch has a configuration file/list of all official 'nodes' in the graph, which drives our automation, docs consolidation, etc... etc..
8. Backstage instance, when we set it up, can host all of this as a 'catalog' of branches, etc..