Nixpkgs: Add more topic labels (was: [Nix-dev] Skillset labels)

[rasendubi]

Moved from the mailing list (http://lists.science.uu.nl/pipermail/nix-dev/2016-July/021181.html).

The original proposal was to add skill labels, however, I find they are mostly covered by 6.topic: labels. Currently, we have next labels:

• closure-size
• darwin
• emacs
• erlang
• gnome3
• golang
• grsecurity
• haskell
• hygiene
• kernel
• nixos
• non-nixos
• policy discussion
• printing
• python
• qt/kde
• reproducible builds
• ruby
• rust
• usability
• user experience
• vim

Out of those proposed on ML, next are not covered:

• shell
• javascript
• erlang
• c/c++
• build toolchain
• systemd
• containers
• virtualization
• nixos tests
• module system
• java
• tex
• perl
• cross-compilation

Questions I have are:

• should we add a separate skill label?
• any other labels to add?

/cc @wmertens @Profpatsch @danbst @matthiasbeyer

[wmertens]

I wouldn't mind renaming all topic labels to skill, to make things more obvious.

[vcunat]

/participate

[joachifm]

Suggestions for new topic labels off the top of my head: ocaml, graphics (or some variation thereof), games (or some variation thereof), typesetting (potentially subsumed by tex), fonts.

Also, the Review, Done, Backlog, and Working labels seem to be virtually unused --- can they be pruned?

[domenkozar]

@joachifm 0 - Backlog is just an indicator for the label category.

[groxxda]

We should clarify what "needs: feedback" means and maybe split it into two separate labels to distinguish whether feedback from maintainer or reporter is needed.

[vcunat]

I think feedback from _reporter_ was meant originally. That's a typical bug tag, called e.g. "moreinfo" or "needinfo". Creating some reference like https://www.debian.org/Bugs/Developer would help.

[NeQuissimus]

Since I've been applying labels like a madman, I've noticed a few things:

• What is the difference between "Usability" and "User experience"?
• We need "needs: Investigation" and "needs: Maintainer feedback"
• I would keep "topic" instead of turning them into "skill"
• Labeling "good first bug" more often may invite more contributions, we have been bad at using that label :)
• Some labels are PR-specific, some are issue-specific; not sure how you could mark them as such

[groxxda]

Can we rename "needs: feedback" to "needs: reporter-feedback" then?

[vcunat]

Renamed and added "needs: community feedback". Some probably now have the wrong of those two, so we at least can switch.

[NeQuissimus]

:D

[vcunat]

"usability" had fewer tickets than "user experience", so I replaced the former by the latter (by hand).

[vcunat]

I see no "needs: investigation" (anymore?).

[NeQuissimus]

Because we need that!

[vcunat]

I see; maybe we do. We also have various tiny issues that would take disproportionately lots of work to fix and thus noone wants to do it, but I don't see how a label could help it.

[mmahut]

Are there any updates on this issue, please

[stale[bot]]

Thank you for your contributions.

This has been automatically marked as stale because it has had no activity for 180 days.

If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.

Here are suggestions that might help resolve this more quickly:

1. Search for maintainers and people that previously touched the related code and @ mention them in a comment.
2. Ask on the NixOS Discourse.
3. Ask on the #nixos channel on irc.freenode.net.

[wmertens]

Is this still a good idea?

If yes, we should make an RFC - if no, we can close.

I'm OK to close, not sure any more if these extra skill labels will make any difference in participation and managing the labels takes extra time and knowledge