mindshare/docs
mindshare/docs
6
1
Fork 3
Code Issues Pull requests 4 Activity Actions

🏗️ events: Create new Antora module

Browse source 
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č
This commit is contained in:
Justin Wheeler 2023-04-27 20:13:00 +00:00
commit 901ce84c4c
12 changed files with 263 additions and 205 deletions
Download patch file Download diff file Expand all files Collapse all files

1
antora.yml
View file

@ -20,3 +20,4 @@ start_page: ROOT:index.adoc
# This lists all the menu definitions of your component.
nav:
- modules/ROOT/nav.adoc
- modules/events/nav.adoc

9
modules/ROOT/nav.adoc
View file

@ -1,14 +1,7 @@
* xref:teams.adoc[Mindshare Teams]
* xref:advocate.adoc[Advocate Program]
* xref:contributor_recruitment/index.adoc[Contributor Recruitment]
* Attending and Holding Events
** xref:release-parties.adoc[Holding a Release Party]
** xref:covid19-guidance.adoc[COVID-19 Guidance]
** xref:small-events.adoc[Small Events ($150)]
** xref:medium-events.adoc[Medium Events ($1000)]
** xref:large-events.adoc[Large Events]
** xref:swag-only-requests.adoc[Swag-only Events]
** xref:event-report-policy.adoc[Event Report Policy]
* xref:event-report-policy.adoc[Event Report Policy]
* Committee Procedures
** xref:procedures/swag.adoc[Creating and Ordering Swag]
** xref:procedures/meetbot.adoc[Meetbot Script]

69
modules/ROOT/pages/covid19-guidance.adoc
View file

@ -1,69 +0,0 @@
= In Person Event Guidance Related to Covid-19
== Overview
NOTE: SUBJECT TO CHANGE
This page holds COVID-19 related guidance for in person events. This applies to Fedorans who are receiving Fedora funding related to events. By receiving funds related in in person events, you are agreeing to the Terms posted at the bottom of this page. The state of the virus is ever changing, so take this information as a general guideline and not hard fact. Feel free to direct any questions to the Mindshare Committee. Contact the Mindshare Committee through chat in https://matrix.to/#/#mindshare:fedoraproject.org[#fedora-mindshare] or by https://pagure.io/mindshare/new_issue[opening a ticket] on the Mindshare repo.
To learn more about requesting funds for Fedora related events, take a look at the https://docs.fedoraproject.org/en-US/mindshare-committee[Mindshare Committee docs].
== What you need to know
=== What is an event?
For the purpose of this page, an event is any internal (Fedora contributors), external (collaborations, partners, neighbor communities), or a mix of both internal/external gathering of people that takes place in person.
This is for all Fedora related events regardless of size, location/region, audience (internal, external), or type (Fedora hosted events or third party events).
=== How will Mindshare evaluate what events to fund?
This is the part that is ever-changing. As we have witnessed, COVID-19 seems to spread, and then we suppress it some, and then evolves and spreads again. Hopefully we will soon see developments that can neutralize COVID-19, or significantly decrease the severity. Until that time, we have to remain flexible.
This means evaluating event funding requests on a case-by-case basis. The Fedora Project must comply with all applicable laws and regulations for events that we sponsor and/or fund.
In order for the Mindshare Committee to make a decision about event related funding the following information will be required along with usual info. Please submit this information when https://pagure.io/mindshare/new_issue[opening an event related ticket] on the Mindshare Committee repo. See below for details.
. Event website
. Specific COVID-19 safety measures that the Event will be implementing
. Approximate number of attendees
. Country where event is taking place
. Will your travel to/from the event bring you across a Country border?
. Local official COVID-19 guidance
=== Safety requirements
Every event is encouraged to follow the highest possible safety standards for the protection of all participants. For example:
* Adherence to third party or venue safety measures that are required.
* Understanding of and adherence to government requirements.
* Vaccination requirements.
* Communication of link:Terms[Terms] to participants of Fedora organized events
Every individual should be aware of and are encouraged to follow the highest possible safety standards for the protection of all participants. For example:
* Adherence to requirements related to traveling and any costs associated(i.e. testing, isolation periods, documentation etc).
* If you become sick with COVID-19 near the time of the funded event, you must test negative before traveling to or participating in any Fedora related events.
== Terms
By receiving funding related to in person events, you agree to the following:
While onsite, you agree to comply with all laws and rules with regard to public health including social distancing protocols and face mask requirements. You acknowledge the health risks associated with the novel coronavirus (COVID-19) outbreak, and the risk of exposure or infection by COVID-19.
Neither Fedora, the event venue, the event organizer, or any of their respective parents, affiliates, sponsors, shareholders, employees, agents, officers, directors, successors, or assignees will be liable for any injury or illness, however caused, arising from, or in any way relate to COVID-19 in connection with the event.
You assume any and all risk, whatsoever, related to any Fedora or Fedora-related event, and release and discharge Fedora, their sponsors, and their agents from any liability to the fullest extent allowed by the law.

