#88 Metrics for Release Parties
Closed: Complete 3 months ago by bee2502. Opened 2 years ago by bee2502.

During the CommOps workshop at FLOCK 2016, we asked the community about the metrics the would be interested in and the idea of having metrics for Fedora Release Parties popped up.

These metrics could be measured by creating and awarding badge for attending a release party. It could be helpful to generate metrics about release parties in general - Where are they happening ? How many are happening ? What are the peak times and days for these release parties according to cities ?

But most importantly, we could measure the impact at release parties (since they are more closer environment than a large conference) by having metrics like how many many people attended these release parties ? How much percentage of Fedora and non-Fedora contributors amongst the attendees ? How many non contributors went on to create FAS accounts ? How many went on to become long-term contributors and in what areas ?


I created a ticket for release party attendee badges on the Fedora Badges Trac.

Badge created

The first release party attendee badge, Fedora 25 Release Partygoer, was used for the past release, with 38 awardees across three of four regions of the world. It would be interesting to try building a test case for running some metrics on this, especially once we have more badges from a few more releases.

I would also be curious to think of other things we might want to look at other than just the badge, but I'd need more time to think on this one.

Reading this ticket makes me think about the loco.ubuntu.com site that listed Local Team events and meetings.

http://loco.ubuntu.com/events/

I think the idea of allowing people to register a 'Fedora' event would allow for the following:
1. People to search for events in their area
2. People to 'check-in' at the event (badges)
3. Give anonymous feedback to event organizers to help improve future events

Combining this type of system with something similar to meetup would help.

@cprofitt To the first point, I think this is something being addressed in the regional hubs idea for Fedora Hubs by @shillman! I haven't followed the discussion too much recently, but I think the idea of making it easier to find Fedora events in the area would be something addressed by the regional hub feature.

As for points 2 and 3, this would be nice to have too. I'm wondering if this is something we could pitch to Hubs or if we'd want to consider other options.

I would like to work on metrics for this.

Metadata Update from @bee2502:
- Issue assigned to bee2502

2 years ago

Metadata Update from @jflory7:
- Issue priority set to: critical (next week) (was: minor (3-4 weeks))
- Issue set to the milestone: Fedora 26 (was: Future releases)

2 years ago

@cprofitt +1 regarding the post-event feedback, do you think having a uniform website for feedback is better ? or should all ambassadors create a feedback form themselves ?

cc'ing @bex to hear his thoughts on post-event feedback idea.

Metadata Update from @bee2502:
- Issue priority set to: minor (3-4 weeks) (was: critical (next week))
- Issue set to the milestone: Future releases (was: Fedora 26)

2 years ago

@cprofitt +1 regarding the post-event feedback, do you think having a uniform website for feedback is better ? or should all ambassadors create a feedback form themselves ?

I can see two sides of this coin:

A custom form would allow organizers to get very specific feedback to their region or specific questions -- like was this location better than the other location.

On the flip side having a uniform website with the same questions would allow for some deeper data analysis from the larger community.

Given that I wonder if this could be a dual purpose form with some basic questions relevant to all events and some additional organizer questions added on.

Metadata Update from @jflory7:
- Issue tagged with: meeting

a year ago

@bt0dotninja @skamath @x3mboy Thanks for discussing this ticket at the meeting this week.

You mentioned the release party badge, but I remembered that we didn't actually create a ticket for one this release like we did last time. A new Badges ticket for F26 release parties is created here.

An important step of having any sort of data for us to use is to make sure this badge is shared with the Ambassador community. Once it's pushed, we should be sure to communicate that it exists to the Ambassador mailing list, and maybe even reach out to release party organizers if there's any already on the wiki.

Here you have all F26 release parties and the organizers. If you want help feel free to ask me, and I can help to ask the organizers to award the badge for the participants. Meanwhile, we have only this badge for the release party organizers, but still waiting for their reports to award the badge.

@jonatoni Do you still think you could help us with this for F26 release parties? We could also use your help for promoting the F27 release party badge, once it's ready.

The ticket for F27 Release party badge is here: https://pagure.io/Fedora-Badges/issue/573

Once the badge is pushed, we need to -

  1. Communicate that it exists to the Ambassador mailing list and how organizers can award it.
  2. Reach out to release party organizers if there's any already on the wiki.
  3. Community Blog/ Magazine post about release parties happening.

Metadata Update from @bee2502:
- Issue untagged with: meeting
- Issue tagged with: blocked

a year ago

Metadata Update from @jflory7:
- Issue priority set to: no deadline (was: minor (3-4 weeks))

a year ago

Hello @bee2502,

The badge is actually implemented , can we close this ticket?

@bt0dotninja Since the page was used for at least two release cycles now, I think it is okay to close it.

In some of the follow-up metrics tickets from Flock, it would be great to try and use this data in some of our fedmsg explorations. It offers a potentially quantifiable insight to release party attendance.

Metadata Update from @jflory7:
- Issue untagged with: blocked
- Issue close_status updated to: Complete
- Issue set to the milestone: Fedora 29 (to Oct. 2018) (was: Future releases)
- Issue status updated to: Closed (was: Open)

3 months ago

Login to comment on this ticket.

Metadata