🏗️ events: Create new Antora module

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č

modules/events/pages/release-parties.adoc

@@ -0,0 +1,90 @@
+include::ROOT:partial$attributes.adoc[]
+
+= What is a Release Party?
+:page-aliases: ROOT:release-parties.adoc
+
+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]]
+== 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 link:{FWIKI}/Fedora_29_talking_points[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]]
+== 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 link:{team_asynch_communication}[#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 link:{team_issue_tracker}[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 https://apps.fedoraproject.org/calendar/Events/[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 link:{team_issue_tracker}[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, file a reimbursement ticket in the link:https://gitlab.com/fedora/mindshare/event-requests[Event Requests repository].
+
+
+[[assistance-swag]]
+== 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.
+
+Follow the Getting Financial Assistance and Swag section xref:ROOT:advocate.adoc#_getting_swag_or_financial_support[here].
+
+
+[[event-report]]
+== Writing Your Event Report
+
+* *Community Blog* (a.k.a. *CommBlog*):
+  You can link:{COMMBLOG}/wp-login.php[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 link:{COMMBLOG}/writing-community-blog-article/[guide on publishing articles on the CommBlog].
+  Here's an example of a link:{COMMBLOG}/fedora-27-release-party-at-taipei/[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 link:{FWIKI}/Planet[check out this 'how to'].
+
+Comment on your issue in the link:{team_issue_tracker}[Mindshare repo] with a link to your event report.