Re: Relicensing Nautilus to GPLv3+

2017-05-25 Thread Carlos Soriano via desktop-devel-list
Thanks Michael, looks interesting and seems there are enough reasons to upgrade 
files too.
We can take a look after we "assume" the project license is gpl3+ and no 
problem arises.

Best,
Carlos Soriano

 Original Message 
Subject: Re: Relicensing Nautilus to GPLv3+
Local Time: May 25, 2017 2:07 PM
UTC Time: May 25, 2017 12:07 PM
From: mike.catanz...@gmail.com
To: Carlos Soriano 
Sébastien Wilmet , desktop-devel-list@gnome.org 


On Thu, May 25, 2017 at 5:10 AM, Carlos Soriano via desktop-devel-list
 wrote:
> Aha!
> I still get different opinions from different people on that. But
> that makes sense to me. Probably makes sense to relicense the files
> too at some point, but that would be a later decision.
> Do you know any advantage of relicensing the files themselves?
>
> Best,
> Carlos Soriano

The advantages of relicensing are:

* Easier to copy code into Nautilus from other GNOME projects. You
cannot currently copy code into Nautilus from the handful of projects
that have already transitioned to GPLv3+.
* Less confusion. It's confusing for the project license to be GPLv3+
while nearly all of the source code is licensed GPLv2+.
* Promote stronger, more effective copyleft. Many people believe GPLv3
is a better license than GPLv2. See [1].

This is why I've relicensed all the source files in Epiphany.

The disadvantage is that after relicensing, it will become harder to
copy code from Nautilus into other GNOME projects. You cannot copy into
GPLv2+ projects unless you relicense the other project to GPLv3+ or go
back in the commit history to before the relicensing. This is only a
transition problem, because it can be solved by upgrading the license
of the other project.

Michael

[1] https://www.gnu.org/licenses/rms-why-gplv3.en.html___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Relicensing Nautilus to GPLv3+

2017-05-25 Thread Carlos Soriano via desktop-devel-list
The project, not everyfile. It's more like accepting that Nautilus is gpl3+ now 
since some files are gpl3+ already. That's what I mean by re licensing.

Best,
Carlos Soriano

 Original Message 
Subject: Re: Relicensing Nautilus to GPLv3+
Local Time: May 25, 2017 12:36 PM
UTC Time: May 25, 2017 10:36 AM
From: swil...@gnome.org
To: Carlos Soriano 
desktop-devel-list@gnome.org 

On Thu, May 25, 2017 at 06:10:56AM -0400, Carlos Soriano wrote:
> I still get different opinions from different people on that. But that
> makes sense to me. Probably makes sense to relicense the files too at
> some point, but that would be a later decision.
> Do you know any advantage of relicensing the files themselves?

Well, I thought you wanted to license Nautilus as GPLv3+, that's the
topic of this thread…

See:
https://www.gnu.org/licenses/gpl-faq.html#v3HowToUpgrade

--
Sébastien___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Relicensing Nautilus to GPLv3+

2017-05-25 Thread Michael Catanzaro
On Thu, May 25, 2017 at 5:10 AM, Carlos Soriano via desktop-devel-list 
 wrote:

Aha!
I still get different opinions from different people on that. But 
that makes sense to me. Probably makes sense to relicense the files 
too at some point, but that would be a later decision.

Do you know any advantage of relicensing the files themselves?

Best,
Carlos Soriano


The advantages of relicensing are:

* Easier to copy code into Nautilus from other GNOME projects. You 
cannot currently copy code into Nautilus from the handful of projects 
that have already transitioned to GPLv3+.
* Less confusion. It's confusing for the project license to be GPLv3+ 
while nearly all of the source code is licensed GPLv2+.
* Promote stronger, more effective copyleft. Many people believe GPLv3 
is a better license than GPLv2. See [1].


This is why I've relicensed all the source files in Epiphany.

