-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
Signed-off-by: Stefan Prodan <[email protected]>
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
## Code of Conduct | ||
|
||
Flagger follows the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md). |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -14,10 +14,28 @@ 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. | ||
|
||
## Chat | ||
We require all commits to be signed. By signing off with your signature, you | ||
certify that you wrote the patch or otherwise have the right to contribute the | ||
material by the rules of the [DCO](DCO): | ||
|
||
`Signed-off-by: Jane Doe <[email protected]>` | ||
|
||
The signature must contain your real name | ||
(sorry, no pseudonyms or anonymous contributions) | ||
If your `user.name` and `user.email` are configured in your Git config, | ||
you can sign your commit automatically with `git commit -s`. | ||
|
||
## Communications | ||
|
||
The project uses Slack: To join the conversation, simply join the | ||
[Weave community](https://slack.weave.works/) Slack workspace #flagger channel. | ||
[CNCF](https://slack.cncf.io/) Slack workspace and use the | ||
[#flux](https://cloud-native.slack.com/messages/flux/) channel. | ||
|
||
The developers use a mailing list to discuss development as well. | ||
Simply subscribe to [flux-dev on cncf.io](https://lists.cncf.io/g/cncf-flux-dev) | ||
to join the conversation (this will also add an invitation to your | ||
Google calendar for our [Flux | ||
meeting](https://docs.google.com/document/d/1l_M0om0qUEN_NNiGgpqJ2tvsF2iioHkaARDeh6b70B0/edit#)). | ||
|
||
## Getting Started | ||
|
||
|
@@ -69,4 +87,3 @@ For Flagger we prefer the following rules for good commit messages: | |
The [following article](https://chris.beams.io/posts/git-commit/#seven-rules) | ||
has some more helpful advice on documenting your work. | ||
|
||
This doc is adapted from [FluxCD](https://github.com/fluxcd/flux/blob/master/CONTRIBUTING.md). |
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. |
This file was deleted.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.