Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure OpenSSF Badging For FDC3 #810

Open
robmoffat opened this issue Aug 31, 2022 · 1 comment · May be fixed by #1480
Open

Configure OpenSSF Badging For FDC3 #810

robmoffat opened this issue Aug 31, 2022 · 1 comment · May be fixed by #1480

Comments

@robmoffat
Copy link
Member

robmoffat commented Aug 31, 2022

FINOS has a policy of adopting OpenSSF for it's major / strategic projects.

The way this works is, you fill out a questionnaire here (https://bestpractices.coreinfrastructure.org/en) and you get given a badge to add to your project, just like Spring Bot has done.

It's about 1/2 hour work to fill out the badge. If for any reason we are missing some criteria, please report them back on the finos-fdc3-maintainers slack channel and we can discuss how to close the gaps.

thanks!

@robmoffat robmoffat added the bug Something isn't working label Aug 31, 2022
@kriswest kriswest added this to the post-2.0 tasks milestone Sep 5, 2022
@kriswest kriswest added project governance and removed bug Something isn't working labels Sep 14, 2022
@kriswest
Copy link
Contributor

@robmoffat is this done and closeable now? I believe we're @ 99% because we don't use code coverage testing, and the security scanning is yet to be enabled. Perhaps wait for the latter to be done?

@kriswest kriswest removed this from the 2.1-release-tasks milestone Sep 18, 2024
@robmoffat robmoffat linked a pull request Dec 19, 2024 that will close this issue
3 tasks
@kriswest kriswest linked a pull request Dec 19, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants