📝 events: 2023-2024 refresh of event request guidelines

This commit is a refresh of the Fedora Mindshare Committee event request
guidelines. There are not major content changes, but some content was
updated to account for recent work in other commits, e.g. GitLab issue
templates for new event requests. Additionally, the structuring of all
event pages was drastically changed by introducing the use of Antora
partials for creating reusable content.

Props to @nmilosev for bringing attention to the outdated documentation
and @pbokoc for calling that this would happen some time back. 😉

Content changes
===============

* Use 2023 GitLab issue template URLs for event request instructions.
* Better explain what is considered a recognized vote by a Mindshare
  Committee member.
* Eliminate cross-links to the Advocate Program, which is not well-
  documented and has not been reviewed since 2018/2019.
* Provide accepted methods for how to share an event report. The methods
  remain the same, but they were suggested/recommended before. Now, this
  makes it more clear that only methods are accepted as valid.

Introduction of Antora partials
===============================

The method of how the event request pages are composed is totally
different. Now, there is minimal copytext included on the event request
instruction AsciiDoc source pages. Instead, most of the content comes
from a library of reusable partials. These are reusable pieces of
content that can be embedded onto multiple pages at once.

So, where the steps remain identical across event request processes,
they are applied consistently to each page. This means less content is
being duplicated in more places. There is one source of truth, and when
it is changed, it is reflected immediately on all pages.

For the parts of the processes that are different (e.g. ticket templates
and voting policies), separate partials are used.

The motive for making this change is to make our documentation easier to
maintain. If we propose future changes to the process, it will be easier
to make sure our language is consistent and that the documentation does
not contradict itself.

Signed-off-by: Justin W. Flory (he/him) <jwf@redhat.com>

modules/ROOT/partials/attributes.adoc

@@ -25,6 +25,11 @@
 // Meetings
 :team_meetings: https://apps.fedoraproject.org/calendar/mindshare/
 
+// Approved budget amounts
+:event_budget_small: under $150.00 USD
+:event_budget_medium: under $1000.00 USD
+:event_budget_large: over $1000.00 USD
+
 // Miscellaneous data
 :COMMBLOG: https://communityblog.fedoraproject.org
 :FISCALYEAR: CY25

modules/ROOT/partials/event-request-instruction-blocks/step01-open-ticket-medium-large-events.adoc

@@ -0,0 +1,18 @@
+include::ROOT:partial$attributes.adoc[]
+
+[[open-ticket]]
+== Step 1: Open a request ticket
+
+Open a {team_name} ticket in the link:{team_issue_tracker}[team issue tracker].
+Click link:{team_issue_tracker}++/-/issues/new?issuable_template=medium-large-events&issue[title]=My%20Event%20Name%20-%20YEAR%20MONTH%20DAY%20-%20My%20City,%20My%20Country++[*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.

modules/ROOT/partials/event-request-instruction-blocks/step01-open-ticket-small-events.adoc

@@ -0,0 +1,13 @@
+include::ROOT:partial$attributes.adoc[]
+
+[[open-ticket]]
+== Step 1: Open a request ticket
+
+Open a {team_name} ticket in the link:{team_issue_tracker}[team issue tracker].
+Click link:{team_issue_tracker}++/-/issues/new?issuable_template=small-events&issue[title]=My%20Event%20Name%20-%20YEAR%20MONTH%20DAY%20-%20My%20City,%20My%20Country++[*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.

modules/ROOT/partials/event-request-instruction-blocks/step01-open-ticket-swag-only.adoc

@@ -0,0 +1,8 @@
+include::ROOT:partial$attributes.adoc[]
+
+[[open-ticket]]
+== Step 1: Open a request ticket
+
+Open a {team_name} ticket in the link:{team_issue_tracker}[team issue tracker].
+Click link:{team_issue_tracker}++/-/issues/new?issuable_template=swag-only&issue[title]=My%20Event%20Name%20-%20YEAR%20MONTH%20DAY%20-%20My%20City,%20My%20Country++[*here*] to open the ticket template.
+Complete the ticket template fully.

modules/ROOT/partials/event-request-instruction-blocks/step02-monitor-ticket.adoc

@@ -0,0 +1,6 @@
+include::ROOT:partial$attributes.adoc[]
+
+[[monitor-ticket]]
+== Step 2: Monitor ticket for comments
+
+Monitor your ticket for questions from the {team_name}.

modules/ROOT/partials/event-request-instruction-blocks/step03-committee-vote-large-events.adoc

@@ -0,0 +1,13 @@
+include::ROOT:partial$attributes.adoc[]
+
+[[committee-vote]]
+== Step 3: {team_name} voting period
+
+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 update the ticket with an approved message.
+
+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.).

modules/ROOT/partials/event-request-instruction-blocks/step03-committee-vote-medium-events.adoc

@@ -0,0 +1,12 @@
+include::ROOT:partial$attributes.adoc[]
+
+[[committee-vote]]
+== Step 3: {team_name} voting period
+
+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 update the ticket with an approved message.
+
+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.).

modules/ROOT/partials/event-request-instruction-blocks/step03-committee-vote-small-events.adoc

@@ -0,0 +1,10 @@
+include::ROOT:partial$attributes.adoc[]
+
+[[committee-vote]]
+== Step 3: {team_name} voting period
+
+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 update the ticket with an approved message.

modules/ROOT/partials/event-request-instruction-blocks/step04-request-swag.adoc

@@ -0,0 +1,8 @@
+include::ROOT:partial$attributes.adoc[]
+
+[[request-swag]]
+== Step 4: Request swag (if applicable)
+
+If this event needs Fedora swag, 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.

modules/ROOT/partials/event-request-instruction-blocks/step05-hold-event.adoc

