Minutes Status: Pending Review and Approval
Date/Time
Friday, June 28, 2019 at 10:00 AM Eastern Standard Time
Attendees
Name | Organisation | Github ID | Attended? |
---|---|---|---|
Nicholas Kolba | OpenFin | nkolba | Y |
Johan Sandersson | FactSet | donbasuno | Y |
Jonathan Teper | JPM | N | |
Neil Slinger | JPM | N | |
Riko Eksteen | Adaptive | rikoe | Y |
Tim Kolecke | Citadel | tkolecke | N |
Frank Tarsillo (Deactivated) | IHS Markit | N | |
Former user (Deleted) | Refinitv | Y | |
Rob Underwood (Deactivated) | FINOS | brooklynrob | Y |
Tosha Ellison | FINOS | toshaellison | Y |
Aitana Myohl | FINOS | aitana16 | Y |
...
5 min | Roll Call | group | Attendance recorded. |
5 min | Review of open actions | group | Most open actions closed, only remaining are header and licensing, website redesign work. |
10 min | WG cadence | group | An idea was floated of moving all WG meetings to a single cadence and having a dedicated slot (e.g. Tuesday at 10am EST). Ideally have fewer meetings and more work being done via PRs and Github threads & issues. People on the call are very supportive. Nick will socialize this idea to other PMC members on an e-mail thread. A suggestion was made that it could even be quarterly. |
10 min | Standardizing on Github – i.e., moving to Github for collaboration infrastructure use cases like meeting minutes | group | FINOS proposed moving to GitHub for all collaboration, minutes, etc (totally ditch confluence). What do we think? We need to plan accordingly and make sure that we have equivalent workflow tooling on Github to the one we use on confluence. Check out Github wikis We need to have someone show how to replicate what we do currently in Confluence, e.g. a screen share/demo of Github wiki. Educating people on how people around how the pages are structured – a problem is that FDC3 uses it a different way than FO. We should use it in a consistent way. Migrating existing content was discussed, and how easy/hard this would be, and whether it would be worth spending time on. FINOS would like programmes to spend time on more valuable tasks. API Working group to pilot moving content and meeting minutes to GitHub wiki (Nicholas Kolba and Riko Eksteen), provide feedback to PMC. Is there a good project that has used Github wiki well?
|
5 min | Website design | group | Aaron from FINOS has raised a PR: https://github.com/FDC3/FDC3/pull/96 (See https://grizzwolf.github.io/FDC3/ to see what it looks like) PMC happy for Riko Eksteen and Nicholas Kolba to keep working with Aaron Griswold on this. |
5 min | Help Wanted | group | Help wanted for "this week in FINOS”. It is difficult to identify "help wanted" tasks for FDC3 because it is focused on schemas, not code. Domain knowledge is really need. FDC3 will continue to look for such opportunities. |
5 min | Housekeeping & Hygiene | group |
Wiki permissions have been fixed to only PMC members, who can add additional editors. (See FINOS "Tasks and Asks" Google Sheet for more context, as ) |
20 min | OKRs | group | Set OKRs for 2019 roadmap. See FDC3 Use Cases WG OKRs. Objective is to increase the desktop interop API user base. Could we adopt the use cases OKRs as FDC3 use cases, as a skeleton to get us started (FDC3 UC Working Group Objectives - 2019). |
5 min | AOB | group | No other business. |
Action items
- Follow-up on pull requests to introduce standard CCLA language into CONTRIBUTING.md files of FDC3 repos, especially the the FDC3/FDC3 mono repo (Maurizio Pillitu, Aitana Myohl)
- Ask Jamie for examples of Github wiki use to compare and contrast use cases like doing meeting minutes (Aitana Myohl, Jamie Jones, Rob Underwood (Deactivated))
- API Working Group to pilot GitHub wiki and provide feedback to PMC (Nicholas Kolba, Riko Eksteen)
- Send an email to PMC members about monthly meeting cadence in dedicated slot (Nicholas Kolba)
Tasks and asks
Task report | ||
---|---|---|
|