2019-06-04 Meeting Notes

Meeting minutes status: Draft (pending approval)

Table of Contents

Date/Time

06/04/2019

Attendees


NameOrganisationGithub ID (optional)
GitHub
Morgan Stanley
Rob Underwood (Deactivated)Finosbrooklynrob
Maurizio PillituFinos
Aitana MyohlFinosaitana16
Gabriele ColumbroFinos

Outstanding Action Items

<insert a {Task report} macro here, configured with the group's task page>

Agenda

TimeItemWhoNotes from the Meeting
5 minConvene & roll call
10 min

How's everyone liking the bi-monthly PMC?

  - bi-weekly async email chain?

  - GitHub radar/issue?


Standup is ok.

GitHub radar: repository for FDX PMC – get an activity overview. can use Jira API to extract information.

Very interesting. We've been doing a lot of work on metrics.github.org; getting this information on markdown would be very useful. but there are no current issues this addresses. allows you to have conversations, discussions, updates,...

More interesting GitHub fork: start using GitHub issues as a framework where we have discussions. more accessible for Brian bc right now there's issues with accessing and moderating google groups. the more we get Brian engaged, the more help we'll get. we can also test this and then eventually expand it to other PMCs. 

GitHub issues seems easier than email/Google Groups/wiki. Allows to report out of existing task management. 

Sounds good but there's already many channels we're using. Would try not to create too much infrastructure. Let's try & if it doesn't work we'll change

Whatever you create, please link it back to the PMC wiki so that we have a trail for people who come in through another system. should be a private repo where only PMCs have access to edit but the public has access to reading.

Can it be set up so that only team members can create issues?

30 min

General Announcements

  • Update ROADMAPS!
  • GitHub Pages instead of confluence?
  • Do we think there are relevant differences between projects and working groups?

bring rigour and process into programs; acknowledge that the purpose of finos is to enable adoption of OS in finserv community. focus should be the programs

  • Google Groups: moderating and accepting join requests 
  • Github: readme files updates. CCLA PRs– please review and approve
  • FAQs on wiki: has been updated, feedback welcome
  • wiki permission: currently 2-tiered
  • FDX repo move into consolidated finos repo
  • FDX support to other WGs
  • eligibility criteria for WG: try to keep as low bar as possible
  • improving FINOS self-onboarding/ platforms/ membership/ participation
10 min

Dx update
  - GitHub issues
  - OSR support for OSS workflows
  - Org migration support
    - github.com/finos-fdx migration to github.com/finos

  - GitHub participation statistics 
  - GitHub Satellite update/Roadmap

Jamie Jones

FDX migration to github. Discussion about moving individual programs to the FINOS repo on GitHub. Would like to do this for FDX to start out. Create group/ permissions/ .... to figure out rough edges

Rationale: FDX does not have a lot of activity so it looks like a safe place to try.

Participation statistics. Significant drop in activity within financial institutions. 2017 vs. 2018 stats; figuring out which year was an outlier. Cleaning up data and making sure that all of the relevant data is included.

FINOS state of Open Source report. Factsheets. Tables. Stats. 


5 minODP update


5 minAOB & 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

  •  
  •  

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.