#475: Fedora 25 Release Party Attendee -------------------------------------+------------------------------------- Reporter: | Owner: jflory7 | Status: new Type: | Keywords: New badge idea | Has a description: 1 Priority: | Artwork status: Concept minor | External requirements: Has a name: | Triaged (triagers only): 1 1 | Concept approved (reviewers only): | 0 | Badge definition status: | Not yet possible | Manually awarded: | 1 | -------------------------------------+------------------------------------- = Metadata =
* '''Badge Name''': Fedora 25 Release Partygoer * '''Badge Description''': Attended a local release party to celebrate the launch of Fedora 25!
= Artwork ideas =
One thing to note is distinguishing between the [https://fedorahosted.org /fedora-badges/attachment/ticket/452/release_party_24.png badge] for release party organizers. It may be helpful to come up with ways to keep the same theme between the two but separate them in another way (sort of similar to Flock attendee vs. organizer badges).
1. One panda with a party hat on, with the number of the release 2. Cake with the release number on it 3. Ball drop-esque tower, with the release number on the ball (as it "descends" down)
= Understanding badge =
1. '''What activities''': Awarded to those who attend a release event but aren't necessarily organizing it 2. '''Who does it''': Newcomers to the project who may not have a FAS account yet (but this may encourage them to get one), or current contributors who may be nearby the area for a party 3. '''Why''': Gives some kind of "achievement" for going to a party and participating in the event, like a milestone that could be shown or displayed later on 4. '''When''': Once a release, when an attendee could make it a local release party happening in their area 5. '''How''': Scanning the QR code at the party or getting the link at the event
To expand on this badge idea a little more, it would be helpful to have this from a community metrics perspective. This specific badge idea popped up at the CommOps workshop at Flock. For this badge, we would be able to have all party organizers have the QR code at their event. After release parties wind down, we could look at the dates where the badge was claimed and associate the dates with specific events. It would be possible to evaluate the impact the event had towards bringing more interested people into Fedora (e.g. did someone already have a FAS account before the event? Or did they make one there? Did they become more active in the project after the event? etc.). This would also be useful to compare against other events to see where we are having more of an impact. bee2502 may be able to expand on this too if there's any angle that I missed.
Going to CC some designers to this ticket too since the ticket should be triaged / pending designer feedback now.