CONTRIBUTIONS 7.5 KB

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