[Bug 776582] Confirm licensing of smolt
https://bugzilla.novell.com/show_bug.cgi?id=776582
https://bugzilla.novell.com/show_bug.cgi?id=776582#c5
Ciaran Farrell
A quick follow up summary about this open case.
From the point of view of main contributor, there's no reason to not re release the software with a gpl-3+ licence.
But this need the following
Thanks Mike for the feedback, in fact the opened bug, is more about the "general chaos" there's in sources.
What would be the best approach, contact each contributor and ask them to publish a patch
and then release a new version full gplized 3?
That's probably best.
-Mike
So now what else can we do as dowstream ? Fix the upstream sources, and get the acknowledge of each contributor mentioned in sources - Quite a lot of time and work - Prepare the patch for upstream, and wait green light
Question, is it still work done on that software, or is it yet another great idea that is no more developed and maintained, and thus a request for removal has to be done, due to the licence issue.
Ciaran your output is welcomed
The main issue that would prevent the package (as a whole) from being seen as GPL-3.0+ is the file /client/fs_util.py. I'd suggest that the first step should be to try to get that relicensed to GPL-2.0+. To make the outwardly licensing appearance of the package uniform and understandable, the instances that purport to identify the package as GPL-2.0+ and GPL-3.0 should be found and fixed (e.g. what does the user see - in the UI "About" box, there seems to be a GPL-3.0 notice whereas in the .po files (not sure if the user actually sees this, but the content might be propogated to the UI and with it the license text) there is mention of GPL-2.0. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com