European Union Public Licence

Last updated

European Union Public Licence
Logo EUPL.svg
Author European Commission
Latest version1.2
Publisher European Union
PublishedJanuary 2007 (v 1.0), May 2017 (v 1.2)
SPDX identifierEUPL-1.0, EUPL-1.1
Debian FSG compatible Yes [1]
FSF approved Yes [2] [3]
OSI approved Yes [4]
GPL compatible Yes, by licensing derivatives that include GPL covered code [2] [3]
Copyleft Yes [2] [3]
Linking from code with a different licence Yes, as it depends on the applicable copyright law in the European Union country where the Licensor resides or has his or her registered office for defining what qualifies as a derivative work. [5]
Website joinup.ec.europa.eu/page/eupl-guidelines-faq-infographics OOjs UI icon edit-ltr-progressive.svg

The European Union Public Licence (EUPL) is a free software licence that was written and approved by the European Commission. The licence is available in 23 official languages of the European Union. All linguistic versions have the same validity. Its latest version, EUPL v1.2, was published in May 2017. Revised documentation for v1.2 was issued in late‑2021. [6]

Contents

Software, mainly produced by European administrations, has been licensed under the EUPL [7] since the launch of the European Open Source Observatory and Repository (OSOR) in October 2008, now part of Joinup collaborative platform. [8]

History

EUPL was originally intended to be used for the distribution of software developed in the framework of the IDABC programme, [9] given its generic scope it was also suitable for use by any software developer. Its main goal is its focusing on being consistent with the copyright law in the Member States of the European Union, while retaining compatibility with popular free software licences such as the GNU General Public License. The first IDABC software packages mentioned are CIRCA groupware, [10] IPM [11] [12] and the eLink [13] G2G, G2C, G2B specification software.

Comparison to other open source/free software licences

EUPL is the first open source licence to be released by an international governing body. A goal of this licence is to create an open-source licence available into 23 official languages of the European Union, [14] and that is sure to conform to the existing copyright laws of the Member States of the European Union.

The licence was developed with other open-source licences in mind and specifically authorizes covered works to be re-released under the following licences, when combined with their covered code in larger works:

Explicit license compatibilityAdded in version
GNU General Public License (GPL) v. 2 & v. 3GPL v3 added in EUPL v1.2
Open Software License (OSL) v. 2.1, v. 3.0EUPL v1.0
Common Public License v. 1.0EUPL v1.0
Eclipse Public License v. 1.0EUPL v1.0
CeCILL v. 2.0 & V 2.1EUPL v1.0
Mozilla Public License v. 2EUPL v1.2
LGPL v2.1 & V3EUPL v1.2
LiLIQ-R & LiLIQ-R+ EUPL v1.2
GNU Affero General Public License (AGPL) v. 3EUPL v1.2

Many other OSI-approved licences are compatible with the EUPL: JOINUP publish a general compatibility matrix between all OSI-approved licences and the EUPL. [15]

An overview of the EUPL licence and on what makes it different has been published in OSS-Watch. [16]

In 2020, the European Commission publishes its Joinup Licensing Assistant, [17] which makes possible the selection and comparison of more than 50 licences, with access to their SPDX identifier and full text.

Versions

EUPL v1.0 was approved on 9 January 2007. [18]

EUPL v1.1 was approved by the European Commission on 9 January 2009. EUPL v1.1 is OSI certified as from March 2009. [19]

EUPL v1.2 was published in May 2017. [20] EUPL v1.2 is OSI certified in July 2017. [21]

Version 1.2

The EUPL v1.2 was prepared as from June 2013 [22] its decision process started in 2016 and [23] released on 19 May 2017. A principal objective of the EUPL v1.2 is to update the appendix of compatible licences to cover newer popular licences such as the GNU GPLv3 and AGPLv3. [23]

According to the EUPL v.1.1, the European Commission may publish other linguistic versions and/or new versions of the EUPL, so far this is required and reasonable, without reducing the scope of the rights granted by the Licence. Future upgrades will not be applicable automatically when software was expressly released "under the EUPL v.1.1 only". [24]

New provisions cover the Application service provider loophole of software distribution: Distribution and/or Communication (of software) includes providing on-line "access to its essential functionalities". [25]

A specificity of the EUPL v1.2 is that, at the contrary of the GPL, it is compatible with all other reciprocal licenses listed in the EUPL appendix. Compatibility means that after merging the covered code with code covered by a compatible license, the resulting (combined) derivative work can be distributed under the compatible license.

