Description
Date
Thursday 26th September 2024 - 10am (US eastern timezone EDT) / 3pm (London, BST)
Zoom info
- Join Zoom Meeting
- Meeting ID: 969 4029 4948
- Passcode: 636931
- Dial-in:
Country International Dial-in Toll-free Dial-in US +1 929 205 6099 (New York) 877 853 5247 UK +44 330 088 5830 0800 031 5717 France +33 1 8699 5831 0 800 940 415 Find your local number https://zoom.us/u/ad2WVnBzb8
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.
Participation Requirements
Note: Meeting participants are expected to accept the terms of the FDC3 license (Community Specification License), understand the governance process and have a CLA in place.
Please click the following links at the start of the meeting if you have not done so previously.
- View the CSL
- View the GOVERNANCE of the Project
- Click here to start a PR.
- Edit the page to add your details.
- Hit the save button.
- Click "Create Pull Request".
- Click "Accept" on the EasyCLA dialog in the PR's discussion section.
- Click here to send email to become a voting participant on the FDC3 Project
Tracking Attendance
Note: Meeting participants are expected to add a comment to this GitHub issue in order that we can track attendance of FDC3 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 (5mins)
- Announcements: OSFF presentations (5mins)
- Proposal to include FDC3 for the Web in the FDC3 2.2 draft as @experimental (15 mins)
- Check consensus on the inclusion of several smaller issues in 2.2 (10mins):
- Intent Proposal: Create or Update Profile #591
- CommonJs vs ES6 #1351
- fdc3.entity.fileAttachment is only defined inline in the fdc3.message schema and example has wrong type #1255
- Merge api/ref/types and api/ref/metadata pages and correct links, including from generated context docs #1282
- Support broadcast in FDC3 Action #1353
- Proposal to close the scope for FDC3 2.2 and push other open issues and PRs to FDC3 2.3 (10mins)
- Adjourn
Minutes
- Incomplete action items from the previous meeting were rolled over
- @kriswest Asked the Standards Working Group participants if there was consensus for the inclusion of the FDC3 for the Web proposal in the FDC3 2.2 scope as @experimental and for the PR (FDC3 for Web specification #1191) to be merged once it clears review by FDC3's editor.
- Consensus was given (unanimous, with several participants speaking for the proposal and the and the rigour of the process used to create it)
- @kriswest Also asked if there was consensus for the inclusion of the set of issues detailed in the agenda to be included in the FDC3 2.2 scope.
- There was consensus that the following issues be included:
- Intent Proposal: Create or Update Profile #591
- fdc3.entity.fileAttachment is only defined inline in the fdc3.message schema and example has wrong type #1255
- Merge api/ref/types and api/ref/metadata pages and correct links, including from generated context docs #1282
- Support broadcast in FDC3 Action #1353
- An objection was recorded to the following issue, with the maintainers requested to review alternative options (as CommonJS is still in use in some places in front-end apps):
- There was consensus that the following issues be included:
- @kriswest Asked if there was consensus on closing the resulting 2.2 scope (and provided an overview of the proposed scope, a possible scope for 2.3 and open issues not in any proposed scope), allowing the maintainers to focus on the delivery of that scope, with any further issues being bumped to FDC3 2.3 or beyond).
- There was consensus that we should adopt the proposed 2.2 scope.
Action Items
- @finos/fdc3-editors and @finos/fdc3-maintainers to complete review of FDC3 for Web specification #1191 and merge into the current (FDC3 2.2) draft
- FDC3 maintainers and interested contributors to revisit CommonJs vs ES6 #1351 as it should continue to be possible to publish a combined CommonJS and ES6 module, or to raise an alternative proposal.
- @kriswest to update milestones to finalize 2.2 scope and @finos/fdc3-maintainers and @finos/fdc3-editors to work towards delivering 2.2
Rolled over:
- All encourage review of the fdc3-dtnet 2.1 update:
- @kriswest Update the proposal for Support for Multiple Application Scopes (Agents) within a single window process #1250 to include a tear down function for 'subAgents'.
- @julianna-ciq and @Davidhanson90 to meet and discuss the alternative proposal to resolve Add property to support analytics across apps #1290 posted @kriswest as a comment on the issue, before it is debated at next month's meeting
- @bingenito create a PR to add the advice about consistent use of pascal case in enums in the API (implementation language and context docs (The Context Interface section after advice on union types).
- @kriswest @hellosmithy PR to be raised for Context Clearing #1197
Untracked attendees
| Full name | Affiliation | GitHub username |
|---|---|---|