gt;>
Subject: Re: [License-discuss] FAQ entry (and potential website page?) on "why
standard licenses"?
Philip Odence suggested:
> Hey maybe “well-understood” is a good alternative to “standard."
Note that the GPL is one of the "least-understood" licenses
kipedia refers to the CPOL license as "mainly applied to content
that is being published on a single community site for software developers"
known as The Code Project. Wikipedia further reports that the CPOL license is
neither "open" as defined by OSI nor "free" as def
In case it helps, Black Duck publishes a top licenses list based on the
number of projects in our KnowledgeBase (out of a current total of about a
million) that utilize each respective license.
http://www.blackducksoftware.com/resources/data/top-20-open-source-licenses
The webpage only shows the
Below is a simple example of a marked up license.
The symbols << and >> designate the beginning and end of mark up statements.
In this case the top section is optional and marked as such with beginoptional
and endoptional.
Within that and further down in the text are a total of three places where
We'll get you some examples and some more detail, but the main idea is to
support matching (for both humans and programs). The idea is to do as much as
we can with the general guidelines, but to mark up where need be (as in my BSD
copyright text example).
From: Luis Villa mailto:l...@lu.is>>
R
rally coordinate for mutual benefit. I would
be happy to organize, if someone will suggest the appropriate OSI participants.
Thanks for your time,
Phil
L. Philip Odence
Vice President of Corporate and Business Development
Black Duck Software, Inc.
8 New England Executive Park, Suite 211, Burl
rally coordinate for mutual benefit. I would
be happy to organize, if someone will suggest the appropriate OSI participants.
Thanks for your time,
Phil
L. Philip Odence
Vice President of Corporate and Business Development
Black Duck Software, Inc.
8 New England Executive Park, Suite 211, Burl
7 matches
Mail list logo
