FDC3 Sail Project Meeting - March 30th 2026 #229

Date & Time

2026 March 30th - 13:00 UTC

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

Those logged in using the LF Meetings will be automatically tracked.

Agenda

• Convene & roll call (5mins)
• Display FINOS Antitrust Policy summary slide
• Review Meeting Notices (see above)
• Review action items from previous meeting FDC3 Sail Project Meeting - March 2nd 2026 #221 (5mins)

Review Items:

• Security Demo - Sail security demo #234
• Releases Retrospective releases: tag v1.0.0 and v2.0.0, and document versioning policy #222 - https://github.com/finos/FDC3-Sail/releases

Issues:

• Vote: Project Structure - Sail v3 #223
• Upgrade FINOS App Directory Apps to use FDC3 for the web. #163
• Branch Pruning #233
• Remove the Directory Folder #232

PRs:

• Add zoom details to meeting minutes template #235
• Fix #226: Add meeting registration and join links #237
• Feature/issue 177 enhanced config screens #238
• Update README.md to enhance badge display and improve alignment #239

Project Info

• Project Board for work and Release Tracking - FDC3-Sail (view)

Events:

• OSFF Toronto

• OSFF London

• AOB, Q&A & Adjourn (5mins)

Action Items

• @SeeWhatsOn : Temporarily migrate FDC3 testing code into Sail, ensuring tests are functional, and mark this as technical debt to be replaced when the official FDC3 testing package is available
• @robmoffat: Move non-example apps from the top-level directory into the example apps directory in Sail
• @SeeWhatsOn : Create an issue and gap analysis in FDC3 for required example applications, propose a style guide/README for FDC3 example apps, and create issues for missing example apps (in the FDC3 Repo)
• @SeeWhatsOn : Add OpenSSF scorecard to FDC3 repository
• @SeeWhatsOn : Investigate current FINOS project lifecycle status and requirements for Sail
• @SeeWhatsOn : Follow up with Adaptable (or relevant contact) regarding updating their app to support FDC3 2.2
• @robmoffat: Create a pull request to merge the "added build instruction" branch (which adds NPM run build to README)
• Chris: Review outstanding security issues in Sail and determine/propose workflow for PR review/merge of security-related changes

Meeting Minutes

Quick Recap
The meeting focused on reviewing progress and addressing issues for the FDC3 Sail project, including updates on security demos, testing packages, and project structure. Rob demonstrated new security features and applications, while discussions centered on challenges with testing dependencies and the need to migrate testing packages from personal namespaces to properly governed Finos projects. The team agreed to temporarily disable failing tests and manually migrate existing test code from FDC3 to Sail as a stopgap solution. They also discussed updating example applications to use FDC3 2.2, creating a style guide for consistent visual presentation, and implementing OpenSSF scorecard best practices. The conversation ended with plans to clean up old branches and improve project organization, with particular attention to aligning V2 to V3 development standards.

Next Steps:
(see action items)

Summary
FDC3 Meeting Registration Issues:
The team discussed meeting time zone alignment with the US, which has been restored. Chris experienced issues with not being added to the FDC3 meeting invitee list despite registering, and Kris helped troubleshoot by checking the project control center. They discovered Chris's registration wasn't properly recorded in the system, and Kris suggested Chris should re-register for each meeting individually to resolve the issue.

FDC3 Sail Project Updates:
The meeting focused on updates to the FDC3 Sail project and welcoming new participants. Chris reviewed previous meeting outcomes, including changes to meeting times and the implementation of a project board for tracking releases. The team discussed a new project structure, which was agreed upon by most participants, and noted that it remains open for feedback. Vinayak, a new participant, introduced himself as a principal architect from SCL Tech with an interest in FDC3 for financial services applications. Chris provided guidance on resources for learning more about FDC3 and Sail, including the FINOS website and GitHub repository.

Sail Project Updates and Features:
Chris and Rob discussed updates to the Sail project, including new releases (Sail 1 and Sail 2) and various demos added to the system. Rob demonstrated the security features and encrypted channels functionality, showcasing how intents and identity tokens work within the system. He mentioned having to republish versions of FTC3 and FTC3 Security due to compile errors in the 2.2 branch, and noted that he had raised a PR to address missing exports in the agent proxy package.

FDC3 Export and Governance Issues:
The team discussed issues with exporting fields and testing packages for FDC3. Kris raised concerns about exporting unnecessary internal implementation details and suggested reviewing each field's use case for external consumption. Rob explained his work on creating a separate testing package called "Standard Cucumber Steps" to be used across multiple projects, but Kris emphasized the importance of following governance practices by publishing it under proper Fino's governance rather than a personal namespace. The team agreed to temporarily disable the failing tests in Sail while working toward a solution that would either publish the testing package from FDC3 or contribute it to the foundation properly.

FDC3 to Sail Migration Strategy:
Chris proposed a solution to handle tests by manually migrating code from FDC3 to Sail as a stopgap measure, ensuring tests continue passing while avoiding heavy reliance on the FDC3 project. Rob agreed to this approach, and they decided to leave the main FDC3 project untouched for now. Regarding demos, Rob mentioned starting work on moving them into the FDC3 project but faced compile issues with metadata, and Kris suggested focusing on simpler demos first before tackling security-related ones. Kris noted they would return to addressing metadata compile issues after completing their PI planning.

FDC3 App Directory Migration Planning:
The team discussed moving the app directory to use FDC3 for web, with Chris deciding to close the current issue and handle it through FDC3 instead. They determined that most existing examples were outdated or only one app (Adaptable) still needed updating, and agreed to create new example applications that would be independent of Sail. The team aligned on developing both real-world examples contributed by FDC3 standard working group members and simple reference examples, with Kris suggesting they should establish consistent styling guidelines for the examples to follow FDC3 and Sail branding standards.

FDC3 Style Guide Planning Meeting:
The team discussed creating a style guide for FDC3 examples, with Chris agreeing to create a basic style sheet and README file in the FDC3 examples folder. They decided to conduct a gap analysis of existing example apps and raise issues to fill in any gaps. Regarding the Adaptable product integration, they determined that upgrading to FDC3 2.2 would be needed, but access to the required code is restricted as it's part of their proprietary product. The team also confirmed decision B for project structure, putting everything under packages, and agreed to close the related issue.

FTC Repository Cleanup Discussion:
The team discussed cleaning up old branches in the FTC repository, with Chris identifying several branches over a year old that needed deletion. Rob confirmed these could be removed, and Kris suggested extending the same cleanup to the FDC3 repository. The group also discussed organizing application directories more efficiently, with Rob agreeing to move certain applications into the example apps directory. Chris proposed implementing the OpenSSF scorecard for security assessment, which Kris supported as a good starting point for improving security practices. The team noted that while there are currently only two active maintainers, there is growing interest from other firms in adopting the FTC3 desktop agent implementation.