From: Ricardo Wurmus <rekado@elephly.net>
To: Adonay Felipe Nogueira <adfeno@hyperbola.info>
Cc: 35234@debbugs.gnu.org
Subject: [bug#35234] [PATCH] gnu: Add the-dark-mod.
Date: Mon, 22 Apr 2019 13:56:01 +0200 [thread overview]
Message-ID: <877ebm6ypa.fsf@elephly.net> (raw)
In-Reply-To: <DAEA3491-A0CB-420D-AD9B-3B45B5D00CC1@hyperbola.info>
Adonay Felipe Nogueira <adfeno@hyperbola.info> writes:
> What I do think must be done is have a policy not to do a full
> copy-paste to the description from the original project in the
> package's metadata, this way we can foster a better compliance with
> the GNU FSDG in regards to not referencing non-free/non-libre
> functional data or nonfunctional ones that forbid unlimited sharing
> and selling.
>
> This "avoid full copy-paste" policy would be similar to what we have
> in the Free Software Directory[1] - not equal since the motive would
> be different.
>
> The next challenge would be making sure that the software and
> documentation don't mention stuff that isn't FSDG-compliant.
This is usually addressed during patch review.
--
Ricardo
prev parent reply other threads:[~2019-04-22 11:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 18:16 [bug#35234] [PATCH] gnu: Add the-dark-mod Pierre Neidhardt
2019-04-11 19:40 ` Ricardo Wurmus
2019-04-12 9:39 ` Pierre Neidhardt
2019-04-12 11:22 ` Ricardo Wurmus
2019-04-12 12:02 ` Pierre Neidhardt
2019-04-21 14:13 ` Ricardo Wurmus
2019-04-21 16:18 ` Ludovic Courtès
2019-04-22 9:02 ` Pierre Neidhardt
2019-04-22 9:19 ` Ricardo Wurmus
2019-04-22 9:42 ` Pierre Neidhardt
2019-04-22 16:50 ` Ludovic Courtès
2019-04-22 17:42 ` Pierre Neidhardt
2019-04-22 10:01 ` Adonay Felipe Nogueira
2019-04-22 9:40 ` Adonay Felipe Nogueira
2019-04-22 11:56 ` Ricardo Wurmus [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=877ebm6ypa.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=35234@debbugs.gnu.org \
--cc=adfeno@hyperbola.info \
/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).