Project License - Revision history

Lcc at 20:38, 7 February 2012

2012-02-07T20:38:39Z

Daleathan: /* 3rd Party Addon License */ 3.3

2011-09-28T02:04:27Z

‎3rd Party Addon License: 3.3

Daleathan: get to the point

2011-09-28T02:03:27Z

get to the point

Romjerome at 09:45, 27 June 2010

2010-06-27T09:45:52Z

Pez4brian: Fix statement about switching to AGPL

2009-12-10T14:05:25Z

Fix statement about switching to AGPL

Dsblank: /* 3rd Party Addon License */

2009-12-10T11:54:25Z

‎3rd Party Addon License

Dsblank: /* Official Gramps Project License */ clarification

2009-12-10T11:45:44Z

‎Official Gramps Project License: clarification

Dsblank: /* Network Usage */ typo and clarification

2009-12-10T11:11:31Z

‎Network Usage: typo and clarification

Pez4brian: New page: == Official Gramps Project License == The Gramps project source files are released under the "GPLv2 or later" license. The Gramps team wishes to promote reuse and openness of the Gramps co...

2009-12-10T05:04:12Z

New page: == Official Gramps Project License == The Gramps project source files are released under the "GPLv2 or later" license. The Gramps team wishes to promote reuse and openness of the Gramps co...

New page

== Official Gramps Project License ==
The Gramps project source files are released under the "GPLv2 or later" license. The Gramps team wishes to promote reuse and openness of the Gramps codebase with other projects. The "GPLv2 or later" license was chosen because it is the most compatible with the other GNU licenses. The Gramps source code can be combined with code from other projects as long as the resulting code is used in a way that is compatible with both licenses. See the [http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility| GNU license compatibility table] for more information about license compatibility.

== 3rd Party Addon License ==
Gramps makes no requirement that 3rd party addons use the same license as the code in the official Gramps repository. However, addon authors should be aware of how their selection of license may empower or limit the use of their code in the future.

== Project License Implications ==
This section provides some examples of how the Gramps source code can be used. These use cases demonstrate implications that result from the Gramps Project License.

==== 3rd Party Addon Promotions ====
If a 3rd party addon becomes popular, it may be advantageous to add it to the official source repository for distribution with the core code. However, in order for the addon to be distributed with the core source code, the addon must already be released under the "GPLv2 or later" license.

==== Network Usage ====
It seems likely that in the near future it will be possible to use Gramps over the Internet as a web application. When this functionality is available, it would be possible for a person or organization to host the source code on their own server, make changes to the source code, and never contribute those changes back to the project. This type of use is allowed by GPLv2, and as long as that person is using Gramps is a way that is compatible with GPLv2, they are allowed to keep their source code changes.

Some people may see this possibility as a disadvantage because there is a risk that someone will use the code to their advantage and never contribute back. The Gramps project contributors are aware of the risk and if it were ever to become a problem, the project could choose to exercise the "or later" part of the license and release under AGPL or some other more restrictive license.

== Will Gramps Ever Change to GPLv3? ==
Because the Gramps Project License is "GPLv2 or later", the project has the option at any time to start releasing code under "GPLv3" or "GPLv3 or later". The topic comes up from time to time, but there are no plans at this time to change the license.