55
modules/ROOT/pages/release-parties.adoc
View file

@ -1,55 +0,0 @@
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 https://fedoraproject.org/wiki/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’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.
Hosting Release Parties
~~~~~~~~~~~~~~~~~~~~~~~
_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 https://lists.fedoraproject.org/admin/lists/mindshare@lists.fedoraproject.org/[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 https://pagure.io/mindshare/new_issue?type=releaseparty[_Release Party_ template].
. Once your party is approved, do the following:
https://apps.fedoraproject.org/calendar/Events/[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 https://pagure.io/mindshare/new_issue?title=BadgeforEventName[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 https://pagure.io/fedora-budget/new_issue[Fedora Budget Repository]
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’re going to request swag, plan for 2 weeks for shipping.
Follow the Getting Financial Assistance and Swag section https://docs.fedoraproject.org/en-US/mindshare-committee/advocate/#_getting_swag_or_financial_support[here].
Writing Your Event Report
~~~~~~~~~~~~~~~~~~~~~~~~~~
* *Community Blog* (a.k.a. *CommBlog*): You can https://communityblog.fedoraproject.org/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 https://communityblog.fedoraproject.org/writing-community-blog-article/[guide on publishing articles on the CommBlog].
Here's an example of a https://communityblog.fedoraproject.org/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 check out this https://fedoraproject.org/wiki/Planet?rd=Planet_HowTo['how to'].
Comment on your issue in the https://pagure.io/mindshare/issues[mindshare repo with a link to your event report].

40
modules/ROOT/pages/swag-only-requests.adoc
View file

@ -1,40 +0,0 @@
= Swag Only Requests
If you only need swag to help you hold an event, we have a fast-track policy to help you out.
Anyone can request swag for an event, you don't have to be an Ambassador.
If you're new to Fedora events, checkout our xref:advocate.adoc[Advocate Program].
. Please open a Mindshare ticket in the link:https://pagure.io/mindshare/new_issue[Mindshare Repository].
You need to select the **swag-only** template from the `Type` drop down.
Please complete the fields required.
. Monitor your ticket for questions from the Committee.
. Voting ususally starts very quickly.
The ticket needs to get 2 +1s and no -1s in three days.
When this happens, a committee member will update the ticket with an approved message.
. Open a **swag-shipment** request in the link:https://pagure.io/fedora-budget/issues[Fedora Budget Pagure] using the provided template.
Please allow 2-3 weeks for shipping as swag is generally not stored in your country.
Most of the delay is to allow time for customs processing in your country, not shipping.
. Hold your event!
. Write your event report
+
Fedora Events are often featured in the Mindshare newsletters and hence the event report holds a significant amount of importance.
The report is a general summary of an event which gives the project an idea of what's going on and reports on successes as well as lessons learned.
+
Reporting can be done in many ways.
Here's are a couple of commonly used methods for sharing the event report with the community:
+
* *Community Blog* (a.k.a. *CommBlog*): You can https://communityblog.fedoraproject.org/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 https://communityblog.fedoraproject.org/writing-community-blog-article/[guide on publishing articles on the CommBlog].
Here's an example of a https://communityblog.fedoraproject.org/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, You may syndicate your blog to Fedora Planet.
For more information https://fedoraproject.org/wiki/Planet?rd=Planet_HowTo[check out this 'how to'.]
. Comment on your issue in the https://pagure.io/mindshare/issues[mindshare repo with a link to your event report.]

