On Wed, Jan 11, 2017, at 01:22 PM, Zamir SUN wrote:
On 01/11/2017 07:29 PM, Brian Exelbierd wrote:
> On Tue, Jan 10, 2017, at 07:02 PM, Gabriele Trombini wrote:
>> Il giorno mar 10 gen 2017 alle ore 17:26 Brian Exelbierd
>> <bex(a)pobox.com <mailto:bex@pobox.com>> 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 think we need to consider this from each angle:
>
> 1. We want an event report/blog post that is posted somewhere where
> people will read it. I'd like to see attendees writing on the Magazine,
> the Planet, their blog, the Community Blog, etc. Whichever is best.
>
> 2. We need to know that the attendee wrote the report in order to
> reimburse them. This can be done by providing a link in the ticket
> which would trigger reimbursement/closure.
>
>>
>>> 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 am not aware of any infrastructure in Fedora to handle this today.
> Let's think about getting it.
>
> However, I would also like to see the event owner writing an event
> report/blog post that is posted somewhere where people will read it.
> I'd like to see attendees writing on the Magazine, the Planet, their
> blog, the Community Blog, etc. Whichever is best.
>
> As for where the other data is stored, I think it needs to be somewhere
> where it can be gotten to easily by the responsible party (see below)
> for analysis and reporting as needed. I suggest we start simpler with a
> wiki or file somewhere and then figure out what are needs are once we
> are actually collecting the data rather than building something we think
> will work first and delaying during construction.
>
>>
>>> 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
>
> No. This is the responsibility of the group that authorized the budget
> and any other reviewers they may have. In today's world I see this as a
> regional responsibility with periodic oversight by FAmSCo. Other
> outreach groups may want to ask for the data, but it isn't there
> responsibility to ensure it is collected or to collect it.
IIRC this is kind of the work of the regional storyteller (collect data
and information and offer these statistics when FAmSCo, FOSCo or some
other part needs ).
I don't believe many, if any, of the regions are having lots of luck
with the storyteller positions. I think we need to think about how to
make this more of a shared responsibility. I think putting it all on
one person may be too much.
regards,
bex