This is the text of an email sent to the mailing lists.
In today's APAC Ambassadors meeting we were talking about how tickets were not moving through the system despite ambassadors ready to do events. We've tried a few things in the past, but it has been super hard to get real-time meetings working or to get ticket voting to happen in all cases. Questions seems to block events from being approved, even when the question is about details not related to the approvals.
You can read some of the conversation here:
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2018-06-14/apac_ambassadors.2018-06-14-12.00.txt
The end result of this was to use APAC as the leading edge of the Mindshare movement. The proposal is to ask Mindshare to start working with APAC events/requests immediately. This provides the following benefits:
1. APAC gets a group of people to help move tickets through a process and it unblocks ambassadors to do what they do best -- FANTASTIC FEDORA EVENTS!
2. Mindshare gets a queue of real requests to apply the strategy they are working on too. This will expose gaps and holes.
3. It gives Mindshare the ability to make decisions to generate their procedures as they work on translatino their proposal into procedures.
The request in this email is to find out if both groups are willing to do this.
Mindshare can review this in their next meeting on Monday. This is opened in their ticket queue as: XXXX
Because APAC ambassadors is a large group across many timezones and doesn't meet as frequently, let's use a modified lazy consensus model. Let's get some +1s in the Mindshare ticket to indicate sentiment and address any -1s to identify challenges and respond to them. I strongly encourage anyone who has concerns to raise them and to note what could be done to solve their concern as well solve the overall issues.
I think this is an excellent idea. It may come with its own challenges, but I think it will be a huge benefit for both groups to help iterate and improve on this process, as was previously discussed on the Ambassadors list.
+1 from me. Sounds like a good way to move forward on several fronts.
Sounds good, at least worth a try. We may always revert back if things don't seem to work out.
+1 from me. This sounds like a great idea
Metadata Update from @jflory7:
- Issue set to the milestone: Fedora 29 (to Oct. 2018)
- Issue tagged with: ambassadors
How can we move this ticket forward now? It has been almost a month after the initial outreach, so given the quiet and our lazy consensus voting model, how can we formalize this into policy? How should we communicate and make the guidance on the updated process visible?
This is something we should get done via the ambassadors/advocate work at Flock. I think we also need to develop templates there and start processing tickets.
to comment on this ticket.