📝 events: 2026 refresh of event request guidelines
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 is contained in:
parent
fe609689e3
commit
44be9eda82
GPG key ID:
7748B15FA8FA4C7E
18 changed files with 269 additions and 192 deletions
|
|
@ -14,7 +14,7 @@
|
|||
:team_status: Active
|
||||
|
||||
// Preferred asynchronous communication channel
|
||||
:team_asynch_communication: https://discussion.fedoraproject.org/tag/mindshare
|
||||
:team_asynch_communication: https://discussion.fedoraproject.org/tags/c/project/7/mindshare/292
|
||||
|
||||
// Preferred synchronous communication channel
|
||||
:team_synch_communication: https://matrix.to/#/#mindshare:fedoraproject.org
|
||||
|
|
@ -25,6 +25,11 @@
|
|||
// Meetings
|
||||
:team_meetings: https://apps.fedoraproject.org/calendar/mindshare/
|
||||
|
||||
// Approved budget amounts
|
||||
:event_budget_small: maximum $150 USD
|
||||
:event_budget_medium: maximum $1000 USD
|
||||
:event_budget_large: over $1000 USD
|
||||
|
||||
// Miscellaneous data
|
||||
:COMMBLOG: https://communityblog.fedoraproject.org
|
||||
:FISCALYEAR: CY26
|
||||
|
|
|
|||
|
|
@ -0,0 +1,3 @@
|
|||
include::ROOT:partial$attributes.adoc[]
|
||||
|
||||
Comment on your issue in the link:{team_issue_tracker}[team issue tracker] with a link to your final event report.
|
||||
|
|
@ -0,0 +1,10 @@
|
|||
include::ROOT:partial$attributes.adoc[]
|
||||
|
||||
Discussion and voting starts after the ticket is opened.
|
||||
Once all questions are answered, a vote will be called for.
|
||||
The ticket must receive *three +1 votes and zero -1 votes in eleven days*.
|
||||
A {team_name} member casts a vote by leaving an explicit comment on the ticket by top-posting "+1", "+0", or "-1".
|
||||
After voting concludes, a {team_name} member will add the `state/approved` label to the ticket to indicate that it is officially approved by the Committee.
|
||||
|
||||
If all {team_name} members vote sooner, the ticket can be approved sooner.
|
||||
The goal of the eleven-day voting period is to ensure there is at least one meeting during the discussion period (allowing for holidays, etc.).
|
||||
|
|
@ -0,0 +1,9 @@
|
|||
include::ROOT:partial$attributes.adoc[]
|
||||
|
||||
Discussion and voting starts after the ticket is opened.
|
||||
The ticket must receive *three +1 votes and zero -1 votes in eleven days*.
|
||||
A {team_name} member casts a vote by leaving an explicit comment on the ticket by top-posting "+1", "+0", or "-1".
|
||||
After voting concludes, a {team_name} member will add the `state/approved` label to the ticket to indicate that it is officially approved by the Committee.
|
||||
|
||||
If all {team_name} members vote sooner, the ticket can be approved sooner.
|
||||
The goal of the eleven-day voting period is to ensure there is at least one meeting during the discussion period (allowing for holidays, etc.).
|
||||
|
|
@ -0,0 +1,7 @@
|
|||
include::ROOT:partial$attributes.adoc[]
|
||||
|
||||
Voting starts after the ticket is opened.
|
||||
Small Events tickets must receive *two +1 votes and zero -1 votes in three days*.
|
||||
|
||||
A {team_name} member casts a vote by leaving an explicit comment on the ticket, usually by top-posting "+1", "+0", or "-1".
|
||||
After the voting period concludes, a {team_name} member will add the `state/approved` label to the ticket to indicate that it is officially approved by the Committee.
|
||||
|
|
@ -0,0 +1,14 @@
|
|||
include::ROOT:partial$attributes.adoc[]
|
||||
|
||||
Write your event report.
|
||||
Reporting can be done in many ways.
|
||||
Here are accepted methods for sharing the event report with the community:
|
||||
|
||||
* *Community Blog* (AKA *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, you may syndicate your blog to Fedora Planet.
|
||||
For more information on how to syndicate, link:{FWIKI}/Planet[check out this 'how to'].
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
include::ROOT:partial$attributes.adoc[]
|
||||
|
||||
Hold your event!
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
include::ROOT:partial$attributes.adoc[]
|
||||
|
||||
Monitor your ticket for questions from the {team_name}.
|
||||
|
|
@ -0,0 +1,15 @@
|
|||
include::ROOT:partial$attributes.adoc[]
|
||||
|
||||
Open a {team_name} ticket in the link:{team_issue_tracker}[team issue tracker].
|
||||
Click link:{team_issue_tracker}/issues/new?template=.forgejo%2fissue_template%2fmedium-large-events.yml[*here*] to open the ticket template.
|
||||
Complete the ticket template fully.
|
||||
|
||||
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 {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 be successful.
|
||||
If you require larger budget, we encourage you to team up with a Fedora Ambassador.
|
||||
A Fedora Ambassador can 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.
|
||||
|
|
@ -0,0 +1,10 @@
|
|||
include::ROOT:partial$attributes.adoc[]
|
||||
|
||||
Open a {team_name} ticket in the link:{team_issue_tracker}[team issue tracker].
|
||||
Click link:{team_issue_tracker}/issues/new?template=.forgejo%2fissue_template%2fsmall-events.yml[*here*] to open the ticket template.
|
||||
Complete the ticket template fully.
|
||||
|
||||
When you are planning for an event, consider using Fedora stickers and similar swag along with a budget of {event_budget_small}.
|
||||
If you require larger budget, we encourage you to team up with a Fedora Ambassador.
|
||||
A Fedora Ambassador can 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.
|
||||
|
|
@ -0,0 +1,5 @@
|
|||
include::ROOT:partial$attributes.adoc[]
|
||||
|
||||
Open a {team_name} ticket in the link:{team_issue_tracker}[team issue tracker].
|
||||
Click link:{team_issue_tracker}/issues/new?template=.forgejo%2fissue_template%2fswag-only.yml[*here*] to open the ticket template.
|
||||
Complete the ticket template fully.
|
||||
|
|
@ -0,0 +1,4 @@
|
|||
include::ROOT:partial$attributes.adoc[]
|
||||
|
||||
Submit a reimbursement request by following the xref:mindshare-committee:policy:reimbursements.adoc[Fedora Reimbursement Requests (FRR) process].
|
||||
Reimbursements are typically paid within two weeks.
|
||||
|
|
@ -0,0 +1,5 @@
|
|||
include::ROOT:partial$attributes.adoc[]
|
||||
|
||||
If this event needs Fedora swag, open a swag request in the link:{team_issue_tracker}[Mindshare tickets tracker] using the link:{team_issue_tracker}/issues/new?template=.forgejo%2fissue_template%2fswag-only.yml[swag-only 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.
|
||||
|
|
@ -60,7 +60,7 @@ When you’re ready, you need to do a few simple things:
|
|||
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].
|
||||
. If you have financial assistance approved, submit a reimbursement request by following the xref:mindshare-committee:policy:reimbursements.adoc[Fedora Reimbursement Requests (FRR) process].
|
||||
|
||||
|
||||
[[assistance-swag]]
|
||||
|
|
|
|||
|
|
@ -1,60 +1,51 @@
|
|||
include::ROOT:partial$attributes.adoc[]
|
||||
|
||||
= Holding or Attending a Large Event
|
||||
Brian Exelbierd; Justin Wheeler; Fedora Mindshare Committee
|
||||
:description: Guidelines for proposing and funding events with a budget of {event_budget_large}.
|
||||
:page-aliases: ROOT:large-events.adoc
|
||||
:revdate: 2026-07-10
|
||||
|
||||
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:{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 {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 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.
|
||||
[[open-ticket]]
|
||||
== Step 1: Open a request ticket
|
||||
|
||||
. Monitor your ticket for questions from the Committee.
|
||||
These tickets will often attract questions from the Committee.
|
||||
include::ROOT:partial$event-request-instruction-blocks/open-ticket-medium-large-events.adoc[]
|
||||
|
||||
. Expect discussion about your ticket to start fairly quickly.
|
||||
Once all the questions are answered, a vote will be called for.
|
||||
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 after the discussion period (allowing for holidays, etc.).
|
||||
[[monitor-ticket]]
|
||||
== Step 2: Monitor ticket for comments
|
||||
|
||||
. 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.
|
||||
include::ROOT:partial$event-request-instruction-blocks/monitor-ticket.adoc[]
|
||||
These tickets will often attract questions from the Committee.
|
||||
|
||||
. Hold your event!
|
||||
[[committee-vote]]
|
||||
== Step 3: {team_name} voting period
|
||||
|
||||
. 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, You may syndicate your blog to Fedora Planet.
|
||||
For more information link:{FWIKI}/Planet[check out this 'how to'].
|
||||
include::ROOT:partial$event-request-instruction-blocks/committee-vote-large-events.adoc[]
|
||||
|
||||
. 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.
|
||||
[[request-swag]]
|
||||
== Step 4: Request swag (if applicable)
|
||||
|
||||
. Comment on your issue in the link:{team_issue_tracker}[Mindshare repo] with a link to your event report.
|
||||
include::ROOT:partial$event-request-instruction-blocks/request-swag.adoc[]
|
||||
|
||||
[[hold-event]]
|
||||
== Step 5: Hold the event
|
||||
|
||||
include::ROOT:partial$event-request-instruction-blocks/hold-event.adoc[]
|
||||
|
||||
[[event-report]]
|
||||
== Step 6: Write and publish an event report
|
||||
|
||||
include::ROOT:partial$event-request-instruction-blocks/event-report.adoc[]
|
||||
|
||||
[[reimbursement]]
|
||||
== Step 7: Request reimbursement
|
||||
|
||||
include::ROOT:partial$event-request-instruction-blocks/reimbursement.adoc[]
|
||||
|
||||
[[close-ticket]]
|
||||
== Step 8: Close out the request ticket
|
||||
|
||||
include::ROOT:partial$event-request-instruction-blocks/close-ticket.adoc[]
|
||||
|
|
|
|||
|
|
@ -1,58 +1,50 @@
|
|||
include::ROOT:partial$attributes.adoc[]
|
||||
|
||||
= Holding or Attending a Medium Event
|
||||
Brian Exelbierd; Justin Wheeler; Fedora Mindshare Committee
|
||||
:description: Guidelines for proposing and funding events with a budget of {event_budget_medium}.
|
||||
:page-aliases: ROOT:medium-events.adoc
|
||||
:revdate: 2026-07-10
|
||||
|
||||
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 equal to or less than $1,000 USD.
|
||||
A medium event is one where the budget is {event_budget_medium}.
|
||||
|
||||
. 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 {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 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.
|
||||
[[open-ticket]]
|
||||
== Step 1: Open a request ticket
|
||||
|
||||
. Monitor your ticket for questions from the Committee.
|
||||
include::ROOT:partial$event-request-instruction-blocks/open-ticket-medium-large-events.adoc[]
|
||||
|
||||
. 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.).
|
||||
[[monitor-ticket]]
|
||||
== Step 2: Monitor ticket for comments
|
||||
|
||||
. 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.
|
||||
include::ROOT:partial$event-request-instruction-blocks/monitor-ticket.adoc[]
|
||||
|
||||
. Hold your event!
|
||||
[[committee-vote]]
|
||||
== Step 3: {team_name} voting period
|
||||
|
||||
. 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, You may syndicate your blog to Fedora Planet.
|
||||
For more information link:{FWIKI}/Planet[check out this 'how to'].
|
||||
include::ROOT:partial$event-request-instruction-blocks/committee-vote-medium-events.adoc[]
|
||||
|
||||
. 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.
|
||||
[[request-swag]]
|
||||
== Step 4: Request swag (if applicable)
|
||||
|
||||
. Comment on your issue in the link:{team_issue_tracker}[Mindshare repo] with a link to your event report.
|
||||
include::ROOT:partial$event-request-instruction-blocks/request-swag.adoc[]
|
||||
|
||||
[[hold-event]]
|
||||
== Step 5: Hold the event
|
||||
|
||||
include::ROOT:partial$event-request-instruction-blocks/hold-event.adoc[]
|
||||
|
||||
[[event-report]]
|
||||
== Step 6: Write and publish an event report
|
||||
|
||||
include::ROOT:partial$event-request-instruction-blocks/event-report.adoc[]
|
||||
|
||||
[[reimbursement]]
|
||||
== Step 7: Request reimbursement
|
||||
|
||||
include::ROOT:partial$event-request-instruction-blocks/reimbursement.adoc[]
|
||||
|
||||
[[close-ticket]]
|
||||
== Step 8: Close out the request ticket
|
||||
|
||||
include::ROOT:partial$event-request-instruction-blocks/close-ticket.adoc[]
|
||||
|
|
|
|||
|
|
@ -1,52 +1,52 @@
|
|||
include::ROOT:partial$attributes.adoc[]
|
||||
|
||||
= Holding or Attending a Small Event
|
||||
Brian Exelbierd; Justin Wheeler; Fedora Mindshare Committee
|
||||
:description: Guidelines for proposing and funding events with a budget of {event_budget_small}.
|
||||
:page-aliases: ROOT:small-events.adoc
|
||||
:revdate: 2026-07-10
|
||||
|
||||
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 equal to or less than $150 USD.
|
||||
The process is exactly the same as for our xref:ROOT:advocate.adoc[Advocate Program].
|
||||
It is summarized below:
|
||||
Anyone can hold or attend a small Fedora-related event.
|
||||
You do not have to be an Ambassador.
|
||||
A small event is one where the budget is {event_budget_small}.
|
||||
The process of opening a request is described below:
|
||||
|
||||
. 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 you are planning for an event you should think about using Fedora stickers and similar swag along with a budget of $150 USD or less.
|
||||
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.
|
||||
[[open-ticket]]
|
||||
== Step 1: Open a request ticket
|
||||
|
||||
. Monitor your ticket for questions from the Committee.
|
||||
include::ROOT:partial$event-request-instruction-blocks/open-ticket-small-events.adoc[]
|
||||
|
||||
. 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.
|
||||
[[monitor-ticket]]
|
||||
== Step 2: Monitor ticket for comments
|
||||
|
||||
. 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.
|
||||
include::ROOT:partial$event-request-instruction-blocks/monitor-ticket.adoc[]
|
||||
|
||||
. Hold your event!
|
||||
[[committee-vote]]
|
||||
== Step 3: {team_name} voting period
|
||||
|
||||
. 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, You may syndicate your blog to Fedora Planet.
|
||||
For more information link:{FWIKI}/Planet[check out this 'how to'].
|
||||
include::ROOT:partial$event-request-instruction-blocks/committee-vote-small-events.adoc[]
|
||||
|
||||
. 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.
|
||||
[[request-swag]]
|
||||
== Step 4: Request swag (if applicable)
|
||||
|
||||
. Comment on your issue in the link:{team_issue_tracker}[Mindshare repo] with a link to your event report.
|
||||
include::ROOT:partial$event-request-instruction-blocks/request-swag.adoc[]
|
||||
|
||||
[[hold-event]]
|
||||
== Step 5: Hold the event
|
||||
|
||||
include::ROOT:partial$event-request-instruction-blocks/hold-event.adoc[]
|
||||
|
||||
[[event-report]]
|
||||
== Step 6: Write and publish an event report
|
||||
|
||||
include::ROOT:partial$event-request-instruction-blocks/event-report.adoc[]
|
||||
|
||||
[[reimbursement]]
|
||||
== Step 7: Request reimbursement
|
||||
|
||||
include::ROOT:partial$event-request-instruction-blocks/reimbursement.adoc[]
|
||||
|
||||
[[close-ticket]]
|
||||
== Step 8: Close out the request ticket
|
||||
|
||||
include::ROOT:partial$event-request-instruction-blocks/close-ticket.adoc[]
|
||||
|
|
|
|||
|
|
@ -1,45 +1,46 @@
|
|||
include::ROOT:partial$attributes.adoc[]
|
||||
|
||||
= Swag-Only Requests
|
||||
Brian Exelbierd; Justin Wheeler; Fedora Mindshare Committee
|
||||
:description: Guidelines for requesting Fedora swag for local events.
|
||||
:page-aliases: ROOT:swag-only-requests.adoc
|
||||
:revdate: 2026-07-10
|
||||
|
||||
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].
|
||||
Anyone can request swag for an event.
|
||||
You do not have to be an Ambassador.
|
||||
|
||||
. 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.
|
||||
[[open-ticket]]
|
||||
== Step 1: Open a request ticket
|
||||
|
||||
. Monitor your ticket for questions from the Committee.
|
||||
include::ROOT:partial$event-request-instruction-blocks/open-ticket-swag-only.adoc[]
|
||||
|
||||
. 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.
|
||||
[[monitor-ticket]]
|
||||
== Step 2: Monitor ticket for comments
|
||||
|
||||
. 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.
|
||||
include::ROOT:partial$event-request-instruction-blocks/monitor-ticket.adoc[]
|
||||
|
||||
. Hold your event!
|
||||
[[committee-vote]]
|
||||
== Step 3: {team_name} voting period
|
||||
|
||||
. 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].
|
||||
include::ROOT:partial$event-request-instruction-blocks/committee-vote-small-events.adoc[]
|
||||
|
||||
* *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'].
|
||||
[[request-swag]]
|
||||
== Step 4: Request swag
|
||||
|
||||
Comment on your issue in the link:{team_issue_tracker}[Mindshare repo] with a link to your event report.
|
||||
include::ROOT:partial$event-request-instruction-blocks/request-swag.adoc[]
|
||||
|
||||
[[hold-event]]
|
||||
== Step 5: Hold the event
|
||||
|
||||
include::ROOT:partial$event-request-instruction-blocks/hold-event.adoc[]
|
||||
|
||||
[[event-report]]
|
||||
== Step 6: Write and publish an event report
|
||||
|
||||
include::ROOT:partial$event-request-instruction-blocks/event-report.adoc[]
|
||||
|
||||
[[close-ticket]]
|
||||
== Step 7: Close out the request ticket
|
||||
|
||||
include::ROOT:partial$event-request-instruction-blocks/close-ticket.adoc[]
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue