Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

How To Sign Patches

Introduction

In contrast to many other Linux drivers MadWifi makes use of a dual-license (BSD and GPL2). This mostly is because MadWifi shares a lot of code with the Sam Leffler's Atheros driver that is found in FreeBSD, and also makes use of the 802.11 stack used in NetBSD and FreeBSD.

While this is obvious to most people who work with MadWifi for some time, it might not be obvious for everyone who thinks of contributing to the project. On the other hand it is important for the project to make sure that every contribution is made with the dual-license (and the resulting implications) in mind. Even more because several companies contributed to the project in the past.

The idea of "signing off" contributed patches was inspired by a similar procedure for the Linux kernel. Someone who signs his/her contribution can safely be expected to know what that means. Everyone who doesn't know about the meaning will most probably ask, which gives us the chance to point them to this page.

We are aware that the Signed-off-by: mechanism can't be compared to digital signatures. That, however, is no problem. As stated above the main idea is to reduce the chance that contributors cause trouble due to license disagreements.

How to sign your contribution

Contributions which need to be signed are usually submitted by attaching the work to a new ticket (or, eventually, to an e-mail). Sign your contribution by adding the Signed-off-by: line to the description of the contributed work. Unsigned contributions will be rejected.

Example:

The attached patch adds support for changing the TX power of
MadWifi driven cards via 'iwconfig <dev> txpower <power>'. Currently
<power> may only be given in dBm, will fix that in another patch.

Signed-off-by: Random J Developer <rjd@example.com>

The name and e-mail address of course should be adjusted accordingly. If the work is actually contributed by a company (rather than a single person) the company name should be mentioned as well.

MadWifi Developer's Certificate of Origin v1.0

By signing my contribution to the MadWifi project, I certify/agree that:

(a) The contribution may be distributed under the same licenses as the MadWifi project, as detailed in the COPYRIGHT file (called the file from here on).

(b) The contribution was created in whole or in part by me and I have the right to submit it under the open source licenses indicated in the file; or

(c) 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 licenses (unless I am permitted to submit under a different license), as indicated in the file; or

(d) The contribution was provided directly to me by some other person who certified (a) and (b), (c) or (d) and I have not modified it.

(e) In the case of each of (a) and (b), (c) or (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 indicated in the file.

Certificate History

v1.0 - 2005-11-29

v1.0 of our certificate was published on November 29, 2005. It has been derived from the Developer's Certificate of Origin v1.1, which was posted to lkml by Linus Torvalds on June 17, 2005.