mindshare/tickets
mindshare/tickets
6
1
Fork 0
Code Issues 19 Pull requests 1 Projects Activity

🚚 Issue templates: Migrate from GitLab to Forgejo YAML form format #125

Merged
jflory7 merged 2 commits from fix/issue-templates into main 2026-05-29 08:29:05 +00:00
Conversation 10 Commits 2 Files changed 12 +625 -208
jflory7 commented 2026-05-22 07:01:40 +00:00
Owner
Copy link

The Fedora Mindshare Committee repository moved from GitLab to Fedora Forge at forge.fedoraproject.org. GitLab issue templates (Markdown with /labels quick actions) do not function on Forgejo, so all templates are converted to Forgejo's YAML form template format.

Key changes in this migration:

  • Convert five templates to YAML form format with structured inputs (typed fields, dropdowns, required-field validation) instead of fill-in-the-blank Markdown
  • Drop the Hopin request template (Hopin is no longer in use)
  • Add auto-labels to all templates via YAML frontmatter (previously only the two event templates had labels via GitLab quick actions)
  • Surface HTML comments from the originals as visible guidance text in markdown form elements
  • Add config.yml with contact links to Mindshare Committee Discourse and Matrix channels, shown on the "New Issue" chooser page
  • Use Forgejo's / exclusive-label separator (replacing GitLab's :: format)

Label assignments per template:

  • small-events: ?/needs committee vote, category/physical events, team/advocates
  • medium-large-events: ?/needs committee vote, category/physical events, team/ambassadors
  • limesurvey: ?/needs committee vote, category/limesurvey
  • release-party: ?/needs committee vote, category/physical events
  • swag-only: ?/needs committee vote, category/swag
The Fedora Mindshare Committee repository moved from GitLab to Fedora Forge at forge.fedoraproject.org. GitLab issue templates (Markdown with `/labels` quick actions) do not function on Forgejo, so all templates are converted to Forgejo's YAML form template format. **Key changes in this migration:** - Convert five templates to YAML form format with structured inputs (typed fields, dropdowns, required-field validation) instead of fill-in-the-blank Markdown - Drop the Hopin request template (Hopin is no longer in use) - Add auto-labels to all templates via YAML frontmatter (previously only the two event templates had labels via GitLab quick actions) - Surface HTML comments from the originals as visible guidance text in `markdown` form elements - Add `config.yml` with contact links to Mindshare Committee Discourse and Matrix channels, shown on the "New Issue" chooser page - Use Forgejo's `/` exclusive-label separator (replacing GitLab's `::` format) **Label assignments per template:** - _small-events:_ `?/needs committee vote`, `category/physical events`, `team/advocates` - _medium-large-events:_ `?/needs committee vote`, `category/physical events`, `team/ambassadors` - _limesurvey:_ `?/needs committee vote`, `category/limesurvey` - _release-party:_ `?/needs committee vote`, `category/physical events` - _swag-only:_ `?/needs committee vote`, `category/swag`
jflory7 self-assigned this 2026-05-22 07:01:40 +00:00 
The Fedora Mindshare Committee repository moved from GitLab to Fedora
Forge at forge.fedoraproject.org. GitLab issue templates (Markdown with
`/labels` quick actions) do not function on Forgejo, so all templates
are converted to Forgejo's YAML form template format.

Key changes in this migration:

- Convert five templates to YAML form format with structured inputs
  (typed fields, dropdowns, required-field validation) instead of fill-
  in-the-blank Markdown
- Drop the Hopin request template (Hopin is no longer in use)
- Add auto-labels to all templates via YAML frontmatter (previously only
  the two event templates had labels via GitLab quick actions)
- Surface HTML comments from the originals as visible guidance text in
  `markdown` form elements
- Add `config.yml` with contact links to Mindshare Committee Discourse
  and Matrix channels, shown on the "New Issue" chooser page
- Use Forgejo's `/` exclusive-label separator (replacing GitLab's `::`
  format)