The disadvantage is that after relicensing, it will become harder to 
copy code from Nautilus into other GNOME projects. You cannot copy into 
GPLv2+ projects unless you relicense the other project to GPLv3+ or go 
back in the commit history to before the relicensing. This is only a 
transition problem, because it can be solved by upgrading the license 
of the other project.


Michael

[1] https://www.gnu.org/licenses/rms-why-gplv3.en.html

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: Relicensing Nautilus to GPLv3+

2017-05-25 Thread Sébastien Wilmet
On Thu, May 25, 2017 at 06:10:56AM -0400, Carlos Soriano wrote:
> I still get different opinions from different people on that. But that
> makes sense to me. Probably makes sense to relicense the files too at
> some point, but that would be a later decision.
> Do you know any advantage of relicensing the files themselves?

Well, I thought you wanted to license Nautilus as GPLv3+, that's the
topic of this thread…

See:
https://www.gnu.org/licenses/gpl-faq.html#v3HowToUpgrade

--
Sébastien
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Relicensing Nautilus to GPLv3+

2017-05-25 Thread Carlos Soriano via desktop-devel-list
Aha!
I still get different opinions from different people on that. But that makes 
sense to me. Probably makes sense to relicense the files too at some point, but 
that would be a later decision.
Do you know any advantage of relicensing the files themselves?

Best,
Carlos Soriano

 Original Message 
Subject: Re: Relicensing Nautilus to GPLv3+
Local Time: May 25, 2017 12:08 PM
UTC Time: May 25, 2017 10:08 AM
From: swil...@gnome.org
To: Carlos Soriano 
desktop-devel-list@gnome.org 

On Thu, May 25, 2017 at 05:59:02AM -0400, Carlos Soriano wrote:
> For now we won't relicense the files, since that would require
> copyright holders to agree (iiuc). Instead is the project that will
> become GPL3+, since the combination of GPL2+ + GPL3+ files results in
> a project that is GPL3+.

For the files licensed as GPLv2+, the copyright holders have already
agreed with "any later version", so you can directly relicense to GPLv3+
without asking the permission to each copyright holder.

For LGPL -> GPL, you need the explicit approval of all copyright
holders.

--
Sébastien
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Relicensing Nautilus to GPLv3+

2017-05-25 Thread Sébastien Wilmet
On Thu, May 25, 2017 at 05:59:02AM -0400, Carlos Soriano wrote:
> For now we won't relicense the files, since that would require
> copyright holders to agree (iiuc). Instead is the project that will
> become GPL3+, since the combination of GPL2+ + GPL3+ files results in
> a project that is GPL3+.

For the files licensed as GPLv2+, the copyright holders have already
agreed with "any later version", so you can directly relicense to GPLv3+
without asking the permission to each copyright holder.

For LGPL -> GPL, you need the explicit approval of all copyright
holders.

--
Sébastien
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: Relicensing Nautilus to GPLv3+

2017-05-25 Thread Carlos Soriano via desktop-devel-list
Thanks Sebastien!

For now we won't relicense the files, since that would require copyright 
holders to agree (iiuc). Instead is the project that will become GPL3+, since 
the combination of GPL2+ + GPL3+ files results in a project that is GPL3+.

Best,
Carlos Soriano

 Original Message 
Subject: Re: Relicensing Nautilus to GPLv3+
Local Time: May 25, 2017 11:55 AM
UTC Time: May 25, 2017 9:55 AM
From: swil...@gnome.org
To: desktop-devel-list@gnome.org

Hi,

Just to mention that I've written two scripts that ease changing license
headers:
- gcu-multi-line-substitution
- gcu-smart-c-comment-substitution

available at:
https://github.com/swilmet/gnome-c-utils

Cheers,
Sébastien
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Relicensing Nautilus to GPLv3+

2017-05-25 Thread Sébastien Wilmet
Hi,

Just to mention that I've written two scripts that ease changing license
headers:
- gcu-multi-line-substitution
- gcu-smart-c-comment-substitution

available at:
https://github.com/swilmet/gnome-c-utils

Cheers,
Sébastien
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list