Justin Wheeler
387f2c9293
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>
4.8 KiB
What is a Release Party?
Release Parties are an informal gathering of community members hosted by Fedora to celebrate a new release. Release parties are a great way to help spread Fedora in your local area and provide an opportunity for Fedora users in your area to come together as a community.
Release parties can be casual events with a few people meeting in a coffee shop or larger events with numerous people in attendance, planned activities, and speakers.
What to do at Release Parties?
There are many things you can do at a Release Party. A typical release party will have the following:
-
Talks/Presentations: Typically talks at release parties are ones that introduce features in the new release of Fedora. If you’re not sure what are the most interesting and important check the Talking points.
-
Question and Answer session: Host a session where people can come and ask questions about Fedora. This can be a great way to help answer people’s questions and learn what common questions are in the community. It is also an opportunity to help people with installs and upgrades. It is OK if you are not an expert. Make this an “audience participation” event and get everyone to help everyone, just like in the rest of Fedora. This is also a great time to show off the various ways to get help online.
-
Live USB Creation Station: Have a machine with you that you can create Live USB images for people on the USB keys they provide. This can be a great way to send someone home with a Live Fedora image they can work with if they are hesitant to commit to an actual Fedora install.
These are just ideas. You are not required to do any or all of them. Focus your party on your audience. For example, if you are hosting a release party at work, have talks focused on the way you use Linux and how that relates to Fedora.
Hosting Release Parties
It is simple to host a Release Party.
When you’re ready, you need to do a few simple things:
-
Post to the #mindshare tag on Fedora Discussion and let the world know what you are planning. Ambassadors and others may have suggestions or advice that can improve your event. This also lets you find others who may want to help you with your event.
-
Open a ticket in the Mindshare issue tracker and let people know about your event. If your event needs financial or swag support (see below), this is a mandatory step. Please use the Release Party template.
-
Once your party is approved, do the following:
-
Add it to the Events Fedocal, so others can find it.
-
Request a QR code to award the Release Party Attendee badge. You can do it by opening an issue at Mindshare issue tracker.
-
Put in a swag request ticket in the Event Requests repo (see below).
-
Finalize your plans and hold your party.
-
-
After your party, write an event report. An event report lets the community know what happened and how it went. Ideally your report will be shared on the Fedora Community Blog, but posting it on your own blog and the Fedora Planet is fine too. If your event requires financial or swag support (see below), this is mandatory. These reports should help us understand what happened and how the party went. Ideas for what went well and what could be improved are welcome.
-
If you have financial assistance approved, submit a reimbursement request by following the Fedora Reimbursement Requests (FRR) process.
Financial Assistance and Swag
Release Parties and should be planned at least 30-40 days in advance. In our experience, events planned with less lead time are generally less successful. If you request swag, plan two weeks for shipping.
Writing Your Event Report
-
Community Blog (a.k.a. CommBlog): You can sign into the Community Blog WordPress site using your FAS account credentials. Once inside, you can create a new post where you can draft your experience. After you are done, follow the steps in the guide on publishing articles on the CommBlog. Here’s an example of a Fedora 27 release party blog post.
-
Your own Blog: If you have been maintaining your own blog, you can post it there as well. To extend the reach of audience, Advocates may syndicate their blog to Fedora Planet. For more information check out this 'how to'.
Comment on your issue in the Mindshare repo with a link to your event report.