-
Notifications
You must be signed in to change notification settings - Fork 165
Description
Group overview
FDC3 maintainers working meeting
Meeting Date
Wednesday 11th Feb 2026 - 9am (US eastern timezone EDT/EST) / 2pm (London, GMT/BST)
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.
-
A Discussion Group has no direct decision-making power regarding the FDC3 standard - rather it is intended that anything they propose or work on will result in proposals (via Github issues and PRs) for the Standards Working Group participants to consider and vote on for inclusion in the standard.
Participation Requirements
By invitation of the FDC3 maintainers
Tracking Attendance
Agenda
(FDC3-maintainers & FINOS to add agenda items below)
- Convene & roll call, review meeting notices (5mins)
- Review past meeting minutes and action items
- 2.2.2 release status + conformance
- ESM PRs Esm modules fix #1677
- Security & metadata additions
- Workbench PRs Migrate to MUI 5 #1714
- Other open PR reviews
- AOB & Adjourn (5mins)
Meeting Minutes
-
Review past meeting minutes and action items
- Strategic initiative for security is renewed; @robmoffat will continue work for another six months.
- Progress continues on metadata initiative; @julianna-ciq and @kriswest have moved work to a new PR (FDC3 API Metadata #1728). JSDoc updates and further reviews are pending.
- Some outstanding issues remain in schema validation for metadata due to duplicate properties.
- Reference implementation updates and conformance test changes need to be completed before merging metadata PR.
- The maintainers list and Slack group will be trimmed to only active maintainers; action is pending.
- Previous dependency scanning PRs discussed, but some confusion remains about specifics.
-
2.2.2 Release Status + Conformance
- The major 2.2.2 PR has been merged, with many bug fixes.
- Next step is to remove version numbers from conformance test names (Removed version numbers from conformance test names #1726); @robmoffat has a PR for this, with a follow-up PR from @kriswest planned.
- For future releases, conformance tests will be tagged and frozen per release.
- PR to prevent fdc3-web-impl from delivering broadcast messages back to sender (Stop fdc3-web-impl delivering broadcast messages back to the sender #1749) is considered ready, pending review and testing.
- Discussion on whether additional fixes should be included in the 2.2.2 release, especially ESM module fixes.
-
Security & Metadata Additions
- FDC3 API Metadata PR (FDC3 API Metadata #1728) in progress; final JSDoc work and reviews pending.
- FDC3 Security in MonoRepo (FDC3 Security In MonoRepo - NOT READY TO REVIEW #1627) is not ready for review yet, likely to be superseded by further work.
- Metadata changes will enable easier integration for security documentation and future updates.
- Decision made to focus on getting changes correct for FDC3 3.0 rather than adapting for older versions.
-
Workbench PRs
- Workbench has been migrated to MUI 5 (Migrate to MUI 5 #1714) by @Roaders; some additional fixes were applied by @kriswest.
- Issues with tests timing out have been addressed; further review and changelog updates are required.
-
Other Open PR Reviews
- ESM modules fix (Esm modules fix #1677): @Roaders provided details of the migration challenges and proposed solutions. Review is required before merging, with additional input from @julianna-ciq and @hughtroeger.
- Plans to switch code coverage reporting to CodeCov are pending; action item assigned for implementation.
- Dependency scanning PRs (Dependabot): ongoing maintenance and some confusion on specifics.
- Java documentation PR (Added Java documentation #1734) added by @robmoffat for FDC3 3.0, requires review.
- AppDirectory test conversion to Jest and run in CI (test: convert AppDirectory test to Jest and run in CI #1720): flagged as conflicting with the ESM PR; should be merged post-ESM update.
- Instrument classification PR feat(context): add instrument classification property #1665: @hughtroeger flagged as ready, awaiting final review from @openfin-johans.
- Test coverage and static analysis: some ignores added to resolve issues with SAST scanner (Semgrep).
-
Release Planning
- Decision reached (subject to SWG approval) to move forward with a 2.3.0 release instead of 2.2.2, to accommodate additional features (such as context cleared event and instrument classification).
- A conformance test addition will be needed for contextCleared - a definition was already added App Channels, one is needed for User channels and both need to be implemented.
- This work is needed for 3.0 anyway, and can occur after the 2.3 release.
- A conformance test addition will be needed for contextCleared - a definition was already added App Channels, one is needed for User channels and both need to be implemented.
- Next steps include:
- Get approval from SWG for a modest 2.3 release
- Merging outstanding PRs,
- Versioning docs for 2.3
- Running a release candidate for 2.3.0
- Promoting that candidate to final 2.3.0 release
- Decision reached (subject to SWG approval) to move forward with a 2.3.0 release instead of 2.2.2, to accommodate additional features (such as context cleared event and instrument classification).
Action Items
- @julianna-ciq to complete JSDoc updates for Metadata PR (FDC3 API Metadata #1728) and review @kriswest's recent changes.
- @kriswest to raise and merge PR to remove version numbers from conformance tests and implementation details.
- @kriswest to proceed with maintainers list and Slack group trimming.
- @julianna-ciq to review ESM modules PR (Esm modules fix #1677) from @Roaders and check for issues with .js extensions and static analysis ignores.
- @hughtroeger to review ESM modules PR (Esm modules fix #1677) and CommonJS build for compatibility.
- @kriswest to switch code coverage reporting to CodeCov, with support from others as needed.
- @openfin-johans to review instrument classification PR (feat(context): add instrument classification property #1665) as per @hughtroeger’s request.
- @kriswest to merge PR to prevent broadcast messages to sender (Stop fdc3-web-impl delivering broadcast messages back to the sender #1749) after review and testing.
- @Roaders to request or apply updates to and merge AppDirectory Jest test conversion PR (test: convert AppDirectory test to Jest and run in CI #1720) post-ESM update.
- @kriswest and @Roaders to coordinate merging MUI 5 migration and follow-up fixes for Workbench after ESM module changes PR.
- @Roaders to update changelog entry for Workbench migration PR to include PR number.