Refresh the Fedora Mindshare Committee event request guidelines for 2026
and the migration to Forgejo.
Content changes
===============
* Migrate all issue template URLs from GitLab (`?issuable_template=`)
to Forgejo (`?template=.forgejo/issue_template/`) format.
* Replace stale GitLab `event-requests` repo links: swag requests now
point to the Mindshare Committee Tickets tracker, reimbursements now
`xref` the Fedora Reimbursement Requests (FRR) policy page.
* Update the Discourse tag URL in shared attributes to include the right
Fedora Discussion category with the tag.
* Document that approved tickets receive the `state/approved` label
instead of a freeform "approved message."
* Better explain what is considered a recognized vote by a Committee
member.
* Eliminate cross-links to the Advocate Program, which has not been
reviewed since 2018/2019.
* Provide accepted methods for how to share an event report, making it
more clear that only these methods are valid.
Antora partial restructuring
=============================
* Strip headers and anchors from all partials so they are plain reusable
text snippets. Headers and anchors now live in the event request pages
themselves, giving each page full control over its document hierarchy
and table of contents.
* Rename partial files to drop the `step0N-*` prefix, using descriptive
names only (e.g. `open-ticket-small-events.adoc`,
`committee-vote-medium-events.adoc`, etc.).
Props to @nmilosev for bringing attention to the outdated documentation
and @pbokoc for calling that this would happen some time back.
Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
This commit changes the information architecture of event-related
documentation in the Mindshare Committee docs site. Content was changed
minimally; most changes were to mention GitLab instead of Pagure or to
use Discourse/Matrix instead of mailing lists/IRC.
Additionally, the pages in this section now use attributes for several
links. In the event that a link changes in the future, it will be easier
to update URLs from a single place instead of several links becoming
outdated.
I chose to separate the events documentation into a new module because
it provides a greater degree of separation from other content published
in the Mindshare Committee documentation. It can exist as a more
independent part of our docs instead of getting grouped together with
Committee procedures, policies, and onboarding guidance for members.
Signed-off-by: Justin W. Flory (he/him) <jwf@redhat.com>
Use Camel Case in the navfile
Petr Bokoč