Ticket #3290 (closed task: fixed)

Opened 3 years ago

Last modified 3 years ago

GPL V3

Reported by: roidelapluie Owned by: asterix
Priority: high Milestone: 0.12
Component: None Version: hg
Severity: trivial Keywords: license, gpl v3, discussed
Cc: Blocked By:
OS: All Blocking:

Description

GPL V3 is now out, and we have to decide if we stay with GPL V2 or if we upgrade to GPL v3

 http://www.gnu.org/licenses/gpl-3.0.html

 http://www.gnu.org/licenses/rms-why-gplv3.html

If all the contributors are OK, we could upgrade SVN License to GPL V3.

Attachments

Change History

Changed 3 years ago by roidelapluie

Definitely, OK for me

Changed 3 years ago by roidelapluie

  • priority changed from normal to high
  • severity changed from major to trivial

Changed 3 years ago by roidelapluie

  • keywords license, added; licence, removed

Changed 3 years ago by steve-e

I agree on using the GPL-3 in gajim.

Roidelapluie, mind that all former devs have to agree (including everyone who has ever contributed any code to gajim). The problem occurs because gajim is licensed under „GPL v2“ and not „GPL v2 or later“.

Changed 3 years ago by patrys

If any part of my code was or ever will be merged into Gajim, I'm all for GPLv3

Changed 3 years ago by lukas@…

For those few bits I contributed yet or those I will contribute, GPLv3 is ok.

Changed 3 years ago by roidelapluie

  • type changed from enhancement to task

Changed 3 years ago by roidelapluie

  • keywords v3, discussed added; v3 removed

Changed 3 years ago by roidelapluie

Dimitur Kirov agrees :-)

[17:15:48] dkirov-real: about #3290: 
As a former contributor I agree to go on GPLv3

Changed 3 years ago by sb

From  http://www.gnu.org/licenses/rms-why-gplv3.html:

Change is unlikely to cease once GPLv3 is released. If new threats to users' freedom develop, we will have to develop GPL version 4. It is important to make sure that programs will have no trouble upgrading to GPLv4 when the time comes.

One way to do this is to release a program under “GPL version 3 or any later version”. Another way is for all the contributors to a program to state a proxy who can decide on upgrading to future GPL versions. The third way is for all the contributors to assign copyright to one designated copyright holder, who will be in a position to upgrade the license version. One way or another, programs should provide this flexibility for the future.

So under that condition I agree to change the license to "GPLv3 or any later version" (or maybe one of the other possibilities)

Changed 3 years ago by steve-e

Yes. Sounds good to switch to "GPLv3 or later".

When there is a GPLv4 one day and maybe problematic for gajim, we can switch to "GPLv3 only" without having to aks any former contributers.

Changed 3 years ago by nk

I agree to GPLv3 or later too

Changed 3 years ago by asterix

  • status changed from new to closed
  • resolution set to fixed

(In [2f9ac4d21015df93fe9c187e122346b552f282c4]) next release will be GPL v3. fixes #3290

Add/Change #3290 (GPL V3)

Author


E-mail address and user name can be saved in the Preferences.


Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Next status will be 'needinfo'
 
Note: See TracTickets for help on using tickets.