7
modules/events/nav.adoc Normal file
View file

@ -0,0 +1,7 @@
* Fedora Events
** xref:covid19.adoc[COVID-19 Guidance]
** xref:release-parties.adoc[Release Parties]
** *Tier 0*: xref:requests/swag-only.adoc[Swag-only Events]
** *Tier 1*: xref:requests/small.adoc[Small Events ($150)]
** *Tier 2*: xref:requests/medium.adoc[Medium Events ($1000)]
** *Tier 3*: xref:requests/large.adoc[Large Events]

74
modules/events/pages/covid19.adoc Normal file
View file

@ -0,0 +1,74 @@
include::ROOT:partial$attributes.adoc[]
= In-person event guidance related to COVID-19
:page-aliases: ROOT:covid19-guidance.adoc
[NOTE]
====
SUBJECT TO CHANGE.
====
This page holds COVID-19 related guidance for in person events.
This applies to Fedorans who are receiving Fedora funding related to events.
By receiving funds related to in person events, you are agreeing to the Terms posted at the bottom of this page.
The state of the virus is ever-changing, so take this information as a general guideline and not hard fact.
Feel free to direct any questions to the {team_name}.
Contact the {team_name} through chat in link:{team_synch_communication}[#mindshare:fedoraproject.org] or by link:{team_issue_tracker}[opening a ticket] on the Mindshare repo.
To learn more about requesting funds for Fedora related events, take a look at the xref:mindshare-committee::index.adoc[{team_name} docs].
== What you need to know
=== What is an event?
For the purpose of this page, an event is any internal (Fedora contributors), external (collaborations, partners, neighbor communities), or a mix of both internal/external gathering of people that takes place in person.
This is for all Fedora related events regardless of size, location/region, audience (internal, external), or type (Fedora hosted events or third party events).
=== How will Mindshare evaluate what events to fund?
This is the part that is ever-changing.
As we have witnessed, COVID-19 seems to spread, then we suppress it some, and then evolves and spreads again.
Hopefully we will soon see developments that can neutralize COVID-19, or significantly decrease the severity.
Until that time, we have to remain flexible.
This means evaluating event funding requests on a case-by-case basis.
The Fedora Project must comply with all applicable laws and regulations for events that we sponsor and/or fund.
In order for the {team_name} to make a decision about event related funding the following information will be required along with usual info.
Please submit this information when link:{team_issue_tracker}[opening an event related ticket] on the {team_name} repo.
See below for details:
. Event website
. Specific COVID-19 safety measures that the Event will be implementing
. Approximate number of attendees
. Country where event is taking place
. Will your travel to/from the event bring you across a Country border?
. Local official COVID-19 guidance
=== Safety requirements
Every event is encouraged to follow the highest possible safety standards for the protection of all participants.
For example:
* Adherence to third party or venue safety measures that are required.
* Understanding of and adherence to government requirements.
* Vaccination requirements.
* Communication of link:#terms[Terms] to participants of Fedora organized events
Every individual should be aware of and are encouraged to follow the highest possible safety standards for the protection of all participants.
For example:
* Adherence to requirements related to traveling and any costs associated (i.e. testing, isolation periods, documentation, etc.).
* If you become sick with COVID-19 near the time of the funded event, you must test negative before traveling to or participating in any Fedora related events.
[[terms]]
== Terms
By receiving funding related to in-person events, you agree to the following:
. While onsite, you agree to comply with all laws and rules with regard to public health including social distancing protocols and face mask requirements.
. You acknowledge the health risks associated with the novel coronavirus (COVID-19) outbreak, and the risk of exposure or infection by COVID-19.
. Neither Fedora, the event venue, the event organizer, or any of their respective parents, affiliates, sponsors, shareholders, employees, agents, officers, directors, successors, or assignees will be liable for any injury or illness, however caused, arising from, or in any way relate to COVID-19 in connection with the event.
. You assume any and all risk, whatsoever, related to any Fedora or Fedora-related event, and release and discharge Fedora, their sponsors, and their agents from any liability to the fullest extent allowed by the law.

90
modules/events/pages/release-parties.adoc Normal file
View file

@ -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.

26
modules/ROOT/pages/large-events.adoc → modules/events/pages/requests/large.adoc
View file

@ -1,18 +1,21 @@
include::ROOT:partial$attributes.adoc[]
= Holding or Attending a Large Event
:page-aliases: ROOT:large-events.adoc
While anyone can hold or attend a large Fedora-related event, these events are typically done by experienced Fedora contributors and or existing Fedora Ambassadors.
A large event is one where the budget is over $1000 or the event is generally larger or more complicated.
. Please open a Mindshare ticket in the link:https://pagure.io/mindshare/new_issue[Mindshare Repository].
. Please open a Mindshare ticket in the link:{team_issue_tracker}[Mindshare Repository].
You should use the **advocate** template from the `Type` drop down.
Please complete the fields required.
+
When preparing your ticket, keep these things in mind:
+
* Be clear in what you hope to accomplish and why the event is good for Fedora.
* Help the Mindshare Committee understand how you are qualified to help make this a success.
* Help the {team_name} understand how you are qualified to help make this a success.
You may want to talk about your experience, or contribution history.
* Think about how you will use the budget and what kind of swag support, if any, will help you bue successful.
* Think about how you will use the budget and what kind of swag support, if any, will help you be successful.
We like to see the budget spent directly on the event or attendance and not on swag production.
If you need more budget, we encourage you to team up with a Fedora Ambassador have them sponsor the event and ask for a larger budget.
We are open to you suggesting uses for your budget that make the most sense for you, your area, and the event.
@ -27,7 +30,8 @@ When preparing your ticket, keep these things in mind:
If all committee members vote sooner, the ticket can be approved sooner.
The goal of the eleven day period is to ensure that we have at least one meeting after the discussion period (allowing for holidays, etc.).
. Open a **swag-shipment** request, if you need swag for this event, in the link:https://pagure.io/fedora-budget/issues[Fedora Budget Pagure] using the provided template.
. Open a **swag-shipment** request if you need swag for this event.
Open the request in the link:https://gitlab.com/fedora/mindshare/event-requests[Event Requests repo] using the provided template.
Please allow 2-3 weeks for shipping as swag is generally not stored in your country.
Most of the delay is to allow time for customs processing in your country, not shipping.
@ -41,16 +45,16 @@ The report is a general summary of an event which gives the project an idea of w
Reporting can be done in many ways.
Here's are a couple of commonly used methods for sharing the event report with the community:
+
* *Community Blog* (a.k.a. *CommBlog*): You can https://communityblog.fedoraproject.org/wp-login.php[sign into the Community Blog WordPress site] using your FAS account credentials.
* *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 https://communityblog.fedoraproject.org/writing-community-blog-article/[guide on publishing articles on the CommBlog].
Here's an example of a https://communityblog.fedoraproject.org/fedora-27-release-party-at-taipei/[Fedora 27 release party blog post].
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.
* *Your own Blog*: If you have been maintaining your own blog, you can post it there as well.
To extend the reach of audience, You may syndicate your blog to Fedora Planet.
For more information https://fedoraproject.org/wiki/Planet?rd=Planet_HowTo[check out this 'how to'.]
For more information link:{FWIKI}/Planet[check out this 'how to'].
. Submit a reimbursement request to the link:https://pagure.io/fedora-budget/issues[Fedora Budget Pagure] using the provided template.
. Submit a reimbursement request to the link:https://gitlab.com/fedora/mindshare/event-requests[Event Requests repo] using the provided template.
Reimbursements are typically paid within 2 weeks.
. Comment on your issue in the https://pagure.io/mindshare/issues[mindshare repo with a link to your event report.]
. Comment on your issue in the link:{team_issue_tracker}[Mindshare repo] with a link to your event report.

26
modules/ROOT/pages/medium-events.adoc → modules/events/pages/requests/medium.adoc
View file

@ -1,31 +1,35 @@
include::ROOT:partial$attributes.adoc[]
= Holding or Attending a Medium Event
:page-aliases: ROOT:medium-events.adoc
While anyone can hold or attend a medium Fedora-related event, these events are typically done by experienced Fedora contributors and or existing Fedora Ambassadors.
A medium event is one where the budget is under $1000.
. Please open a Mindshare ticket in the link:https://pagure.io/mindshare/new_issue[Mindshare Repository].
. Please open a Mindshare ticket in the link:{team_issue_tracker}[Mindshare Repository].
You should use the **advocate** template from the `Type` drop down.
Please complete the fields required.
+
When preparing your ticket, keep these things in mind:
+
* Be clear in what you hope to accomplish and why the event is good for Fedora.
* Help the Mindshare Committee understand how you are qualified to help make this a success.
* Help the {team_name} understand how you are qualified to help make this a success.
You may want to talk about your experience, or contribution history.
* Think about how you will use the budget and what kind of swag support, if any, will help you bue successful.
* Think about how you will use the budget and what kind of swag support, if any, will help you be successful.
We like to see the budget spent directly on the event or attendance and not on swag production.
If you need more budget, we encourage you to team up with a Fedora Ambassador have them sponsor the event and ask for a larger budget.
We are open to you suggesting uses for your budget that make the most sense for you, your area, and the event.
. Monitor your ticket for questions from the Committee.
. Voting ususally starts very quickly.
. Voting usually starts very quickly.
The ticket needs to get 3 +1s and no -1s in eleven days.
When this happens, a committee member will update the ticket with an approved message.
If all committee members vote sooner, the ticket can be approved sooner.
The goal of the eleven day period is to ensure that we have at least one meeting during the discussion period (allowing for holidays, etc.).
. Open a **swag-shipment** request, if you need swag for this event, in the link:https://pagure.io/fedora-budget/issues[Fedora Budget Pagure] using the provided template.
. Open a **swag-shipment** request if you need swag for this event.
Open the request in the link:https://gitlab.com/fedora/mindshare/event-requests[Event Requests repo] using the provided template.
Please allow 2-3 weeks for shipping as swag is generally not stored in your country.
Most of the delay is to allow time for customs processing in your country, not shipping.
@ -39,16 +43,16 @@ The report is a general summary of an event which gives the project an idea of w
Reporting can be done in many ways.
Here's are a couple of commonly used methods for sharing the event report with the community:
+
* *Community Blog* (a.k.a. *CommBlog*): You can https://communityblog.fedoraproject.org/wp-login.php[sign into the Community Blog WordPress site] using your FAS account credentials.
* *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 https://communityblog.fedoraproject.org/writing-community-blog-article/[guide on publishing articles on the CommBlog].
Here's an example of a https://communityblog.fedoraproject.org/fedora-27-release-party-at-taipei/[Fedora 27 release party blog post].
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, You may syndicate your blog to Fedora Planet.
For more information https://fedoraproject.org/wiki/Planet?rd=Planet_HowTo[check out this 'how to'.]
For more information link:{FWIKI}/Planet[check out this 'how to'].
. Submit a reimbursement request to the link:https://pagure.io/fedora-budget/issues[Fedora Budget Pagure] using the provided template.
. Submit a reimbursement request to the link:https://gitlab.com/fedora/mindshare/event-requests[Event Requests repo] using the provided template.
Reimbursements are typically paid within 2 weeks.
. Comment on your issue in the https://pagure.io/mindshare/issues[mindshare repo with a link to your event report.]
. Comment on your issue in the link:{team_issue_tracker}[Mindshare repo] with a link to your event report.

26
modules/ROOT/pages/small-events.adoc → modules/events/pages/requests/small.adoc
View file

@ -1,11 +1,14 @@
include::ROOT:partial$attributes.adoc[]
= Holding or Attending a Small Event
:page-aliases: ROOT:small-events.adoc
Anyone can hold or attend a small Fedora-related event, you don't have to be an Ambassador.
A small event is one where the budget is under $150.
The process is exactly the same as for our xref:advocate.adoc[Advocate Program].
The process is exactly the same as for our xref:ROOT:advocate.adoc[Advocate Program].
It is summarized below:
. Please open a Mindshare ticket in the link:https://pagure.io/mindshare/new_issue[Mindshare Repository].
. Please open a Mindshare ticket in the link:{team_issue_tracker}[Mindshare Repository].
You should use the **advocate** template from the `Type` drop down.
Please complete the fields required.
+
@ -15,11 +18,12 @@ We are open to you suggesting uses for your budget that make the most sense for
. Monitor your ticket for questions from the Committee.
. Voting ususally starts very quickly.
. Voting usually starts very quickly.
The ticket needs to get 2 +1s and no -1s in three days.
When this happens, a committee member will update the ticket with an approved message.
. Open a **swag-shipment** request, if you need swag for this event, in the link:https://pagure.io/fedora-budget/issues[Fedora Budget Pagure] using the provided template.
. Open a **swag-shipment** request if you need swag for this event.
Open the request in the link:https://gitlab.com/fedora/mindshare/event-requests[Event Requests repo] using the provided template.
Please allow 2-3 weeks for shipping as swag is generally not stored in your country.
Most of the delay is to allow time for customs processing in your country, not shipping.
@ -33,16 +37,16 @@ The report is a general summary of an event which gives the project an idea of w
Reporting can be done in many ways.
Here's are a couple of commonly used methods for sharing the event report with the community:
+
* *Community Blog* (a.k.a. *CommBlog*): You can https://communityblog.fedoraproject.org/wp-login.php[sign into the Community Blog WordPress site] using your FAS account credentials.
* *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 https://communityblog.fedoraproject.org/writing-community-blog-article/[guide on publishing articles on the CommBlog].
Here's an example of a https://communityblog.fedoraproject.org/fedora-27-release-party-at-taipei/[Fedora 27 release party blog post].
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, You may syndicate your blog to Fedora Planet.
For more information https://fedoraproject.org/wiki/Planet?rd=Planet_HowTo[check out this 'how to'.]
For more information link:{FWIKI}/Planet[check out this 'how to'].
. Submit a reimbursement request to the link:https://pagure.io/fedora-budget/issues[Fedora Budget Pagure] using the provided template.
Reimbursements are typically paid within 2 weeks.
. Submit a reimbursement request to the link:https://gitlab.com/fedora/mindshare/event-requests[Event Requests repo] using the provided template.
Reimbursements are typically paid within 2 weeks.
. Comment on your issue in the https://pagure.io/mindshare/issues[mindshare repo with a link to your event report.]
. Comment on your issue in the link:{team_issue_tracker}[Mindshare repo] with a link to your event report.

45
modules/events/pages/requests/swag-only.adoc Normal file
View file

@ -0,0 +1,45 @@
include::ROOT:partial$attributes.adoc[]
= Swag-Only Requests
:page-aliases: ROOT:swag-only-requests.adoc
If you only need swag to help you hold an event, we have a fast-track policy to help you out.
Anyone can request swag for an event, you don't have to be an Ambassador.
If you are new to Fedora events, checkout our xref:ROOT:advocate.adoc[Advocate Program].
. Please open a Mindshare ticket in the link:{team_issue_tracker}[Mindshare Repository].
You need to select the **swag-only** template from the `Type` drop down.
Please complete the fields required.
. Monitor your ticket for questions from the Committee.
. Voting usually starts quickly.
The ticket needs to get 2 +1s and no -1s in three days.
When this happens, a committee member will update the ticket with an approved message.
. Open a **swag-shipment** request in the link:https://gitlab.com/fedora/mindshare/event-requests[Event Requests repo] using the provided template.
Please allow 2-3 weeks for shipping as swag is generally not stored in your country.
Most of the delay is to allow time for customs processing in your country, not shipping.
. Hold your event!
. Write your event report
+
Fedora Events are often featured in the Mindshare newsletters and hence the event report holds a significant amount of importance.
The report is a general summary of an event which gives the project an idea of what's going on and reports on successes as well as lessons learned.
+
Reporting can be done in many ways.
Here's are a couple of commonly used methods for sharing the event report with the community:
+
* *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.