unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: Ian Denhardt <ian@zenhack.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add ttf-symbola.
Date: Fri, 24 Oct 2014 10:11:53 +0400	[thread overview]
Message-ID: <87wq7qatee.fsf@gmail.com> (raw)
In-Reply-To: <20141023173605.466.47994@rook> (Ian Denhardt's message of "Thu, 23 Oct 2014 13:36:05 -0400")

Ian Denhardt (2014-10-23 21:36 +0400) wrote:

> Quoting Eric Bavier (2014-10-23 10:14:02)
>>
>> Andreas Enge writes:
>>
>> > On Wed, Oct 22, 2014 at 08:51:04PM +0400, Alex Kost wrote:
>> >> «In lieu of a licence: Fonts in this site are offered free for any use;
>> >> they may be opened, edited, modified, regenerated, posted, packaged and
>> >> redistributed.»
>> >> Is it OK to use "fsf-free" for this package?
>> >
>> > To me, this sounds like "public-domain".
>>
>> I was thinking the same.
>
> To me this sounds like "author does not understand licensing/copyright."
> It's pretty obvious the intent is some kind of simple permissive thing
> (whether that's a license or public domain), but it's not clear to me
> how much legal ambiguity there is. IANAL, but for certain entities, the
> ambiguity can be a problem (suppose, for example, you're a designer
> wanting to use this font for something, but you work somewhere with a
> strict legal department that doesn't think this qualifies as a license -
> you may be out of luck).
>
> You run into issues around certain packages, like sqlite-docs, where
> they end up being technically non-free because the developers decide
> "copyright is silly, I'm not going to deal with this." I sympathize,
> but...
>
> We ought to be careful about this one - maybe ask someone at the FSF
> about whether this meets their standards, and if not maybe ask the
> developer if they can put something less ambiguous on it.

According to <http://www.gnu.org/licenses/license-list.html> such
questions may be asked at <licensing@fsf.org>.  But I'm afraid I'm not
able to ask about it properly.

  reply	other threads:[~2014-10-24  6:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <RT-Ticket-954922@rt.gnu.org>
2014-10-22 16:51 ` [PATCH] gnu: Add ttf-symbola Alex Kost
2014-10-23  6:26   ` Andreas Enge
2014-10-23 14:14     ` Eric Bavier
2014-10-23 17:36       ` Ian Denhardt
2014-10-24  6:11         ` Alex Kost [this message]
2014-10-24  6:52           ` Ian Denhardt
2014-10-24 17:47             ` Alex Kost
2014-11-13 20:15             ` Ludovic Courtès
2014-11-16 19:27               ` Ian Denhardt
2014-11-16 21:09                 ` Ludovic Courtès
2014-11-19  3:28                   ` [PATCH] gnu: Add ttf-symbola. [gnu.org #954922] Ian Denhardt
     [not found]                     ` <rt-3.4.5-31938-1416367745-1484.954922-6-0@rt.gnu.org>
2014-12-16 21:58                       ` [gnu.org #954922] Vague "licensing" for the symbola font Donald R Robertson III via RT
2014-12-17 19:53                   ` [PATCH] gnu: Add ttf-symbola Ian Denhardt

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wq7qatee.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ian@zenhack.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).