From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Tagging packages
Date: Wed, 23 Feb 2022 22:46:10 +0100 [thread overview]
Message-ID: <20220223214610.q6zmmTgqQHmJPk562que7s1nQwzt78flQS-OBx3Vc58@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22191@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1809 bytes --]
New comment by motorto on void-packages repository
https://github.com/void-linux/void-packages/issues/22191#issuecomment-1049244718
Comment:
So I took a look at the [Debian tagging system](https://packages.debian.org/about/debtags) as recommended by @leahneukirchen and this are the ones they use:
<details>
<summary><u>Debian Tag System</u> (<i>click to expand</i>)</summary>
<!-- have to be followed by an empty line! -->
* accessibility
* admin
* biology
* culture
* devel
* field
* game
* hardware
* implemented-in
* interface
* iso15924
* junior
* made-of
* mail
* network
* office
* privacy
* protocol
* role
* science
* scope
* security
* sound
* special
* suite
* system
* uitoolkit
* use
* web
* works-with
* works-with-format
* x11
</details>
I took some inspiration and created this tag system that I found that is the best one but still leaves some cases behind like for example where should linux-kernel be tagged as ? (maybe a kernel tag):
<details>
<summary><u>Proposed Tag System</u> (<i>click to expand</i>)</summary>
<!-- have to be followed by an empty line! -->
* accessibility - Accessibility Support
* admin - System Administration
* devel - Software Development
* field/science - maybe one for every field type
* astronomy
* aviation
* biology
* computer science
* mathematics
* game - for games
* hardware - for hardware drivers
* junior - apps recommended for young users
* mail - electronic mail
* network - networking (maybe a field/science type ...)
* office - for office apps
* sound/music - for music apps or sound ones (does pipewire/alsa belong here ??)
* Desktop Environment:
* KDE
* GNOME
* XFCE
* etc
* X11
* Wayland
</details>
What do you guys think ?
next prev parent reply other threads:[~2022-02-23 21:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 5:05 [ISSUE] " anjandev
2020-05-22 5:14 ` xmksv
2020-05-23 4:52 ` GithubPrankster
2020-05-24 2:09 ` ericonr
2020-05-24 2:20 ` ericonr
2020-05-24 2:53 ` anjandev
2020-05-24 3:14 ` ericonr
2020-05-26 6:15 ` Anachron
2020-05-26 8:02 ` travankor
2020-05-26 8:41 ` flexibeast
2020-05-26 14:16 ` Vaelatern
2020-05-26 16:28 ` ericonr
2020-05-26 16:29 ` ericonr
2020-05-26 16:29 ` ericonr
2020-05-26 16:39 ` Vaelatern
2020-05-26 17:56 ` Duncaen
2020-05-27 5:15 ` Vaelatern
2020-05-27 19:12 ` pullmoll
2020-05-30 17:53 ` leahneukirchen
2022-02-23 21:45 ` motorto
2022-02-23 21:46 ` motorto [this message]
2022-02-23 22:23 ` tibequadorian
2022-02-23 22:24 ` tibequadorian
2022-02-23 22:24 ` tibequadorian
2022-02-23 22:25 ` tibequadorian
2022-02-24 18:17 ` motorto
2022-02-24 23:14 ` Anachron
2022-05-26 2:13 ` github-actions
2022-06-10 2:13 ` [ISSUE] [CLOSED] " github-actions
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220223214610.q6zmmTgqQHmJPk562que7s1nQwzt78flQS-OBx3Vc58@z \
--to=motorto@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).