On Tue, Jan 10, 2017, at 03:06 PM, Gabriele Trombini wrote:
IMO is not really useful having event pages if we don't have any idea on how to getting informations from them.
Of course I agree with Bex in making them multitasking and usable for more than only one specific target.
At the moment the benefit of having them is to work on historical events for planning people needed, budget expenses and report to get refund.
I believe the budget planning will be helped by the new way of tracking budgets and expenses (details real soon now).
As for reimbursements, those should be done via tickets and not a table. Event owners can track details on the event page.
I'd like to throw on the table more elements in a marketing perspective:
1) getting infos from events about how to route strategies (e.g. gather requests of swag and other gadgets)
2) getting infos about the release itself (which improvements people are asking)
3) getting infos about different target of people (e.g. developer, newbies, advanced users etc.)
These need to be part of a summary produced by the event owners. It shouldn't be buried in a table. I believe the regions need to be responsible for reviewing this and generating a recommendation about whehter this event should be repeated, etc. I wouldn't overwhelm the list of events with this data.
I think this kind of feedback is strictly on the shoulders of our first lines 'cause they have the skills for doing that.
At last, in this perspective I think we should improve the pages in the wiki (or elsewhere). The goal is that in the future we shall have a big database from which analyze data, checking information we need in several community tasks and strategies.
I'd be happy if we regularly had this:
0. Full consideration of activities versus strategy and goal by the Ambassadors
1. Pre-event publicity to drive impact
2. Public event report for the Magazine (could be in a roundup article)
3. Community event report talking about the items above in the comm blog (could be in a roundup article)
4. Post event review by the Ambassadors for impact and consideration for future years.
Ambassadors here is FAmSCo, region, etc. as needed.
regards,
bex