Re: [new package][licenses] python-cheat + MIT & GPLv3 combination

2016-04-05 Thread Björn Esser
You're welcome! ^_^ And don't forget about whether it is either 'MIT and GPLv3(+)' ---> GPL supersedes MIT or 'MIT or GPLv3(+)' ---> both licenses are equal and independent That's another HUGE difference in meaning of the licensing chosen by upstream… Am 05.04.2016 um 14:41 schrieb P

Re: [new package][licenses] python-cheat + MIT & GPLv3 combination

2016-04-05 Thread Petr Stodulka
Thank You for clarification. I will ask of upstream how it is with GPLv3 & GPLv3+. Cheers, Petr On 5.4.2016 13:52, Björn Esser wrote: > Hi! > > When looking at the github-repo, I found a file "LICENSE" [1], which states > python-cheat is dual-licensed… Since the term "dual-licensing" usually

Re: [new package][licenses] python-cheat + MIT & GPLv3 combination

2016-04-05 Thread Björn Esser
Hi! When looking at the github-repo, I found a file "LICENSE" [1], which states python-cheat is dual-licensed… Since the term "dual-licensing" usually means, that you can freely apply either combination of the named licenses, either using a chosen single license from the offered ones, or a c

[new package][licenses] python-cheat + MIT & GPLv3 combination

2016-04-05 Thread Petr Stodulka
Hi, I need an advice/feedback about licenses. I want to add package **python-cheat** to F25 (and maybe to F24 too). However, the project is now under MIT + GLPv3 licenses - not only some parts, it is meaned by upstream as whole project is MIT and GPLv3. From my point of view, there is not problem