#90 - Fedora Budget Collection Process for 2026/27 - Wiki/Old process/New Process. - mindshare/tickets

lbazan commented

2025-11-11 17:00:44 +00:00

(Migrated from gitlab.com)

We are looking for the best approach to collect the required regional community budget for 2026. In previous years, this process was managed through the regional budget wiki pages.

For this cycle, we should define a clear mechanism to ensure that each reported future event includes the following information:

1 Event details – description, purpose, and expected outcomes.

2 Event owner or Fedora requester – the community member responsible for coordination.

3 Requested budget amount – the total amount of funds needed.

4 Detailed breakdown – explanation of how the funds will be used.

5 Supporting Mindshare ticket – a reference ticket that backs up the event and contains the required information.

This proposal aims to make the budget request and approval process more transparent, traceable, and consistent across all regions.

Reference pages:

https://fedoraproject.org/wiki/Ambassadors/LATAM/Budget
https://fedoraproject.org/wiki/Ambassadors/EMEA/Budget
https://fedoraproject.org/wiki/Ambassadors/APAC/Budget:2016

Please feel free to add any ideas or comments as needed!

@jwwheeler @sumantrom @jonatoni @gridhead @ekidney

We are looking for the best approach to collect the required regional community budget for 2026. In previous years, this process was managed through the regional budget wiki pages. For this cycle, we should define a clear mechanism to ensure that each reported future event includes the following information: 1 Event details – description, purpose, and expected outcomes. 2 Event owner or Fedora requester – the community member responsible for coordination. 3 Requested budget amount – the total amount of funds needed. 4 Detailed breakdown – explanation of how the funds will be used. 5 Supporting Mindshare ticket – a reference ticket that backs up the event and contains the required information. This proposal aims to make the budget request and approval process more transparent, traceable, and consistent across all regions. Reference pages: https://fedoraproject.org/wiki/Ambassadors/LATAM/Budget https://fedoraproject.org/wiki/Ambassadors/EMEA/Budget https://fedoraproject.org/wiki/Ambassadors/APAC/Budget:2016 Please feel free to add any ideas or comments as needed! @jwwheeler @sumantrom @jonatoni @gridhead @ekidney

justwheel commented

2025-11-13 10:58:27 +00:00

(Migrated from gitlab.com)

mentioned in issue #80

justwheel commented

2025-11-13 18:48:36 +00:00

(Migrated from gitlab.com)

Discussed in 2025-11-13 Mindshare Committee meeting.

_Discussed in [2025-11-13 Mindshare Committee meeting](https://discussion.fedoraproject.org/t/fedora-mindshare-committee-meeting-2025-11-13-recognition-digital-ambassadorship-and-regional-event-planning/172593)_.

justwheel commented

2025-11-13 18:48:49 +00:00

(Migrated from gitlab.com)

assigned to @lbazan

justwheel commented

2025-11-13 18:52:12 +00:00

(Migrated from gitlab.com)

The current proposal in the ticket focuses on reviving and modernizing an old, lost process for collecting annual event budgets on a regional basis. This would help with visibility and planning for regional event spending.

In today's meeting, the Mindshare Committee discussed the challenges with the old regional definitions (NA, LATAM, EMEA, APAC), which were based on Red Hat’s corporate structure. These definitions often didn’t fit the Fedora community well and sometimes led to funding inequalities.

A new proposal should perhaps invent a new role like an “event wrangler” who would coordinate between the Mindshare Committee and individual event owners within a specific geographic area. There is a clear need to redefine what “regions” mean for the Fedora community in 2025.

Action items

@lbazan will refine the proposal, focusing on how this regional organization should work and what modern, Fedora-appropriate geographic categories might look like.
All @fedora/mindshare members, please review this ticket and leave your ideas/comments for Luis to work into the next iteration.

The current proposal in the ticket focuses on reviving and modernizing an old, lost process for collecting annual event budgets on a regional basis. This would help with visibility and planning for regional event spending. In today's meeting, the Mindshare Committee discussed the challenges with the old regional definitions (NA, LATAM, EMEA, APAC), which were based on Red Hat’s corporate structure. These definitions often didn’t fit the Fedora community well and sometimes led to funding inequalities. A new proposal should perhaps invent a new role like an “event wrangler” who would coordinate between the Mindshare Committee and individual event owners within a specific geographic area. There is a clear need to redefine what “regions” mean for the Fedora community in 2025. ## Action items * @lbazan will refine the proposal, focusing on how this regional organization should work and what modern, Fedora-appropriate geographic categories might look like. * All @fedora/mindshare members, please review this ticket and leave your ideas/comments for Luis to work into the next iteration.

justwheel commented

2025-12-11 03:25:14 +00:00

(Migrated from gitlab.com)

mentioned in issue #76

justwheel commented

2025-12-11 03:29:23 +00:00

(Migrated from gitlab.com)

mentioned in issue #82

justwheel commented

2025-12-11 03:41:04 +00:00

(Migrated from gitlab.com)

mentioned in issue #87

justwheel commented

2025-12-11 22:37:31 +00:00

(Migrated from gitlab.com)

Did not discuss during the 2025-12-11 Mindshare Committee meeting.

@lbazan We missed you today! I was wondering if it would be helpful for you and me to set up some regular meetings starting in January to work together on this. This piece of the Mindshare Committee charter is critical for a lot of the other parts, so it is important we make some progress here during the Mindshare Committee term. I have several ideas of improvements to the overall event organization strategy, especially defining the "event owner" role better as a Mindshare Committee doc.

What do you think? If you have time before the year-end holidays to write a proposal for the regional organization piece, that would be helpful too, so we can come back focused and clear in 2026.

_Did not discuss during the [2025-12-11 Mindshare Committee meeting](https://discussion.fedoraproject.org/t/fedora-mindshare-committee-meeting-2025-12-11-2026-swag-proposals-digital-ambassadors-year-end-wrap/176583)_. --- @lbazan We missed you today! I was wondering if it would be helpful for you and me to set up some regular meetings starting in January to work together on this. This piece of the Mindshare Committee charter is critical for a lot of the other parts, so it is important we make some progress here during the Mindshare Committee term. I have several ideas of improvements to the overall event organization strategy, especially defining the "event owner" role better as a Mindshare Committee doc. What do you think? If you have time before the year-end holidays to write a proposal for the regional organization piece, that would be helpful too, so we can come back focused and clear in 2026.