Table of Contents
Date/Time
- 10am ET, 10/5/2018
Attendees
| Name | Organisation |
|---|---|
| OpenFin | |
Goals
Action Items
Tasks Identified and Assigned
- Type your task here, using "@" to assign to a user and "//" to select a due date
- Type your subtask here
- Type another task. Make sure to include an owner (assignee) and a due date.
Task Report from Last Meeting
(In the task report select the meetings notes from the LAST meeting in the 'Space(s) and page(s)' field to auto-populate this table– remove this note before publishing)
| Description | Due date | Assignee | Task appears on |
|---|---|---|---|
| Tosha Ellison | 2019-08-23 Meeting |
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 5min | get started | group | |
| 5min | Approve minutes from last meeting | group | |
| 5min | Housekeeping | Rob | Agenda; FINOS board headlines (non-FDC3 related); OSSF |
| 20 min | board meeting debrief | group | There was a focus on delivering things that people can start using, e.g. MVPs and actual products. The idea of marketplace was also raised, i.e. when you come to FINOS you can see what FINOS offers and what the Foundation is producing. Whether this looks like an app store or marketplace is still under consideration. The group also discussed the importance of communicating the value of FINOS and its programs in business terms. |
| 20 min | Standards Strategy | group | A top priority for this body is to get to all WGs to produce first versions of standards/specs and get them ratified by the end of year, if not sooner. Intents WG has approved the first version of the draft spec to be presented to the wider FDC3 community for approval. Unfortunately, the wider group doesn’t meet for another 4 weeks and last time attendance was low for FDC3 General Meeting. An alternative in-line with the existing ratification process is to send out a description of the proposed standard to the wider FDC3 mailing list with a request for comments to the Intents WG. Following this review period the proposal can be put forward to PMC in two weeks. If ratified, it gets labelled as a release with npm published and a document, e.g. the Spec for the API, also published as a pdf on Confluence. This will be labelled as v1. The PMC can also vote over email out of a meeting. At end of the comment period the group can vote by email. Next steps are to:
|
| 15 min | AOB | group |