eLinux.org - User contributions [en]

Legal Issues

2011-04-11T20:32:46Z

Tbm: add another link

== Legal Issues using Linux in embedded projects ==
The intricacies of using the GPL license have been hashed out repeatedly in many
other forums. [references would be nice for major issues]

Here are some highlights:
=== Kernel is licensed GPL v2 only ===
The Linux kernel is licensed under the GNU General Public License, version 2.0 '''ONLY!'''

This is different from many other projects, which use the default wording in the license to allow GPL v2 or any later version.

This means it is unlikely that the kernel will switch to GPL version 3.0.

In September of 2006, a group of Linux kernel developers signed a [http://lwn.net/Articles/200422/ position statement] indicating that they objected to GPL version 3.0 (as then drafted). This further indicates the unlikelyhood of any
change of the kernel to the GPL v3 license.

=== Signed-off-by lines and the DCO ===
When developers contribute to the kernel, they must provide a "Signed-off-by" line, indicating that they acknowledge the licensing and declare the work (to the best of their knowledge) to be either original, or derivative of something compatible with GPL v2.

See the [[Developer Certificate Of Origin]] which is contained in the kernel's [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/SubmittingPatches Documentation/SubmittingPatches] file.

This page has a few specific issues relating to embedded use of Linux.

== EXPORT_SYMBOL_GPL ==
=== EXPORT_SYMBOL_GPL for kernel USB API ===
In January of 2008, Greg Kroah Hartman submitted a patch to change the core
USB API to EXPORT_SYMBOL_GPL. Here is some information about that change:

* [http://lwn.net/Articles/266724/ USB: mark USB drivers as being GPL only (LWN.net)]
* [http://www.linux-magazine.com/online/news/linux_2_6_25_without_closed_source_usb_drivers Linux 2.6.25 without Closed Source USB Drivers (Linux Magazine)]
* [http://www.linuxworld.com/community/?q=taxonomy/term/24 USB drivers going GPL-only in 2.6.25 (LinuxWorld)]
* [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=782e70c6fc2290a0395850e8e02583b8b62264d8 the actual git commit]

== Other Links ==

* http://gpl-violations.org/ - The gpl-violations.org project tries to resolve GPL violations and raises public awareness about GPL compliance.
* http://www.softwarefreedom.org/ - The Software Freedom Law Center provides legal representation for open source projects and publishes information on legal issues around open source.
* http://www.linuxfoundation.org/programs/legal/compliance - Linux Foundation's Open Compliance Program
* http://www.binaryanalysis.org/ - A binary analysis tool for GPL compliance investigations
* http://lwn.net/Articles/386280/ - LWN.net article about the binary analysis tool (published on 2010/05/06)
* http://fossology.org/ - FOSSology is a framework to scan open source code: it currently scans for copyright and license information and can easily be extended.

Developer Certificate Of Origin

2011-04-11T18:25:46Z

Tbm: update year

In May 2004, the kernel development community decided to standardize on
a requirement to adhere to a Developer Certificate of Origin for contributions
to the Linux kernel.

The text of the DCO is located in the file [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/SubmittingPatches Documentation/SubmittingPatches]
in the Linux kernel source tree.

The full text of the DCO version 1.1 (the current version as of 2011) is:

<pre>
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.
</pre>

There is a kernel thread discussing the original proposal from Linus
[http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=1YUY7-6fF-11%40gated-at.bofh.it&rnum=1&prev=/groups%3Fq%3Dg:thl3436074442d%26dq%3D%26hl%3Den%26lr%3D%26ie%3DUTF-8%26selm%3D1YUY7-6fF-11%2540gated-at.bofh.it here (google groups).] And
[http://marc.theaimsgroup.com/?l=linux-kernel&m=108529494402563&w=2 here (aimsgroup).]

Here is another article describing rationale for the 1.1 version:
[http://kerneltrap.org/node/5277 Clarifying the Developer's Certificate of Origin] KernelTrap, June 14, 2005

== Example ==
Here is an example Signed-off-by line, that indicates the submitter accepts the DCO:
<pre>
Signed-off-by: John Doe <john.doe@hisdomain.com>
</pre>

== Older versions ==

The original DCO, version 1.0, read:

<pre>
Developer's Certificate of Origin 1.0

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.
</pre>

[[Category:Categories]]

Legal Issues

2011-04-11T18:22:55Z

Tbm: add more links

== Legal Issues using Linux in embedded projects ==
The intricacies of using the GPL license have been hashed out repeatedly in many
other forums. [references would be nice for major issues]

Here are some highlights:
=== Kernel is licensed GPL v2 only ===
The Linux kernel is licensed under the GNU General Public License, version 2.0 '''ONLY!'''

This is different from many other projects, which use the default wording in the license to allow GPL v2 or any later version.

This means it is unlikely that the kernel will switch to GPL version 3.0.

In September of 2006, a group of Linux kernel developers signed a [http://lwn.net/Articles/200422/ position statement] indicating that they objected to GPL version 3.0 (as then drafted). This further indicates the unlikelyhood of any
change of the kernel to the GPL v3 license.

=== Signed-off-by lines and the DCO ===
When developers contribute to the kernel, they must provide a "Signed-off-by" line, indicating that they acknowledge the licensing and declare the work (to the best of their knowledge) to be either original, or derivative of something compatible with GPL v2.

See the [[Developer Certificate Of Origin]] which is contained in the kernel's [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/SubmittingPatches Documentation/SubmittingPatches] file.

This page has a few specific issues relating to embedded use of Linux.

== EXPORT_SYMBOL_GPL ==
=== EXPORT_SYMBOL_GPL for kernel USB API ===
In January of 2008, Greg Kroah Hartman submitted a patch to change the core
USB API to EXPORT_SYMBOL_GPL. Here is some information about that change:

* [http://lwn.net/Articles/266724/ USB: mark USB drivers as being GPL only (LWN.net)]
* [http://www.linux-magazine.com/online/news/linux_2_6_25_without_closed_source_usb_drivers Linux 2.6.25 without Closed Source USB Drivers (Linux Magazine)]
* [http://www.linuxworld.com/community/?q=taxonomy/term/24 USB drivers going GPL-only in 2.6.25 (LinuxWorld)]
* [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=782e70c6fc2290a0395850e8e02583b8b62264d8 the actual git commit]

== Other Links ==

* http://gpl-violations.org/ - The gpl-violations.org project tries to resolve GPL violations and raises public awareness about GPL compliance.
* http://www.softwarefreedom.org/ - The Software Freedom Law Center provides legal representation for open source projects and publishes information on legal issues around open source.
* http://www.binaryanalysis.org/ - A binary analysis tool for GPL compliance investigations
* http://lwn.net/Articles/386280/ - LWN.net article about the binary analysis tool (published on 2010/05/06)
* http://fossology.org/ - FOSSology is a framework to scan open source code: it currently scans for copyright and license information and can easily be extended.

Legal Issues

2011-04-11T18:16:28Z

Tbm: link to the actual article

== Legal Issues using Linux in embedded projects ==
The intricacies of using the GPL license have been hashed out repeatedly in many
other forums. [references would be nice for major issues]

Here are some highlights:
=== Kernel is licensed GPL v2 only ===
The Linux kernel is licensed under the GNU General Public License, version 2.0 '''ONLY!'''

This is different from many other projects, which use the default wording in the license to allow GPL v2 or any later version.

This means it is unlikely that the kernel will switch to GPL version 3.0.

In September of 2006, a group of Linux kernel developers signed a [http://lwn.net/Articles/200422/ position statement] indicating that they objected to GPL version 3.0 (as then drafted). This further indicates the unlikelyhood of any
change of the kernel to the GPL v3 license.

=== Signed-off-by lines and the DCO ===
When developers contribute to the kernel, they must provide a "Signed-off-by" line, indicating that they acknowledge the licensing and declare the work (to the best of their knowledge) to be either original, or derivative of something compatible with GPL v2.

See the [[Developer Certificate Of Origin]] which is contained in the kernel's [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/SubmittingPatches Documentation/SubmittingPatches] file.

This page has a few specific issues relating to embedded use of Linux.

== EXPORT_SYMBOL_GPL ==
=== EXPORT_SYMBOL_GPL for kernel USB API ===
In January of 2008, Greg Kroah Hartman submitted a patch to change the core
USB API to EXPORT_SYMBOL_GPL. Here is some information about that change:

* [http://lwn.net/Articles/266724/ USB: mark USB drivers as being GPL only (LWN.net)]
* [http://www.linux-magazine.com/online/news/linux_2_6_25_without_closed_source_usb_drivers Linux 2.6.25 without Closed Source USB Drivers (Linux Magazine)]
* [http://www.linuxworld.com/community/?q=taxonomy/term/24 USB drivers going GPL-only in 2.6.25 (LinuxWorld)]
* [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=782e70c6fc2290a0395850e8e02583b8b62264d8 the actual git commit]

== Other Links ==

* http://gpl-violations.org/ -
* http://lwn.net/Articles/386280/ - A binary analysis tool for GPL compliance investigations, LWN.net 2010/05/06