Another specificity of the EUPL is that it is interoperable, without any "viral effect" in case of static and dynamic linking. [26] This currently depends on European and national law, according to the Computer Programs Directive (Directive 91/250 EEC or 2009/24). Recital 10 of this Directive defines interoperability and recital 15 states that for making two programs interoperable, the code needed can be copied, translated or adapted. For example take program A (new original code just written) and program B (a program licensed by a third party), the developer/licensor of A, who is also a legitimate holder or recipient of B may reproduce in A the needed code from B (e.g. the APIs or the needed data structures from program B) without copyright infringement and without authorization from the copyright holder of B. The licensor of A can do and distribute this without being bonded by conditions or limitations imposed by a licence of program B. This must stay compatible with the normal use of program B and cannot prejudice the legitimate interest of the copyright holder of B.

Unlike the "articles", the directive "recitals" are not transposed as such in national laws. However, recitals are part of European law: they are serving for understanding the scope and rationale of the law, and will be used by the court for interpreting the law, as the case may be. While recitals in EU Directives and Regulations are not considered to have independent legal value, they can expand an ambiguous provision's scope. They cannot restrict an unambiguous provision's scope, but they can be used to determine the nature of a provision, or to adapt it to new circumstances.

Interoperability

It is important to make a distinction between the various flavours of the “Strong Copyleft” concept. According to the GPL/AGPL licensor vision, this means some restrictions and conditions regarding interoperability (due to the theory that linking other software with the covered code creates a combined derivative) and regarding compatibility (since no derivative could be licensed under another license, which may create incompatibilities). The EUPL vision that is depending on the EU law is all the contrary: linking makes no derivatives and when merging source code licensed differently is a necessity, the resulting derivative can be licensed under a compatible license. For some of those, the copyleft is known to be “weaker” (i.e. the MPL), but this has no impact because according to the EUPL the compatible license will prevail when its provisions conflict with those of the EUPL. Since none of the compatible license prohibits the strong reciprocity implemented by the EUPL (obligation to publish and share the source code of derivatives, even distributed through a network) the copyleft resulting from the EUPL can be considered as strong. For this reason, the German lawyer Niklas Plutte created for the EUPL the new category of "Interoperable copyleft licence". [27]

Philosophy

In November 2023, a discussion paper, "The seven pillars of wisdom", published in the framework of the adoption of the Interoperable Europe Act, was proposed for discussion by the writing author of the EUPL-1.2 and explains the philosophy behind the EUPL text. [28]

Member states policies

As from 2010, EU member states adopt or revise policies aimed to encourage – when appropriate – the open source distribution of public sector applications. The EUPL is formally mentioned in some of these policies:

See also

Related Research Articles

The MIT License is a permissive software license originating at the Massachusetts Institute of Technology (MIT) in the late 1980s. As a permissive license, it puts very few restrictions on reuse and therefore has high license compatibility.

<span class="mw-page-title-main">Open-source license</span> Software license allowing source code to be used, modified, and shared

Open-source licenses are software licenses that allow content to be used, modified, and shared. They facilitate free and open-source software (FOSS) development. Intellectual property (IP) laws restrict the modification and sharing of creative works. Free and open-source licenses use these existing legal structures for an inverse purpose. They grant the recipient the rights to use the software, examine the source code, modify it, and distribute the modifications. These criteria are outlined in the Open Source Definition.

<span class="mw-page-title-main">Apache License</span> Free software license

The Apache License is a permissive free software license written by the Apache Software Foundation (ASF). It allows users to use the software for any purpose, to distribute it, to modify it, and to distribute modified versions of the software under the terms of the license, without concern for royalties. The ASF and its projects release their software products under the Apache License. The license is also used by many non-ASF projects.

<span class="mw-page-title-main">Free and open-source software</span> Software whose source code is available and which is permissively licensed

Free and open-source software (FOSS) is software that is available under a license that grants the right to use, modify, and distribute the software, modified or not, to everyone free of charge. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. FOSS is in contrast to proprietary software, where the software is under restrictive copyright or licensing and the source code is hidden from the users.

A permissive software license, sometimes also called BSD-like or BSD-style license, is a free-software license which instead of copyleft protections, carries only minimal restrictions on how the software can be used, modified, and redistributed, usually including a warranty disclaimer. Examples include the GNU All-permissive License, MIT License, BSD licenses, Apple Public Source License and Apache license. As of 2016, the most popular free-software license is the permissive MIT license.

