2019-06-28 Data Technologies PMC Meeting
- Rob Underwood (Deactivated)
- Aitana Myohl
- Alvin Shih
Meeting minutes status: Approved (on 7/29/2019)
Minutes Status: Review and Approval Pending
Table of Contents
Date/Time
2019-06-28
Attendees
| Name | Organisation | Github ID (optional) | PMC Member? |
|---|---|---|---|
| Morgan Stanley | alvin-c-shih | Lead | |
| FINOS | brooklynrob | ex officio | |
| Sailesh Pandey | Nomura | Yes | |
| Aitana Myohl | FINOS | No |
Absent
Andrew Carr (He/Him), Former user (Deleted)
Outstanding Action Items
| Description | Due date | Assignee | Task appears on |
|---|---|---|---|
| 2019-01-25 Data Technologies PMC Meeting |
Agenda
| Time | Item | Who | Notes from the Meeting |
|---|---|---|---|
| 5 min | Convene & roll call | ||
| 5 min | Kdb WG Update | Alvin Shih | Things have gone into incubator branches (e.g., qdoc); some more things have been added included something for structured logging. Others have asked about elk style logging. |
| 5 min | Security Reference Working Group Update | Sailesh Pandey | Bloomberg has gotten back to us Concern re OpenCorporate: Bloomberg and Refinitiv would have to matching and linking to make this work. Is it easier just to match Bloomberg and Refinitiv Do we need to develop a contingency plan? Also need to explore other areas where we could make a difference; Tosha had suggested that we do a forum to identify key challenges |
| 5 min | DRM Update | Former user (Deleted) | Working Group is effectively on hold right now |
| 5 min | Data Helix Update | Andrew Carr (He/Him) | On-boarding on contribution in progress; announcement being drafted and will shared via announce@ |
| 5 min | Exodus Contrib Vote | All | Vote call. No declining votes. Contribution approved. |
| 5 min | Data Tech Meetup Idea | All | Kx responded to Alvln and Rob; likely a decision from Mark Sykes |
| 5 min | Wiki vs. Docusaurus for Roadmaps? | All | Not yet. DT does not yet need a Github Pages site; stick with Confluence wiki for now on collaboration on use cases. |
| 5 min | When to move repos into /finos org (from /finos-data-tech) | All | Migration can move forward |
| 5 min | Roadmap Review and Prep for Board Meeting | All | Please send your completed slide for the board update to Aitana by July 10th Key to do: create a some content/white paper/blog posts in order to market the program to more |
| 5 min | Review and Approve Kdb eligibility criteria | Kdb eligibility criteria reviewed and called to vote. No declining votes. Eligibility criteria approved. | |
| 5 min | Tasks and Asks (See below) | ||
| 5 min | AOB & adjourn | 5 min |
|
Decisions Made
- DT does not yet need a Github Pages site; stick with Confluence wiki for now on collaboration on use cases → For now, program activities will continue to be documented first and foremost on the wiki
- Exodus contribution approved
- Kdb Participation eligibility criteria approved
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
Tasks and Asks
- 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
Need help? Email help@finos.org we'll get back to you.
Content on this page is licensed under the CC BY 4.0 license.
Code on this page is licensed under the Apache 2.0 license.