← Older revision		Revision as of 20:38, 7 February 2012
Line 1:		Line 1:
−	Gramps is released under the [http://www.gnu.org/licenses/old-licenses/gpl-2.0.html GNU General Public License, version 2] (GPLv2) or later license	+	Gramps is released under the [http://www.gnu.org/licenses/old-licenses/gpl-2.0.html GNU General Public License, version 2] (GPLv2) or later license.

	== Official Gramps Project License ==		== Official Gramps Project License ==

@@ Line 5: / Line 5: @@
 == 3rd Party Addon License ==
-Gramps makes no requirement that [[3.2_Addons|3rd party addons]] use the same license as the code in the official Gramps repository. However, addon authors should be aware of how their selection of license may empower or limit the use of their code in the future.
+Gramps makes no requirement that [[3.3_Addons|3rd party addons]] use the same license as the code in the official Gramps repository. However, addon authors should be aware of how their selection of license may empower or limit the use of their code in the future.
 == Project License Implications ==

← Older revision		Revision as of 02:03, 28 September 2011
Line 1:		Line 1:
		+	Gramps is released under the [http://www.gnu.org/licenses/old-licenses/gpl-2.0.html GNU General Public License, version 2] (GPLv2) or later license
		+
	== Official Gramps Project License ==		== Official Gramps Project License ==
	The Gramps project source files are released under the [http://www.gnu.org/licenses/old-licenses/gpl-2.0.html GNU General Public License, version 2] (GPLv2) or later license. The Gramps team wishes to promote reuse and openness of the Gramps codebase with other projects. The "GPLv2 or later" license was chosen because it is the most compatible with the other GNU licenses. The Gramps source code can be combined with code from other projects as long as the resulting code is used in a way that is compatible with both licenses. See the [http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility\| GNU license compatibility table] for more information about license compatibility.		The Gramps project source files are released under the [http://www.gnu.org/licenses/old-licenses/gpl-2.0.html GNU General Public License, version 2] (GPLv2) or later license. The Gramps team wishes to promote reuse and openness of the Gramps codebase with other projects. The "GPLv2 or later" license was chosen because it is the most compatible with the other GNU licenses. The Gramps source code can be combined with code from other projects as long as the resulting code is used in a way that is compatible with both licenses. See the [http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility\| GNU license compatibility table] for more information about license compatibility.

← Older revision		Revision as of 09:45, 27 June 2010
Line 18:		Line 18:
	== Will Gramps Ever Change to GPLv3? ==		== Will Gramps Ever Change to GPLv3? ==
	Because the Gramps Project License is "GPLv2 or later", the project has the option at any time to start releasing code under "GPLv3" or "GPLv3 or later". The topic comes up from time to time, but there are no plans at this time to change the license.		Because the Gramps Project License is "GPLv2 or later", the project has the option at any time to start releasing code under "GPLv3" or "GPLv3 or later". The topic comes up from time to time, but there are no plans at this time to change the license.
		+
		+	[[Category:Developers/Reference]]
		+	[[Category:Developers/General]]

@@ Line 14: / Line 14: @@
 It seems likely that in the near future it will be possible to use Gramps over the Internet as a web application. When this functionality is available, it would be possible for a person or organization to host the source code on their own server, make changes to the source code, and never contribute those changes back to the project. This type of use is allowed by GPLv2, and as long as that person is using Gramps in a way that is compatible with GPLv2, they are allowed to keep their source code changes.
-Some people may see this possibility as a disadvantage because there is a risk that someone will use the code to their advantage and never contribute back. The Gramps project contributors are aware of the risk and if it were ever to become a problem, the project could choose to exercise the "or later" part of the license and release Gramps under the [http://www.fsf.org/licensing/licenses/agpl-3.0.html Affero GPL] or some other more restrictive license.
+Some people may see this possibility as a disadvantage because there is a risk that someone will use the code to their advantage and never contribute back. The Gramps project contributors are aware of the risk and if it were ever to become a problem, the project could re-release Gramps under the [http://www.fsf.org/licensing/licenses/agpl-3.0.html Affero GPL] or some other more restrictive license. However, this would require agreement among all contributors.
 == Will Gramps Ever Change to GPLv3? ==
 Because the Gramps Project License is "GPLv2 or later", the project has the option at any time to start releasing code under "GPLv3" or "GPLv3 or later". The topic comes up from time to time, but there are no plans at this time to change the license.

@@ Line 1: / Line 1: @@
 == Official Gramps Project License ==
-The Gramps project source files are released under the "GPLv2 or later" license. The Gramps team wishes to promote reuse and openness of the Gramps codebase with other projects. The "GPLv2 or later" license was chosen because it is the most compatible with the other GNU licenses. The Gramps source code can be combined with code from other projects as long as the resulting code is used in a way that is compatible with both licenses. See the [http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility| GNU license compatibility table] for more information about license compatibility.
+The Gramps project source files are released under the [http://www.gnu.org/licenses/old-licenses/gpl-2.0.html GNU General Public License, version 2] (GPLv2) or later license. The Gramps team wishes to promote reuse and openness of the Gramps codebase with other projects. The "GPLv2 or later" license was chosen because it is the most compatible with the other GNU licenses. The Gramps source code can be combined with code from other projects as long as the resulting code is used in a way that is compatible with both licenses. See the [http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility| GNU license compatibility table] for more information about license compatibility.
 == 3rd Party Addon License ==