@oe1cxw Please just note that if you use copyleft license, so any modification of standard license, project is not recognized as opensource. Problem comes when you need to re-license in future and have to find all contributors and get them to agree to new one.
-
Show this thread
-
Replying to @micko_mame @oe1cxw
In what way a copyleft license is not "opensource"? Yes, it is a pain to change the license later, but being able to change a license is not in the definition of "opensource" nor it should be (IMO).
2 replies 0 retweets 0 likes -
Replying to @ivan_cukic @oe1cxw
Well copyleft license is not OSI approved license, and then you have other issues, like: not able to use some libraries since their license is not compatible due to your restrictions, can not apply to free licenses for paid software, other projects hesitate to use yours ...
1 reply 0 retweets 0 likes -
Replying to @micko_mame @oe1cxw
GPL is a OSI approced license. And you can not get more copyleft than that. Other reasons you mentioned are valid (except that you *can* use ↄ⃝ licenses for paid software, you just need to provide the sources) and have nothing to do with "open source" definition.
1 reply 0 retweets 0 likes -
The GPL vs BSD-style licenses is a topic as old as these licenses. In a nuthsell: - BSD-style gives the user total freedom - ↄ⃝ licenses give the freedom to the software itself - with this in mind, your 'limitations' become strengths - free code can not be closed
1 reply 0 retweets 0 likes -
Replying to @ivan_cukic @oe1cxw
Problem is not GPL or any known license, issue is if you used modified licenses, like BSD3 - but you are not able to use it in companies doing jet engines for example, then it is not any more BSD3 even its text says it is for most of users
1 reply 0 retweets 0 likes -
his original text was that it would be BSD license (or similar) but with restriction to usage in specific industries, so was referring to that.
1 reply 0 retweets 0 likes
My OP said it would be a viral non-OS license with certain restrictions and it would become a BSD-style license automatically after a certain point in time (something like 8 years after project start).
-
-
Replying to @oe1cxw @micko_mame
Yes, Miodrag explained via a PM. Sadly, Twitter does not show the whole thread to me - the 1st message I see is the one I replied to. Automatic BSD-fication under some circumstances is a great idea. We (
#KDE) have a similar agreement with the#Qt company to protect Qt's freedom0 replies 0 retweets 2 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.