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