You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
There is a kdb-x trial ongoing in MS. Aaron raised an issue with wanting comma number notation with the kdb-x printf module that Péter mentions on a comment to this issue.
Ross to check with Karl about the repo admins. Not visible via the UI if you're not an admin but you can curl the infor out of github.
AI quick recap summary:
The meeting focused on updates regarding the KDBX trial implementation at Morgan Stanley and ongoing maintenance activities for the FINOS project. Aaron Davies discussed plans to create KDBX versions of existing FINOS modules, proposing to add a KDBX directory at the top level of the codebase parallel to the existing q directory. The team reviewed updates to the maintainers file, with Aaron Davies filling in known contributor names and Ross Duffy identifying punx120 as a contributor who had made studio commits in 2022. Rian provided updates on the KDBX migration from PyKX, explaining that they made libraries and threads opt-in rather than opt-out for faster defaults, and mentioned upcoming improvements to make KDB modules operate more like Python classes. The conversation ended with discussions about repository administration permissions and the status of incorporating changes from a KDB+ Studio fork maintained by an external contributor who was willing to share code but not become an official maintainer.
Date
Monday, June 8th, 2026 - 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
Minutes
A more admin focused meeting.
AI quick recap summary:
The meeting focused on updates regarding the KDBX trial implementation at Morgan Stanley and ongoing maintenance activities for the FINOS project. Aaron Davies discussed plans to create KDBX versions of existing FINOS modules, proposing to add a KDBX directory at the top level of the codebase parallel to the existing
qdirectory. The team reviewed updates to the maintainers file, with Aaron Davies filling in known contributor names and Ross Duffy identifying punx120 as a contributor who had made studio commits in 2022. Rian provided updates on the KDBX migration from PyKX, explaining that they made libraries and threads opt-in rather than opt-out for faster defaults, and mentioned upcoming improvements to make KDB modules operate more like Python classes. The conversation ended with discussions about repository administration permissions and the status of incorporating changes from a KDB+ Studio fork maintained by an external contributor who was willing to share code but not become an official maintainer.Join Zoom Meeting