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

Should all OpenSSF projects/repos have CII badges? #45

Closed
christo4ferris opened this issue Dec 16, 2020 · 10 comments
Closed

Should all OpenSSF projects/repos have CII badges? #45

christo4ferris opened this issue Dec 16, 2020 · 10 comments
Labels

Comments

@christo4ferris
Copy link

We should be eating our own cooking, don't you think?

@david-a-wheeler
Copy link
Contributor

I would certainly encourage it :-). At least one does - the CII Best Practices badge project earns it own badge :-).

If anyone needs help, I'd be happy to help. Send me an email at dwheeler AT linuxfoundation DOT org, or use the OpenSSF Slack.

@dlorenc
Copy link
Contributor

dlorenc commented Dec 16, 2020

Yes! Big +1 on that.

@david-a-wheeler
Copy link
Contributor

@dlorenc - do you want to start the process for OpenSSF Scorecard? We could get on a Zoom call together if you'd like, but we always urge project leads to start the process.

@dlorenc
Copy link
Contributor

dlorenc commented Dec 17, 2020

I've done it a few times before, should be fine on that. I think the bigger issue is that we're likely not actually meeting all the requirements there yet!

@david-a-wheeler
Copy link
Contributor

@dlorenc - that's okay! I think showing that things are "in progress" is precisely the right message to send.

@SecurityCRob
Copy link
Contributor

+1 our own projects getting badges helps on multiple levels:
1.) shameless self-advertising
2.) spreading of security good practices
3.) show we respect and follow our own guidelines
4.) will give Badges project feedback to improve processes and overall quality of earning those badges

@christo4ferris
Copy link
Author

christo4ferris commented Mar 4, 2022 via email

@di
Copy link
Member

di commented Jul 10, 2023

It seems like this could be added at some point as an entry requirement to a stage in the Project Lifecycle document.

@SecurityCRob
Copy link
Contributor

This wlll be accounted for as this PR is merged - #226

@SecurityCRob
Copy link
Contributor

pr merged 11dec2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants