generated from kubernetes/kubernetes-template-project
-
Notifications
You must be signed in to change notification settings - Fork 67
Added README #24
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
Merged
Merged
Added README #24
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,29 +1,61 @@ | ||
# Kubernetes Template Project | ||
|
||
The Kubernetes Template Project is a template for starting new projects in the GitHub organizations owned by Kubernetes. All Kubernetes projects, at minimum, must have the following files: | ||
|
||
- a `README.md` outlining the project goals, sponsoring sig, and community contact information | ||
- an `OWNERS` with the project leads listed as approvers ([docs on `OWNERS` files][owners]) | ||
- a `CONTRIBUTING.md` outlining how to contribute to the project | ||
- an unmodified copy of `code-of-conduct.md` from this repo, which outlines community behavior and the consequences of breaking the code | ||
- a `LICENSE` which must be Apache 2.0 for code projects, or [Creative Commons 4.0] for documentation repositories, without any custom content | ||
- a `SECURITY_CONTACTS` with the contact points for the Product Security Team | ||
to reach out to for triaging and handling of incoming issues. They must agree to abide by the | ||
[Embargo Policy](https://git.k8s.io/security/private-distributors-list.md#embargo-policy) | ||
and will be removed and replaced if they violate that agreement. | ||
|
||
## Community, discussion, contribution, and support | ||
|
||
Learn how to engage with the Kubernetes community on the [community page](http://kubernetes.io/community/). | ||
|
||
You can reach the maintainers of this project at: | ||
|
||
- [Slack](http://slack.k8s.io/) | ||
- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-dev) | ||
|
||
### Code of conduct | ||
|
||
Participation in the Kubernetes community is governed by the [Kubernetes Code of Conduct](code-of-conduct.md). | ||
|
||
[owners]: https://git.k8s.io/community/contributors/guide/owners.md | ||
[Creative Commons 4.0]: https://git.k8s.io/website/LICENSE | ||
# Security Special Interest Group | ||
|
||
Covers horizontal security initiatives for the Kubernetes project, including regular security audits, the vulnerability management process, cross-cutting security documentation, and security community management. | ||
|
||
The [charter](https://github.com/kubernetes/community/blob/master/sig-security/charter.md) defines the scope and governance of the Security Special Interest Group. | ||
|
||
## Meetings | ||
*Joining the [mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-security) for the group will typically add invites for the following meetings to your calendar.* | ||
* Regular SIG Meeting: [Thursdays at 9:00 PT (Pacific Time)](https://zoom.us/j/9934z1184192?pwd=L25Tc0ZOL3FqU09KNERlTU12dFhTQT09) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=9:00&tz=PT%20%28Pacific%20Time%29). | ||
* [Meeting notes and Agenda](https://docs.google.com/document/d/1GgmmNYN88IZ2v2NBiO3gdU8Riomm0upge_XNVxEYXp0/edit?usp=sharing). | ||
* [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP1mXOLAc9ti0oX8s_ookQCi). | ||
|
||
## Leadership | ||
|
||
### Chairs | ||
The Chairs of the SIG run operations and processes governing the SIG. | ||
|
||
* Ian Coldwater (**[@IanColdwater](https://github.com/IanColdwater)**), Twilio | ||
* Tabitha Sable (**[@tabbysable](https://github.com/tabbysable)**), Datadog | ||
|
||
## Contact | ||
- Slack: [#sig-security](https://kubernetes.slack.com/messages/sig-security) | ||
- [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-security) | ||
- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fsecurity) | ||
chetak123 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
- [Sig Security Issues](https://github.com/kubernetes/sig-security/issues) | ||
- GitHub Teams: | ||
- [@kubernetes/sig-security-leads](https://github.com/orgs/kubernetes/teams/sig-security-leads) - SIG Security Leads | ||
- [@kubernetes/sig-security-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-security-pr-reviews) - SIG Security PR review notifications | ||
- Steering Committee Liaison: Paris Pittman (**[@parispittman](https://github.com/parispittman)**) | ||
|
||
## Subprojects | ||
chetak123 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
The following [subprojects][subproject-definition] are owned by sig-security: | ||
### security-assessments | ||
Information about Security Assessments | ||
- **Owners:** | ||
- [@kubernetes/sig-security-assessments](https://github.com/kubernetes/sig-security/blob/main/sig-security-assessments/OWNERS) | ||
### security-audit | ||
Third Party Security Audit | ||
- **Owners:** | ||
- [kubernetes/sig-security/sig-security-external-audit](https://github.com/kubernetes/sig-security/blob/main/sig-security-external-audit/OWNERS) | ||
### security-docs | ||
Security Documents and Documentation | ||
- **Owners:** | ||
- [kubernetes/sig-security/sig-security-docs](https://github.com/kubernetes/sig-security/blob/main/sig-security-docs/OWNERS) | ||
- **Contact:** | ||
- Slack: [#sig-security-docs](https://kubernetes.slack.com/messages/sig-security-docs) | ||
### security-tooling | ||
Development and Enhancements of Security Tooling | ||
- **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) | ||
### sig-security | ||
SIG Security discussions, documents, processes and other artifacts | ||
- **Owners:** | ||
- [kubernetes/sig-security](https://github.com/kubernetes/sig-security/blob/master/OWNERS) | ||
- **Contact:** | ||
- Slack: [#sig-security](https://kubernetes.slack.com/messages/sig-security) | ||
|
||
[subproject-definition]: https://github.com/kubernetes/community/blob/master/governance.md#subprojects |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.