This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

LICENSE: base-files and use of CC0


According to:

    git clone git://github.com/dsastrem/base-files.git base-files.git

May files are put out using CC0 license[1]. I'm wondering this as it is to
my understanding recommended only for data (images, pure data files,
databases etc.), or for code snippets that accompany documentation (e.g.
code presented in manual).

The base-files are infrastructure in Cygwin, so wouldn't using MIT, BSD,
GPL or similar license work better for standard code? FSF[2] and OSI[3]
recommend to select some known license for software projects.

Jari

[1] http://creativecommons.org/publicdomain/zero/1.0/
[2] http://www.gnu.org/licenses/license-recommendations.html => topic "Software"
[3] After review, not approved by OSI. See threads published
    http://projects.opensource.org/pipermail/license-review/2012-February/000231.html

    http://opensource.org/faq#cc-zero
    "At this time, we do not recommend releasing software using the the CC0
    public domain dedication."

    http://opensource.org/faq#public-domain
    "We recommend that you always apply an approved Open Source license to
    software you are releasing, rather than try to waive copyright
    altogether. Using a clear, recognized Open Source license actually
    makes it easier for others to know that your software meets the Open
    Source Definition. It also enables the protection of attribution, and
    various other non-restrictive rights, that cannot be reliably enforced
    when there is no license."


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]