Skip to content

Commit

Permalink
Add DCO (#111)
Browse files Browse the repository at this point in the history
  • Loading branch information
tamalsaha authored Aug 6, 2017
1 parent 28a4c3a commit fa9132e
Show file tree
Hide file tree
Showing 2 changed files with 57 additions and 10 deletions.
31 changes: 21 additions & 10 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,15 @@
# Contribution Guidelines
# How to Contribute

AppsCode 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.

## Developer Guide
We have a [Developer Guide](/docs/developer-guide/README.md) that outlines everything you need to know from setting up your
Expand All @@ -13,16 +24,16 @@ If you have found a bug with KubeDB or want to request for new features, please
- For CLI issues, file a bug under [k8sdb/cli](https://github.com/k8sdb/cli) repository.
- For Backend operator issues, file a bug under [k8sdb/operator](https://github.com/k8sdb/operator) repository.

## Submit PR
If you fix a bug or developed a new feature, feel free to submit a PR. In either case, please file a Github issue first, so that we can have a discussion on it.
## Contribution Flow
If you fix a bug or developed a new feature, feel free to submit a PR. In either case, please file a Github issue first, so that we can have a discussion on it. 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.
- 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.

1. Fork the git repo.
2. Add Your changes
3. Add Test Cases to verify the changes
4. Run the tests
5. Build the project
6. Run e2e tests
7. Submit PR. And there you go.
Thanks for your contributions!

## Spread the word
If you have written blog post or tutorial on KubeDB, please share it with us on [Twitter](https://twitter.com/AppsCodeHQ) or [Slack](https://slack.appscode.com).
36 changes: 36 additions & 0 deletions DCO
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.

0 comments on commit fa9132e

Please sign in to comment.