unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <marius@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Non-free data in Poppler test suite
Date: Fri, 01 Jul 2022 15:12:52 +0200	[thread overview]
Message-ID: <877d4x3rjf.fsf@gnu.org> (raw)
In-Reply-To: <87k090qydo.fsf@gnu.org> (Marius Bakke's message of "Tue, 28 Jun 2022 23:19:47 +0200")

Hi!

Marius Bakke <marius@gnu.org> skribis:

> So the million dollar question ... are these files okay to use for Guix?
>
> In my (non-lawyer) opinion, I have faith that Poppler developers would
> not distribute files that are not freely redistributable, and that this
> counts as "non-functional data" per FSDG guidelines:
>
>   https://www.gnu.org/distros/free-system-distribution-guidelines.html
>
> However, we failed to reach a consensus on #guix[0].  What do others
> around here think?  Should we play it safe and disable Poppler tests?
> Raise the issue with FSF?  Something else?

IANAL, but… I would argue that these PDFs are “non-functional” in the
sense that they do not have any impact on the functionality of Poppler.

It may also be that this qualifies as fair use (AIUI, we’re talking
about pages extracted from larger PDF files, right?).

What does Debian do?  :-)

Ludo’.


  parent reply	other threads:[~2022-07-01 13:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 21:19 Non-free data in Poppler test suite Marius Bakke
2022-06-28 21:29 ` Maxime Devos
2022-07-01 12:57   ` Ludovic Courtès
2022-07-19 12:43     ` Maxime Devos
2022-06-29  8:04 ` zimoun
2022-07-01 13:12 ` Ludovic Courtès [this message]
2022-07-01 19:22   ` Mark H Weaver
2022-07-06  0:39     ` Marius Bakke
2022-07-02 14:12   ` Tobias Geerinckx-Rice
2022-07-02  9:04 ` Liliana Marie Prikler

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=877d4x3rjf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=marius@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 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).