Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Standard WG Meeting - March 24, 2022 #637

Closed
11 of 13 tasks
kriswest opened this issue Mar 24, 2022 · 25 comments
Closed
11 of 13 tasks

Standard WG Meeting - March 24, 2022 #637

kriswest opened this issue Mar 24, 2022 · 25 comments
Labels
indexed When a meeting attendance is being tracked meeting Standard WG Meeting

Comments

@kriswest
Copy link
Contributor

kriswest commented Mar 24, 2022 •
edited
Loading

Date

Thursday 24 March 2022 - 10am EDT / 2pm GMT

WebEx info

More ways to join

  • Join by video system:
  • 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 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.

Agenda

Minutes

  • Update on Compliance testing project

    • Will add another application to the FDC3 toolbox folder
    • Implementation team have noticed some initial failures in vendor implementations and will email the support team for each product privately to report
    • The next version will need to run against an app directory to enable intent testing and will need a way to point a vendor platform at an app directory (likely to be a proprietary setup step for each product)
    • Tests will only run against an API implementation and will not test behaviour in apps (e.g. to confirm that the action on receiving an intent)
      • i.e. the scope of the tests is the API specification itself, no more, no less

  • Remaining work to complete FDC3 2.0 pre-draft

    • Discussion groups
      • @kriswest proposed the following goals for the open discussion groups:
        • Attempt to get App Directory group's work done for v2.0 (existing roadmap commitment for FDC3 2.0)
        • Desktop Agent Bridging should not be tied to FDC3 2.0 and can be added in a later release (although enabling issues might be included in FDC3 2.0),
        • Context and Intents group to deliver a batch of additions for 2.0 and then to continue post 2.0 and make further additions
      • No objections were raised and silent consent recorded
    • Experimental features
      • An overview of the proposed policy was provided (see PR 533 experimental features #549)
        • Make experimental features optional by definition
        • Exempt them from versioning/deprecation policies
        • clearly indicate experimental status in sources and documentation
        • designation should be used sparingly as it is expected to reduce uptake of designated features
      • FDC3 maintainer @rikoe @kriswest are both agnostic as to whether this policy is adopted
      • @bertrand-s spoke FOR experimental features as there is a clear use-case for the RichTextBlock proposal from the contexts and intents group
      • No objections were raised to the adoption of the experimental feature policy, one supportive
      • No objections were raised to the referral of the final decision to the maintainers
    • Adoption of Community Specification License
      • @Julia-Ritter / FINOS to Distribute information about what changes or other actions would be required to switch to the CSL.
        • Updates are expected over the next month
    • Allow an app to retrieve its own AppMetadata #603
      • A question was raised about why this API would be used
      • specific concerns to be added to the issue
      • use-cases provided on issue to be expanded
      • No decision was made -> stand over to next meeting
    • Other open issues were skipped skipped -> decisions need to be taken at next meeting
      • Please look at issues before next meeting

  • Require propagation of originating application identity on context/intent handlers #520

    • It was noted that, even if we make it the responsibility of the Desktop Agent to supply originating app credentials, you still have to trust the desktop agent
      • @bingenito commented that someone could implement their own desktop agent, spoof the AppMetadata AND the ImplementationMetadata to appear to be another desktop agent
      • Hence the proposal, as raised, doesn't fully solve for the use-case
        • However, a number of participants still thought it a useful addition that should go ahead - no opposition to this was raised
        • @kriswest recommend that the issue move to a PR next - to be considered at next meeting
      • Further discussion of 'trust' is warranted
        • A one-off special meeting should be arranged for interested parties to discuss and propose a way forward
          • however this shouldn't block the PR and current proposal moving ahead - several meeting participants noted that they would still find that change useful regardless of the trust issue
        • @kriswest to set-up a poll dates/times and arrange meeting

Decisions Made

  • Attempt to get App Directory group's work done for v2.0 (existing roadmap commitment for FDC3 2.0)
  • Desktop Agent Bridging should not be tied to FDC3 2.0 and can be added in a later release (although enabling issues might be included in FDC3 2.0),
  • Context and Intents group to deliver a batch of additions for 2.0 and then to continue post 2.0 and make further additions

Action Items

Untracked attendees

Full name Affiliation GitHub username
@Julia-Ritter
Copy link
Contributor

Julia / FINOS

@pierreneu
Copy link

Pierre Neu / Symphony

@bingenito
Copy link
Member

Brian / Morgan Stanley

@ColinEberhardt
Copy link
Contributor

Colin / Scott Logic

@dbutt-scottlogic
Copy link

David Butt / Scott Logic

@timjenkel
Copy link

Tim / Wellington

@mistryvinay
Copy link
Contributor

Vinay / Symphony

@nicopreto
Copy link

Nico Pretorius / Scott Logic

@bertrand-s
Copy link
Contributor

Bertrand / Symphony

@hampshan
Copy link

hampshan commented Mar 24, 2022 •
edited
Loading

Andrew Hampshire @ UBS

@kriswest
Copy link
Contributor Author

Kris West / Cosaic

@hughtroeger
Copy link
Contributor

Hugh Troeger / FactSet

@dominicgifford
Copy link
Contributor

Dom GIFFORD / S&P Global

@lspiro-Tick42
Copy link

Leslie / Glue42

@robmoffat
Copy link
Member

Rob / FINOS

@WatsonCIQ
Copy link
Contributor

Chris Watson / Cosaic

@sarahaislinnstone
Copy link

Sarah Stone / Cosaic

@thorsent
Copy link
Contributor

Terry Thorsen / Cosaic

@MichaelMCoates
Copy link

Michael / OpenFin

@Soul-Master
Copy link

Sumit / LSEG

@openfin-johans
Copy link
Contributor

Johan / OpenFin 🎁

@mattjamieson
Copy link
Contributor

🚀

@RandallDang-Citi
Copy link

Randall / Citi

1 similar comment
@RandallDang-Citi
Copy link

Randall / Citi

@Qiana-Citi
Copy link

Qiana / Citi

@kriswest kriswest mentioned this issue Apr 28, 2022
Closed
17 tasks
@github-actions github-actions bot added the indexed When a meeting attendance is being tracked label Apr 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
indexed When a meeting attendance is being tracked meeting Standard WG Meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests