Good question, right now is only with what the program offer like swag/budget and specific teams that send other swags or employee for events.
The point is that as community we need to define a list about where we need support because we know better then Mozilla itself. AS community is better to start to work on our own in this cases and give this information to the Reps Council as example.
That’s true, I can confirm too but this doesn’t mean that only one rep can do that in the community itself. Different reps can work on different things inside the community like the program do now with Onboarding/Resources/Review/Newsletter teams as example.
This problems are now fixed ![]()
This is something not for the role but for the Reps Council to see what is missing right now, we are working on different OKRs in the last Q3 and working on the next one Q3.
As you can see on other post on discourse:
- How should an event page for a meetup look like? - Community Feedback
- We want you for the new Campaign!
- Engaging with the Firefox strategy in Q4
We are in a phase (and there will be new threads) where we are asking feedback like this so the council can work on data and improve all the area where is required.