unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Marius Bakke <marius@gnu.org>, guix-devel@gnu.org
Subject: Re: Non-free data in Poppler test suite
Date: Sat, 02 Jul 2022 11:04:28 +0200	[thread overview]
Message-ID: <fedf40df1f2881bf3e5e731d236baae978cb2a22.camel@gmail.com> (raw)
In-Reply-To: <87k090qydo.fsf@gnu.org>

Am Dienstag, dem 28.06.2022 um 23:19 +0200 schrieb Marius Bakke:
> Hello Guix,
> 
> I discovered a potential freedom issue with the Poppler test suite.
> [...]
> 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:
Looking around the repository some more, I think there might actually
have been some neglect w.r.t. how we typically recommend licensing
information ought to be conveyed.  I've raised two issues upstream, 
[1] for data as reported here, [2] for code.  Let's see how poppler
devs reply.

Cheers

[1] https://gitlab.freedesktop.org/poppler/test/-/issues/1
[2] https://gitlab.freedesktop.org/poppler/test/-/issues/2


      parent reply	other threads:[~2022-07-02  9:05 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
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 [this message]

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=fedf40df1f2881bf3e5e731d236baae978cb2a22.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --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).