From: Fabio Pesari <fabiop@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Alex Kost <alezost@gmail.com>
Subject: Re: Adding tags to packages
Date: Sun, 3 Jan 2016 16:31:04 +0100 [thread overview]
Message-ID: <56893EB8.6010500@gnu.org> (raw)
In-Reply-To: <87si2esnzi.fsf@gnu.org>
On 01/03/2016 04:04 PM, Ludovic Courtès wrote:
>
> Maintaining tags means agreeing on a set of tags and adjusting it as we
> see fit, adding tags to existing packages, reviewing them for new
> packages, etc.
I can see why this might sound like a lot of work, but what if all
distros worked together on a common database? It's a problem all package
repositories have, after all, and there's no need to have multiple
people write tags for the same packages over and over.
The Free Software Directory could be used for that purpose, and tags
could be generated from its categories by using the MediaWiki API.
For this purpose, some works needs to be done on the FSD. For example:
https://directory.fsf.org/wiki/Nethack
Nethack isn't really an adventure game, and "Game:roguelike" should also
be a category, but I think that this could work (and as a result of it,
the FSD would gain more contributions and exposure).
next prev parent reply other threads:[~2016-01-03 15:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 19:45 Adding tags to packages Fabio Pesari
2016-01-03 9:02 ` Alex Kost
2016-01-03 14:20 ` Ludovic Courtès
2016-01-03 14:34 ` Fabio Pesari
2016-01-03 15:04 ` Ludovic Courtès
2016-01-03 15:31 ` Fabio Pesari [this message]
2016-01-03 22:37 ` Ludovic Courtès
2016-01-03 14:33 ` Ludovic Courtès
2016-01-03 16:22 ` Ricardo Wurmus
2016-01-03 17:15 ` Ludovic Courtès
2016-01-04 9:19 ` Pjotr Prins
2016-01-04 23:30 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2015-07-08 7:41 Pjotr Prins
2015-07-08 9:24 ` John Darrington
2015-07-08 12:55 ` Ludovic Courtès
2015-07-08 13:55 ` Pjotr Prins
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56893EB8.6010500@gnu.org \
--to=fabiop@gnu.org \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
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).