Fluxnova Maintainers Meeting - 22/01/2026 #73
Description
Date
Thursday 22 JAN 2026 - 9am (US eastern timezone EDT/EST) / 2pm (London, GMT/BST)
Zoom info
- Join Zoom Meeting
- Meeting ID: 965 5333 5469
- Passcode: 536792
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.
Tracking Attendance
Note: Meeting participants are expected to add a comment to this GitHub issue in order that we can track attendance of Fluxnova project meetings. Please do this at the start of the meeting.
Agenda
- Convene & roll call, review meeting notices (5mins)
- Review action items from previous meeting
- Check review status of open PRs on each repo
- AOB & Adjourn (5mins)
Minutes
Note that the minutes were generated by AI and may not be fully accurate
Quick recap
The meeting focused on updates and discussions around the Fluxnova project, including migration tools, training materials, and strategic initiatives. Team highlighted issues with the migration tool, particularly regarding in-place upgrades and job definitions, while positive updates from the board meeting where shared, including budget approval and plans for a Fluxnova Conference. The team discussed the need for better documentation and training materials, with plans to work with Linux Foundation Education on instructor-led training. The team presented a new feature proposal for restricting access to sensitive data, which was well-received, though concerns about performance were raised. The conversation ended with discussions on performance benchmarking and GitHub actions for documentation generation.
Next steps
- Harish's team: Create a GitHub issue listing all migration tool gaps/issues encountered, including specific examples and scenarios
- Ryan: Add items encountered during migration tool demo to Harish's team's list of gaps
- Pieter: Add Maven archetype documentation to examples folder as quick start documentation
- Chris: Present restricted variables implementation details to maintainers next Thursday
- Chris: Add restricted variables feature to March 31st release list
- Gabor: Review and provide commentary on pull requests for GitHub actions for generating documentation, Java docs and API specs
- Juan: Help Gabor with credentials needed for GitHub pages publishing mechanism
- All maintainers: Contribute examples for different integration scenarios while waiting for official training
- Olivier: Ensure all maintainers have access to the formation repo for tracking private discussions
- Harish's team: Document detailed issues with migration tool including complex model test scenarios with async jobs
- Olivier: Start planning for initial set of trainings in Q1
Summary
Fraud Management Tools Discussion
The meeting began with introductions and a brief discussion about fraud management solutions, where exploring BPM and DMN tools where mentioned. Juan confirmed that AI transcription and summarization would be used for future meetings, with notes to be shared internally.
Release Timeline and Migration Tool Issues
The team discussed the release timeline and migration tool issues. The 2.0 release is tentatively scheduled for March 27, including features and the Cammunda 7.24 merge. They identified gaps in the migration tool, such as script tasks not being updated and the need for in-place upgrade. The importance of not requiring business partners to handle instance migration was mentioned, and the team discussed potential solutions like building a plugin or utility for model migration. The tool's gaps will be addressed during the demo next week and added that input on terminal commands to address these issues will also be provided.
Fluxnova Migration Strategy Discussion
The team discussed their use of a tool across two products and plans for migrating to Fluxnova, with strategy explained for an in-place upgrade to eliminate Camunda dependency. The team also outlined challenges with job definitions and proposed a runtime plugin solution to address class name issues during upgrades. Updates from Finos board meeting where shared, where Fluxnova was presented as a strategic initiative with an approved budget. The board meeting included feedback from JP Morgan about AI features, which was countered by other board members emphasizing the value of Fluxnova's current direction. The team also discussed plans for the first Fluxnova Con conference in November, which will be branded as a separate event from OSFF.
Fluxnova Documentation and Features
The team discussed several key topics around Fluxova documentation, training, and new features. They agreed to create example projects and documentation to help users get started, with planning to drive training development through Linux Foundation Education. Team presented a new feature proposal for restricted variables to address PII data security needs, which will be implemented for the next release. The team also discussed performance concerns around the proposed variable authorization system and agreed to explore benchmarking options. Team shared a need for performance benchmarking.