2019-06-24 Meeting Notes

Owned by Tim Kolecke
Last updated: Oct 10, 2019 by Johan Sandersson
2 min read

Table of Contents

Meeting Minutes Status: Approved (on 8/8/2019)

Date/Time

Monday, June 24, 2019 at 10:00 PM Eastern

Attendees

NameOrganisationGithub ID (optional)

Tim Kolecke

Citadeltkolecke
Dan SchleiferChartIQ
Evgeny KovalyovRefinitiv
Johan SanderssonFactSetdonbasuno
Mark ValeirasChartIQ
Rob SchmidtChartIQ
Leslie SpiroTick42
Christian HallChartIQchristian-ciq
Tosha EllisonFINOStoshaellison
Rob Underwood (Deactivated)FINOSbrooklynrob
Aitana MyohlFINOSaitana16
Riko EksteenAdaptive
Nicholas KolbaOpenFin

Outstanding Action Items

DescriptionDue dateAssigneeTask appears on
  • Johan Sandersson to look at how we can link between intents and use cases in FDC3 website documentation
 Johan Sandersson2020-02-13 Meeting Notes
Riko Eksteen2019-10-10 Meeting Notes

Agenda

TimeItemWhoNotes from the Meeting
5 minConvene & roll call

Tim Kolecke


5 minApprove minutes from previous meetingGroupPrior minutes approved. 
10 minReview action items from previous meetings

Tim Kolecke

  • NPM modules: see outstanding GitHub section
  • FO objects discussion: see next topic re: FO
15 minImplementing Financial Objects within FDC3Group
  • JSON Schema + Camel Case
    • Will follow JS standards and use lower case, camel case. FO folks are not concerned about casing, etc. 
    • Schema implementation should be done prior to NPM module publishing. Evgeny Kovalyov offered to pitch in to get this over the line. 
  • Implementations of contact, organisation, instrument
    • Dialog about namespacing type names (include finos? reference financial-objects?); discussion suggests keeping fdc3 prefix and leave as is.
    • Versioning is needed; maybe as simple as a version property in the object
      • This conversation extended into how to really handle this as the details pan out (implies version of FDC3 itself, NPM modules, etc.)
    • Vote was recommended for next meeting to approve Instrument since pretty much done; Contact is not done...and even the FO version is in draft, so maybe not ready for ratification.
    • Broadly speaking, team reminded itself that FDC3 sees FO as defining source of truth on types (and they are happy for FDC3 input on definitions/needs). 
10 minOutstanding GitHub issuesGroup
  • #20 Align IntentMetadata with Intents repository
  • #21 publish NPM module for TS interface
    • Near top of Riko Eksteen's list, but having trouble nailing this down. Help welcome. Soon. 
    • Looks like a couple of days maybe. 
  • #22 id field should be renamed or have its keys moved to the body of the object
5 minFINOS GitHub/namespacingGroup
  • Some general discussion about migrating some items from FDC3 GitHub structure to FINOS GitHub org/structure as part of the final push of all projects into the overarching FINOS umbrella. 
5 minWorkflow discussion for getting things doneGroup
  • Use GitHub issues to track work (including new ideas).
  • Develop PRs and comments there.
  • Conversation in email group may be too granular. 
  • Meet less and do more work offline.
5 minAOB & adjournTim Kolecke

Decisions Made

  • Communicate outside of meetings on issues via GitHub, etc. vs. designing/debating on calls to drive more real work and use meetings for ratifications. 
  • Move meetings to monthly to do more offline work and attempt to align with other FDC3 meetings to ease participation across them. 

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

  • Offline discussion re: GitHub issues from prior meetings to get these done.
  • Meeting cancellation for next slot to move to monthly. 

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.