Label assignments per template:
  small-events:        ?/needs committee vote, category/physical events,
                       team/advocates
  medium-large-events: ?/needs committee vote, category/physical events,
                       team/ambassadors
  limesurvey:          ?/needs committee vote, category/limesurvey
  release-party:       ?/needs committee vote, category/physical events
  swag-only:           ?/needs committee vote, category/swag

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
jflory7 added the due date 2026-05-28 2026-05-22 07:01:54 +00:00
lbazan approved these changes 2026-05-23 13:12:04 +00:00
Dismissed
lbazan left a comment
Copy link

+1

+1
lbazan approved these changes 2026-05-23 13:12:48 +00:00
Dismissed
t0xic0der requested changes 2026-05-25 03:24:40 +00:00
Dismissed
t0xic0der left a comment
Copy link

Thanks for working on this, @jflory7, even while being very occupied.

Here's some suggestions - Let me know if you want me to apply them.

Thanks for working on this, @jflory7, even while being very occupied. Here's some suggestions - Let me know if you want me to apply them.
.forgejo/issue_template/limesurvey.yml Outdated
@ -0,0 +52,4 @@
- type: input
id: related-ticket
attributes:
label: Pagure ticket, Wiki Page, or related event
t0xic0der commented 2026-05-25 03:18:27 +00:00
Owner
Copy link

Say Fedora Forge instead of Pagure.

Say `Fedora Forge` instead of `Pagure`.
👍 1
jflory7 commented 2026-05-28 10:06:08 +00:00
Author
Owner
Copy link

Good catch! Will fix.

Good catch! Will fix.
jflory7 marked this conversation as resolved
.forgejo/issue_template/medium-large-events.yml
@ -0,0 +107,4 @@
attributes:
label: Support requested
description: Select all types of support that apply.
multiple: true
t0xic0der commented 2026-05-25 03:23:28 +00:00
Owner
Copy link

Thank you for doing menu list selection thing!

Quite an improvement over the "ReMoVe AlL tHaT dO nOt ApPlY" monkey business

Thank you for doing menu list selection thing! Quite an improvement over the "ReMoVe AlL tHaT dO nOt ApPlY" monkey business
🎉 1
jflory7 marked this conversation as resolved
.forgejo/issue_template/medium-large-events.yml Outdated
@ -0,0 +152,4 @@
- type: markdown
attributes:
value: |
## This event &amp; Fedora
t0xic0der commented 2026-05-25 03:21:16 +00:00
Owner
Copy link

Write & directly instead of &amp;.

Hmm, but maybe use and instead?

Write `&` directly instead of `&amp;`. Hmm, but maybe use `and` instead?
👍 1
jflory7 commented 2026-05-28 10:06:01 +00:00
Author
Owner
Copy link

Oh no, the AI slop got me here 🌚 Good catch, and I will fix this.

Oh no, the AI slop got me here 🌚 Good catch, and I will fix this.
😆 1
jflory7 marked this conversation as resolved
.forgejo/issue_template/release-party.yml
@ -0,0 +6,4 @@
body:
- type: markdown
attributes:
value: |
t0xic0der commented 2026-05-25 03:16:50 +00:00
Owner
Copy link

The Bangalore release party example was dropped.

FL29 Release Party example was anyway too old.

But we should still provide them with newer examples.

What do you think?

The Bangalore release party example was dropped. FL29 Release Party example was anyway too old. But we should still provide them with newer examples. What do you think?
👍 1
jflory7 commented 2026-05-28 21:39:54 +00:00
Author
Owner
Copy link

This is worthwhile, but maybe someone with a bit more time than I have could get this in a follow-up PR? #good-first-issue

This is worthwhile, but maybe someone with a bit more time than I have could get this in a follow-up PR? `#good-first-issue`
.forgejo/issue_template/small-events.yml
@ -0,0 +3,4 @@
labels:
- "?/needs committee vote"
- "category/physical events"
- "team/advocates"
t0xic0der commented 2026-05-25 03:11:50 +00:00
Owner
Copy link

This should be team/ambassadors, no?

This should be `team/ambassadors`, no?
jflory7 commented 2026-05-28 10:06:58 +00:00
Author
Owner
Copy link

Actually, for small events, this is technically the right fit for Advocates because Ambassadors are permissioned to do medium and large events. Anyone can do a small event without being a "full" Ambassador.

