mindshare/docs

Fork 3

📝 docs(procedures): Document org-level label schema for issue triage #15

Merged

t0xic0der merged 1 commit from add/labels into main

2026-07-29 03:38:23 +00:00

jflory7 commented

2026-07-13 19:22:32 +00:00

Owner

The Mindshare Committee introduced charter areas in the previous term. Now, we have Forgejo labels (charter/events, charter/recognition, charter/ambassadorship) to triage work against any of the three charter areas.

The labels have also been retroactively applied across both the mindshare/docs and mindshare/tickets repositories. Without docs, new members and contributors have no reference for which labels to use or what the exclusive prefix groups mean. This page serves as the canonical reference so label usage stays consistent as the team grows.

The Mindshare Committee introduced charter areas in the previous term. Now, we have Forgejo labels (`charter/events`, `charter/recognition`, `charter/ambassadorship`) to triage work against any of the three charter areas. The labels have also been retroactively applied across both the `mindshare/docs` and `mindshare/tickets` repositories. Without docs, new members and contributors have no reference for which labels to use or what the exclusive prefix groups mean. This page serves as the canonical reference so label usage stays consistent as the team grows. ![A screenshot of the "Issue & PR Labels on Fedora Forge" documentation page in dark mode, showing navigation sidebars and main content that uses multiple tables to categorize and describe repository labels by Charter area, Needs, Scope, State, and Team.](/attachments/23526e8c-0ee6-4957-b475-76509eb5464a "A screenshot of a Fedora documentation web page titled \"Issue & PR Labels on Fedora Forge,\" displaying various tables that define project labels and their corresponding descriptions.")

image.png

782 KiB

jflory7 added the

labels

2026-07-13 19:22:32 +00:00

jnsamyak was assigned by jflory7

2026-07-13 19:22:32 +00:00

lbazan was assigned by jflory7

2026-07-13 19:22:32 +00:00

t0xic0der was assigned by jflory7

2026-07-13 19:22:32 +00:00

theprogram was assigned by jflory7

2026-07-13 19:22:32 +00:00

jflory7 added 1 commit

2026-07-13 19:22:32 +00:00

📝 docs(procedures): Document org-level label schema for issue triage

Antora docs CI / Build pages (main, mindshare namespace) (pull_request) Has been skipped

Details

Antora docs CI / Build preview (PR) (pull_request) Successful in 9s

Details

ae49157f43

The Mindshare Committee introduced charter areas in the previous term.
Now, we have Forgejo labels (`charter/events`, `charter/recognition`,
`charter/ambassadorship`) to triage work against any of the three
charter areas.

The labels have also been retroactively applied across both the
`mindshare/docs` and `mindshare/tickets` repositories. Without docs, new
members and contributors have no reference for which labels to use or
what the exclusive prefix groups mean. This page serves as the canonical
reference so label usage stays consistent as the team grows.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>

lbazan approved these changes

2026-07-13 19:48:19 +00:00

Dismissed

jflory7 force-pushed add/labels from ae49157f43

Antora docs CI / Build pages (main, mindshare namespace) (pull_request) Has been skipped

Details

Antora docs CI / Build preview (PR) (pull_request) Successful in 9s

Details

to 53d93927ae

Antora docs CI / Build pages (main, mindshare namespace) (pull_request) Has been skipped

Details

Antora docs CI / Build preview (PR) (pull_request) Successful in 9s

Details

2026-07-13 19:51:38 +00:00

Compare

lbazan approved these changes

2026-07-13 20:02:37 +00:00

jnsamyak approved these changes

2026-07-14 03:24:02 +00:00

jnsamyak left a comment

The page explains what each label means, but doesn't really touch on who applies them or when. Does the reporter pick scope labels, or does someone add them during triage? Even a line or two would help New folks figure out what to do when they're looking at an issue.
needs/ being exclusive surprised me a bit. Can an issue really only need one thing at a time? Seems like something could need both reporter feedback and a vote. If that's intentional, a quick note worth mentioning where these labels are actually managed (org-level settings in Forgejo) so someone knows where to go if they need to add or change one.

Happy to see this page exists! These are not blocking changes, but my suggestions 0/

- The page explains what each label means, but doesn't really touch on who applies them or when. Does the reporter pick scope labels, or does someone add them during triage? Even a line or two would help New folks figure out what to do when they're looking at an issue. - needs/ being exclusive surprised me a bit. Can an issue really only need one thing at a time? Seems like something could need both reporter feedback and a vote. If that's intentional, a quick note worth mentioning where these labels are actually managed (org-level settings in Forgejo) so someone knows where to go if they need to add or change one. Happy to see this page exists! These are not blocking changes, but my suggestions 0/

t0xic0der approved these changes

2026-07-14 05:42:22 +00:00

t0xic0der left a comment

LGTM on cursory glance.

The page explains what each label means, but doesn't really touch on who applies them or when. Does the reporter pick scope labels, or does someone add them during triage? Even a line or two would help New folks figure out what to do when they're looking at an issue.

+1 @jnsamyak. Could be scoped into this PR or on a different one as long as we track it on an issue ticket.

needs/ being exclusive surprised me a bit. Can an issue really only need one thing at a time? Seems like something could need both reporter feedback and a vote. If that's intentional, a quick note worth mentioning where these labels are actually managed (org-level settings in Forgejo) so someone knows where to go if they need to add or change one.

If something needs reporter feedback then I do not suppose it would be ready for voting, would it? I mean, the very reason we are requesting for reporter feedback is because we do not have enough info to vote on it. Also, IMHO the documentation request on the label management feels irrelevant here because that would be more related to general Fedora Forge tooling.

LGTM on cursory glance. > The page explains what each label means, but doesn't really touch on who applies them or when. Does the reporter pick scope labels, or does someone add them during triage? Even a line or two would help New folks figure out what to do when they're looking at an issue. +1 @jnsamyak. Could be scoped into this PR or on a different one as long as we track it on an issue ticket. > needs/ being exclusive surprised me a bit. Can an issue really only need one thing at a time? Seems like something could need both reporter feedback and a vote. If that's intentional, a quick note worth mentioning where these labels are actually managed (org-level settings in Forgejo) so someone knows where to go if they need to add or change one. If something needs reporter feedback then I do not suppose it would be ready for voting, would it? I mean, the very reason we are requesting for reporter feedback is because we do not have enough info to vote on it. Also, IMHO the documentation request on the label management feels irrelevant here because that would be more related to general Fedora Forge tooling.

t0xic0der commented

2026-07-29 03:36:17 +00:00

Owner

Three approvals? Merging this!

t0xic0der merged commit d32054e0b8 into main

2026-07-29 03:38:23 +00:00

t0xic0der deleted branch add/labels

2026-07-29 03:38:23 +00:00

t0xic0der referenced this pull request from a commit

2026-07-29 03:38:24 +00:00

📝 docs(procedures): Document org-level label schema for issue triage (!15)