Date
Monday, March 9th, 2026 - 9:30am ET / 1:30pm UK
// Second Monday of every month
Attendees
| Fullname |
Affiliation |
GitHub Username |
| Péter Györök |
KX |
@gyorokpeter |
| Aaron Davies |
Morgan Stanley |
@adavies42 |
| Ross Duffy |
Morgan Stanley |
@rdffy |
| Ran Murray |
FD/EPAM |
|
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
AI summary of the meeting
Quick Recap
The meeting focused on discussing the FINOS project, including updates on the Linux Foundation dashboard, versioning in the repository, and potential contributions from EPAM. Participants addressed issues with Gradle upgrades, font customizations, and handling long strings in Studio. They also discussed the transition between KDB and KDBX, considering the coexistence of both systems during a trial period. The group explored licensing options for KDBX, with concerns raised about RAM usage limits and monitoring. Additionally, they touched on upcoming KX meetups and the porting of modules to the new module system. The conversation ended with a brief discussion on licensing terms and the need for further clarification on usage tracking.
Next Steps
Ryan Murray: Follow up with Steven at EPAM to check on available resources for the Studio upgrade and provide an update at the next call.
Ross Duffy: Contact Carol (Linux Foundation admin) regarding the issue with updating company affiliation from FD Technologies to KX in the Linux Foundation dashboard.
Aaron Davies: Experiment with porting the zip and statistics modules to the new KDBX module system and consider the appropriate directory structure for KDBX-specific code in the FINOS repo.
Péter: Discuss with the core team whether changes can be made to the framework to allow FINOS functions to hook into the KDBX module system, and explore solutions to avoid code duplication.
Ryan Murray: Review and respond to KX regarding the 150-day KDBX trial period, specifically requesting non-consecutive periods (e.g., 30-45 days for MSKDB onboarding, then a separate period for internal testing).
Ryan Murray: Look into the solution for coexistence and migration between FINOS depends and KDBX module systems for users migrating from Core to KDBX.
Aaron Davies: Update usage of old kdb+ versions in testing to avoid hygiene violations (e.g., by launching de-organized or with usage tracker disabled).
Summary
Linux Foundation Dashboard Issues:
Ross Duffy and Aaron Davies discussed issues with the Linux Foundation dashboard, including difficulties with scheduling meetings and tracking attendance. They encountered problems with the website's functionality, such as slow loading times and inaccurate attendee logs. Aaron Davies noticed that the system showed an incorrect number of attendees and an outdated entry from 1980.
FINOS Project Guidelines Review:
Ross Duffy and Aaron Davies discussed the FINOS project guidelines, including antitrust policies and meeting conduct. They reviewed previous meeting notes and discussed the Linux Foundation dashboard. The agenda for the current meeting was briefly mentioned, though Ryan Murray's absence was noted as potentially affecting FD or EPAM-related topics.
Project Versioning and Website Updates:
Ross Duffy and Péter discussed the version numbering system for their project, with Péter suggesting a more automated approach using Git tags and release jobs. They also touched on the need to update the company name on the Linux Foundation website, though Péter expressed concerns about potential permission issues. Ross Duffy mentioned that Ryan Murray would be joining the meeting shortly.
KX System Access Challenges:
The team discussed issues with adding KX as a company in the system, where Péter encountered problems with the CLA rejection and domain association with FD Technologies PIC. Ross Duffy and Aaron Davies explored potential solutions, including updating the issue template and contacting Carol for administrative assistance. Aaron Davies mentioned he would report the Sidekick recognition issue in the Teams channel, while Ross Duffy confirmed he was the host of the meeting with no pending participants.
FinOS Repository Versioning Updates:
The team discussed updates to the FinOS repository, with Péter explaining that versioning should be implemented through a script in the release job and a GitHub job similar to the QBarse project. Ross Duffy noted that while Dimitri's work could be incorporated directly, there was no current EPAM initiative for Studio development, though Ryan Murray agreed to follow up with Steven about potential resources. Aaron Davies raised concerns about font customization limitations in the output panel, particularly for remote collaboration, and mentioned previous issues filed regarding this problem.
Large Dataset Rendering Challenges:
The team discussed issues with rendering large data sets in Studio, particularly problems with memory allocation and rendering entire tables at once. Aaron Davies suggested implementing pagination for large datasets, while Ross Duffy and Aaron Davies debated whether to merge changes from a fork that may address these issues, with Aaron Davies noting that rebasing could effectively make them a fork of the other project.
Gradle Upgrade and Codebase Alignment:
The team discussed differences between their codebase and Charlie's, noting they are a fork with around 500 commits. Ryan Murray highlighted that upgrading Gradle would unblock Morgan Stanley from building the repository, as there was a hygiene violation due to an outdated Studio release. Aaron Davies suggested addressing the issues in two stages: first fixing Gradle, then picking up new features, as many open issues might already be resolved in Charlie's codebase.
Socket Handle Experimentation Discussion:
The team discussed an email about a socket being opened on handle zero, which Aaron Davies explained was from his experimentation with replicating the automated queue process environment. Péter clarified that this was a safeguard for cases where functions expect handle zero to be standard input. Aaron Davies mentioned using older versions of the software for testing, with permission from Alvin, and discussed ways to launch the software without organization to avoid hygiene violations. Ross Duffy suggested a simpler method to disable usage tracking by modifying an environment variable.
KDBX Migration and Access Noise:
The team discussed ongoing issues with Access usage noise and module deletion, confirming that while the noise persisted, no complaints were received until a script-dependent on the module load broke when it was deleted. Ryan Murray provided an update on KDBX negotiations at MSK, noting they are seeking a 150-day trial period to be split into 30-45 days for MSKDB onboarding and remaining days for internal testing. Péter raised concerns about migration solutions for Core to KDBX users, suggesting potential framework changes to accommodate FinOS dependencies, though further discussion with the core team is needed.
KDBX Transition and Licensing Discussion:
The team discussed the transition between core and KDBS, agreeing that there would likely be an overlap period where both systems coexist, especially during the trial phase. They also addressed the issue of KX's licensing model, with Ross Duffy explaining that KX plans to offer CPU or RAM-limited licenses rather than enterprise-wide ones. The team expressed concerns about the monitoring and enforcement of these licenses, with Aaron Davies suggesting that a flat fee might be more practical than tracked usage. Finally, they briefly touched on upcoming KX meetups and the need to experiment with porting modules to the new KDBX system.
Join Zoom Meeting
Date
Monday, March 9th, 2026 - 9:30am ET / 1: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
AI summary of the meeting
Quick Recap
The meeting focused on discussing the FINOS project, including updates on the Linux Foundation dashboard, versioning in the repository, and potential contributions from EPAM. Participants addressed issues with Gradle upgrades, font customizations, and handling long strings in Studio. They also discussed the transition between KDB and KDBX, considering the coexistence of both systems during a trial period. The group explored licensing options for KDBX, with concerns raised about RAM usage limits and monitoring. Additionally, they touched on upcoming KX meetups and the porting of modules to the new module system. The conversation ended with a brief discussion on licensing terms and the need for further clarification on usage tracking.
Next Steps
Ryan Murray: Follow up with Steven at EPAM to check on available resources for the Studio upgrade and provide an update at the next call.
Ross Duffy: Contact Carol (Linux Foundation admin) regarding the issue with updating company affiliation from FD Technologies to KX in the Linux Foundation dashboard.
Aaron Davies: Experiment with porting the zip and statistics modules to the new KDBX module system and consider the appropriate directory structure for KDBX-specific code in the FINOS repo.
Péter: Discuss with the core team whether changes can be made to the framework to allow FINOS functions to hook into the KDBX module system, and explore solutions to avoid code duplication.
Ryan Murray: Review and respond to KX regarding the 150-day KDBX trial period, specifically requesting non-consecutive periods (e.g., 30-45 days for MSKDB onboarding, then a separate period for internal testing).
Ryan Murray: Look into the solution for coexistence and migration between FINOS depends and KDBX module systems for users migrating from Core to KDBX.
Aaron Davies: Update usage of old kdb+ versions in testing to avoid hygiene violations (e.g., by launching de-organized or with usage tracker disabled).
Summary
Linux Foundation Dashboard Issues:
Ross Duffy and Aaron Davies discussed issues with the Linux Foundation dashboard, including difficulties with scheduling meetings and tracking attendance. They encountered problems with the website's functionality, such as slow loading times and inaccurate attendee logs. Aaron Davies noticed that the system showed an incorrect number of attendees and an outdated entry from 1980.
FINOS Project Guidelines Review:
Ross Duffy and Aaron Davies discussed the FINOS project guidelines, including antitrust policies and meeting conduct. They reviewed previous meeting notes and discussed the Linux Foundation dashboard. The agenda for the current meeting was briefly mentioned, though Ryan Murray's absence was noted as potentially affecting FD or EPAM-related topics.
Project Versioning and Website Updates:
Ross Duffy and Péter discussed the version numbering system for their project, with Péter suggesting a more automated approach using Git tags and release jobs. They also touched on the need to update the company name on the Linux Foundation website, though Péter expressed concerns about potential permission issues. Ross Duffy mentioned that Ryan Murray would be joining the meeting shortly.
KX System Access Challenges:
The team discussed issues with adding KX as a company in the system, where Péter encountered problems with the CLA rejection and domain association with FD Technologies PIC. Ross Duffy and Aaron Davies explored potential solutions, including updating the issue template and contacting Carol for administrative assistance. Aaron Davies mentioned he would report the Sidekick recognition issue in the Teams channel, while Ross Duffy confirmed he was the host of the meeting with no pending participants.
FinOS Repository Versioning Updates:
The team discussed updates to the FinOS repository, with Péter explaining that versioning should be implemented through a script in the release job and a GitHub job similar to the QBarse project. Ross Duffy noted that while Dimitri's work could be incorporated directly, there was no current EPAM initiative for Studio development, though Ryan Murray agreed to follow up with Steven about potential resources. Aaron Davies raised concerns about font customization limitations in the output panel, particularly for remote collaboration, and mentioned previous issues filed regarding this problem.
Large Dataset Rendering Challenges:
The team discussed issues with rendering large data sets in Studio, particularly problems with memory allocation and rendering entire tables at once. Aaron Davies suggested implementing pagination for large datasets, while Ross Duffy and Aaron Davies debated whether to merge changes from a fork that may address these issues, with Aaron Davies noting that rebasing could effectively make them a fork of the other project.
Gradle Upgrade and Codebase Alignment:
The team discussed differences between their codebase and Charlie's, noting they are a fork with around 500 commits. Ryan Murray highlighted that upgrading Gradle would unblock Morgan Stanley from building the repository, as there was a hygiene violation due to an outdated Studio release. Aaron Davies suggested addressing the issues in two stages: first fixing Gradle, then picking up new features, as many open issues might already be resolved in Charlie's codebase.
Socket Handle Experimentation Discussion:
The team discussed an email about a socket being opened on handle zero, which Aaron Davies explained was from his experimentation with replicating the automated queue process environment. Péter clarified that this was a safeguard for cases where functions expect handle zero to be standard input. Aaron Davies mentioned using older versions of the software for testing, with permission from Alvin, and discussed ways to launch the software without organization to avoid hygiene violations. Ross Duffy suggested a simpler method to disable usage tracking by modifying an environment variable.
KDBX Migration and Access Noise:
The team discussed ongoing issues with Access usage noise and module deletion, confirming that while the noise persisted, no complaints were received until a script-dependent on the module load broke when it was deleted. Ryan Murray provided an update on KDBX negotiations at MSK, noting they are seeking a 150-day trial period to be split into 30-45 days for MSKDB onboarding and remaining days for internal testing. Péter raised concerns about migration solutions for Core to KDBX users, suggesting potential framework changes to accommodate FinOS dependencies, though further discussion with the core team is needed.
KDBX Transition and Licensing Discussion:
The team discussed the transition between core and KDBS, agreeing that there would likely be an overlap period where both systems coexist, especially during the trial phase. They also addressed the issue of KX's licensing model, with Ross Duffy explaining that KX plans to offer CPU or RAM-limited licenses rather than enterprise-wide ones. The team expressed concerns about the monitoring and enforcement of these licenses, with Aaron Davies suggesting that a flat fee might be more practical than tracked usage. Finally, they briefly touched on upcoming KX meetups and the need to experiment with porting modules to the new KDBX system.
Join Zoom Meeting