Actually, for small events, this is technically the right fit for Advocates because Ambassadors are permissioned to do medium and large events. Anyone can do a small event without being a "full" Ambassador.
jflory7 marked this conversation as resolved
.forgejo/issue_template/small-events.yml Outdated
@ -0,0 +119,4 @@
- type: markdown
attributes:
value: |
## This event &amp; Fedora
t0xic0der commented 2026-05-25 03:21:32 +00:00
Owner
Copy link

Write & directly instead of &amp;.

Hmm, but maybe use and instead?

Write `&` directly instead of `&amp;`. Hmm, but maybe use `and` instead?
👍 2
lbazan marked this conversation as resolved
lbazan approved these changes 2026-05-28 12:29:39 +00:00
lbazan left a comment
Copy link

+1

+1
The initial migration from GitLab to Forgejo carried over a stale
"Pagure" reference in the LimeSurvey template's related-ticket label and
the HTML entity `&amp;` leaked into section headings in both event
templates. These were likely artifacts from a prior Markdown-to-YAML
conversion step that encoded the ampersand as an HTML entity rather
than writing plain text.

Changed "Pagure ticket" to "Fedora Forge ticket" in `limesurvey.yml`,
and replaced `&amp;` with the word "and" in the "This event and Fedora"
section headings in both `small-events.yml` and
`medium-large-events.yml`, per reviewer preference.

Addresses review feedback from Akashdeep Dhar (@t0xic0der) on PR #125.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
jflory7 commented 2026-05-28 21:59:01 +00:00
Author
Owner
Copy link

Re: review comment — Say Fedora Forge instead of Pagure

Fixed in 05b6cc3. Changed "Pagure ticket" to "Fedora Forge ticket."

This comment posted on Justin's behalf with Claude Code Opus 4.6.

