-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
11 changed files
with
532 additions
and
24 deletions.
There are no files selected for viewing
This file contains 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 |
---|---|---|
@@ -0,0 +1,23 @@ | ||
<!-- Thanks for sending a pull request! Here are some tips for you: | ||
1. If this is your first time sending a pull request, please read our contributing guidelines: https://github.com/kubermatic/kubelb/blob/main/CONTRIBUTING.md | ||
2. Make sure *all* commits in a pull request have the DCO signoff message. Without a DCO signoff, we can't review and merge your pull request due to legal reasons. Check the contributing guidelines for more information about DCO and how to sign commits: https://github.com/OWNER/PROJECT/blob/master/CONTRIBUTING.md#certificate-of-origin | ||
3. If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests | ||
--> | ||
|
||
**What this PR does / why we need it**: | ||
|
||
**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close | ||
the issue(s) when PR gets merged)*: | ||
Fixes # | ||
|
||
**Special notes for your reviewer**: | ||
|
||
**Does this PR introduce a user-facing change?**: | ||
<!-- Write your release note: | ||
1. Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required". | ||
2. If no release note is required, just write "NONE". | ||
--> | ||
|
||
```release-note | ||
``` |
This file contains 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 |
---|---|---|
@@ -0,0 +1,28 @@ | ||
# Copyright 2020 The KubeLB Authors. | ||
# | ||
# Licensed under the Apache License, Version 2.0 (the "License"); | ||
# you may not use this file except in compliance with the License. | ||
# You may obtain a copy of the License at | ||
# | ||
# http://www.apache.org/licenses/LICENSE-2.0 | ||
# | ||
# Unless required by applicable law or agreed to in writing, software | ||
# distributed under the License is distributed on an "AS IS" BASIS, | ||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
# See the License for the specific language governing permissions and | ||
# limitations under the License. | ||
|
||
# presubmits: | ||
# - name: pre-kubelb-verify-boilerplate | ||
# always_run: true | ||
# decorate: true | ||
# clone_uri: "ssh://[email protected]/kubermatic/kubelb.git" | ||
# spec: | ||
# containers: | ||
# - image: quay.io/kubermatic-labs/boilerplate:v0.1.1 | ||
# command: | ||
# - ./hack/verify-boilerplate.sh | ||
# resources: | ||
# requests: | ||
# cpu: 200m | ||
# memory: 256Mi |
This file contains 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 |
---|---|---|
@@ -0,0 +1,36 @@ | ||
# Kubermatic 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 others' 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 contacting the Kubermatic Conduct | ||
Committee via [email protected]. | ||
|
||
This Code of Conduct is adapted from | ||
the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md) | ||
and [Contributor Covenant](http://contributor-covenant.org/version/1/2/0/), version 1.2.0. |
This file contains 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 |
---|---|---|
@@ -0,0 +1,104 @@ | ||
# How to Contribute | ||
|
||
Kubermatic projects are [Apache 2.0 licensed](LICENSE) and accept contributions via GitHub pull requests. This document | ||
outlines some of the conventions on development workflow, commit message formatting, contact points and other resources | ||
to make it easier to get your contribution accepted. | ||
|
||
## Certificate of Origin | ||
|
||
By contributing to this project you agree to the Developer Certificate of Origin (DCO). This document was created by the | ||
Linux Kernel community and is a simple statement that you, as a contributor, have the legal right to make the | ||
contribution. See the [DCO](DCO) file for details. | ||
|
||
Any copyright notices in this repo should specify the authors as "the Kubermatic KubeLB project contributors". | ||
|
||
To sign your work, just add a line like this at the end of your commit message: | ||
|
||
``` | ||
Signed-off-by: Joe Example <[email protected]> | ||
``` | ||
|
||
This can easily be done with the `--signoff` option to `git commit`. | ||
|
||
Note that we're requiring all commits in a PR to be signed-off. If you already created a PR, you can sign-off all | ||
existing commits by rebasing with the `--signoff` flag. | ||
|
||
``` | ||
git rebase --signoff origin/master | ||
``` | ||
|
||
By doing this you state that you can certify the following (from https://developercertificate.org/): | ||
|
||
``` | ||
Developer Certificate of Origin | ||
Version 1.1 | ||
Copyright (C) 2004, 2006 The Linux Foundation and its contributors. | ||
1 Letterman Drive | ||
Suite D4700 | ||
San Francisco, CA, 94129 | ||
Everyone is permitted to copy and distribute verbatim copies of this | ||
license document, but changing it is not allowed. | ||
Developer's Certificate of Origin 1.1 | ||
By making a contribution to this project, I certify that: | ||
(a) The contribution was created in whole or in part by me and I | ||
have the right to submit it under the open source license | ||
indicated in the file; or | ||
(b) The contribution is based upon previous work that, to the best | ||
of my knowledge, is covered under an appropriate open source | ||
license and I have the right under that license to submit that | ||
work with modifications, whether created in whole or in part | ||
by me, under the same open source license (unless I am | ||
permitted to submit under a different license), as indicated | ||
in the file; or | ||
(c) The contribution was provided directly to me by some other | ||
person who certified (a), (b) or (c) and I have not modified | ||
it. | ||
(d) I understand and agree that this project and the contribution | ||
are public and that a record of the contribution (including all | ||
personal information I submit with it, including my sign-off) is | ||
maintained indefinitely and may be redistributed consistent with | ||
this project or the open source license(s) involved. | ||
``` | ||
|
||
## Email and Chat | ||
|
||
The KubeLB project currently uses the general Kubermatic email list and Slack channel: | ||
|
||
- Email: [kubermatic-dev](https://groups.google.com/forum/#!forum/kubermatic-dev) | ||
- Slack: #[Slack](http://slack.kubermatic.io/) on Slack | ||
|
||
Please avoid emailing maintainers found in the MAINTAINERS file directly. They are very busy and read the mailing lists. | ||
|
||
## Reporting a security vulnerability | ||
|
||
Due to their public nature, GitHub and mailing lists are not appropriate places for reporting vulnerabilities. If you | ||
suspect you have found a security vulnerability, please do not file a GitHub issue, but instead email | ||
[email protected] with the full details, including steps to reproduce the issue. | ||
|
||
## Getting Started | ||
|
||
- Fork the repository on GitHub | ||
- Read the [README](README.md) for build and test instructions | ||
- Play with the project, submit bugs, submit patches! | ||
|
||
### Contribution Flow | ||
|
||
This is a rough outline of what a contributor's workflow looks like: | ||
|
||
- Create a topic branch from where you want to base your work (usually master). | ||
- Make commits of logical units. | ||
- Make sure your commit messages are in the proper format (see below). | ||
- Push your changes to a topic branch in your fork of the repository. | ||
- Make sure the tests pass, and add any new tests as appropriate. | ||
- Submit a pull request to the original repository. | ||
|
||
Thanks for your contributions! |
This file contains 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 |
---|---|---|
@@ -0,0 +1,36 @@ | ||
Developer Certificate of Origin | ||
Version 1.1 | ||
|
||
Copyright (C) 2004, 2006 The Linux Foundation and its contributors. | ||
660 York Street, Suite 102, | ||
San Francisco, CA 94110 USA | ||
|
||
Everyone is permitted to copy and distribute verbatim copies of this | ||
license document, but changing it is not allowed. | ||
|
||
|
||
Developer's Certificate of Origin 1.1 | ||
|
||
By making a contribution to this project, I certify that: | ||
|
||
(a) The contribution was created in whole or in part by me and I | ||
have the right to submit it under the open source license | ||
indicated in the file; or | ||
|
||
(b) The contribution is based upon previous work that, to the best | ||
of my knowledge, is covered under an appropriate open source | ||
license and I have the right under that license to submit that | ||
work with modifications, whether created in whole or in part | ||
by me, under the same open source license (unless I am | ||
permitted to submit under a different license), as indicated | ||
in the file; or | ||
|
||
(c) The contribution was provided directly to me by some other | ||
person who certified (a), (b) or (c) and I have not modified | ||
it. | ||
|
||
(d) I understand and agree that this project and the contribution | ||
are public and that a record of the contribution (including all | ||
personal information I submit with it, including my sign-off) is | ||
maintained indefinitely and may be redistributed consistent with | ||
this project or the open source license(s) involved. |
Oops, something went wrong.