Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Current »

Date

Attendees

NameOrganisation
Former user (Deleted)Thomson Reuters
David CarlsonWellington
Johan SanderssonFactset
Jonathan TeperJPMC
Former user (Deleted)Thomson Reuters
Leslie SpiroTick42
Rhyddian OldsDB
Svyatoslav KryukovDB
Tom SchadyGreenkey
Victor RodriguezJPMC
Cesar MorgadinhoWespac
Nicholas KolbaOpenfin

Agenda

TopicNotes
  • Introductions for new joiners
  • Working rhythm - most work done in wiki docs, meetings are for escalations and synch-ups.  
  • Great offline work done to date - well done everyone!
  • Timeframes
  • Do we process use cases in Tranches?  Or per use case?
    • GROUP DECISION: do it per use case
    • Early on we don't want to kick start one use case without setting up some initial consistency between them, so do a 'first batch' just in the beginning before progressing one on its own.
  • Ratification - what does that mean?
  • Use Cases Scope - let's clarify:
    • Focus on Desktop (FDC3)
    • Mention/Capture non-Desktop and flag explicitly - decide specifics as we go through each actual example
    • GROUP DECISION: OK for not every workflow to have a standard
  • STATES of Use Cases (this is not for the specific individual workflows inside each of the Use Case but the use case as a whole):
    • Backlog/Draft
    • In Review
    • Approved/Accepted (as a well defined and relevant use case only - not 'approved' as a FDC3 standard)
    • Rejected (with reason)
  • Process & Tooling
    • GROUP DECISION: Not in Jira yet, try to use confluence as much as possible
    • See actions below to get this started
  • Voting
    • Do it via standard FINOS way and via  email - not require meeting - see action below for Nick to check with FINOS and let this group know.
    • Working group members must be diligent in assessment of use cases
      • Not everyone will be a stakeholder in all use cases (not expected) but use cases must have enough detail to allow review and assessment
  • Use Case 7 - Platform agnostic interop API - by Leslie Spiro
    • CTO use cases
    • GROUP QUESTION: Are non-financial-professional use cases in scope?  Are CTO/CIO/CCO valid "users"?  No consensus yet (ran out of time), so please discuss offline and let's decide by or at next meeting.
  • Others to be discussed at next meeting (start with this). All to provide comments on the docs in the meantime.
  • Templates for Use Cases
  • Discussion barely started due to time, but ideas to include in template:
    • flag for whether there is a standard defined to meet this specific workflow
    • must be factual and detailed
  • Inter working group communication 
  • Not really discussed.  Saori will try to start group discussion in Google groups.
  • Wider FINOS interlock   
  • Not really discussed.  Saori will try to start group discussion in Google groups.

Open Questions (for next session)

  • Presentation of use cases (Rhyddian and Tom)
  • Voting - how should we do this?
  • How do we gauge interest to move a use case from backlog/draft into review mode?
  • Template items - what to include?
  • Are "CTO Use Cases" in scope?

Action items

  • No labels