| 1 |
Contributions to hostap.git |
| 2 |
--------------------------- |
| 3 |
|
| 4 |
This software is distributed under a permissive open source license to |
| 5 |
allow it to be used in any projects, whether open source or proprietary. |
| 6 |
Contributions to the project are welcome and it is important to maintain |
| 7 |
clear record of contributions and terms under which they are licensed. |
| 8 |
To help with this, following procedure is used to allow acceptance and |
| 9 |
recording of the terms. |
| 10 |
|
| 11 |
All contributions are expected to be licensed under the modified BSD |
| 12 |
license (see below). Acknowledgment of the terms is tracked through |
| 13 |
inclusion of Signed-off-by tag in the contributions at the end of the |
| 14 |
commit log message. This tag indicates that the contributor agrees with |
| 15 |
the Developer Certificate of Origin (DCO) version 1.1 terms (see below; |
| 16 |
also available from http://developercertificate.org/). |
| 17 |
|
| 18 |
|
| 19 |
The current requirements for contributions to hostap.git |
| 20 |
-------------------------------------------------------- |
| 21 |
|
| 22 |
To indicate your acceptance of Developer's Certificate of Origin 1.1 |
| 23 |
terms, please add the following line to the end of the commit message |
| 24 |
for each contribution you make to the project: |
| 25 |
|
| 26 |
Signed-off-by: Your Name <[email protected]> |
| 27 |
|
| 28 |
using your real name. Pseudonyms or anonymous contributions cannot |
| 29 |
unfortunately be accepted. |
| 30 |
|
| 31 |
|
| 32 |
The preferred method of submitting the contribution to the project is by |
| 33 |
email to the hostap mailing list: |
| 34 |
[email protected] |
| 35 |
Note that the list may require subscription before accepting message |
| 36 |
without moderation. You can subscribe to the list at this address: |
| 37 |
http://lists.infradead.org/mailman/listinfo/hostap |
| 38 |
|
| 39 |
The message should contain an inlined patch against the current |
| 40 |
development branch (i.e., the master branch of |
| 41 |
git://w1.fi/hostap.git). Please make sure the software you use for |
| 42 |
sending the patch does not corrupt whitespace. If that cannot be fixed |
| 43 |
for some reason, it is better to include an attached version of the |
| 44 |
patch file than just send a whitespace damaged version in the message |
| 45 |
body. |
| 46 |
|
| 47 |
The patches should be separate logical changes rather than doing |
| 48 |
everything in a single patch. In other words, please keep cleanup, new |
| 49 |
features, and bug fixes all in their own patches. Each patch needs a |
| 50 |
commit log that describes the changes (what the changes fix, what |
| 51 |
functionality is added, why the changes are useful, etc.). |
| 52 |
|
| 53 |
Please try to follow the coding style used in the project. |
| 54 |
|
| 55 |
In general, the best way of generating a suitable formatted patch file |
| 56 |
is by committing the changes to a cloned git repository and using git |
| 57 |
format-patch. The patch can then be sent, e.g., with git send-email. |
| 58 |
|
| 59 |
A list of pending patches waiting for review is available in |
| 60 |
Patchwork: https://patchwork.ozlabs.org/project/hostap/list/ |
| 61 |
|
| 62 |
|
| 63 |
History of license and contributions terms |
| 64 |
------------------------------------------ |
| 65 |
|
| 66 |
Until February 11, 2012, in case of most files in hostap.git, "under the |
| 67 |
open source license indicated in the file" means that the contribution |
| 68 |
is licensed both under GPL v2 and modified BSD license (see below) and |
| 69 |
the choice between these licenses is given to anyone who redistributes |
| 70 |
or uses the software. As such, the contribution has to be licensed under |
| 71 |
both options to allow this choice. |
| 72 |
|
| 73 |
As of February 11, 2012, the project has chosen to use only the BSD |
| 74 |
license option for future distribution. As such, the GPL v2 license |
| 75 |
option is no longer used and the contributions are not required to be |
| 76 |
licensed until GPL v2. In case of most files in hostap.git, "under the |
| 77 |
open source license indicated in the file" means that the contribution |
| 78 |
is licensed under the modified BSD license (see below). |
| 79 |
|
| 80 |
Until February 13, 2014, the project used an extended version of the DCO |
| 81 |
that included the identical items (a) through (d) from DCO 1.1 and an |
| 82 |
additional item (e): |
| 83 |
|
| 84 |
(e) The contribution can be licensed under the modified BSD license |
| 85 |
as shown below even in case of files that are currently licensed |
| 86 |
under other terms. |
| 87 |
|
| 88 |
This was used during the period when some of the files included the old |
| 89 |
license terms. Acceptance of this extended DCO version was indicated |
| 90 |
with a Signed-hostap tag in the commit message. This additional item (e) |
| 91 |
was used to collect explicit approval to license the contribution with |
| 92 |
only the modified BSD license (see below), i.e., without the GPL v2 |
| 93 |
option. This was done to allow simpler licensing terms to be used in the |
| 94 |
future. It should be noted that the modified BSD license is compatible |
| 95 |
with GNU GPL and as such, this possible move to simpler licensing option |
| 96 |
does not prevent use of this software in GPL projects. |
| 97 |
|
| 98 |
|
| 99 |
===[ start quote from http://developercertificate.org/ ]======================= |
| 100 |
|
| 101 |
Developer Certificate of Origin |
| 102 |
Version 1.1 |
| 103 |
|
| 104 |
Copyright (C) 2004, 2006 The Linux Foundation and its contributors. |
| 105 |
660 York Street, Suite 102, |
| 106 |
San Francisco, CA 94110 USA |
| 107 |
|
| 108 |
Everyone is permitted to copy and distribute verbatim copies of this |
| 109 |
license document, but changing it is not allowed. |
| 110 |
|
| 111 |
|
| 112 |
Developer's Certificate of Origin 1.1 |
| 113 |
|
| 114 |
By making a contribution to this project, I certify that: |
| 115 |
|
| 116 |
(a) The contribution was created in whole or in part by me and I |
| 117 |
have the right to submit it under the open source license |
| 118 |
indicated in the file; or |
| 119 |
|
| 120 |
(b) The contribution is based upon previous work that, to the best |
| 121 |
of my knowledge, is covered under an appropriate open source |
| 122 |
license and I have the right under that license to submit that |
| 123 |
work with modifications, whether created in whole or in part |
| 124 |
by me, under the same open source license (unless I am |
| 125 |
permitted to submit under a different license), as indicated |
| 126 |
in the file; or |
| 127 |
|
| 128 |
(c) The contribution was provided directly to me by some other |
| 129 |
person who certified (a), (b) or (c) and I have not modified |
| 130 |
it. |
| 131 |
|
| 132 |
(d) I understand and agree that this project and the contribution |
| 133 |
are public and that a record of the contribution (including all |
| 134 |
personal information I submit with it, including my sign-off) is |
| 135 |
maintained indefinitely and may be redistributed consistent with |
| 136 |
this project or the open source license(s) involved. |
| 137 |
|
| 138 |
===[ end quote from http://developercertificate.org/ ]========================= |
| 139 |
|
| 140 |
|
| 141 |
The license terms used for hostap.git files |
| 142 |
------------------------------------------- |
| 143 |
|
| 144 |
Modified BSD license (no advertisement clause): |
| 145 |
|
| 146 |
Copyright (c) 2002-2022, Jouni Malinen <[email protected]> and contributors |
| 147 |
All Rights Reserved. |
| 148 |
|
| 149 |
Redistribution and use in source and binary forms, with or without |
| 150 |
modification, are permitted provided that the following conditions are |
| 151 |
met: |
| 152 |
|
| 153 |
1. Redistributions of source code must retain the above copyright |
| 154 |
notice, this list of conditions and the following disclaimer. |
| 155 |
|
| 156 |
2. Redistributions in binary form must reproduce the above copyright |
| 157 |
notice, this list of conditions and the following disclaimer in the |
| 158 |
documentation and/or other materials provided with the distribution. |
| 159 |
|
| 160 |
3. Neither the name(s) of the above-listed copyright holder(s) nor the |
| 161 |
names of its contributors may be used to endorse or promote products |
| 162 |
derived from this software without specific prior written permission. |
| 163 |
|
| 164 |
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS |
| 165 |
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT |
| 166 |
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR |
| 167 |
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT |
| 168 |
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, |
| 169 |
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT |
| 170 |
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, |
| 171 |
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY |
| 172 |
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT |
| 173 |
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE |
| 174 |
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |