[GH-ISSUE #2824] Proposal for tagging of labels #1766

Open
opened 2026-05-05 08:26:18 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @matu3ba on GitHub (Jul 2, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2824

1.information, 2.question are not very specific regarding documentation.
What do you think of guideline,FAQ,appimage,network ?

Originally created by @matu3ba on GitHub (Jul 2, 2019). Original GitHub issue: https://github.com/netblue30/firejail/issues/2824 1.information, 2.question are not very specific regarding documentation. What do you think of **guideline**,**FAQ**,**appimage**,**network** ?
gitea-mirror added the
enhancement
label 2026-05-05 08:26:18 -06:00
Author
Owner

@rusty-snake commented on GitHub (Jul 2, 2019):

splitting up lables/more labels is IMHO a good idea.

old labels new labels
information, question guideline,FAQ,appimage,network
bug bug-profiles, bug-code

let's wait for more feedback.

<!-- gh-comment-id:507712580 --> @rusty-snake commented on GitHub (Jul 2, 2019): splitting up lables/more labels is IMHO a good idea. | old labels | new labels | | --- | --- | | information, question | guideline,FAQ,appimage,network | | bug | bug-profiles, bug-code | let's wait for more feedback.
Author
Owner

@rusty-snake commented on GitHub (Sep 7, 2019):

Q: guideline, Q: FAQ, Q: appimage, Q: network, Q: usage, Q: ...
Profiles: enhancment, C: enhancment
Profiles: bug, C: bug
new-profile (PR)

<!-- gh-comment-id:529095341 --> @rusty-snake commented on GitHub (Sep 7, 2019): Q: guideline, Q: FAQ, Q: appimage, Q: network, Q: usage, Q: ... Profiles: enhancment, C: enhancment Profiles: bug, C: bug new-profile (PR)
Author
Owner

@matu3ba commented on GitHub (May 3, 2020):

I would advise against the notation of Q:, because it is shitty to search fast.
If we want abbreviations, we can still use that.

Fields: documentation/wiki, FAQ, guideline, appimage, network, usage, dbus
Difficulty: difficult, easy,
Area: profiles, control flow, tooling?
Feature handling: feature/enhancement, maintenance, refactor, (speed regression), discussion, BREAKING
Bug handling: review, information-needed, bug,

About tagging OS-specific or program-specific bugs, which we dont want to fix accordingly due to their mess, I am yet unsure.

There is also the conventional commit specification, but I found that to be often abit unsufficient.

<!-- gh-comment-id:623087388 --> @matu3ba commented on GitHub (May 3, 2020): I would advise against the notation of `Q:`, because it is shitty to search fast. If we want abbreviations, we can still use that. Fields: documentation/wiki, FAQ, guideline, appimage, network, usage, dbus Difficulty: difficult, easy, Area: profiles, control flow, tooling? Feature handling: feature/enhancement, maintenance, refactor, (speed regression), discussion, BREAKING Bug handling: review, information-needed, bug, About tagging OS-specific or program-specific bugs, which we dont want to fix accordingly due to their mess, I am yet unsure. There is also the [conventional commit](https://www.conventionalcommits.org/en/v1.0.0-beta.4/) specification, but I found that to be often abit unsufficient.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#1766
No description provided.