This is the mail archive of the
libc-locales@sourceware.org
mailing list for the GNU libc locales project.
[Bug localedata/11213] localedata licencing issues
- From: "jrnieder at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: libc-locales at sources dot redhat dot com
- Date: Fri, 13 Jul 2012 21:02:26 +0000
- Subject: [Bug localedata/11213] localedata licencing issues
- Auto-submitted: auto-generated
- References: <bug-11213-716@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=11213
--- Comment #5 from Jonathan Nieder <jrnieder at gmail dot com> 2012-07-13 21:02:26 UTC ---
(In reply to comment #4)
> As long as itâs not an explicit Public Domain (which is probably
> illegal), much would be fine with me.
Heh, I was about to post the following:
| I'm fond of
|
| % This file has been put in the public domain.
| % You can do whatever you want with this file.
| %
| % Author: Chris Leonard
|
| Some[*] might object that under some systems of law, there is no such
| thing as putting a work in the public domain. These people would be
| right. Luckily the above wording makes the intent clear and
| unambiguous enough that reasonable courts recognize it as a license
| grant.
|
| [*] http://www.rosenlaw.com/lj16.htm
| Rebuttal: http://cr.yp.to/publicdomain.html
|
| If you want to dodge that issue, here's another reasonable way to go:
|
| % Copyright  2012 Chris Leonard
| % License: Zlib <http://www.zlib.net/zlib_license.html>
Thorsten's "any OSI-approved license" is fine, too. Even something
that requires reproducing a disclaimer of warranty like the LGPL, GPL,
Expat license, or a two-clause BSD-style license is fine, though it
seems silly for locale data.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.