* bug#46385: User awareness of Anti-Features
@ 2021-02-08 13:28 soheil--- via Bug reports for GNU Guix
2021-02-10 14:38 ` Maxime Devos
2021-02-10 16:53 ` Leo Famulari
0 siblings, 2 replies; 5+ messages in thread
From: soheil--- via Bug reports for GNU Guix @ 2021-02-08 13:28 UTC (permalink / raw)
To: 46385
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
Users should be aware of anti-feature of packages.
It is best to have anti-feature tag in anti-feature packages so that user know which program has anti-features; Like F-Droid. Also, user should be aware of anti-feature during installation. And wherever this awareness is needed...
An example is Telegram, Telegram is a program that user connects to a proprietary server, and users who know less about computer softwares, are not aware of the anti-feature.
[-- Attachment #2: Type: text/html, Size: 727 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#46385: User awareness of Anti-Features
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
2021-02-10 16:53 ` Leo Famulari
1 sibling, 1 reply; 5+ messages in thread
From: Maxime Devos @ 2021-02-10 14:38 UTC (permalink / raw)
To: soheil, 46385
[-- Attachment #1: Type: text/plain, Size: 1695 bytes --]
Hi,
On Mon, 2021-02-08 at 13:28 +0000, soheil--- via Bug reports for GNU Guix wrote:
> Users should be aware of anti-feature of packages.
> It is best to have anti-feature tag in anti-feature packages so that user know
> which program has anti-features; Like F-Droid. Also, user should be aware of
> anti-feature during installation. And wherever this awareness is needed...
>
> An example is Telegram, Telegram is a program that user connects to a
> proprietary server, and users who know less about computer softwares,
> are not aware of the anti-feature.
I'll have to think some more on whether this is something Guix needs, but I
do have a partial concrete implementation proposal:
Packages can have a ‘properties’ field, e.g. from gnu/packages/bioconductors.scm:
(define-public r-reactome-db
(package
(name "r-reactome-db")
(version "1.70.0")
[...]
(properties `((upstream-name . "reactome.db")))))
Maybe add a ‘anti-features’ entry field for some packages?
E.g.,
(define-public some-twitter-app
(package
(name "tweet")
[...]
(properties `((anti-features x y z)))))
x, y and z can be symbols, e.g. based upon from https://f-droid.org/en/docs/Anti-Features/
* 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.
Greetings,
Maxime
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#46385: User awareness of Anti-Features
2021-02-10 14:38 ` Maxime Devos
@ 2021-02-19 15:22 ` Ludovic Courtès
2022-06-09 21:12 ` Maxim Cournoyer
0 siblings, 1 reply; 5+ messages in thread
From: Ludovic Courtès @ 2021-02-19 15:22 UTC (permalink / raw)
To: Maxime Devos; +Cc: soheil, 46385
Hi,
Maxime Devos <maximedevos@telenet.be> skribis:
> I'll have to think some more on whether this is something Guix needs, but I
> do have a partial concrete implementation proposal:
>
> Packages can have a ‘properties’ field, e.g. from gnu/packages/bioconductors.scm:
>
> (define-public r-reactome-db
> (package
> (name "r-reactome-db")
> (version "1.70.0")
> [...]
> (properties `((upstream-name . "reactome.db")))))
>
> Maybe add a ‘anti-features’ entry field for some packages?
> E.g.,
>
> (define-public some-twitter-app
> (package
> (name "tweet")
> [...]
> (properties `((anti-features x y z)))))
>
> x, y and z can be symbols, e.g. based upon from https://f-droid.org/en/docs/Anti-Features/
>
> * 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.
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?
Ludo’.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#46385: User awareness of Anti-Features
2021-02-19 15:22 ` Ludovic Courtès
@ 2022-06-09 21:12 ` Maxim Cournoyer
0 siblings, 0 replies; 5+ messages in thread
From: Maxim Cournoyer @ 2022-06-09 21:12 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: soheil, Maxime Devos, 46385
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#46385: User awareness of Anti-Features
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-10 16:53 ` Leo Famulari
1 sibling, 0 replies; 5+ messages in thread
From: Leo Famulari @ 2021-02-10 16:53 UTC (permalink / raw)
To: 46385
On Mon, Feb 08, 2021 at 01:28:40PM +0000, soheil--- via Bug reports for GNU Guix wrote:
> Users should be aware of anti-feature of packages.
> It is best to have anti-feature tag in anti-feature packages so that user know which program has anti-features; Like F-Droid. Also, user should be aware of anti-feature during installation. And wherever this awareness is needed...
I use F-Droid, but I dislike their "anti-feature" messaging. It's not
clear to me that it's an example we should follow.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-06-09 21:14 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2021-02-10 16:53 ` Leo Famulari
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).