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.
Date
Monday, June 10, 2024 - 9:30am ET / 2:30pm UK
// Second Monday of every month
Attendees
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
(5 min) Convene, roll call, welcome new people.
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
(5 min) Approve previous meeting minutes.
(10 min) TurinTech applicable to kdb+?
https://www.turintech.ai/
Seems I/O would be hard for a software tool to optimize by just looking at the code:
SSDs vs spinning disk? SSDs cost 10x.
Local vs network.
Native
q
vs C plugin..Q.MAP[]
and understanding various levels of compression.How much of a splayed table is read for a given query?
Integration with I/O measurements and other hooks would be required.
Some looking at software optimization from an ESG angle.
OS-Climate joining FINOS!
AI-Readiness may also look at sustainability due to the amount of GPU compute used for LLMs.
May have tie-ins with Modernization.
Various discussions in industry about Technology Sustainability Frameworks.
Texas and Florida unfriendly to ESG?
(10 min) Contributor License Agreement in the context of contractors / consultants doing enhancements for users at banks.
(10 min) HN : Arthur Whitney releases an open-source subset of K with MIT license (shakti.com)
(5 min) HN : BQN: Finally, an APL for your flying saucer](https://mlochbaum.github.io/BQN/)
https://news.ycombinator.com/item?id=33180842
https://mlochbaum.github.io/BQN/tutorial/expression.html
Backports some features from
k
/q
.Borrows tacit programming?
Lightweight anonymous functions from lisp.
Code golfing languages:
Purportedly one out there that encodes 100,000 operators as Unicode characters (including Chinese).
"Sudoku solver" in
k
:Operator in
q
only works for 3x3 case but works in the general case fork
.(5 min) GitHub Copilot trick
#file
:q
programming language details into the LLM.(5 min) AOB, Q&A, Adjourn.
Join Zoom Meeting