Licensing:SoftwareTypes

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (1 revision(s))
(Shareware)
Line 9: Line 9:
 
However, it is worth noting that some non-executable content exists that is required to make Open Source applications functional. An example of this would be open sourced game engines, such as Doom, Heretic, and Descent. These game engines come with freely distributable shareware gamedata files.
 
However, it is worth noting that some non-executable content exists that is required to make Open Source applications functional. An example of this would be open sourced game engines, such as Doom, Heretic, and Descent. These game engines come with freely distributable shareware gamedata files.
  
In this case, the gamedata files can be packaged and included in Fedora, as long as the files meet the requirements for [[BinaryFirmware| binary firmware]] .
+
In this case, the gamedata files can be packaged and included in Fedora, as long as the files meet the requirements for [https://fedoraproject.org/wiki/Packaging/LicensingGuidelines#Binary_Firmware| binary firmware] .
  
 
{{Anchor|LegalPatents}}
 
{{Anchor|LegalPatents}}
 +
 
=== Patented Software ===
 
=== Patented Software ===
  

Revision as of 21:13, 16 December 2008

Contents

Software Types

There are some specific software types worth mentioning from a licensing/legal perspective.

Shareware

Shareware applications are not Open Source code, and are not acceptable for Fedora.

However, it is worth noting that some non-executable content exists that is required to make Open Source applications functional. An example of this would be open sourced game engines, such as Doom, Heretic, and Descent. These game engines come with freely distributable shareware gamedata files.

In this case, the gamedata files can be packaged and included in Fedora, as long as the files meet the requirements for binary firmware .

Patented Software

If a package contains code covered by known patents, then you should seek a written patent grant (and include that grant inside the package) before submitting it for Fedora. This is especially important for GPL/LGPL licensed packages, because of the following clause (from GPLv2):

For example, if a patent license would not permit royalty-free redistribution
of the Program by all those who receive copies directly or indirectly through you,
then the only way you could satisfy both it and this License would be to refrain
entirely from distribution of the Program.

It isn't safe to assume that the patent holder permits royalty-free redistribution, you need to get it in writing.

Emulators

Most emulators (applications which emulate another platform) are not permitted for inclusion in Fedora. The rule of thumb to follow is: If it requires ROMs (or image files in any format) of copyrighted or patented material to be useful (and the owners of those copyrights and patents have not given their express written permission), then it's not permitted.

Binary Firmware

Some applications and drivers require binary-only firmware to function. Fedora permits inclusion of these files as long as they meet the following requirements:

Requirements:

  • The files are non-executable (note: this means that the files cannot run on their own, not that they are just chmod -x)
  • The files are not libraries.
  • The files are standalone, not embedded in executable or library code.
  • Explicit permission is given by the owner to freely redistribute without restrictions (this permission must be included, in "writing", with the files in the packaging)
  • The files must be necessary for the functionality of open source code being included in Fedora.

If you are unsure whether or not your files meet these requirements, ask on fedora-devel-list, and we will examine them for you.

The License tag for any firmware that disallows modification must be set to: "Redistributable, no modification permitted"

Firmware packages must be named <foo>-firmware, where <foo> is the driver or other hardware component that the firmware is for.