From: David Sastre <d.sastre.medina@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Contributing license information?
Date: Fri, 21 Oct 2011 16:42:00 -0000 [thread overview]
Message-ID: <20111021164145.GA7027@jethro.local.lan> (raw)
In-Reply-To: <20111021085901.GG13505@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
On Fri, Oct 21, 2011 at 10:59:01AM +0200, Corinna Vinschen wrote:
> On Oct 21 13:02, Luke Kendall wrote:
> > Can I ask a related question: for the few shell scripts and /etc
> > files provided in base-files: what license are they under? The
> > package contains lots of licenses, as we've been discussing, but I
> > couldn't find any indication of which license applies to the actual
> > non-license files in base-files itself!
>
> Isn't that hard on the verge of nit-picking? These are simple scripts.
> Their Linux brothers and sisters are under PD so I think it makes much
> sense to define the Cygwin files as PD, too.
>
> David, that's ok with you?
Yes, it's ok for me :)
Also, it's possible to specifically mention it in the header of every
shellscript in base-files, maybe using CC0[1][2]?
CC0 would then be included under /usr/share/doc/common-licenses.
Please note IANAL, i.e., I'm not aware of possible uncompatibilities
of CC0 with the rest of the project's licensing.
(Generally speaking, it's an interesting topic, BTW.[3])
[1]https://www.gnu.org/licenses/license-list.html#CC0
[2]https://creativecommons.org/publicdomain/zero/1.0/legalcode
[3]https://secure.wikimedia.org/wikipedia/en/wiki/Public_domain
--
Huella de clave primaria: AD8F BDC0 5A2C FD5F A179 60E7 F79B AB04 5299 EC56
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2011-10-21 16:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 1:09 Luke Kendall
2011-08-19 12:04 ` Corinna Vinschen
2011-08-22 23:46 ` Luke Kendall
2011-10-20 3:49 ` Luke Kendall
2011-10-20 7:39 ` Corinna Vinschen
2011-10-20 7:49 ` Corinna Vinschen
2011-10-21 2:02 ` Luke Kendall
2011-10-21 8:59 ` Corinna Vinschen
2011-10-21 16:42 ` David Sastre [this message]
2011-10-21 17:36 ` Corinna Vinschen
2011-10-25 1:01 Luke Kendall
2011-10-25 13:51 ` Corinna Vinschen
2011-10-25 20:07 ` David Sastre
2011-10-31 5:27 ` Luke Kendall
2011-10-31 14:27 ` Christopher Faylor
2011-11-01 2:18 ` Luke Kendall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111021164145.GA7027@jethro.local.lan \
--to=d.sastre.medina@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).