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.

Sign up for GitHub

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

Add cve-feed-osv project #7966

Merged
merged 1 commit into from
Jul 5, 2024
Merged

Add cve-feed-osv project #7966

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions sig-security/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,7 @@ Security Documents and Documentation
### security-tooling
Development and Enhancements of Security Tooling
- **Owners:**
- [kubernetes-sigs/cve-feed-osv](https://github.com/kubernetes-sigs/cve-feed-osv/blob/main/OWNERS)
- [kubernetes/sig-security/sig-security-tooling](https://github.com/kubernetes/sig-security/blob/main/sig-security-tooling/OWNERS)
- **Contact:**
- Slack: [#sig-security-tooling](https://kubernetes.slack.com/messages/sig-security-tooling)
Expand Down
1 change: 1 addition & 0 deletions sigs.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2815,6 +2815,7 @@ sigs:
contact:
slack: sig-security-tooling
owners:
- https://raw.githubusercontent.com/kubernetes-sigs/cve-feed-osv/main/OWNERS
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@PushkarJ can you confirm if adding it as a project under the sig-security-tooling subproject is accurate or do we require a new subproject to be created?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this mostly for documentation purposes or does this mean some permissions like approving or lgtm will be granted to owners of that subproject?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it's documentation purposes it's fine to keep the sub-project as sig-security-tooling

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just documenting @PushkarJ :)
Will need an lgtm from a sig security lead though!

- https://raw.githubusercontent.com/kubernetes/sig-security/main/sig-security-tooling/OWNERS
- name: sig-security
description: SIG Security discussions, documents, processes and other artifacts
Expand Down