Licensing

As BabbleSim is formed of multiple, independent, and mostly optional components, different licenses may apply to different components. Overall, and unless otherwise stated, BabbleSim components use the Apache 2.0 license (as found in the LICENSE file in each component GitHub repo), both for their source code and documentation.

Components using other Licenses

There are some components in BabbleSim which use different licenses than the Apache 2.0. In the component in which it is applicable, it will be described in its LICENSE file, which is placed in that component docs/ folder.

Developer Certification of Origin (DCO)

The BabbleSim project requires the Developer Certificate of Origin (DCO) process to be followed for its contributions.

This is done as a resonable measure to ensure all code in BabbleSim components can be licensed under the claimed terms.

By adding a Signed-off-by line to the commit body message like:

   Signed-off-by: John Doe <JohnDoe@somedomain.com>

the contributor certifies that he has the right to, and does submit that patch, under the applicable license, and, that he agrees to the DCO.

The DCO agreement can be found in http://developercertificate.org/, and is shown below:

   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.