all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Clément Lassieur" <clement@lassieur.org>
To: 26588@debbugs.gnu.org
Subject: bug#26588: Add some (non-free?) font licenses.
Date: Fri, 21 Apr 2017 16:46:27 +0200	[thread overview]
Message-ID: <87a879zum4.fsf@lassieur.org> (raw)

The first patch adds Bitstream Vera license, which IMHO is non-free.
Feel free to discuss it though, I'm not sure of the comment I wrote.

The font could be added even though it is non-free because it could be
considered a "Non-fonctional data".  See
https://www.gnu.org/distros/free-system-distribution-guidelines.html#non-functional-data.

The second patch adds Arev license, which is almost like Bitsteam Vera,
and is needed by 0ad-data (which I'm working on).

The third patch fixes font-bitstream-vera, which IMHO erroneously had
X11-style license.

             reply	other threads:[~2017-04-21 14:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21 14:46 Clément Lassieur [this message]
2017-04-21 14:48 ` bug#26588: [PATCH 1/3] licenses: Add Bitstream Vera Clément Lassieur
2017-04-21 14:48   ` bug#26588: [PATCH 2/3] licenses: Add Arev Clément Lassieur
2017-04-21 14:48   ` bug#26588: [PATCH 3/3] gnu: font-bitstream-vera: Change license to Bitstream Vera Clément Lassieur
2017-04-21 15:30     ` Clément Lassieur
2017-04-26  9:13   ` bug#26588: [PATCH 1/3] licenses: Add " Marius Bakke
2017-04-29  9:57     ` Clément Lassieur
2017-04-29 14:00       ` Marius Bakke
2017-05-01 11:00         ` Clément Lassieur
2017-05-01 11:01           ` bug#26588: [PATCH 1/2] licenses: Add new meta-license fsdg-compatible Clément Lassieur
2017-05-01 11:01             ` bug#26588: [PATCH 2/2] gnu: font-bitstream-vera: Change license to fsdg-compatible Clément Lassieur
2017-05-01 14:53           ` bug#26588: [PATCH 1/3] licenses: Add Bitstream Vera Marius Bakke
2017-05-01 19:37             ` Clément Lassieur

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=87a879zum4.fsf@lassieur.org \
    --to=clement@lassieur.org \
    --cc=26588@debbugs.gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.