Skip to content
Snippets Groups Projects
Select Git revision
  • bac8ca7802010a8b308c405831ea7fdfa00d630b
  • master default protected
  • doctest
  • 3.2.5
  • 3.2.4
  • 3.2.3
  • 3.2.2
  • 3.2.1
  • 3.2.0
  • 3.1.5
  • 3.1.4
  • 3.1.3
  • 3.1.2
  • 3.1.1
  • 3.1.0
  • 3.1.0-pre1
  • 3.0.0
  • 2.3.0
  • 2.2.2
  • 2.2.1
  • 2.2.0
  • 2.1.0
  • AndroidSdk_v0.2.0
23 results

CONTRIBUTING.rst

Blame
    • user avatar
    Request patches to olm@matrix.org
    Richard van der Hoff authored
    0dc27f73
    History
    user avatar 0dc27f73
    History
    Code owners
    Assign users and groups as approvers for specific file changes. Learn more.
    After you've reviewed these contribution guidelines, you'll be all set to contribute to this project.
    CONTRIBUTING.rst 2.96 KiB

    Contributing code to libolm

    To contribute code to this library, the preferred way is to clone the git repository, create a git patch series (for example via git format-patch --stdout origin/master), and send this by email to olm@matrix.org.

    Naturally, you must be willing to license your contributions under the same license as the project itself - in this case, Apache Software License v2 (see LICENSE).

    Sign off

    In order to have a concrete record that your contribution is intentional and you agree to license it under the same terms as the project's license, we've adopted the same lightweight approach that the Linux Kernel, Docker, and many other projects use: the DCO (Developer Certificate of Origin). This is a simple declaration that you wrote the contribution or otherwise have the right to contribute it to Matrix:

    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.

    If you agree to this for your contribution, then all that's needed is to include the line in your commits or covering email:

    Signed-off-by: Your Name <your@email.example.org>

    ...using your real name; unfortunately pseudonyms and anonymous contributions can't be accepted. Git makes this trivial - just use the -s flag when you do git commit, having first set user.name and user.email git configs (which you should have done anyway :)