Closed prokoudine closed 7 months ago
As with Fasteners, I'll be happy to re-license to LGPL2.1. The code is based on @JMG1 's work and one of the main components is @ulrich1a 's sheetmetal unfolder which both are LGPL2 so we are good with that. It was only by my mistake that the current license is GPL.
As a contributor, I'm fine with my contributions being relicensed.
waiting for response of: @Syres916, @easyw, @ASzc, @bgamari, @ceremcem, @mumme74
My contribution isn't really noteworthy, I'm ok with relicensing.
No objection to the license change!
No objection on my side neither
I have no objection to the license change.
I agree with the change!
i am happy with the change!
I am ok with the change
07.12.2023 20:47:33 Stefan Krüger @.***>:
i am happy with the change!
— Reply to this email directly, view it on GitHub[https://github.com/shaise/FreeCAD_SheetMetal/issues/286#issuecomment-1845999632], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAU5EKQQSEENK7FDOZ75APLYIIMNJAVCNFSM6AAAAABAIGRKK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBVHE4TSNRTGI]. You are receiving this because you were mentioned. [Verfolgungsbild][https://github.com/notifications/beacon/AAU5EKXU5QLRKY5UWCAF4FTYIIMNJA5CNFSM6AAAAABAIGRKK2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTOA64BA.gif]
As they say in my country I am for and even against This is an ironic admission that the previous speaker is right. :laughing:
I agree with the change.
I'm OK with LGPL2.1.
I agree with the change.
I agree with the change. Totally makes sense to integrate it
I think I only fixed a typo here, but I'm totally good with the license change.
On Thu, Dec 7, 2023, 9:39 PM mangelozzi @.***> wrote:
I agree with the change. Totally makes sense to integrate it
— Reply to this email directly, view it on GitHub https://github.com/shaise/FreeCAD_SheetMetal/issues/286#issuecomment-1846575440, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHDICTXWC2HOZMMQUTFDUL3YIKRYLAVCNFSM6AAAAABAIGRKK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBWGU3TKNBUGA . You are receiving this because you were mentioned.Message ID: @.***>
I also agree with the change.
Not sure if i have contributed to this repo but its ok for me too.
I have no objections to the LGPL2.1 license.
No objection! Congratulations!
No objections from my side!
No objection
go for it! sorry being late, but I don't watch very often my GH notifications
No objection, sorry for responding late. Change as you se fit as long as its an open source license.
@ceremcem , @Syres916
Your responses?
No objection
@ASzc What's your take on this?
I'm ok with re-licensing to LGPL2.1
Only up to you now, @bgamari and @ceremcem!
Hi. Sorry for the delay. I'm okay with the change you propose.
I am fine with relicensing.
Great!! All in! @prokoudine , what is the next step?
Great!! All in! @prokoudine , what is the next step?
I can do a PR changing the contents of LICENSE and boilerplates in .py files to LGPLv2.1, unless you want to do that yourself.
if you can do it, that would be great!
Close as accomplished.
The Workbench Creation guide recommends licensing addons under the terms of LGPL2.1 — the same license that FreeCAD source code is available under. The recommendation’s rationale is that it should be possible to ship a FreeCAD distribution, either upstream, or a custom one, with 3rd-party addons that are considered useful. While a workbench developer is free to choose an alternative license, doing so may impact the long-term viability and use of the workbench and should be considered carefully.
Ondsel would like to integrate the Sheet Metal workbench into its distribution of FreeCAD, because the company’s market study suggests that, just like iwth the Fasteners WB, this feature is expected to be available in 3D CAD programs by default. We want to provide our end-users the best possible experience. There’s a possibility that this workbench then will go back to become part of upstream FreeCAD. However neither the upstream version of FreeCAD, nor Ondsel’s version of FreeCAD can distribute this workbench as long as it’s licensed under the terms of GPL3.
We are asking for a conversation about relicensing this workbench under LGPL2+ or another compatible license to allow wider distribution.