-
Notifications
You must be signed in to change notification settings - Fork 183
HowToContribute
erikarn edited this page Mar 27, 2013
·
1 revision
Contributing is easy.
Firstly - make sure you've subscribed to the mailing list!
Next - when you contribute patches, you must abide by the Linux coding "Signed-off-by" concept. That is, that you did the work; that you don't know of any patent infringements introduced by your code; that you contribute you work under the same licence as the file falls under.
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.
So, whenever you send a patch or merge request, it must include a signed-off-by tag indicating you agree to the above.
That's it! Send a merge request or patch with a signed-off-by tag and be prepared to haggle with the maintainers / developers!