Hi,
I find this policy a little bit strange. Does KDE really forbid any GPLv3 code as part of KDE SC? This would mean KDE is for ever stuck to a outdated license. GPLv2 is the past, GPLv3 the present and GPLvX the future.
Remember what would happen if projects had a similar policy back the days GPLv1 was in the position GPLv2 is today. Than we would still have a lot of GPLv1(+) licensed software. Scarry, isn't it?
Sure if a program want to link to a GPLv2-only lib it has to be GPLv2(+). But if I program doesn't have such dependencies I don't see a reason to use a old license.
Hi, I find this policy a
Hi,
I find this policy a little bit strange. Does KDE really forbid any GPLv3 code as part of KDE SC? This would mean KDE is for ever stuck to a outdated license. GPLv2 is the past, GPLv3 the present and GPLvX the future.
Remember what would happen if projects had a similar policy back the days GPLv1 was in the position GPLv2 is today. Than we would still have a lot of GPLv1(+) licensed software. Scarry, isn't it?
Sure if a program want to link to a GPLv2-only lib it has to be GPLv2(+). But if I program doesn't have such dependencies I don't see a reason to use a old license.