<span class="mw-page-title-main">Eclipse Public License</span> Free software license similar to the Common Public License

The Eclipse Public License (EPL) is a free and open source software license most notably used for the Eclipse IDE and other projects by the Eclipse Foundation. It replaces the Common Public License (CPL) and removes certain terms relating to litigations related to patents.

This comparison only covers software licenses which have a linked Wikipedia article for details and which are approved by at least one of the following expert groups: the Free Software Foundation, the Open Source Initiative, the Debian Project and the Fedora Project. For a list of licenses not specifically intended for software, see List of free-content licences.

<span class="mw-page-title-main">WTFPL</span> Permissive free software license

The WTFPL is a permissive free software license. As a public domain like license, the WTFPL is essentially the same as dedication to the public domain. It allows redistribution and modification of the work under any terms. The name is an abbreviation of Do What The Fuck You Want To Public License.

License proliferation is the phenomenon of an abundance of already existing and the continued creation of new software licenses for software and software packages in the FOSS ecosystem. License proliferation affects the whole FOSS ecosystem negatively by the burden of increasingly complex license selection, license interaction, and license compatibility considerations.

License compatibility is a legal framework that allows for pieces of software with different software licenses to be distributed together. The need for such a framework arises because the different licenses can contain contradictory requirements, rendering it impossible to legally combine source code from separately-licensed software in order to create and publish a new program. Proprietary licenses are generally program-specific and incompatible; authors must negotiate to combine code. Copyleft licenses are commonly deliberately incompatible with proprietary licenses, in order to prevent copyleft software from being re-licensed under a proprietary license, turning it into proprietary software. Many copyleft licenses explicitly allow relicensing under some other copyleft licenses. Permissive licenses are compatible with everything, including proprietary licenses; there is thus no guarantee that all derived works will remain under a permissive license.

<span class="mw-page-title-main">GNU Affero General Public License</span> Free software license published by Affero, Inc.

The GNU Affero General Public License is a free, copyleft license published by the Free Software Foundation in November 2007, and based on the GNU GPL version 3 and the Affero General Public License (non-GNU).

<span class="mw-page-title-main">Free-software license</span> License allowing software modification and redistribution

A free-software license is a notice that grants the recipient of a piece of software extensive rights to modify and redistribute that software. These actions are usually prohibited by copyright law, but the rights-holder of a piece of software can remove these restrictions by accompanying the software with a software license which grants the recipient these rights. Software using such a license is free software as conferred by the copyright holder. Free-software licenses are applied to software in source code and also binary object-code form, as the copyright law recognizes both forms.

BSD licenses are a family of permissive free software licenses, imposing minimal restrictions on the use and distribution of covered software. This is in contrast to copyleft licenses, which have share-alike requirements. The original BSD license was used for its namesake, the Berkeley Software Distribution (BSD), a Unix-like operating system. The original version has since been revised, and its descendants are referred to as modified BSD licenses.

<span class="mw-page-title-main">Copyleft</span> Practice of mandating free use in all derivatives of a work

Copyleft is the legal technique of granting certain freedoms over copies of copyrighted works with the requirement that the same rights be preserved in derivative works. In this sense, freedoms refers to the use of the work for any purpose, and the ability to modify, copy, share, and redistribute the work, with or without a fee. Licenses which implement copyleft can be used to maintain copyright conditions for works ranging from computer software, to documents, art, scientific discoveries and even certain patents.

<span class="mw-page-title-main">GNU General Public License</span> Series of free software licenses

The GNU General Public License is a series of widely used free software licenses or copyleft that guarantee end users the four freedoms to run, study, share, and modify the software. The license was the first copyleft for general use and was originally written by Richard Stallman, the founder of the Free Software Foundation (FSF), for the GNU Project. The license grants the recipients of a computer program the rights of the Free Software Definition. The licenses in the GPL series are all copyleft licenses, which means that any derivative work must be distributed under the same or equivalent license terms. It is more restrictive than the Lesser General Public License and even further distinct from the more widely used permissive software licenses BSD, MIT, and Apache.

A free license or open license is a license which allows others to reuse another creator’s work as they wish. Without a special license, these uses are normally prohibited by copyright, patent or commercial license. Most free licenses are worldwide, royalty-free, non-exclusive, and perpetual. Free licenses are often the basis of crowdsourcing and crowdfunding projects.