Re: [review comment](https://forge.fedoraproject.org/mindshare/tickets/pulls/125#issuecomment-759854) — Say `Fedora Forge` instead of `Pagure` Fixed in [`05b6cc3`](https://forge.fedoraproject.org/mindshare/tickets/commit/05b6cc33cc331ed354d66ca73f04a66fac130658). Changed "Pagure ticket" to "Fedora Forge ticket." _This comment posted on Justin's behalf with Claude Code Opus 4.6._
jflory7 commented 2026-05-28 21:59:03 +00:00
Author
Owner
Copy link

Re: review comment — Write & directly instead of &amp;

Fixed in 05b6cc3. Went with "and" per your suggestion — reads better and avoids any YAML encoding ambiguity.

This comment posted on Justin's behalf with Claude Code Opus 4.6.

Re: [review comment](https://forge.fedoraproject.org/mindshare/tickets/pulls/125#issuecomment-759855) — Write `&` directly instead of `&amp;` Fixed in [`05b6cc3`](https://forge.fedoraproject.org/mindshare/tickets/commit/05b6cc33cc331ed354d66ca73f04a66fac130658). Went with "and" per your suggestion — reads better and avoids any YAML encoding ambiguity. _This comment posted on Justin's behalf with Claude Code Opus 4.6._
jflory7 commented 2026-05-28 21:59:05 +00:00
Author
Owner
Copy link

Re: review comment — Write & directly instead of &amp;

Also fixed in 05b6cc3. Same change applied here — "and" instead of &amp;.

This comment posted on Justin's behalf with Claude Code Opus 4.6.

Re: [review comment](https://forge.fedoraproject.org/mindshare/tickets/pulls/125#issuecomment-759856) — Write `&` directly instead of `&amp;` Also fixed in [`05b6cc3`](https://forge.fedoraproject.org/mindshare/tickets/commit/05b6cc33cc331ed354d66ca73f04a66fac130658). Same change applied here — "and" instead of `&amp;`. _This comment posted on Justin's behalf with Claude Code Opus 4.6._
jflory7 commented 2026-05-28 22:00:05 +00:00
Author
Owner
Copy link

@t0xic0der @lbazan Please take another look? I think this PR is ready.

@t0xic0der @lbazan Please take another look? I think this PR is ready.
t0xic0der approved these changes 2026-05-29 02:07:03 +00:00
t0xic0der left a comment
Copy link

LGTM.

If things slip through, we can probably fix them later.

LGTM. If things slip through, we can probably fix them later.
jflory7 commented 2026-05-29 08:28:52 +00:00
Author
Owner
Copy link

Thanks @t0xic0der! I'm going to merge now. @lbazan can use the new templates for reopening the previous event request we discussed yesterday.

Thanks @t0xic0der! I'm going to merge now. @lbazan can use the new templates for reopening the previous event request we discussed yesterday.
👍 2
jflory7 deleted branch fix/issue-templates 2026-05-29 08:29:05 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
ekidney
joseph
gwmngilfen
lbazan
t0xic0der
Labels
Clear labels   
category
budget
 Related to the Mindshare Committee spending allocation and budget management

  
category
docs
 Improving documentation about the Fedora Mindshare Committee or community processes

  
category
limesurvey
 Requests for using Fedora's LimeSurvey instance for community surveys and polls

  
category
meta
 Improvements and changes to the Fedora Mindshare Committee itself

  
category
physical events
 Requests, planning, & other organizing for a physical event presence

  
category
swag
 Management, distribution, and purchasing of Fedora-branded swag and merchandise

  
category
virtual events
 Planning and organizing our virtual event presences

  
charter
ambassadorship
 Promote Fedora, its projects, and its values by actively interacting with and fostering engagement within online communities

  
charter
events
 Support and coordinate budget requests for events in each region, acting as a liaison between the regions, the FCA, and the wider committee

  
charter
recognition
 Recognize the efforts of contributors across the project by working with project teams to reward contributions

  
good first issue
Good tickets to begin with (if you want to get involved, try working on one of these!)

  
help wanted
Tickets where we need help or need feedback from the wider Fedora community

  
needs
event report
 An event request that needs a published event report before closing as complete

  
needs
reporter feedback
 Additional feedback or information from the reporter is needed to advance

  
needs
vote
 A vote is required from Mindshare Committee members in order to advance

  
scope
bug
 Something isn't working

  
scope
improvement
 Requests for something we are either repeating or improving

  
scope
new
 Requests for something brand new that has not been done before

  
state
approved
 Tickets that received approval by the Fedora Mindshare Committee

  
state
blocked
 Cannot move forward: blocked by feedback, other tickets, etc.

  
state
duplicate
 This issue or pull request already exists

  
state
invalid
 This doesn't seem right

  
state
wontfix
 This will not be worked on

  
team
advocates
 Requests, tickets, & discussions about Fedora Advocates

  
team
ambassadors
 Requests, tickets, & discussions about Fedora Ambassadors

  
team
commops
 Requests, tickets, & discussions about Fedora Community Operations (CommOps)

  
team
council
 Requests, tickets, & discussions about the Fedora Council

  
team
design
 Requests, tickets, & discussions about the Fedora Design Team

  
team
docs
 Requests, tickets, & discussions about the Fedora Documentation Team

  
team
g11n
 Requests, tickets, & discussions about the Fedora Globalization Team (including Localization and Internationalization)

  
team
marketing
 Requests, tickets, & discussions about the Fedora Marketing Team

  
team
mindshare
 Requests, tickets, & discussions about the Fedora Mindshare Committee itself

  
team
websites-apps
 Requests, tickets, & discussions about the Fedora Websites & Apps Team

No labels
category
budget
category
docs
category
limesurvey
category
meta
category
physical events
category
swag
category
virtual events
charter
ambassadorship
charter
events
charter
recognition
good first issue
help wanted
needs
event report
needs
reporter feedback
needs
vote
scope
bug
scope
improvement
scope
new
state
approved
state
blocked
state
duplicate
state
invalid
state
wontfix
team
advocates
team
ambassadors
team
commops
team
council
team
design
team
docs
team
g11n
team
marketing
team
mindshare
team
websites-apps
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
jflory7
ekidney
gwmngilfen
joseph
lbazan
t0xic0der
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

2026-05-28

Dependencies

No dependencies set.

Reference
mindshare/tickets!125
No description provided.