@@ -0,0 +1,6 @@
+include::ROOT:partial$attributes.adoc[]
+
+[[hold-event]]
+== Step 5: Hold the event
+
+Hold your event!

modules/ROOT/partials/event-request-instruction-blocks/step06-event-report.adoc

@@ -0,0 +1,17 @@
+include::ROOT:partial$attributes.adoc[]
+
+[[event-report]]
+== Step 6: Write and publish an event report
+
+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'].

modules/ROOT/partials/event-request-instruction-blocks/step07-reimbursement.adoc

@@ -0,0 +1,7 @@
+include::ROOT:partial$attributes.adoc[]
+
+[[reimbursment]]
+== Step 7: Request reimbursement
+
+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 two weeks.

modules/ROOT/partials/event-request-instruction-blocks/step08-close-ticket.adoc

@@ -0,0 +1,6 @@
+include::ROOT:partial$attributes.adoc[]
+
+[[close-ticket]]
+== Step 8: Close out the request ticket
+
+Comment on your issue in the link:{team_issue_tracker}[team issue tracker] with a link to your final event report.

modules/events/pages/requests/large.adoc

@@ -2,59 +2,25 @@ include::ROOT:partial$attributes.adoc[]
 
 = Holding or Attending a Large Event
 :page-aliases: ROOT:large-events.adoc
+Guidelines for proposing and funding events with a budget of {event_budget_large}.
+Tuesday, 21 November 2023
 
 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.
+include::ROOT:partial$event-request-instruction-blocks/step01-open-ticket-medium-large-events.adoc[]
 
-. Monitor your ticket for questions from the Committee.
-  These tickets will often attract questions from the Committee.
+include::ROOT:partial$event-request-instruction-blocks/step02-monitor-ticket.adoc[]
+These tickets will often attract questions from the Committee.
 
-. 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.).
+include::ROOT:partial$event-request-instruction-blocks/step03-committee-vote-large-events.adoc[]
 
-. 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/step04-request-swag.adoc[]
 
-. Hold your event!
+include::ROOT:partial$event-request-instruction-blocks/step05-hold-event.adoc[]
 
-. 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/step06-event-report.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.
+include::ROOT:partial$event-request-instruction-blocks/step07-reimbursement.adoc[]
 
-. 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/step08-close-ticket.adoc[]

modules/events/pages/requests/medium.adoc

@@ -2,57 +2,24 @@ include::ROOT:partial$attributes.adoc[]
 
 = Holding or Attending a Medium Event
 :page-aliases: ROOT:medium-events.adoc
+Guidelines for proposing and funding events with a budget of {event_budget_medium}.
+Tuesday, 21 November 2023
 
 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.
+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.
+include::ROOT:partial$event-request-instruction-blocks/step01-open-ticket-medium-large-events.adoc[]
 
-. Monitor your ticket for questions from the Committee.
+include::ROOT:partial$event-request-instruction-blocks/step02-monitor-ticket.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.).
+include::ROOT:partial$event-request-instruction-blocks/step03-committee-vote-medium-events.adoc[]
 
-. 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/step04-request-swag.adoc[]
 
-. Hold your event!
+include::ROOT:partial$event-request-instruction-blocks/step05-hold-event.adoc[]
 
-. 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/step06-event-report.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.
+include::ROOT:partial$event-request-instruction-blocks/step07-reimbursement.adoc[]
 
-. 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/step08-close-ticket.adoc[]

modules/events/pages/requests/small.adoc

@@ -2,51 +2,26 @@ include::ROOT:partial$attributes.adoc[]
 
 = Holding or Attending a Small Event
 :page-aliases: ROOT:small-events.adoc
+Guidelines for proposing and funding events with a budget of {event_budget_small}.
+Tuesday, 21 November 2023
 
-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: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 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.
+include::ROOT:partial$event-request-instruction-blocks/step01-open-ticket-small-events.adoc[]
 
-. Monitor your ticket for questions from the Committee.
+include::ROOT:partial$event-request-instruction-blocks/step02-monitor-ticket.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.
+include::ROOT:partial$event-request-instruction-blocks/step03-committee-vote-small-events.adoc[]
 
-. 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/step04-request-swag.adoc[]
 
-. Hold your event!
+include::ROOT:partial$event-request-instruction-blocks/step05-hold-event.adoc[]
 
-. 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/step06-event-report.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.
+include::ROOT:partial$event-request-instruction-blocks/step07-reimbursement.adoc[]
 
-. 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/step08-close-ticket.adoc[]

modules/events/pages/requests/swag-only.adoc

@@ -2,44 +2,28 @@ include::ROOT:partial$attributes.adoc[]
 
 = Swag-Only Requests
 :page-aliases: ROOT:swag-only-requests.adoc
+Guidelines for requesting Fedora swag for local events.
+Tuesday, 21 November 2023
 
 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.
+include::ROOT:partial$event-request-instruction-blocks/step01-open-ticket-swag-only.adoc[]
 
-. Monitor your ticket for questions from the Committee.
+include::ROOT:partial$event-request-instruction-blocks/step02-monitor-ticket.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.
+include::ROOT:partial$event-request-instruction-blocks/step03-committee-vote-small-events.adoc[]
 
-. 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/step04-request-swag.adoc[]
 
-. Hold your event!
+include::ROOT:partial$event-request-instruction-blocks/step05-hold-event.adoc[]
 
-. 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/step06-event-report.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'].
+// Override the header used in the partial, since it is not a sequential match for swag-only requests.
+// From line 6 to the last line of the partial is included.
+[[close-ticket]]
+== Step 7: Close out the request ticket
 
-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/step08-close-ticket.adoc[lines=6..-1]