[PATCH] Revert "menu: add Adult category to registry"
vuntz at gnome.org
Thu Dec 1 00:07:59 PST 2011
Le mercredi 23 novembre 2011, à 13:38 +0000, Peter TB Brett a écrit :
> This reverts commit c51aa112f53adc87250177002aa3e008305e0777.
> There are several serious issues with the stated rationale for and
> intended use of the "Adult" Additional Category that have yet to be
FWIW, I don't care much about that category. But:
> - The menu specification is designed for worldwide application, and
> thus must be culturally impartial. Different cultures have
> different criteria for something that is "adult-only". Ambiguous
> examples provided on the XDG list include "Bible" and "Art Gallery"
True. But on the other hand, past examples have shown that we can be
blocked forever (for instance: the discussion on something like a
Religion category). And moving forward with something that is not
perfect is better than staying blocked.
> - Given a set of criteria for what constitutes "Adult" content, the
> categorisation is binary, but whether an application is "Adult" is
> not. Ambiguous examples provided on the XDG list include a
> "Breastfeeding Tutorial" application; the "PornView" application,
> which does not in fact include or provide access to any pornography;
> web browsers, which provide access to a wealth of pornography on the
> Internet; and text adventure games that include the possibility of
> violent death.
Hrm, this is probably an argument that is valid for all categories :-)
It's really up to app developers to use the relevant categories, and
then to distributors to decide if those should be overridden or not.
> - The purpose of the "Category" field in .desktop files is to aid in
> organisation of applications into a navigable hierarchy. By
> contrast, the proponents of the "Adult" Additional Category view the
> "Adult" additional category is as a tool for censorship.
Hrm, I don't think it's censorship: the apps are still there, after all.
It's filtering, and filtering is actually what the menu spec is about.
Sure, in this case, it's filtering to hide stuff.
> Until these issues are addressed and consensus is achieved, this
> category should be removed. In the interim period, there is no
> obstacle to Menu Specification implementors using Additional
> Categories not listed in the Specification, should they wish to do so.
Do you see any way those issues can be addressed?
The way I see it, it's just additional metadata that is not used by
default and that people can use if they want. So I'm not that much
worried about it.
Les gens heureux ne sont pas pressés.
More information about the xdg