...
...
...
...
...
Status:
...
Approved (At 2019-7-26 Meeting)
Date/Time
Friday, June 28July 12, 2019 at 10:00 AM Eastern Standard Time
Attendees
| Name | Organisation | Github IDAttended | ?FDC3 PMC Member | |||
|---|---|---|---|---|---|---|
| Nicholas Kolba | OpenFin | nkolba | Johan Sandersson | FactSet | donbasunox | |
| Jonathan Teper | JPM | Neil Slinger | JPMx | |||
| Riko Eksteen | Adaptive | rikoe | x | |||
| Tim Kolecke | Citadel | tkolecke | Frank Tarsillo (Deactivated) | IHS Markit | Former user (Deleted) | Refinitvx |
| Rob Underwood (Deactivated) | FINOS | brooklynrob | (foundation) | |||
| Tosha Ellison | FINOS | toshaellison | (foundation) | |||
| Aitana Myohl | FINOS | aitana16 | (foundation) |
PMC Committee Members Absent
...
Open Action Items
| Task report | ||||||
|---|---|---|---|---|---|---|
|
Discussion items
| 5 min |
| Roll call |
All | |
| 5 min | Review of previous minutes and open actions |
| All |
| ||
| 10 min | Review new Issues and PRs | Riko Eksteen |
(PR Screenshots)
|
| 5 min | WG cadence vote |
| All | Proposed: Move all WGs to Monthly on Thursdays targeting a window between 9am 12pm EST (up to the WG, API is 10 - 11:30, Use Cases is 11 - 12) . Currently, Use Cases is the 3rd Thursday, API is the 4th Thursday Proposal is for AppD on the 1st Thursday and Context & Intents on the 2nd. We can keep them at their current times (11am for AppD, 10am for Context) unless the WGs participants want to change that. | ||
| 5 min | FDC3 activation vote | All | Based on the email chain from Rob/Gab/Riko, finalise vote on whether FDC3 can move to activated status. Positive votes so far:
Activation checklist: /wiki/spaces/FINOS/pages/75530376 No votes against moving FDC3 to activated status. |
| 20 min | OKRs |
| All | Proposed: Demonstrate business transformation with significant adoption of FDC3 in 2019
Discussion on FDC3-UC WG effort to gather qualitative (i.e. getting quotes on the impact of these interop workflows, FDC3 NPS) and quantitative feedback (i.e., discrete KRs). Example cited was "number of interop workflows implemented", possibility of capturing FDC3 usage data in an anonymized way? Ensure a sustainable level of engagement with the community
| |
| 15 min | Board Deck review | All |
See slide HERE
for Q2 milestones, this is what I have as a first pass:
This is what we had last Quarter:
|
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
- 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)
"Tasks and Asks" List
- Someone from the program has provided input on the FAQ
- PMC provided direction on what their confluence entitlements and security should be ("Please prioritize getting infra@finos.org guidance on your wiki permissions per slide 22 of the pan-PMC presentation")
- Demonstrated evidence of publishing agenda ahead of meetings
- Demonstrated evidence of becoming self-sufficient in doing meeting minutes
- PMC has provided guidance on if/when they want/need a Github Microsite
- PMC has provided guidance on if/when they want to use Github (either Github Wiki or GH Pages) to replace collaboration use cases currently done on Confluence
- PMC has provided direction on if/when they would like to move their repos into the FINOS github ORG
- Evidence that those in program (at member) are getting Github IDs
- Programs Repos have been updated with README.md and CONTRIBUTING.md that reflects CCLA language [INT-643]
- Have provided at least one help wanted to "This Week at FINOS" or done a "Good First Issue" in a github repo
- Have built and socialized their 2019 roadmap
- Have contextualized their 2019 roadmap in OKR terms ("Review and reaffirm objectives on which your program roadmap has been built; review progress towards those objectives")
- Have produced (Are working on) their board report for July 17th board meeting
- Demonstrated evidence of staying on top of google groups moderation (both join requests and messages posted by those not in the respective google group already)
- As applicable, project/working group with eligibility criteria have 1) had them approved by the PMC, 2) published them on the site, and 3) are using them to review join requests to the mailing list
| AOB & Adjourn | All | Review and approve past meeting minutes (should be done at beginning of the meeting): |