Action items for Regional Event Support team from Fedora Council Strategy Summit 2026 #114

Closed
opened 2026-04-01 08:31:50 +00:00 by t0xic0der · 3 comments
Owner

This action item includes a necessary activity prescribed from the discussions that took place during the Fedora Council Strategy Summit 2026, for the Regional Event Support team of the Fedora Mindshare committee.

  • Event owners are to be requested to document their experiences covering their responsibilities of organising a certain event, to help others to step up in the event owner role for either upcoming or recurring events.

  • Regional event box inventory has to be recorded somewhere publicly accessible, and these also need to be restocked with existing swag design items (for example, Fedora mascots, Fedora Loves Python, Fedora SIGs, etc.).

The aforementioned requirements are expected to be completed and reported upon by the commencement of the annual flagship community conference, Flock To Fedora 2026 (that is, on or before 14th June 2026).

This action item includes a necessary activity prescribed from the discussions that took place during the **Fedora Council Strategy Summit 2026**, for the [**Regional Event Support**](https://docs.fedoraproject.org/en-US/mindshare-committee/#responsibilities-regional-events) team of the [**Fedora Mindshare**](https://docs.fedoraproject.org/en-US/mindshare-committee/) committee. - Event owners are to be requested to document their experiences covering their responsibilities of organising a certain event, to help others to step up in the event owner role for either upcoming or recurring events. - Regional event box inventory has to be recorded somewhere publicly accessible, and these also need to be restocked with existing swag design items (for example, Fedora mascots, Fedora Loves Python, Fedora SIGs, etc.). The aforementioned requirements are expected to be completed and reported upon by the commencement of the annual flagship community conference, **Flock To Fedora 2026** (that is, on or before **14th June 2026**).
Author
Owner

Hey @jflory7 and @lbazan, as we are little over a month away from the Flock To Fedora 2026 event dates, I am following up on the progress. Was any progress being able to be made on this part? Is there anyway with which we can help out here? Let us know.

Hey @jflory7 and @lbazan, as we are little over a month away from the Flock To Fedora 2026 event dates, I am following up on the progress. Was any progress being able to be made on this part? Is there anyway with which we can help out here? Let us know.
Author
Owner

Ping. We are roughly a couple of weeks away from Flock and my questions remain the same. Got updates? Need help?

Ping. We are roughly a couple of weeks away from Flock and my questions remain the same. Got updates? Need help?
Owner

Closing this out. Both action items from the Fedora Council Strategy Summit are addressed:

1. Event owner documentation: The expectation for event owners to document their experiences is best served through the event report process. mindshare/docs#11 adds an "After Your Event" section establishing that event owners are responsible for working with the Committee to update inventory and report back. For the broader goal of guiding event owners on what to include in their reports, I will open a separate ticket to develop event report templates with clear expectations. That is a concrete, actionable piece of work better suited to its own ticket than this meta-level issue.

2. Regional event box inventory: mindshare/docs#11 centralizes the NA and EMEA event box inventories into the Fedora Docs site as the single public source of truth. Both inventories have been updated from the shared Pelican tracker spreadsheet, with the NA box last verified after LFNW 2026 and the EMEA box last verified after DevConf.cz 2026. The pages include shipping specifications, maintainer contact information, and a maintenance history log.

We did not meet the original June 14 deadline, but the work is done and awaiting merge. With the new committee term underway, I would ask @lbazan and the incoming members to review and merge mindshare/docs#11 to formally close this out. Swag restocking is tracked separately as an ongoing operational responsibility of the FCA.

Thank you @t0xic0der for driving these action items and following up.

Assisted-by: Claude Opus 4.6 (1M context)

Closing this out. Both action items from the Fedora Council Strategy Summit are addressed: **1. Event owner documentation:** The expectation for event owners to document their experiences is best served through the event report process. mindshare/docs#11 adds an "After Your Event" section establishing that event owners are responsible for working with the Committee to update inventory and report back. For the broader goal of guiding event owners on what to include in their reports, I will open a separate ticket to develop event report templates with clear expectations. That is a concrete, actionable piece of work better suited to its own ticket than this meta-level issue. **2. Regional event box inventory:** mindshare/docs#11 centralizes the NA and EMEA event box inventories into the Fedora Docs site as the single public source of truth. Both inventories have been updated from the shared Pelican tracker spreadsheet, with the NA box last verified after LFNW 2026 and the EMEA box last verified after DevConf.cz 2026. The pages include shipping specifications, maintainer contact information, and a maintenance history log. We did not meet the original June 14 deadline, but the work is done and awaiting merge. With the new committee term underway, I would ask @lbazan and the incoming members to review and merge mindshare/docs#11 to formally close this out. Swag restocking is tracked separately as an ongoing operational responsibility of the FCA. Thank you @t0xic0der for driving these action items and following up. <sub>_Assisted-by: Claude Opus 4.6 (1M context)_</sub>
t0xic0der canceled time tracking 2026-08-03 05:20:36 +00:00
Sign in to join this conversation.
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
mindshare/tickets#114
No description provided.