Announce and socialise automated GitHub actions for governance, quality and compliance checks

[mcleo-d]

Goals

• Announce FINOS automated project compliance scan - https://finosfoundation.atlassian.net/wiki/spaces/FDX/pages/75530344/Code+Validation#CodeValidation-Projectcompliancescan - also check the project-blueprint documentation, which contains all repo contents and settings
• Announce meeting minutes - https://finosfoundation.atlassian.net/wiki/spaces/FDX/pages/75530554/Project+Collaboration+on+Github#ProjectCollaborationonGithub-MeetingMinutes
• Announce automated invitation to FINOS GitHub org - https://finosfoundation.atlassian.net/wiki/spaces/FDX/pages/75530554/Project+Collaboration+on+Github#ProjectCollaborationonGithub-BecomingGitHubFINOSOrganizationmember
• Run checks and monitor execution

Tasks

• Draft email to community@finos.org and schedule sending
• Review email internally
• Send email - Monday 4th May
• Confirm that the action is creating GitHub issues and sending invitations as expected
• @mcleo-d and @toshaellison to understand the right platform for introducing directly to FINOS project leads once background email has been sent.
• Add invite-clas-to-finos-org to the a schedule GitHub Action (as done for project compliance&quality)

Related to:

• Ensure all GitHub repositories comply with project-blueprint repo template Implement tooling to ensure all GitHub repositories comply with project-blueprint repo template #31
• Automatically invite people to github.com/orgs/finos/people when CLA covered Automatically invite people to github.com/orgs/finos/people when CLA covered metadata-tool#54
• Implement meeting minutes (and attendance tracking) on GitHub Implement meeting minutes (and attendance tracking) on GitHub #78

This item was moved to #139

• Enable project quality&compliance check and automated invitation actions

[mcleo-d]

Related to finos/metadata-tool#54

[mcleo-d]

Announce email being created by @mcleo-d and @maoo in the following restricted Google Doc ...

• https://docs.google.com/document/d/1QRzcDFKRXesFTeLZ6hUUGSKlUI8ff-SnRQv9lwCKCHQ/edit?usp=sharing

[mcleo-d]

@maoo - Draft email done and available 👇 for review and feedback ...

• https://docs.google.com/document/d/1QRzcDFKRXesFTeLZ6hUUGSKlUI8ff-SnRQv9lwCKCHQ/edit?usp=sharing 👀

Enjoy! 😁

James.

[mcleo-d]

@brooklynrob and @toshaellison suggests ...

@mcleo-d to add to the agenda of PMC meetings to introduce directly to the community once background email has been sent.

James.

[maoo]

Decided to go out this Thursday 30th

[mcleo-d]

It was agreed to email each team to update them on enabling the ODP items and meet the teams in project meetings moving forward.

The following table highlights the teams that have been contacted and our ability to move forward.

Team	Update	Next Step
Perspective	Emailed Neil and Rhyddian. Awaiting feedback from team before enabling features.	Community Call
DataHelix	The team have been contacted and ready to join project meeting	Community Call
Synthetic DataHub	The team have been contacted and ready to join project meeting	Community Call
Waltz	The team have been contacted and ready to join project meeting	Community Call
CLA Bot	The team have been contacted and ready to join project meeting	Community Call
OpenFin React Hooks	The team have been contacted and ready to join project meeting	Community Call
Plexus Interop	The team have been contacted and ready to join project meeting	Community Call
Plexus Desktop Interop API	The team have been contacted and ready to join project meeting	Community Call
Kdb	@brooklynrob has invited @maoo and @mcleo-d to next Kdb project meeting to take team through ODP initiatives	Community Call

[mcleo-d]

@maoo - This is to confirm the GitHub actions for governance, quality and compliance checks were socialised during the FINOS All Community call on Thursday 11th June. This means the socialisation task is now complete.

[maoo]

All done! Re. quality reports, check issue #139