2019-06-28 Meeting

Owned by Nicholas Kolba
Last updated: Sept 20, 2019
3 min read

Minutes Status: Pending Review and Approval


Date/Time

Friday, June 28, 2019 at 10:00 AM Eastern Standard Time

Attendees

NameOrganisationGithub IDAttended?
Nicholas KolbaOpenFinnkolbaY
Johan SanderssonFactSetdonbasunoY
Jonathan TeperJPM
N
Neil SlingerJPM
N
Riko EksteenAdaptiverikoeY
Tim KoleckeCitadeltkoleckeN
Frank Tarsillo (Deactivated)IHS Markit
N
Former user (Deleted)Refinitv
Y
Rob Underwood (Deactivated)FINOSbrooklynrobY
Tosha EllisonFINOStoshaellisonY
Aitana MyohlFINOSaitana16Y

Open action items

DescriptionDue dateAssigneeTask appears on
Tosha Ellison2019-08-23 Meeting

Discussion items


5 minRoll Call

group

Attendance recorded.
5 minReview of open actionsgroupMost open actions closed, only remaining are header and licensing, website redesign work.
10 minWG cadencegroup

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 minWebsite designgroup

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 minHelp Wantedgroup

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 minHousekeeping & Hygienegroup
  • Wiki editing permissions email from Rob
  • If/when to move off of Confluence to Github
  • Moving FDC3 Calendar invite from Nick Kolba's calendar to FINOS Programs Meetings Calendar

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 minOKRsgroup

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 minAOBgroupNo other business.

Action items

Tasks and asks

DescriptionDue dateAssigneeTask appears on
  • Someone from the program has provided input on the FAQ
 Tasks and Asks
  • Demonstrated evidence of publishing agenda ahead of meetings
 Tasks and Asks
  • Demonstrated evidence of becoming self-sufficient in doing meeting minutes
 Tasks and Asks
  • 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
 Tasks and Asks
  • PMC has provided direction on if/when they would like to move their repos into the FINOS github ORG
 Tasks and Asks
  • Evidence that those in program (at member) are getting Github IDs
 Tasks and Asks
Tasks and Asks
  • Have provided at least one help wanted to "This Week at FINOS" or done a "Good First Issue" in a github repo
 Tasks and Asks
  • Have built and socialized their 2019 roadmap
 Tasks and Asks
  • 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")
 Tasks and Asks
  • Have produced (Are working on) their board report for July 17th board meeting
 Tasks and Asks
  • 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)
 Tasks and Asks
  • 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
 Tasks and Asks


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.