mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2824] Proposal for tagging of labels #1766
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#1766
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 ?
@rusty-snake commented on GitHub (Jul 2, 2019):
splitting up lables/more labels is IMHO a good idea.
let's wait for more feedback.
@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)
@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.