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.
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’s also an opportunity to help people with installs and upgrades.It’s OK if you’re 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’re not required to do any or all of them. Focus your party on your audience. For example, if you’re hosting a release party at work, have talks focused on the way you use Linux and how that relates to Fedora.
It’s simple to host a Release Party
When you’re ready, you need to do a few simple things: . Send an email to the mindshare mailing list and let the world know what you’re 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 crucial (and mandatory) step. Please use the Release Party template. . Once your party is approved, do the following: calendar, so others can easily find it. .. Request a QR code to award the Release Party Attendee badge. You can do it by opening an issue at mindshare pagure .. Put in a swag request ticket in the Fedora Budget 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, file a reimbursement ticket in the Fedora Budget Repository
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’re going to request swag, plan for 2 weeks for shipping.
Follow the Getting Financial Assistance and Swag section here.
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.