Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added notes from today's call to be amended as necessary.

Date


Attendees

IndividualOrganisation
Nicholas KolbaOpenFin
Espen Overbye (Espen Overbye)OpenFin

Frank Tarsillo (Deactivated)

IHS Markit
Neil Slinger (Neil Slinger)JP Morgan
Jonathan TeperJP Morgan
Former user (Deleted)Refinitiv
Tim Kolecke

...

Goals

  • Complete spec ratification
  • Come up with a plan for productization of v1
  • Prep for NYC meetup

...

TimeItemWhoNotes
1minroll callgroupWe need someone Tosha Ellison agreed to minute the meeting.
5 minRatification Votesgroup

AppDirectory Ratification

  • The AppDirectory specification has been open to the community for feedback for two weeks and has received no further comment. 
  • Nick proposed a motion to ratify the proposed V 1.0 AppDirectory standard (previously approved by the working group and made available for wider comment for at least the obligatory two week period).
  • Frank seconded the motion.
  • A voice vote was conducted with all in favour of passing and no objections or abstentions. The motion to ratify V1.0 of the AppDirectory standard was passed unanimously.

Context Data Ratification

  • The Context Data specification has been open to the community for feedback for two weeks and all comments and PRs raised during this time were addressed satisfactorily.
  • Nick proposed a motion to ratify the proposed V 1.0 Context Data standard (previously approved by the working group

AppD

Context Data
  • and made available for wider comment for at least the obligatory two week period).
  • Saori seconded the motion.
  • A voice vote was conducted with all in favour of passing and no objections or abstentions. The motion to ratify V1.0 of the Context Data standard was passed unanimously.
10 minMeetup Planninggroup

The

FINOS website is being updated with the information below so feel free to use this to promote promote both within your organisation and externally

next FINOS meetup will be on December 5th 2018 at IHS Markit in NY. It is an open meetup so anyone can come and members attend free.

Please ensure that any promotion requests that individual 

Individuals must register for the event 

here - registration is required

and Tosha Ellison will register Nick, Frank and Saori who all plan to attend.

Nick will start and circulate a presentation to be used for the meetup. The group, particularly those who can attend, should update it.  Saori noted that she would like to present the use cases and the group agreed this is a good idea. Others in attendance can also speak to work in specific working groups.


FORMAT
We expect this to be a reasonably intimate gathering with around 15-25 people attending
. I propose something along these lines for timing and format
with a proposed format of:
6:00 to 6:15 - Arrival and networking
6:15 to 6:20 - Welcome (FINOS)
6:20 to 6:35 - IHS Markit case study (SERV-to-Symphony integration - Mark Bloomberg)
6:35 to 7:15 - FDC3 standards discussion/walkthrough (Nick
and others from FDC3 - we can discuss how you want to do this and what AV requirements you have)
Topic: Open source enabling interoperability
, Saori and Frank
7:15 to 8:00 - Networking, pizza and drinks
Vanessa - I’ll set up a call for Thursday to cover logistics. All, please let me know if you’d like to be included on the invite.
MEETUP INFO
LOCATION
Location: IHS Markit, 450 West 33rd, 5th Floor New York, NY 10001
Time: 6:00-8:00pm
Description: Join us on December 5, 2018 for the next meeting in our Open Source in FinTech event series.
35 minProductization PlanninggroupAgree upon plan and deliverables.  Proposal to follow
35 minProductization Planninggroup

Rob recapped some of the recent conversations around documentation and described the aim of the document circulated, which is to give the FDC3 site a more comprehensive, complete and informative feel now that there are V1.0 standards ratified. This is important as it is one of our first major releases within FINOS. In future, this will also have wider remit than just FDC3 and likely used as a template of sorts for other programs.


Notes and discussion included:

  • Rob noted that the plan is to use the Wiki going forward to manage deliveries, including a specific go-live checklist and other materials.
  • Rob started with an overview of the analysis around information architecture including looking at personas, the type of information needed and an initial gap analysis.
  • This included evaluating target personas: Consumers, Contributors, FINOS Community, Others (first time visitors, evaluators, etc.) and the different information they may need (e.g. describing business value, access to the standards, information on how it all fits together)
  • Gab walked through the information architecture, proposing what data could reside in the different locations (FDC3 micro-site, Wiki, GitHub, FINOS website). He also covered how this maps back to target personas and who should be responsible for the documentation.Image Added
  • Frank asked if the persona of Contributor for GitHub is correct and suggested that it should also include consumers, e.g. for the people who actually pull the spec. The group agreed and will introduce another persona, perhaps “evaluator” or “consumer technical”.
  • Nick pointed out that another channel to think about is NPM and Frank suggested we generalise to published repositories.
  • Gab walked through the interconnectivity between different locations of information. Saori suggested adding a consume connection from the Wiki to GitHub.
  • Gab noted that there are certain expectations for a 1.0 release and it should meet specific criteria and quality levels in order to fulfil the “released” status as laid out be the FINOS community handbook. Link here.
  • Initial documentation gap analysis has been completed and compiled into a documentation readiness assessment, including the content to be produced, who should produce it and the priority (in the form of MoSCow - must, should, could have)Image Added
  • Frank asked how me make FDC3 consistent as a machine as the material gets created by different people at different times. For example, when we say code sample, does this need to be structured and look the same across all examples.
  • Nick queried whether all of the separate standards should be packaged into one single FDC3 standard, which prompted discussion around compatibility within and across the standards across all streams as well as naming convention.
  • Looking at the variables of quality, time and effort to implement the proposal, Nick suggested taking some time to productize this to a high quality level - potentially still complete in Q1. He didn't see this as a blocker to progress on the standards since the people doing initial implementations have already been involved. The group agreed on this approach and will take the timeline discussion offline.
  • Overall feedback on the proposal was positive and FINOS and the FDC3 PMC will work together on specifics of the delivery plan.
10minAOBgroupThere was no other business.

Action items