- qualify "no [actions]" with "without being at risk..."
- mention exceptions and limitations, jurisdiction-specific
- mention that collaborators don't give you permission, either
- remove trivial example copyright notice, suggest adding statement symmetric with for-users section below
- suggest exploring contributor agreement so non-licensor has permission from contributors
closes#444#445
This is a **draft**, probably will be controversial, definitely needs
wordsmithing.
Fixes#380 "No clear message on why to choose an open source license"
-- added line under heading
Fixes#335 "Feedback from John Sullivan talk on license choosers"
-- remaining items were (roughly) to not surface patents at this
level, and to surface choice between allowing proprirary/closed
source or not
Fixes#239 "Consider discussing ecosystems with an already predominant
license" (well, it doesn't *discuss* but there's a page for that,
unlinked til now) and makes the default recommendation of just about
everyone -- use exisitng project/community's license if applicable
-- prominent on the site
Closes#48 "Proposed modified workflow: make permissive/copyleft
and patents orthogonal" though probably not in way submitter would
favor. I could be convinced that Apache-2.0 should be featured
rather than MIT because of the former's express patent grant, but
as it stands I'm not sure the complexity of Apache-2.0 (and for a
weak grant, relative to GPLv3) is worth it relative to MIT. There's
some value in the first license a user looks at being really easy
to understand. The continued popularity of MIT and simialar ISC and
BSD-2/3 seems to indicate people want that simplicity. And where
are the holdups based on patents supposedly infringed by open source
projects under licenses without an express patent grant that could
not have happened had those projects been under Apache-2.0? Please
educate me! :)
Any and all feedback most welcome.
Based on feeedback from people looking for BSD licenses and wanting to
use site as a reference.
I'm not thrilled with any distraction from flow of choices that
work for most on home page through spectrum covering range of open
source licenses without redundant ones, but obviously some people
prefer seeing everything in a table, so let them find it, accommodate
use as reference and people whose learning style involes poring
over a reference rather than being guided.
