Add comprehensive guide for organizing a small Fedora event #21
Labels
No labels
charter
ambassadorship
charter
events
charter
recognition
good first issue
help wanted
needs
event report
needs
reporter feedback
needs
vote
scope
bug
scope
improvement
scope
new
state
approved
state
blocked
state
duplicate
state
invalid
state
wontfix
team
advocates
team
ambassadors
team
commops
team
council
team
design
team
docs
team
g11n
team
marketing
team
mindshare
team
websites-apps
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Blocks
Reference
mindshare/docs!21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rmcbryde/docs:add-small-events-sop"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds a comprehensive event-owner guide covering planning, funding, promotion, execution, reporting, and reimbursement. Places the guide first under Event Guidelines & Resources and adds a cross-link from the existing procedural Small Events page.
Incorporates Justin Wheeler's preliminary review feedback, including stable heading anchors, contributor attribution, corrected Antora cross-references, and AsciiDoc formatting fixes.
Validation: Generated the local Antora preview successfully. Cross-references to other Fedora Docs components cannot resolve in the single-repository preview.
So far, so good.
Here are a few suggested changes.
@ -0,0 +11,4 @@You do not have to be a xref:commops:teams:ambassadors.adoc[Fedora Ambassador] to request support for a small event.Use these steps as practical guidance.The xref:ROOT:index.adoc[linked Mindshare policies] define funding and reimbursement requirements.Are we sure that the home page has the policies that we are trying to point towards here?
@ -0,0 +56,4 @@Consult the Fedora Design Team with 4-6 weeks advance notice for graphic design assets.Ask other Fedora contributors for advice or help as needed.a|Request up to $150 USD for a Fedora activityTry using annotated variables for these.
@ -0,0 +62,4 @@a|Request only Fedora swaga|Follow the xref:events:requests/swag-only.adoc[Swag-Only process].a|Request more than $150, up to $1,000 USDTry using annotated variables for these.
@ -0,0 +120,4 @@a|At least 30 days before Ta|Aim to submit any badge request with artwork or a clear reuse proposal.This is a planning target based on the pending proposal in Mindshare #145.Thank you for the reference mindshare/tickets#145.
Please ensure that it gets hyperlinked.
@ -0,0 +156,4 @@Use this as a baseline and add time where local customs or delivery conditions require it.For local printing, get the vendor's production and delivery estimate; there is no universal local-print turnaround.*Do NOT spend money you expect Fedora to cover before Mindshare Committee approval.* For travel or lodging for anyone NOT employed by Red Hat, the required Budget/Event Authorization Request (BEAR) pre-approval must also be complete before booking.Did we change the BEAR acronym?
Was it not "Business Entertainment and Amenities Review" before though?
@ -0,0 +179,4 @@[[create-a-planning-page-people-can-find]]=== Create a planning page people can findUse the link:https://fedoraproject.org/wiki/Event_Wiki_Template[Event Wiki Template] as a starting point.Since the Fedora Wiki is used more than twice here, it makes sense to have it inside of an annotated variable too.
@ -0,0 +223,4 @@[[use-the-current-request-path]]=== Use the current request pathOpen event funding and swag requests in link:https://forge.fedoraproject.org/mindshare/tickets[Mindshare's Fedora Forge tracker].Since the Fedora Forge is used more than twice here, it makes sense to have it inside of an annotated variable too.
@ -0,0 +252,4 @@It is a historical reference, not a current source for event budget availability.Ask Mindshare about funding availability and priorities through your request.Example budget proposal: link:https://fedoraproject.org/wiki/Data_Con_LA_2026_Event#Budget_proposal[https://fedoraproject.org/wiki/Data_Con_LA_2026_Event#Budget_proposal]No need for raw URL text.
Use descriptive anchor text.
@ -0,0 +259,4 @@. Sign in to Fedora Forge and open the link:https://forge.fedoraproject.org/mindshare/tickets/issues/new/choose[Mindshare template chooser].. Select the template for your request.For up to $150, use the link:https://forge.fedoraproject.org/mindshare/tickets/issues/new?template=.forgejo%2Fissue_template%2Fsmall-events.yml[small-event template].Try using annotated variables for these.
@ -0,0 +372,4 @@Use these prompts to tell the story.These concrete details are often the most useful parts of the report for reviewers, because they show what Fedora support made possible and what future organizers can learn:* What did people ask?Try "What questions were asked" without the question mark here.
@ -0,0 +373,4 @@These concrete details are often the most useful parts of the report for reviewers, because they show what Fedora support made possible and what future organizers can learn:* What did people ask?* What attracted them?Try "What attracted the people" without the question mark here.
@ -0,0 +374,4 @@* What did people ask?* What attracted them?* Which demonstrations worked?Try "What demonstrations were made" without the question mark here.
@ -0,0 +375,4 @@* What did people ask?* What attracted them?* Which demonstrations worked?* Where you ran into problems?Try "What problems were faced" without the question mark here.
@ -0,0 +379,4 @@* Distinguish your booth or session attendance from total conference attendance, and label estimates.* Take photos with permission and avoid collecting personal information you do not need.For example, instead of saying only that a booth was busy, explain which topic drew questions, what you changed to help visitors, and whether that created useful follow-up.This sentence feels repeated below verbatim.
Focus on onsite observations.
@ -0,0 +417,4 @@Explain differences and link the updated public budget without exposing receipts or personal financial details.* *Next steps and thanks:* Who will follow up, what should happen next, and who helped make the event possible?For example, instead of saying only that a booth was busy, explain which topic drew questions and what you changed to help visitors.This sentence feels repeated above verbatim.
Focus on final reporting.
@ -0,0 +431,4 @@Add a written summary, captions, and budget link where needed so the account is understandable and useful to other organizers.For a video-only report, confirm acceptance with the reviewer because the published policy does not explicitly name that format.For the link:https://communityblog.fedoraproject.org/[Community Blog], follow the link:https://communityblog.fedoraproject.org/writing-community-blog-article/[article-writing guide]: create the draft in WordPress, then follow the editor-review instructions.Since the Community Blog is used more than twice here, it makes sense to have it inside of an annotated variable too.
Thanks, @t0xic0der !
I addressed the feedback and updated PR #21.
During the event: capture observations
Before:
Use these prompts to tell the story. These concrete details are often the most useful parts of the report for reviewers, because they show what Fedora support made possible and what future organizers can learn:
After:
During breaks, record onsite observations while they are fresh. Capture the following details for the report:
I also replaced:
For example, instead of saying only that a booth was busy, explain which topic drew questions, what you changed to help visitors, and whether that created useful follow-up.
With:
Record specific questions, visitor reactions, and adjustments you made to demonstrations or activities. These notes will help you write the report after the event.
Close-out: explain results
Before:
For example, instead of saying only that a booth was busy, explain which topic drew questions and what you changed to help visitors.
After:
Use your onsite notes to explain the event's results and lessons for future organizers. Describe what Fedora's support made possible and identify any follow-up commitments.
The sentence “Do not invent attendance or impact numbers to make a report sound stronger” now appears only in Close-out. Previously, it appeared in both sections.
Hi @t0xic0der,
Thinking about this some more. I'm concerned that changing the first four bullets to descriptive phrases breaks the parallel structure with the final two, which are commands.
I recommend that we make all six bullets commands. That would keep the flow consistent and focus the list on onsite observations.
It would look like this:
I will await your feedback before submitting another commit.
cc: @jflory7
Hi @t0xic0der, cc @jflory7,
I've pushed commit
6b086d1to make all six onsite-observation bullets commands, as proposed above. This keeps the list consistent and focused on what organizers should record during the event. The earlier review corrections remain in place, and the Antora preview CI check has passed.Could you please take another look and approve the PR if everything looks good? Thanks again for your guidance and review!
@rmcbryde, looks good to me.
Subsequent changes can be added atop this change.
Let us wait on @jflory7's feedback before merging.
Hi @jflory7,
Please review when you get a chance. Thanks!!
LGTM! Thanks so much @rmcbryde for working on this! 🚀