X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.7 required=5.0	tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
Date: Fri, 21 Oct 2011 18:41:45 +0200
From: David Sastre <d.sastre.medina@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Contributing license information?
Message-ID: <20111021164145.GA7027@jethro.local.lan>
References: <4E4DB7AC.7070702@cisra.canon.com.au> <20110819120318.GB2506@calimero.vinschen.de> <4E9F9A2A.2060806@cisra.canon.com.au> <20111020073807.GC23092@calimero.vinschen.de> <4EA0D2AB.30402@cisra.canon.com.au> <20111021085901.GG13505@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="ReaqsoxgOBHFXBhH"
Content-Disposition: inline
In-Reply-To: <20111021085901.GG13505@calimero.vinschen.de>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

--ReaqsoxgOBHFXBhH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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!
>=20
> 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.
>=20
> 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
--=20
Huella de clave primaria: AD8F BDC0 5A2C FD5F A179  60E7 F79B AB04 5299 EC56

--ReaqsoxgOBHFXBhH
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iF4EAREIAAYFAk6hoMkACgkQ95urBFKZ7FZ2MQD+OKlqDvZQ0U+5TxTXF6Mdw8Ig
Wq1i3bR3Yz+JI7GLzwoA/iIBn5WukO4NSoECxViJcucVRLH+HkrpqOc/Z3u4IjjQ
=Irho
-----END PGP SIGNATURE-----

--ReaqsoxgOBHFXBhH--
