-
Notifications
You must be signed in to change notification settings - Fork 49
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
First draft of project tier definitions #551
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Trevor Rosen <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, thanks for pulling this together.
Signed-off-by: Trevor Rosen <[email protected]>
How will consumers of these projects know whether a repo is Core or Community? Most consumers aren't aware of this community repo where these designations exist. Creating a badge in the readmes of the repos? A custom property? Something else? |
@priyawadhwa @lukehinds @SantiagoTorres any other thoughts here? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
* [sigstore-java](https://github.com/sigstore/sigstore-java) | ||
* [sigstore-python](https://github.com/sigstore/sigstore-python) | ||
* [sigstore-ruby](https://github.com/sigstore/sigstore-ruby) | ||
* [cosign-installer](https://github.com/sigstore/cosign-installer) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should not be services/ tools?
* [sigstore-python](https://github.com/sigstore/sigstore-python) | ||
* [sigstore-ruby](https://github.com/sigstore/sigstore-ruby) | ||
* [cosign-installer](https://github.com/sigstore/cosign-installer) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add a section for infrastructure, with helm-charts, scaffolding, and terraform-modules? And maybe sigstore-probers too?
* [GitSign](https://github.com/sigstore/gitsign) | ||
* [Rekor-monitor](https://github.com/sigstore/rekor-monitor) | ||
* [helm-sigstore](https://github.com/sigstore/helm-sigstore) | ||
* [cosign-gatekeeper-provider](https://github.com/sigstore/cosign-gatekeeper-provider) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://github.com/sigstore/rekor-search-ui as a community project?
* [sigstore-python](https://github.com/sigstore/sigstore-python) | ||
* [sigstore-ruby](https://github.com/sigstore/sigstore-ruby) | ||
* [cosign-installer](https://github.com/sigstore/cosign-installer) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Section for documentation, with https://github.com/sigstore/architecture-docs, sigstore/docs, and sigstore/sigstore-website?
Just wanted to bump my question about how consumers will learn the status of each project, the community repo isn't well known. A badge? |
What
Definitions of project tiers for Sigstore
Why
Differentiate between various levels of support, adoption, etc. Describe
Community
andCore
projects and how something up-levels fromCommunity
toCore