Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Minutes Status: Pending Review and Approval


Date/Time

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

Attendees

NameOrganisationGithub IDAttended?
Nicholas KolbaOpenFinnkolba
Johan SanderssonFactSetdonbasuno
Jonathan TeperJPM

Neil SlingerJPM

Riko EksteenAdaptiverikoe
Tim KoleckeCitadeltkolecke
Frank Tarsillo (Deactivated)IHS Markit

Former user (Deleted)Refinitv

Rob Underwood (Deactivated)FINOSbrooklynrob
Tosha EllisonFINOStoshaellison
Aitana MyohlFINOSaitana16

Open action items

DescriptionDue dateAssigneeTask appears on
Tosha Ellison2019-08-23 Meeting

Discussion items


5 minroll call

group


5 minReview of open actionsgroup
10 minReview new Issues and PRsRiko Eksteen
5 minWG cadence votegroup

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.

20 min OKRsgroup

Proposed:

Demonstrate business transformation with significant adoption of FDC3 in 2019
  • 5 documented case studies of implementations in production
  • Survey of FDC3 participants showing
    • 100% of contributing participants adopted FDC3 in production or in flight on adoption
    • Over 50% of all participants with adoption or in flight

Ensure a sustainable level of engagement with the community
  • 0 unplanned meeting cancelations in Q4
  • All WG chairs communicate with their WG at least once a week through email, GitHub, or confluence
  • PRs and issues being filed for all WGs between meetings
15 minBoard Deck reviewgroup
  • Q2 Headlines and Highlights
  • Q3 Plans and Expected Milestones
  • Issues & Risks
  • Requests of Board and/or FINOS
for Q2 milestones, this is what I have as a first pass:

  • Context Channel Linking APIs

  • Consolidation and alignment of Context Data, Intents WGs and FO work

  • Live implementations

This is what we had last Quarter:
  • Q1 Headlines and Highlights
    • Released 1.0 Standards
  • Q3 Plans and Expected Milestones

    • Context Channel Linking APIs

    • App Directory Search

    • Consolidation and alignment of Context Data, Intents WGs and FO work

    • Live implementations

  • Issues & Risks
    • none
  • Requests of Board and/or FINOS

    • Board/FINOS - help deepen the bench for talent that can contribute

    • Better differentiation between the needs and output of Standards-oriented groups vs Code-oriented groups

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

  • No labels

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.