Replied in thread
@haui see, #PHP's license is #permissive BSD-like, and how it nicely got adopted.
It didn't need #copyleft licensing, and there were and still are tons of webhosting providers.
Recent searches
Search options
Administered by:
#permissive
0 posts0 participants0 posts today
#PSA:
Both #Linux the various #BSD projects are awesome #FOSS endeavors that deserve respect and curious investigation.
Both #CopyLeft and #Permissive licenses like the BSD/MIT/ISC have valid use cases.
Let's back away from the meme polemics and learn to respect everyone working towards freedom.
As you were.
Replied in thread
@gondolyr personally, I also loke #permissive licenses like #0BSD.
Open for business: #Chinese firms are #Singapore-bound
"We shld also not allow the world to think tt an easy #business environment also means a #permissive one. Some hv even suggested tt #Singaporewashing – the process where foreign actors take advantage of our simple registration processes & global reputation for incorruptibility to incorp fronts for #dubiousbusiness activities – is some form of quid pro quo for investing in 
.. Such a mindset will come back to bite us"
https://www.scmp.com/week-asia/economics/article/3271163/open-business-chinese-firms-are-singapore-bound-will-they-stay
South China Morning Post · Open for business: Chinese firms are Singapore-bound but will they stay?Singapore has emerged as the preferred hub for Chinese firms to expand in the region, even amid greater regulatory scrutiny and Hong Kong’s rebound.
Replied in thread
in either case, previous versions remain available.
Correct. Even if the controller of the public #git repo takes it down without warning, the community can still fork the project based on the local copies of the repo that various people have lying around.
It seems to me like the core problem is not about using a copyleft licence or not, but about assigning ownership.
It's both. If you have #permissive licensing or copyright assignment (or similar), then one entity can take their ball and go home, closing all future versions that they make. If you have #CopyLeft and you don't have copyright assignment, then they can't.
With all this #Redis fallout, it is really bothersome to see how a lot of people that are vocal about #foss values keep confusing the licensing topic with the copyright one. No #copyleft source license would be an automatic salvation in such a case to begin with - because ANY license can be changed by the copyright holder. Go ahead and hate/blame Redis Ltd. to your heart‘s content for what they did, but please, stop spreading #fud about #permissive #licensing in general.
TIL: "There are two kinds of free: free as in free puppies, and free as in free beer." - What’s a #Permissive #License – and Why Should I Care?
https://freebsdfoundation.org/blog/whats-a-permissive-license-and-why-should-i-care/
FreeBSD Foundation | A non-profit organization dedicated to supporting and building the FreeBSD Project · “What’s a Permissive License – and Why Should I Care?” | FreeBSD FoundationYou may have heard the term “permissive license” being thrown around, especially with reference to FreeBSD, but why should you care?
Continued thread
And yes, after considering the mountain of evidence I decided to choose a #permissive instead of #copyleft license.
In fact, I did choose the same license that @landley chose for #toybox: #0BSD.
https://github.com/OS-1337/OS1337/blob/main/LICENSE.md
Since #copyleft would not guarantee improvements as can be seen not only from #BusyBox but also @grsecurity and #Viprinet #VPN - #Routers.
["#Viprinux" is a botched and horribly outdated #OpenADK mess based off what they released on their website]...
https://web.archive.org/web/20230331121150/https://www.viprinet.com/en/support/downloads
GitHubOS1337/LICENSE.md at main · OS-1337/OS1337OS/1337 Project . Contribute to OS-1337/OS1337 development by creating an account on GitHub.
The Blue Oak Model License is the one that fits all my requirements perfectly, namely:
- it is permissive
- has patent and contribution coverage
- clear text, no legalese
- simple and modern template
- maintenance-friendly, with no personalized copyright header in the template itself
- no dreaded ALL-CAPS
Going to use it for all my projects and highly recommended to everyone else out there! 
blueoakcouncil.orgBlue Oak Model License 1.0.0
Being rather picky about and unsatisfied with most #permissive #licenses, I am kinda on the verge of writing my own one... license proliferation be damned.
#floss #opensource
The so called "strong" #copyleft philosophy is deeply unethical and has nothing to do with protecting freedom. You can twist the definition to suit your political agenda, like some do, but ultimately - your ideology is hypocritical.
If you care about the freedom and making the society better - go with #permissive licensing for your next #floss project.
If you insist on reciprocity (non-viral) for your code, at least go with #MPL - the most sane of share-alike licenses. Don't go #GPL, pls.
#Permissive #licenses allow proprietary forks, meaning the original project may be embraced, extended, and extinguished without the creator ever gaining a penny for their work. #GPL and other #copyleft licenses grant an unspoken freedom from extinguishment.
Replied in thread
@msw @timbray @sogrady @ahl Do not forget #permissive #copyright of many #freesoftware pieces.