Help with the Debtags tag editor

Editing on website broken / Help wanted

As of 2020-06-09 it seems like editing in https://debtags.debian.org is broken, see https://bugs.debian.org/876881. When logged in via SSO and submitting changes the AJAX POST to https://debtags.debian.org/api/patch gets a 403 Forbidden.

From IRC (2020-06-10):

<tpo2> Maybe you want to give other people commit access to the
       detabgs-tagsdb project? A lot of categorization/tag
       assignment merges should be only busy-work, so
       potentially a lot of people can take care of that instead
       of you personally?
<enrico> tpo2: currently the tagdb project is fed by the site,
         I'm not sure what happens with the site if changes start
         appearing on it that the site doesn't know
<enrico> tpo2: I'd be very happy to give other people commit
         access to the site

Adding and removing tags

There are only 3 things to know for editing tags:

Searching for tags

There are two ways to search for tags: the "all" view and the "search" view.

The "all" view has a fast, search-as-you-type mechanism that will show you the tags matching our keyword in their name and description. This is useful if you remember part of the name of a tag and you want to look it up.

The "search" view is a different kind of search, designed to answer questions like "what tag can I use for a package that is like this?".

The tagging hints

The tagging hints come from various sources: one is a hardcoded set of general rules, the other is a set of hints that are statistically computed by analysing tagging trends.

The tagging hints are generally right, but in some cases they are not. If you get some wrong suggestion, it is probably because the package fits in some corner case. Corner cases are the reason why these statistical analysis do not add the suggested tags directly, but they just give hints.

Some wrong hints are generally bound to stay: there is currently no way to hide a wrong hint, but it's ok to just leave it there.

Frequently Asked Questions

Many ruby/python/perl library packages provide a shared library, but you use these packages to develop software as well: are they also devel::library?

Since you use them as development libraries, tag them as such: their main role in the system is to be development libraries, and it does not change if they do that by providing a shlib.

When you are tagging, consider the facet as a question: What does the package look like from this point of view?, and then tag as the answer to that question.