Table of Contents
...
| Time | Item | Who | Notes from the Meeting |
|---|
| 5 min | Convene & roll call | |
|
| 5 min | Approve minutes from previous meeting | Group | Prior minutes approved. |
| 10 min | Review action items from previous meetings | | - NPM modules: see outstanding GitHub section
- FO objects discussion: see next topic re: FO
|
| 15 min | Implementing Financial Objects within FDC3 | Group | - 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 min | Outstanding GitHub issues | Group | - #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 min | FINOS GitHub/namespacing | Group | - 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 min | Workflow discussion for getting things done | Group | - 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 min | AOB & adjourn | Tim Kolecke |
|
...
- 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.