Date/Time

Wednesday, 2019-12-18, 12am ET

Attendees

Description	Assignee	Task appears on
Next ODP meeting notes onto GitHub; check examples: https://github.com/tc39/notes , https://github.com/emberjs/core-notes , https://github.com/reactiveui/meeting-minutes , https://github.com/nteract/meeting-minutes , https://github.com/finos/voice-metadata-standard/wiki		2019-12-18 ODP WG Meeting notes
Create an issue template for new ODP suggestion into https://github.com/finos/open-developer-platform/issues (see cloud service certification as example		2019-12-18 ODP WG Meeting notes
Create epic with the workflow proposed by OSR /cc James McLeod (Unlicensed)	James McLeod (Unlicensed)	2019-10-9 ODP WG Meeting notes
GitHub consolidation docs on handbook - INT-748 - Getting issue details... STATUS		2019-08-28 ODP WG Meeting notes
GitHub Actions spike for license scanning - ODP-10 - Getting issue details... STATUS (see https://github.com/finos/odp-test/blob/master/.github/workflows/fossa-cli.yml)		2019-08-28 ODP WG Meeting notes
Add docs to GitHub consolidation re. security checks on GitHub		2019-08-14 ODP WG Meeting notes

Time	Item	Who	Notes from the Meeting
5 mins	Convene & Roll Call	Maurizio Pillitu
5 mins	Retrospective on current sprint	Group
10 mins	Next Sprint priorities	Group
10 mins	Cleanup outstanding action items	Group	If items are discussed and part of the sprint, they can be marked as done; otherwise, create ODP story for each item, before checking it
10mins	WhiteSource rollout	Group	How to complete datahelix setup (ie, fork the project and test there?). Plan actions for rolling out on next projects Questions: when a CVE is solved, GitHub Issues must be manually closed, correct? And what if a GitHub Issue (created by WhiteSource) is manually marked as closed, but the vulnerability is still there? What happens in that case, a new issue is created or the existing one is reopened?
10 mins	Backlog scrubbing	Group
5	AOB & adjourn	Group

Start rollout for Plexus repos. James McLeod (Unlicensed) and Maurizio Pillitu
Whitesource will get back re. the datahelix issue (mao will get notified)
FINOS discusses internally if/how to expose support@whitesourcesoftware.com to FINOS members (WS can associate requests to FINOS depending on the scope; ie. if a repo on github.com/finos is linked) - Rob Underwood (Deactivated) + Maurizio Pillitu + James McLeod (Unlicensed)
Document: WhiteSource integration does NOT mark issues as fixed, if fix is applied manually
Mao to look into WhiteSource PR automatic fix - https://www.whitesourcesoftware.com/whitesource-remediate/ (enabled by default for github.com integration)
Create an issue template for new ODP suggestion into https://github.com/finos/open-developer-platform/issues (see cloud service certification as example
Next ODP meeting notes onto GitHub; check examples: https://github.com/tc39/notes , https://github.com/emberjs/core-notes , https://github.com/reactiveui/meeting-minutes , https://github.com/nteract/meeting-minutes , https://github.com/finos/voice-metadata-standard/wiki
Plan socialization via Pan PMC and community@ email