2019-10-17 uc-wg meeting notes

Owned by Jonathan Teper
Last updated: Dec 19, 2019 by Johan Sandersson
3 min read

Meeting minutes status: Draft (pending approval)

Table of Contents

Date/Time

 

Attendees

NameOrganisationGithub ID (optional)

Jonathan Teper

JP Morgan
Johan SanderssonFactSet
Tom Schady

Aitana MyohlFINOS

Outstanding Action Items

DescriptionDue dateAssigneeTask appears on
Cesar Morgadinho2019-06-27 uc-wg meeting notes
Rhyddian Olds2019-06-27 uc-wg meeting notes
Leslie Spiro2019-06-27 uc-wg meeting notes
Evgeny Kovalyov2019-06-27 uc-wg meeting notes


Agenda

TimeItemWhoNotes from the Meeting
5 minConvene & roll call

Jonathan Teper


2 minReview action items from previous meetings (see above)


10 min

OKR Review & Next Steps

  + 

Objectives & Strategy 

  + 

Retrospective

Jonathan Teper

OKR Review 

Objectives & Strategy Proposal: 

  1. Primary focus on getting a few use cases to adoption by (1) the standards groups, and the (2) the businesses
    1. Rationale: (1) several unattended use cases, (2) a few strong success stories  >  many partial success stories, (3) our OKRs may not be attainable
    2. UCWG feedback: 
    3. Decision: Approved!
  2. Review: process for submitting use cases to other working groups - what is the preferred method? Can we document it? 
    1. Raise an issue in the respective GitHub project and link to the use case
    2. To be considered: reverse flow - other working groups submitting use cases in our repo 

Retrospective

  • Are we being as effective as we possibly could? Probably not.
  • Why?
    • There may be unwritten use cases driving the roadmap of other working groups
    • There may adoption that hasn't been shared (ex: teams focused on delivering, not evangelising)
    • The way the UCWG is working is not optimized for delivery
    • There may be an inevitable delay between standards definition, adoption, and reporting of success
  • What can be done?
    • Solicit use cases from other working groups; perhaps other WG could raise GitHub issues in the UC working group.  
    • Focus on a few success stories and examples of "what you can do with FDC3" - see above
    • Sleep on it
10 minNew Use Cases

Johan Sandersson 

Leslie Spiro

Use Case 17: Fine-tuning InterOp with Channels

  • Target date for a vote? As soon as we move to voting on GitHub
  • See feedback from previous meeting 
    • What is the best way to gather meaningful feedback?  // not discussed

"I want my application to be FDC3 compatible" - Leslie Spiro  // not discussed 

5 minPMC UpdateJonathan TeperSee: 2019-10-04 Meeting
10 minReview and sign off new persona definitionJonathan Teper
  • Current persona definition: FDC3 Persona/Participant Definition
  • Updated persona definition:
    • Key points are:              
      • Separate FDC3 “Participant” from FDC3 “Persona”
      • Make sure we align with the terminology on our FDC3 compliance website: https://fdc3.finos.org/docs/1.0/fdc3-compliance (“Application Provider” and “Platform Provider”)
      • Suggest that we actually change the compliance document above and ask them to use “Implementors” instead of “Personas”.  The website should not be using the word “Persona” here, as readers could get confused with the UC Personas.  We can ask for the change in github or to Riko (via PMC).  
    • See: FDC3 Persona Participant Definition.docx and 
    • Decisions: Approved! 
  • Q: Should this be in GitHub rather than Confluence? YES
5 minProposal: documenting adoption in GitHubJonathan Teper

See: use cases adoption summary here and here (proposed)  // not discussed 

10 minOpen discussion: how we workJonathan Teper
  • Online vs offline
  • GitHub Kanban  
    • Tom Schady set up the GitHub board for the voice program 
    • Proposal to pilot a GitHub Kanban board for UCWG
  • Improving efficiency and reach? 
5 minAOB & adjourn


Proposal to move voting on use cases to GitHub

  • Tom Schady to submit proposal to vote on use cases in GitHub to the WG

Proposal to pilot a GitHub Kanban Board for the Use Cases Working Group. Decision: unanimously approved by the WG participants! See: https://github.com/FDC3/FDC3/projects/1?add_cards_query=is%3Aopen

Decisions Made

Action Items

Capture any actions that were identified here, and make sure they are also captured on the group's task page during, or immediately after, the meeting

  •  
  •  


Need help? Email help@finos.org we'll get back to you.

Content on this page is licensed under the CC BY 4.0 license.
Code on this page is licensed under the Apache 2.0 license.