Merge pull request #408 from kubespray/upstreaming_to_k8s
upstreaming to k8s
This commit is contained in:
commit
612266f3e5
4 changed files with 84 additions and 0 deletions
10
CONTRIBUTING.md
Normal file
10
CONTRIBUTING.md
Normal file
|
@ -0,0 +1,10 @@
|
||||||
|
# Contributing guidelines
|
||||||
|
|
||||||
|
## How to become a contributor and submit your own code
|
||||||
|
|
||||||
|
### Contributing A Patch
|
||||||
|
|
||||||
|
1. Submit an issue describing your proposed change to the repo in question.
|
||||||
|
2. The [repo owners](OWNERS) will respond to your issue promptly.
|
||||||
|
3. Fork the desired repo, develop and test your code changes.
|
||||||
|
4. Submit a pull request.
|
6
OWNERS
Normal file
6
OWNERS
Normal file
|
@ -0,0 +1,6 @@
|
||||||
|
# See the OWNERS file documentation:
|
||||||
|
# https://github.com/kubernetes/kubernetes/blob/master/docs/devel/owners.md
|
||||||
|
|
||||||
|
owners:
|
||||||
|
- Smana
|
||||||
|
- ant31
|
9
RELEASE.md
Normal file
9
RELEASE.md
Normal file
|
@ -0,0 +1,9 @@
|
||||||
|
# Release Process
|
||||||
|
|
||||||
|
The Kargo 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
|
||||||
|
2. At least on of the [OWNERS](OWNERS) must LGTM this release
|
||||||
|
3. An OWNER runs `git tag -s $VERSION` and inserts the changelog and pushes the tag with `git push $VERSION`
|
||||||
|
4. The release issue is closed
|
||||||
|
5. An announcement email is sent to `kubernetes-dev@googlegroups.com` with the subject `[ANNOUNCE] kargo $VERSION is released`
|
59
code-of-conduct.md
Normal file
59
code-of-conduct.md
Normal file
|
@ -0,0 +1,59 @@
|
||||||
|
## Kubernetes Community Code of Conduct
|
||||||
|
|
||||||
|
### Contributor Code of Conduct
|
||||||
|
|
||||||
|
As contributors and maintainers of this project, and in the interest of fostering
|
||||||
|
an open and welcoming community, we pledge to respect all people who contribute
|
||||||
|
through reporting issues, posting feature requests, updating documentation,
|
||||||
|
submitting pull requests or patches, and other activities.
|
||||||
|
|
||||||
|
We are committed to making participation in this project a harassment-free experience for
|
||||||
|
everyone, regardless of level of experience, gender, gender identity and expression,
|
||||||
|
sexual orientation, disability, personal appearance, body size, race, ethnicity, age,
|
||||||
|
religion, or nationality.
|
||||||
|
|
||||||
|
Examples of unacceptable behavior by participants include:
|
||||||
|
|
||||||
|
* The use of sexualized language or imagery
|
||||||
|
* Personal attacks
|
||||||
|
* Trolling or insulting/derogatory comments
|
||||||
|
* Public or private harassment
|
||||||
|
* Publishing other's private information, such as physical or electronic addresses,
|
||||||
|
without explicit permission
|
||||||
|
* Other unethical or unprofessional conduct.
|
||||||
|
|
||||||
|
Project maintainers have the right and responsibility to remove, edit, or reject
|
||||||
|
comments, commits, code, wiki edits, issues, and other contributions that are not
|
||||||
|
aligned to this Code of Conduct. By adopting this Code of Conduct, project maintainers
|
||||||
|
commit themselves to fairly and consistently applying these principles to every aspect
|
||||||
|
of managing this project. Project maintainers who do not follow or enforce the Code of
|
||||||
|
Conduct may be permanently removed from the project team.
|
||||||
|
|
||||||
|
This code of conduct applies both within project spaces and in public spaces
|
||||||
|
when an individual is representing the project or its community.
|
||||||
|
|
||||||
|
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by
|
||||||
|
opening an issue or contacting one or more of the project maintainers.
|
||||||
|
|
||||||
|
This Code of Conduct is adapted from the Contributor Covenant
|
||||||
|
(http://contributor-covenant.org), version 1.2.0, available at
|
||||||
|
http://contributor-covenant.org/version/1/2/0/
|
||||||
|
|
||||||
|
### Kubernetes Events Code of Conduct
|
||||||
|
|
||||||
|
Kubernetes events are working conferences intended for professional networking and collaboration in the
|
||||||
|
Kubernetes community. Attendees are expected to behave according to professional standards and in accordance
|
||||||
|
with their employer's policies on appropriate workplace behavior.
|
||||||
|
|
||||||
|
While at Kubernetes events or related social networking opportunities, attendees should not engage in
|
||||||
|
discriminatory or offensive speech or actions regarding gender, sexuality, race, or religion. Speakers should
|
||||||
|
be especially aware of these concerns.
|
||||||
|
|
||||||
|
The Kubernetes team does not condone any statements by speakers contrary to these standards. The Kubernetes
|
||||||
|
team reserves the right to deny entrance and/or eject from an event (without refund) any individual found to
|
||||||
|
be engaging in discriminatory or offensive speech or actions.
|
||||||
|
|
||||||
|
Please bring any concerns to to the immediate attention of Kubernetes event staff
|
||||||
|
|
||||||
|
|
||||||
|
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/code-of-conduct.md?pixel)]()
|
Loading…
Reference in a new issue