2019-08-27 Meeting Notes
Meeting minutes status: Draft (pending approval)
Table of Contents
Date/Time
2019-08-27
Attendees
| Name | Organisation | Github ID (optional) |
|---|---|---|
| GitHub | ||
| Brian Ingenito (Deactivated) | Morgan Stanley | |
| Tosha Ellison | FINOS | |
| Maurizio Pillitu | FINOS | |
| Aaron Williamson | FINOS |
Outstanding Action Items
<insert a {Task report} macro here, configured with the group's task page>
Agenda
Time | Item | Who | Notes from the Meeting |
|---|---|---|---|
5 min | Convene & roll call | ||
Approve past meeting minutes |
| ||
10 min | Review action items from previous meetings (see above) | ||
10 mins | How to leverage GitHub membership | Discussion. We are in the process of downgrading github.com/finos to "Team for Open Source" tier, as we managed to move all our private repos elsewhere. How do we want to manage GitHub Org Membership? Shall membership to github.com/finos be public? Who is (and who is not) a member of the org? Who manages membership and when? Proposal. Any FINOS active participant SHOULD be part of a GitHub Team, and therefore should be a FINOS (GitHub org) member; membership should be public; FINOS Staff will take care of membership, anytime a new project or contributor is onboarded; an internal sync tool will periodically check if GitHub Teams and members list are in sync (as project leads are also maintainers of GitHub Teams. Given the mentioned permission strategy, at repository level, there should be need to define user-specific permissions, all individuals should be mapped to at least 1 GitHub Team (making permission management much simpler, especially for multi-repo projects, who share the same team definitions). | |
5 min | Update on FINOS org transitions | Discussion. Update on moving organizations for separate foundation programs into the finos organization on GitHub | |
10 mins | Moving OSR into FDX - update | Group |
|
5 min | AOB & adjourn |
Decisions Made
Action Items
- Maurizio Pillitu and Jamie Jones - follow up on documentation re. FINOS governance on GitHub => lead to Handbook documentation
- Maurizio Pillitu and Rob - follow up with teams (ie Perspective) to use GitHub Team (ie dav-perspective)
- Interest to use FINOS GitHub org members as list of "active participants", but too difficult to manage; let's keep it simple, membership will be affected by Team configurations
- Cleanup Outside Collaborators: adding them as members (or remove from repos, sometimes it applies for archived repos)
- Maurizio Pillitu and Tosha Ellison - marketing updates re. github org consolidation (ie link changes)
- Discuss again "OSR WG merging with ODP WG call (or vice versa)" for next FDX PMC 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.