- add FSF list
- slight rewording, eg OSI list not exactly comprehensive
- add Cowan wizard
- rm TLDRLegal; can't seem to keep junk/spam additions off its home page
Claiming open source licenses need to be demystified is a claim
that they are mysterious. Choosealicense.com is not *Capital*; its
topic does not need to be mystified and demystified at once.
http://robertpaulwolff.blogspot.com/2014/09/more-on-language-and-social-reality.html
Someone encountering open source licenses for the first time at
choosealicense.com should have zero reason to think open source
licensing is mysterious.
Remove "If you have questions or issues, it is always best to consult
a legal professional."
It's not always best, especially considering it's costly and for
most finding one knowledgable about open source licensing will be
difficult.
If it were always best, the site should consist of
<h1>Consult a legal professional.</h1>
But seriously, claiming one should consult a legal professional is
no way to make choosing an open source license non-scary.
"[D]oesn't have to be scary" is hardly non-judgmental nor inviting
for anyone whose first encounter with open source licensing is this
site. I've also never heard anyone other than this site claim that
choosing an open source license can be scary. Confusing or extremely
boring, yes. Choosing to go open source, yes that can be scary.
Choosing among open source licenses, no.
- remove descrption of v2 v3 difference
- add to description v3 express patent grant
- update example projects to only include v3 ones
- move v2 projects to gplv2 license using property
partially addresses feedback in #335
and are structured
grant (permissions)
conditioned on (conditions)
with limitations
Permissions coming first combats mistaken but apparently widespread
impression that licenses impose conditions, even such that without
a license, there would be no conditions/work would be in the public
domain.
Requirements->Conditions emphasizes that they are pertinent if one
wants to take advantage of permissions.
Forbiddens->Limitations is more accurate: in most cases licenses
don't give permission to hold licensors liable, in some cases to
use licensors' trademarks or patents, but a licensee does not lose
the permissions granted by the license if the licensee holds licensor
liable, etc. Also emphasizes that there are limitatations on the
license grant, not that the license imposes prohibitions.
The most concise place to see both the rename and reorder is in
_includes/license-overview.html
I did not reorder the appearance of the groups of properties in
license source files (.txt files in _licenses) as those orderings
are not used to render anything on the webiste. Might do so later.
