Mail Archives: cygwin/2011/10/21/12:42:19
--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--
- Raw text -