Packages

This package contains vague terminology “Open Source”:

community/stone-soup 0.19.5-1
    Open-source, single-player, role-playing roguelike game of exploration and treasure-hunting

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

Free-software, single-player, role-playing roguelike game of exploration and treasure-hunting

This package contains vague terminology “Open Source”:

community/sysdig 0.15.1-2
    Open source system-level exploration and troubleshooting tool

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

Free software system-level exploration and troubleshooting tool

This package contains vague terminology “Open Source”:

community/tkabber 1.1.2-1
    Tkabber is an open source Jabber client, written in Tcl/Tk.

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

Tkabber is a free software Jabber client, written in Tcl/Tk.

This package contains vague terminology “Open Source”:

community/topbeat 1.3.1-1
    Open source server monitoring agent that stores metrics in Elasticsearch

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

Free software server monitoring agent that stores metrics in Elasticsearch

This package contains vague terminology “Open Source”:

community/ttf-overpass 2.1-2
    An open source font family inspired by Highway Gothic esp. suited for signs, lettering and web sites

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

A free software font family inspired by Highway Gothic esp. suited for signs, lettering and web sites

This package contains vague terminology “Open Source”:

community/unrealircd 4.0.11-2
    Open Source IRC Server

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

Free Software IRC Server

This package contains vague terminology “Open Source”:

community/wiredtiger 2.9.1-1
    High performance, scalable, production quality, NoSQL, Open Source extensible platform for data management

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

High performance, scalable, production quality, NoSQL, Free Software extensible platform for data management

This package contains vague terminology “Open Source” and “Linux”:

community/xwax 1.6-1
    Open-source vinyl emulation software for Linux.

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source” and “Linux” as operating system, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

https://www.gnu.org/philosophy/words-to-avoid.html#Linux

It would be good example to set to have proper description of packages without using “Open Source” and “Linux” as operating system.

eg.

Free-software vinyl emulation software for GNU/Linux.

This package contains vague terminology “Open Source”:

community/zynaddsubfx 3.0.1-1
    Opensource software synthesizer capable of making a countless number of instruments.

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

Free software synthesizer capable of making a countless number of instruments.

This package contains vague terminology “Alternative”:

extra/libspnav 0.2.3-1
    Alternative to the proprietary 3Dconnexion device driver and SDK for their 3D input devices

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Alternative”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Alternative

It would be good example to set to have proper description of packages without using “Alternative”.

eg.

Replacement to the proprietary 3Dconnexion device driver and SDK for their 3D input devices

This package contains vague terminology “Commercial”:

extra/bogofilter 1.2.4-2.hyperbola2
    A fast Bayesian spam filtering tool, without noncommercial files

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Commercial”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Commercial”.

eg.

A fast Bayesian spam filtering tool, without nonfree files

This package contains vague terminology “Content”:

community/drupal 8.3.2-1
    A PHP-based content management platform

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Content”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Content

It would be good example to set to have proper description of packages without using “Content”.

eg.

A PHP-based web site revision system platform

This package contains vague terminology “Linux”:

community/clamtk 5.24-1
    Easy to use, light-weight, on-demand virus scanner for Linux systems

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Linux” as operating system, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Linux

It would be good example to set to have proper description of packages without using “Linux” as operating system.

eg.

Easy to use, light-weight, on-demand virus scanner for GNU/Linux systems

This package contains vague terminology “Linux”:

community/oprofile 1.1.0-3
    System-wide profiler for Linux systems

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Linux” as operating system, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Linux

It would be good example to set to have proper description of packages without using “Linux” as operating system.

eg.

System-wide profiler for GNU/Linux systems

This package contains vague terminology “Linux”:

community/shorewall 5.1.4-1
    An iptables-based firewall for Linux systems

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Linux” as operating system, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Linux

It would be good example to set to have proper description of packages without using “Linux” as operating system.

eg.

An iptables-based firewall for GNU/Linux systems

This package contains vague terminology “Linux”:

community/shorewall6 5.1.4-1
    An iptables-based firewall for Linux systems (with IPv6 support)

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Linux” as operating system, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Linux

It would be good example to set to have proper description of packages without using “Linux” as operating system.

eg.

An iptables-based firewall for GNU/Linux systems (with IPv6 support)

This package contains vague terminology “MP3 Player”:

community/gmtp 1.3.10-2
    A simple MP3 player client for MTP based devices

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “MP3 Player”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#MP3Player

It would be good example to set to have proper description of packages without using “MP3 Player”.

eg.

A simple audio player client for MTP based devices

This package contains vague terminology “Vendor”:

extra/kdb 3.0.1.1-2
    A database connectivity and creation framework for various database vendors

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Vendor”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Vendor

It would be good example to set to have proper description of packages without using “Vendor”.

eg.

A database connectivity and creation framework for various database suppliers

This package contains vague terminology “Vendor”:

extra/publicsuffix-list 20170118.560.45a2bf8-1
    Cross-vendor public domain suffix database

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Vendor”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Vendor

It would be good example to set to have proper description of packages without using “Vendor”.

eg.

Cross-supplier public domain suffix database

This package contains vague terminology “Vendor”:

community/glide 0.12.3-1
    Dependency management and vendoring for Go projects

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Vendor”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Vendor

It would be good example to set to have proper description of packages without using “Vendor”.

eg.

Dependency management and suppliering for Go projects

This package contains vague terminology “Vendor”:

community/ndiswrapper-dkms 1.60.20160717-1
    Module for NDIS (Windows Network Drivers) drivers supplied by vendors.Use with DKMS

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Vendor”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Vendor

It would be good example to set to have proper description of packages without using “Vendor”.

eg.

Module for NDIS (Windows Network Drivers) drivers.Use with DKMS

Description:

community/ext3grep 0.10.2-4
    A tool to investigate an ext3 file system for deleted content and possibly recover it

Description is vague because of the word “content”. Why not say instead “data”?

See:
https://www.gnu.org/philosophy/words-to-avoid.html#Content

Description:

community/webfs 1.21-13
    Simple and instant http server for mostly static content.

Description is vague because of the word “content”. Why not simply say “files” instead and be more specific.

Even empty files without data inside can be served.

See:
https://www.gnu.org/philosophy/words-to-avoid.html#Content

Description:

community/openstreetmap-map-icons-svn 31588-1 [installed]
    A set of public domain licensed map icons for general OSM use

It is questionable if it is “Licensed” or dedicated.

See the file:
/usr/share/licenses/openstreetmap-map-icons/svg-twotone/LICENSE.txt

it does not matter if the file is named “LICENSE”, it could be also named anyhow else.

There must be reason why the organization Creative Commons is not using the word “License” in that text, and that is why I propose to simply say in description:

    A set of public domain map icons for general OSM use

community/autoconf-archive 1:2017.03.21-1
    A collection of freely re-usable Autoconf macros

See:
https://www.gnu.org/philosophy/words-to-avoid.html#FreelyAvailable

Don’t use “freely available software” as a synonym for “free software.” The terms are not equivalent. Software is “freely available” if anyone can easily get a copy. “Free software” is defined in terms of the freedom of users that have a copy of it. These are answers to different questions.