Fluxnova Maintainers Meeting - 19/03/2026 #131
Description
Date
Thursday 19 MARCH 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 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.
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)
- Documentation resolution update @gaborherr-db @gaborherr
- OSFF London CFP - OSFF London - June 25 #83
- FluxnovaCon: Initial discussion (Nov 3, NYC) @opoupeney
- Spring Boot 4.0 @pieter-schutte
- PEN Testing Cont. @pieter-schutte
- Unit Tests
- Meeting organization
- Restricted variables update @mr-dibbs
- Continue admin UI/authorization management discussion
- Admin/Authorization UI screens strategy for 3.0
- Review action items from previous meeting
Fluxnova Maintainers Meeting - 12/03/2026 #125 - Following PRs need reviews for release 2.0:
- Check review status of open PRs - Fluxnova Project Board
- 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 related to the Fluxnova project. Topics included sponsorship opportunities for the upcoming Fluxnova Con event, plans to improve code coverage, and the potential modularization of the admin UI.
The team discussed the need for a private repository to support partners and reviewed the upcoming release strategy, including whether the next release should be labeled version 2.1 or 3.0. Progress updates were shared on Docker image publication, migration pull requests, and the development of backward‑compatibility plugins.
The group also reviewed meeting structure and agreed to separate AI‑related discussions into bi‑weekly sessions. Additionally, plans were made to finalize the agenda for public meetings to better support and onboard new participants.
Next Steps
- Olivier: Talk to Harish Malavade separately to determine if a dedicated session or just an announcement is needed for OSFF London, and communicate decision.
- Olivier: Share the sponsorship deck for Fluxnova Con in the private mailing list.
- Juan/Participants: Identify and put decision makers in contact with Olivier regarding potential sponsorship for Fluxnova Con.
- Pieter: Discuss with Riaz what exactly needs to be tested for pen testing and inform Olivier.
- prajwol bhandari: Create a ticket/story in the project board for adding Jacoco (or similar) for code coverage measurement.
- Ryan: Create a new story/issue for requiring 80% code coverage for new contributions and tag it with the existing coverage issue.
- Gábor/Team: Find and reference the previous issue for check style formatting, and proceed with implementation as a separate task.
- Edson Gianesi (Fidelity Investments): Create a new page for roadmaps on the project website and coordinate with team to agree on published content.
- Juan: Create a discussion (or issue) for the proposed public meeting agenda and send a follow-up to Harish Malavade (Fidelity Investments)'s email.
- Juan: Change the AI working group call cadence to bi-weekly and set up next meeting accordingly.
- Juan/Team: Start working on an AI roadmap and begin discussion in the next AI working group call.
- Edson Gianesi (Fidelity Investments): Take note to get a style guide in place for UI apps (to allow for consistent look and feel across different tech stacks).
- Rachana Ramshetty: Notify Juan when the Fluxnova Docker image PR is ready so Juan can inform interested parties.
- Pieter: Communicate to Suresh to look at the migration PR (PR 117) and related issue, and facilitate resolution of outstanding comments.
- Harish Malavade: Approve and merge migration PR 117 once build is passing, and coordinate with Pieter for final approval.
- Harish Malavade: Approve and merge PR 724 (tagged Pieter and Gabor) for the 2.0 release.
- Karl: Ping Juan offline to discuss next steps for the private "Fluxnova support" repo for partner collaboration.
- Olivier: Talk to Gab and Grace to see if a 10-15 minute Fluxnova overview/demo can be included in the OSFF London keynote.
- Harish Malavade: Contribute backward compatibility plugin to plugins folder after internal implementation (and forward compatibility if possible).
Summary
OSFF London Presentation Planning
The main business discussion focused on OSFF London preparations, where it was reported that the submitted talk content was insufficient. An alternative approach was suggested: using a keynote announcement for Fluxnova 3.0 and the new UI. It was agreed to follow up to determine whether a dedicated session or a keynote announcement would be sufficient for the presentation.
Fluxnova Con Planning and Sponsorship
Plans were announced for Fluxnova Con, a half‑day event scheduled for Monday, November 6, ahead of OSFF New York on Tuesday. The event will feature keynotes and technical sessions across multiple tracks. Sponsorship opportunities were outlined, including main sponsorships for banks at $10K, with five spots available. The group discussed the need to secure sponsorships before proceeding with the event and agreed to connect decision‑makers with the event organizer. A sponsorship deck will be shared via the private mailing list.
Regarding pen testing, it was agreed that requirements would be reviewed internally, with follow‑up communication to be sent via email.
80% Unit Test Coverage Implementation
The team discussed implementing 80% unit test coverage for the platform. There was support for requiring this level of coverage for all new code contributions. Suggestions included adopting a “fix it as you go” approach using SonarQube and implementing coverage checks within the CI/CD pipeline. The group also discussed adding style and formatting checks, noting that some related issues already exist. New stories will be created and linked to existing issues where appropriate.
Meeting Structure Restructuring Discussion
The team discussed separating meeting types to better serve different audiences. It was agreed that public meetings should focus on roadmap updates, demonstrations of new functionality, and Q&A for new participants, while AI working group calls should remain focused on AI‑specific topics. The group also discussed using these meetings to promote upcoming OSFF events and improve the project website. Adjusting the AI meeting cadence from weekly to bi‑weekly was proposed due to the current pace of development.
Bi‑Weekly Meeting Cadence Change
The team agreed to move to a bi‑weekly meeting cadence. The next meeting will be skipped, with the AI working group reconvening the following week. The need to develop an AI‑specific roadmap was discussed and will be addressed in future meetings with a dedicated timebox. The group confirmed that technical and maintainer calls will remain separate, with acknowledgment that topics had previously overlapped.
Microservices Admin UI Authorization
The team discussed implementing a microservices approach for the admin UI authorization management system. There was support for separating functionality into distinct applications, citing benefits such as reduced resource requirements and the ability to test components independently. The idea of allowing each application to grow independently while maintaining smooth navigation between them was discussed.
A concern was raised about potential divergence in frontend technology stacks, particularly between Angular and React. The discussion concluded with a suggestion to publish a shared style guide to help address these concerns.
Technology Stack Decision Discussion
The team continued discussions around Angular versus React, referencing recent experiences where AI‑assisted design tools generated React‑based code. Action items from a previous meeting were reviewed, including the publication of a Fluxnova Docker image, which is currently in progress but not part of the 2.0 release.
The team also discussed the migration of AI code to a new plugins repository. While overall feedback was positive, some comments highlighted unresolved local setup issues that still need to be addressed.
Release 3.0 Planning and Preparations
Several key topics were discussed related to the upcoming release scheduled for the 27th, including PR reviews and preparations for code freeze. It was proposed that two critical PRs be merged to initiate the code freeze, with agreement to finalize builds within the next few days.
The group debated version numbering for the next release, with a proposal to move to version 3.0 due to breaking changes in the cockpit UI, alongside concerns about increasing major versions too frequently.
The team approved creating a private Fluxnova Support repository for partners to share best practices and documentation. Plans for presenting Fluxnova at SFF London were also discussed, with follow‑up coordination planned around potential keynote opportunities.