directory-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: About the use of the term "anti-feature" in the FSD.


From: Lorenzo L. Ancora
Subject: Re: About the use of the term "anti-feature" in the FSD.
Date: Wed, 25 Dec 2024 20:08:53 +0100
User-agent: Zoho Mail

@Craig
>>>>  I think we should reconsider the use of the term "anti-feature" and 
>>>> replace it with something a little more versatile.
>>> "Anti-Features" aligns with the naming and categorization found on the 
>>> F-Droid Anti-Features page.
>> Is the FSF holding any public agreements with F-Droid that would justify 
>> keeping such name?šŸ¤”
> I don't know of any agreements with f-droid.[...] The problem is there are 
> other potential aspects of a program which might be worth bringing to the 
> attention of or explaining to a potential user.

I fully agree: the FSD has the occasion of distinguish itself, bringing novelty 
and ethical development on the table.
In particular, the complexity of ethics grows with the complexity of the 
applications, so the current system can't be considered future-proof.
Replacing the old concept with a more flexible one would surely ease the 
learning curve for both visitors and young volunteers.

"Anti-feature" is a word fit for technical issues, but surely the FSD needs to 
also address ethical issues.

The beginning of the new year would be a lucky occasion to introduce the 
concept of User Notice.


@David
> I did not explicitly state that there is a public agreement with F-Droid.

The userbase can ask any question it deems appropriate to clear ambiguities.šŸ˜…


@all
 >  Agreed. For starters, can you please add new subsections of your examples 
 > to 
 > https://directory.fsf.org/wiki/Free_Software_Directory:Antifeatures#Non-features
 >  ?

In 2016 Sullivan and Dr. Stallman noted that the names of the antifeatures were 
a bit too aggressive.
When the FSF needs more friends, appearing irrational or aggressive isn't a 
good calling card.šŸ•Šļø

I suggest that the best course of action would be to implement the following 
redirections:

1. "Free_Software_Directory:Antifeatures" -> 
"Free_Software_Directory:UserWarnings"
2A. "Antifeature: Bait and surrenderā€ā€Ž" -> "UserWarning: Tiered software"
2B.  "Software with Bait and Surrender antifeatureā€ā€Ž" -> "UserWarning: Tiered 
software"
2C. "Software with Nonfree Compensation Software Promotion antifeatureā€ā€Ž " -> 
"UserWarning: Non-free software promotionā€ā€Ž"
2D. "Non-free software promotionā€ā€Ž " -> "UserWarning: Non-free software 
promotionā€ā€Ž"
3. "Antifeature: Free fork needed!"ā€ā€Ž -> "UserWarning: Free fork missing"
4. "Antifeature: Software names with words to avoid: Linuxā€ā€Ž" -> "UserWarning: 
Ambiguous terminology"

After that, the road ahead will be much less steep.ā›°ļø

~Lorenzo









reply via email to

[Prev in Thread] Current Thread [Next in Thread]