cleanup boilerplate files slightly
- update README with non-boilerplate content - remove boilerplate RELEASE.md that doesn't apply here currently - add myself to SECURITY_CONTACTS, I'm in OWNERS and already have agreed to the terms elswhere
This commit is contained in:
parent
493fd485c8
commit
ca75b4b34e
14
README.md
14
README.md
|
|
@ -1,16 +1,6 @@
|
||||||
# Kubernetes Template Project
|
# oci-proxy
|
||||||
|
|
||||||
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:
|
This project is currently an experiment, for more see [cmd/archeio](./cmd/archeio/README.md)
|
||||||
|
|
||||||
- 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
|
## Community, discussion, contribution, and support
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,9 +0,0 @@
|
||||||
# Release Process
|
|
||||||
|
|
||||||
The Kubernetes Template Project is released on an as-needed basis. The process is as follows:
|
|
||||||
|
|
||||||
1. An issue is proposing a new release with a changelog since the last release
|
|
||||||
1. All [OWNERS](OWNERS) must LGTM this release
|
|
||||||
1. An OWNER runs `git tag -s $VERSION` and inserts the changelog and pushes the tag with `git push $VERSION`
|
|
||||||
1. The release issue is closed
|
|
||||||
1. An announcement email is sent to `kubernetes-dev@googlegroups.com` with the subject `[ANNOUNCE] kubernetes-template-project $VERSION is released`
|
|
||||||
|
|
@ -11,6 +11,7 @@
|
||||||
# INSTRUCTIONS AT https://kubernetes.io/security/
|
# INSTRUCTIONS AT https://kubernetes.io/security/
|
||||||
|
|
||||||
ameukam
|
ameukam
|
||||||
|
bentheelder
|
||||||
dims
|
dims
|
||||||
spiffxp
|
spiffxp
|
||||||
thockin
|
thockin
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue