Hi all,
Just FYI, I intend to relicense fontpackages from LGPL3+ to GPL3+, to make sharing parts with go-macros easier.
Since fontpackages only contains templates and scripts and is not linked anywhere there is no practical difference.
If you see a problem with this change, or have contributed to fontpackages to the past and do not like this change, please say so now.
Regards,
Hi,
On Sun, Oct 28, 2018 at 9:14 PM Nicolas Mailhot nicolas.mailhot@laposte.net wrote:
Hi all,
Just FYI, I intend to relicense fontpackages from LGPL3+ to GPL3+, to make sharing parts with go-macros easier.
Can it be possible for you to explain this further? I want to understand how license change can help here.
Since fontpackages only contains templates and scripts and is not linked anywhere there is no practical difference.
If you see a problem with this change, or have contributed to fontpackages to the past and do not like this change, please say so now.
Regards,
-- Nicolas Mailhot
Parag.
Le mardi 30 octobre 2018 à 11:47 +0530, Parag Nemade a écrit :
Hi,
On Sun, Oct 28, 2018 at 9:14 PM Nicolas Mailhot < nicolas.mailhot@laposte.net> wrote:
Hi all,
Just FYI, I intend to relicense fontpackages from LGPL3+ to GPL3+, to make sharing parts with go-macros easier.
Can it be possible for you to explain this further? I want to understand how license change can help here.
I just have two macro sets under different licenses to maintain, with pretty much the same functions and layout, and I'd like to copy good ideas from one to the other without needing to worry about licensing. The easiest one to relicense is fontpackages as the Go macro project contains big amounts of code to workaround the lack of standard native packaging tech Go-side.
As I wrote in my message, it does not change anything effectively for fontpackages. The differences between GPL and LGPL trigger on linking, and fontpackages does not include any lib linked elsewhere.
Regards,
-
Nicolas Mailhot -
Parag Nemade