<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 6, 2015 at 10:58 AM, Matthew Miller <span dir="ltr"><<a href="mailto:mattdm@fedoraproject.org" target="_blank">mattdm@fedoraproject.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">On Fri, Nov 06, 2015 at 09:11:45AM -0600, inode0 wrote:<br>
> Event reports being required for reimbursement doesn't work that well<br>
> for lots of situations. And expecting reports with any sort of<br>
> useful/valid impact analysis to be presented within two weeks of an<br>
> event is unreasonable. I'm not sure the people we send to an event to<br>
> promote Fedora are necessarily the best people to do impact analysis<br>
> anyway, but that is way too short of a window to do much that is<br>
> meaningful.<br>
<br>
</span>I'd really like to hear ideas on who (and how, what, etc) would be good<br>
for doing impact analysis.<br></blockquote><div><br></div><div>As laid out, event reporters are not (necessarily) doing the analysis, only the reporting. This type of reporting is mostly about reporting raw numbers and gathering links.<br><br></div><div>--Snipped From Wiki--<br></div><div><ul><li> Attendees contacted or reached
</li><li> Fedora Badges issued at or as a result of the event
</li><li> Pull requests and patches submitted as a result of event
</li><li> Bugs reported
</li><li> Candidates sourced (i.e. Outreachy, GSoC, and/or other FOSS programs)
</li><li> Articles/Videos/Photos/Content published by or about regional team
</li><li> Social media mentions and interactions generated by event
</li><li> Other supporting evidence data that shows the results of your effort
</li><li> Links to and reach of Posts on Fedora Channels
</li></ul><p>--Snipped From Wiki--</p><p>Most of these elements can be tracked by:</p><ul><li>Keeping a Sign-in sheet at the event<br></li><li>Having a QR code for badge awarding</li><li>using tags such as "python3 VFAD" to associate with an event with a PR/Bugzilla Report<br></li><li>Candidate sourced would join the Outreachy or Summer-Coding mail list, and should include which event they started at in their introduction email.</li><li>Articles/Content/Videos may be harder to find, but we want them for more than just reimbursement, we want to promote awesome Fedora things. By using a hashtag for an event, we should be able to aggregate some of that stuff from social media.</li><li>Anec-data and other personal accounts can be included as a blurb when sending the report.</li><li>CommOps and Fedora Social Media Manager (via OSAS) can help promote these, and get metrics too.<br></li></ul>As far as analysis, we need to start with data and metrics, which don't necessarily need to be number-crunched by the ambassadors.<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">
> I think we would maybe get better reports if we asked for one report<br>
> per event rather than one report per funded person per event and if we<br>
> involved marketing/magazine writers to help present the activities at<br>
> the event rather than relying solely on exhausted ambassadors to do<br>
> this immediately after an event.<br></span></blockquote><div><br></div><div>I'm ok with this, which is why having a dedicated storyteller to aggregate the information for an event report was a proposed solution.<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">
<br>
</span>This makes a lot of sense to me — and in general fits with the the idea<br>
of better collaboration/communication between ambassadors and<br>
marketing.<br></blockquote><div><br></div><div>Agreed. Ideally, the storyteller would be working with mktg and commops to get their event promoted on the channels. <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<span class=""><br>
> > - With only one guaranteed travel accommodation included as a benefit,<br>
> > I fear we're going to run into difficulties deciding who gets that<br>
> > benefit out of the three.<br>
> Yeah, potentially three people do something and one based on some<br>
> unknown factors gets a big benefit - recipe for unhappy campers.<br>
<br>
</span>I'd love to live in a world where it'd be easy for us to tell our<br>
sponsor that it's worth sending all three from all regions. Maybe we<br>
can get there. In the world we have where that might not be possible, I<br>
think the best we can do is reduce the "unknown factors".<br></blockquote><div><br></div><div>Yes, preferably we'd be able to get travel funded for all members, but I think that is something that we'd need to make the case for in a future budget cycle. Four regions x three reps = 12 Funded trips, which will be rather costly without having that be a planned portion of the budget.<br><br></div><div>If there are other benefits for being a regional delegate besides funded event travel, I'd be very interested to hear what people have in mind (Ambassador Polo/Swag kits? Featured articles on the Magazine/CommBlog?)<br><br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<span class=""><font color="#888888"><br>
<br>
--<br>
Matthew Miller<br>
<<a href="mailto:mattdm@fedoraproject.org">mattdm@fedoraproject.org</a>><br>
Fedora Project Leader<br>
</font></span><div class=""><div class="h5">_______________________________________________<br>
council-discuss mailing list<br>
<a href="mailto:council-discuss@lists.fedoraproject.org">council-discuss@lists.fedoraproject.org</a><br>
Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct" rel="noreferrer" target="_blank">http://fedoraproject.org/code-of-conduct</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/council-discuss" rel="noreferrer" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/council-discuss</a><br>
<br>
The Fedora Project's mission is to lead the advancement of free and<br>
open source software and content as a collaborative community.</div></div></blockquote></div><br></div></div>