From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: soheil@disroot.org, Maxime Devos <maximedevos@telenet.be>,
46385@debbugs.gnu.org
Subject: bug#46385: User awareness of Anti-Features
Date: Thu, 09 Jun 2022 17:12:42 -0400 [thread overview]
Message-ID: <87wndph779.fsf@gmail.com> (raw)
In-Reply-To: <87v9aokrph.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 19 Feb 2021 16:22:34 +0100")
Hi,
Ludovic Courtès <ludo@gnu.org> writes:
[...]
>> * ads (I don't think any application in Guix has these?)
>> * tracking (should be patched out if possible)
>> * non-free-network-services
>> * non-free-dependencies (probably not allowed in upstream Guix, but maybe in a channel)
>>
>> The code behind ‘guix show’ and ‘guix search’ would need to
>> be adjusted to display anti-features, and the ‘guix install’ code
>> should warn if someone installs a package with anti-features.
>
> I’m sympathetic with the idea of raising awareness of those
> anti-features. However, I don’t see a clear way we could “define” each
> possible anti-feature; some are definitely ill-defined (for instance, a
> service is neither “free” nor “non-free” in the same sense as software
> can be free or non-free.) It’s also not entirely clear to me how the UI
> could make good use of it.
I agree. It's not well defined, and to me following the FSDG seems an
already good warranty that you're getting only free software from a
project dedicated to fixing any freedom issues that may be discovered.
> That said, there are anti-features that we have always patched out in
> the past, such as tracking/“phoning home” and auto-upgrades. Perhaps we
> could formalize that in our packaging guidelines?
It'd be good to have this documented, indeed.
Thanks,
Maxim
next prev parent reply other threads:[~2022-06-09 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 13:28 bug#46385: User awareness of Anti-Features soheil--- via Bug reports for GNU Guix
2021-02-10 14:38 ` Maxime Devos
2021-02-19 15:22 ` Ludovic Courtès
2022-06-09 21:12 ` Maxim Cournoyer [this message]
2021-02-10 16:53 ` Leo Famulari
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=87wndph779.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=46385@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=maximedevos@telenet.be \
--cc=soheil@disroot.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).