FDC3
FDC3 copied to clipboard
Standard WG Meeting - July 28th, 2022
Date
Thursday 28th July 2022 - 10am EST / 3pm BST
WebEx info
- Meeting Link Meeting number: 665 568 411
More ways to join
- Join by video system:
- Dial [email protected]
- You can also dial 173.243.2.68 and enter your meeting number
- Join by phone
- +1-415-655-0003 US Toll
- +44-20319-88141 UK Toll
- Access code: 665 568 411
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.
Agenda
- [x] Convene & roll call, review meeting notices (5mins)
- [x] Review action items from previous meeting (5mins)
- #757
- [x] Maintainers update (5 mins)
- FDC3 2.0 release progress and timeline
- https://github.com/finos/FDC3/milestones
- #753
- Adoption of Community Specification License
- #775
- FDC3 Workbench update plans
- #785
- #786
- #787
- #788
- FDC3 Conformance Framework #583
- FDC3 2.0 release progress and timeline
- [x] Discussion groups update (10 mins)
- Desktop Agent Bridging
- #634
- Context & Intents
- #765
- #766
- #767
- #768
- #592
- #771
- #644
- #655
- #656
- #387
- Release Frequency
- AppD discussion group (some outstanding issues from #718)
- Desktop Agent Bridging
- [x] FDC3 2.1 scope discussion (30 mins)
- Open issues:
- Project infrastructure
- #412
- #579
- #762
- #749
- AppD issues:
- #312
- #559
- #563
- #564
- #674
- #719
- API issues:
- #301
- #242
- #311
- #386
- #387
- #735
- Context & Intents issues
- See discussion group update above
- #684
- Project infrastructure
- Open issues:
- [x] AOB & Adjourn (5mins)
Minutes
- Discussion groups:
- AppD: There was no consensus that the appD discussion group should be revived to deal with the remaining issues, hence these will be dealt with through SWG meetings.
- Desktop Agent bridging: the group is closing in on a first complete draft which may be ready to share at one of the next couple of SWG meetings
- The Context & Intents group remains active and will continue to manage its own scope and bring back a batch or batches of issues for inclusion in the next FDC3 draft.
- The group is still seeking a way to release its work faster (than the typical cadence for FDC3 releases, which is about once a year) - API changes etc. are not needed for new Contexts & Intents to go into use.
- FDC3 maintainers to discuss options for a solution:
- Introduce a third tier to version numbers for Context & Intents releases and do them quarterly?
- Release an updated NPM module on merges to trunk (version: "next")
- Separate versioning on Intents and Contexts from the API standards (Desktop Agent and AppD).
- FDC3 maintainers to discuss options for a solution:
- The group is still seeking a way to release its work faster (than the typical cadence for FDC3 releases, which is about once a year) - API changes etc. are not needed for new Contexts & Intents to go into use.
- FDC3 2.1 scope discussion
- Context & Intents issues to stay with that group until ready
- Desktop Agent Bridging issues to stay with that group until ready
- Project infrastructure issues to be handled by maintainers - volunteers to assist most welcome!
- All other open issues were briefly reviewed - most warrant further discussion.
- Rough ordering by interest expressed in discussion by meeting participants:
- #719
- #387
- @kriswest believes this could be dealt with through Intents & Contexts + FDC3 2.0's ability to return results from intents and suggested that brief PoC is sketched out for discussion at a future meeting.
- #312
- #674
- #242
- #301
- #559
- #563
- #735
- #386
- #311
- #564
- The end of the meeting curtailed discussion before we reached:
- #684
- All were invited to raise new issues for issues they would like to see discussed and/or addressed in a future FDC3 version.
Action Items
- [ ] @hampshan Review appD 2.0 record properties and raise an issue to add a link to an app's help documentation (if the
moreInfo
link is not sufficient). This might be used, for example, to add a help link to window chrome in a desktop agent. - [ ] @kriswest Plan agendas for future SWG meetings
- base the plan on a queue of issues that we can maintain, ordered using the input given at this meeting
- [ ] @robmoffat further the discussion of #684 outside of SWG meetings - then request adding to an agenda when ready.
Untracked attendees
Full name | Affiliation | GitHub username |
---|---|---|
Brian Ingenito / Morgan Stanley :wave:
Milind Chidrawar / Singletrack
Julia / FINOS
Pierre Neu / Symphony
Jane / FINOS
Vinay / Symphony
Georgi / Tick42
Kris / Cosaic
Andrew Hampshire @ UBS
Qiana / Citi
Tiago Pina / Cosaic
Hugh Troeger / FactSet
Riko Eksteen / Adaptive
Minutes for yesterday's meeting have now been posted.
Please do raise issues or (github) discussions for anything you'd like to see discussed at future meetings!
Thanks Kris. Will take a careful look.
From: [github.com] Kris West @.***> Sent: Saturday, July 30, 2022 1:00 AM To: finos/FDC3 Cc: Chen, Qia Qiana [ICG-IT]; Comment Subject: Re: [finos/FDC3] Standard WG Meeting - July 28th, 2022 (Issue #784)
This Message is From an External Sender
This message came from outside of your organization.
Minutes for yesterday's meeting have now been posted.
Please do raise issues or (github) discussions for anything you'd like to see discussed at future meetings!
— Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/finos/FDC3/issues/784*issuecomment-1199751649__;Iw!!Jkho33Y!gjqIeM4z9SuDytDTJsAVnC_L7Bv1TaVsfEIuyZKYuT1r5sXvls-gBjJjSTeS1F69cjPQ0HA5ImP4x_RL0EWydllqlAU$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AVCUVSPGSHC3E3N4PDCVQHDVWQEXFANCNFSM544XFGKA__;!!Jkho33Y!gjqIeM4z9SuDytDTJsAVnC_L7Bv1TaVsfEIuyZKYuT1r5sXvls-gBjJjSTeS1F69cjPQ0HA5ImP4x_RL0EWyMxIu-oU$. You are receiving this because you commented.Message ID: @.***>