[Ambassadors] Re: Where is Fedora? What are we Doing?

[Gabriele Trombini]

Il giorno mar 10 gen 2017 alle ore 17:26 Brian Exelbierd <bex(a)pobox.com&gt; ha
scritto:

[snip]

>  As for reimbursements, those should be done via tickets and not a
> table.
>  Event owners can track details on the event page.
>  
Yes, but I meant that one of the conditions to get the reimbursement is to
draft a report of the event.


>  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.)
>  and so on.
>
>
>  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.
>  
Not at all. I thought we can setup a sort of questionnaire to be filed
online (just like the ones you find when someone is asking for your opinion
in the web) for owners and another for the people attending the event (if
he/she wants) available in a working space at booth.
We cannot ask to the owner of the event to write a report somewhere in the
wiki and another elsewhere with useful data. Again if the event owner has a
blog we should surf the web to read reports.
With the online questionnaire the attendance part is filed by guests and
compiling the owner-side of the report takes few minutes.


>  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.
>  
This is a FOSCo task, isn't it? :-D


>  regards,
>
>  bex
>  
 Thanks.

Gabri
-- 
Gabri