A public license or public copyright licenses is a license by which a copyright holder as licensor can grant additional copyright permissions to any and all persons in the general public as licensees. By applying a public license to a work, provided that the licensees obey the terms and conditions of the license, copyright holders give permission for others to copy or change their work in ways that would otherwise infringe copyright law.

<span class="mw-page-title-main">Joinup</span> Type of collaboration platform

Joinup is a collaboration platform created by the European Commission. It is funded by the European Union via its Interoperability Solutions for Public Administrations Programme.

On April 21, 2021 data.europa.eu was launched as a single access point for open data published by EU Institutions, national portals of EU Member states and non-member states, as well as international organisations of predominantly European scope. The portal consolidates datasets previously available via the EU Open Data Portal and the European Data Portal into a single meta-catalogue. The European Data Portal, launched in its beta version on November 16, 2015, was an initiative of the European Commission, and part of the Digital Single Market.

Software relicensing is applied in open-source software development when software licenses of software modules are incompatible and are required to be compatible for a greater combined work. Licenses applied to software as copyrightable works, in source code as binary form, can contain contradictory clauses. These requirements can make it impossible to combine source code or content of several software works to create a new combined one.

References

  1. ↑ "ausweisapp2 in Debian Package Tracker". Debian Package Tracker. Retrieved 3 January 2020.
  2. 1 2 3 Donald Robertson (26 June 2018). "European Union Public License v. 1.2 added to license list". Free Software Foundation. Retrieved 2 August 2018.
  3. 1 2 3 "Various Licenses and Comments about Them". The GNU Operating System and the Free Software Movement. 26 June 2018. Retrieved 2 August 2018.
  4. ↑ OSI approval published on Joinup
  5. ↑ "EUPL 1.1" (PDF).
  6. ↑ Schmitz, Patrice-Emmanuel (30 September 2021). European Union Public Licence (EUPL) Guidelines July 2021 — NO-08-21-281-EN-N. Brussels, Belgium: Directorate-General for Informatics, European Commission. doi:10.2799/77160. ISBN   978-92-76-41527-5. Landing page .
  7. ↑ "Joinup forge". Archived from the original on 2016-04-04. Retrieved 2016-04-04.
  8. ↑ "Osor.eu migration". Archived from the original on 2012-06-10. Retrieved 2012-06-13.
  9. ↑ Overview of the IDABC project.
  10. ↑ CIRCA groupware
  11. ↑ IPM technical architecture
  12. ↑ IPM EUPL
  13. ↑ eLink
  14. ↑ - European Union Public License [ permanent dead link ]
  15. ↑ Matrix of EUPL compatible licences
  16. ↑ The EUPL - An Overview by Rowan Wilson, last updated 9 September 2012 (EUPL v1.1 only)
  17. ↑ "Joinup Licensing Assistant" . Retrieved 31 March 2020.
  18. ↑ EUPL v1.0 was published on 9 January 2007
  19. ↑ "Introduction to the EUPL licence | Joinup". joinup.ec.europa.eu. Retrieved 2017-11-20.
  20. ↑ "Commission Implementing Decision (EU) 2017/863".
  21. ↑ "Introduction to the EUPL licence | Joinup". joinup.ec.europa.eu. Retrieved 2017-11-20.
  22. ↑ "Public Consultation on the draft EUPL v 1.2 has been fruitful". 20 March 2013. Retrieved 3 December 2015.
  23. 1 2 "Public Consultation on the draft EUPL v1.2". Archived from the original on 24 December 2015. Retrieved 3 December 2015.
  24. ↑ "Understanding the EUPL v1.2 | Joinup". Archived from the original on 2017-12-01. Retrieved 2017-11-27.
  25. ↑ See Article 1 of the EUPL 1.2 last subpoint, definition of ‘Distribution’ and ‘Communication’.
  26. ↑ License compatibility in the case of static and dynamic linking.
  27. ↑ "Open Source Software Recht: Große FAQ mit vielen Praxistipps". 10 November 2019. Retrieved 31 March 2020.
  28. ↑ Schmitz, Patrice-Emmanuel (23 November 2023). "The seven pillars of wisdom" (PDF). Joinup . Retrieved 25 March 2024.
  29. ↑ Schmitz, Patrice-Emmanuel (3 December 2021). "The EUPL is a 'Legal Licence' in France". Joinup . Retrieved 6 December 2021.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.