2019-07-12 Plexus PMC Meeting

Meeting minutes status: Approved (on 9/27/2019)

Table of Contents

Date/Time

2019 - 07 -12

Attendees


NameOrganisationGithub ID (optional)
Program Management Committee

FINOSbrooklynrob
Leslie SpiroTick42
Deutsche Bank
Gabriele Columbro (ex officio)FINOS
Aitana Myohl (FINOS support)FINOS
Paul WhitbyDeutsche Bank
Guests
Dan SchleiferChartIQ
@ChristianChartIQ

Apologies

NameOrganisationGithub ID (optional)
Refinitiv
Rhyddian OldsJP-Morgan
Anton NikolaevDeutsche Bank

Outstanding Action Items

DescriptionDue dateAssigneeTask appears on
  • RBC introduction
2020-04-24 Plexus PMC Meeting
James McLeod (Unlicensed)2020-04-24 Plexus PMC Meeting
  • JPMC on-going evaluation
2020-04-24 Plexus PMC Meeting
  • All to RFC on the Program/Project split proposal
2020-01-24 Plexus PMC Meeting
  • Redo the scope expansion scope (and figuring out who will support it, including and especially the banks) - Paul Whitby
Paul Whitby2019-08-09 Plexus PMC Meeting
  • 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")
2019-07-12 Plexus PMC Meeting
  • Demonstrated evidence of publishing agenda ahead of meetings
2019-07-12 Plexus PMC Meeting
  • Demonstrated evidence of becoming self-sufficient in doing meeting minutes
2019-07-12 Plexus PMC Meeting
  • PMC has provided guidance on if/when they want/need a Github Microsite
2019-07-12 Plexus PMC Meeting
  • 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
2019-07-12 Plexus PMC Meeting
  • PMC has provided direction on if/when they would like to move their repos into the FINOS github ORG
2019-07-12 Plexus PMC Meeting
  • Evidence that those in program (at member) are getting Github IDs
2019-07-12 Plexus PMC Meeting
2019-07-12 Plexus PMC Meeting
  • Have provided at least one help wanted to "This Week at FINOS" or done a "Good First Issue" in a github repo
2019-07-12 Plexus PMC Meeting
  • 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")
2019-07-12 Plexus PMC 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)
2019-07-12 Plexus PMC Meeting
  • 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
2019-07-12 Plexus PMC Meeting
Leslie Spiro2019-03-29 Plexus PMC Meeting
  • Someone from the program has provided input on the FAQ
2019-07-12 Plexus PMC Meeting

Agenda

TimeItemWhoNotes from the Meeting
5 minConvene & roll call



50 minReview action items from previous meetings (see above)


Proposal to the Board set up two new Working Groups:

  1. Proposal to rename Plexus program. Purpose is to identify it as a place in which an OS platform for financial services will be produced. Important to have the name reflect the scope of the program. Proposed name: "desktop services". Call for other name proposals. Paul Whitby to work on a formal name change proposal with FINOS support.
  2. OS Desktop Web Container based on Electron. Proposal to add desktop web container WG to the Plexus Program. There's no potential overlap with FDC3 and Hadouken, but a layered approach. Leslie Spiro and Dan Schleifer to work on a formal proposal describing the newly proposed WG scope and rationale. 
  3. Desktop-FDC3.JS. 


5 minAOB & adjourn


Board update:


Decisions Made

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

  • 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.