/
2019-07-30 Meeting Notes

2019-07-30 Meeting Notes

Aug 23, 2019

Meeting minutes status: Draft (pending approval)

Table of Contents

Date/Time

07/30/2019

Attendees



Name

Organisation

Github ID (optional)

Name

Organisation

Github ID (optional)

@Jamie Jones

GitHub



@Rob Underwood (Deactivated)

FINOS

brooklynrob

@Maurizio Pillitu

FINOS



Absent

  • @Jason Nelson

  • @Former user (Deleted)

  • @Colin Eberhardt (He/Him)

Outstanding Action Items

Agenda

Time

Item

Who

Notes from the Meeting

Time

Item

Who

Notes from the Meeting

5 min

Convene & roll call

@Jamie Jones



10 min

Future of ODP Working Group and the ODP overall

@Maurizio Pillitu, Group

Shall we continue meeting every 2 weeks? Shall we move to an on-demand meeting schedule? Is there value for the community to do sprint planning and backlog scrubbing?

5 min

AOB & adjourn





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

Review and Approve the Revised POP - @Jamie Jones
Relabeled working groups as projects (Respective working group leads)
Complete merge in of OSR into FDX - @Jamie Jones w/ @Aaron Williamson and @Rob Underwood (Deactivated))
Someone from the program PMC has provided input on the FAQ (has suggested at least one 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, and, if move is approved, move has happened. 
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]

Program Repos have a NOTICE file with copyright statements; code docs have license headers
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")
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, any FDX projects with eligibility criteria have 1) had them approved by the FDX PMC, 2) published them on the FDX site (the wiki), 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.