On 30-06-2023 04:43, Justin W. Flory wrote:

NOTE: Once upon a time, we made a decision to discontinue the speaker and contributor badges. There was context for that at the time. However, I deliberately want us to bring them back, both to visibly recognize contributions of people to our events, and also to incentivize these activities further. Badges are a helpful way for us to track and measure these kind of community engagements.

I think that's a great idea.

• Flock 2018 Contributor

That badge has never been awarded. :(

• Flock 2017 Organizer

That one has.

I think we need to decide on the term being used. An organizer is also a
contributor. But a contributor does not need to be an organizer.

I wasn't involved in any Flock of the recent iterations and therefore
don't have any preferences. I just noticed this overlap and the fact
that one of the badges has never been awarded.

I prefer the term Organizer. But either is fine with me. If I can find the old speaker list, etc, I can go back and award the 2018 ones.

Hey @gui1ty and @nb :wave:

@gui1ty wrote…
I think we need to decide on the term being used. An organizer is also a contributor. But a contributor does not need to be an organizer.

I prefer the term Contributor for the reason I gave in the ticket:

"Contributor: Help volunteer or organize Flock."

I want this badge to be used both for people who played a leading role in organizing Flock, but also for volunteers and people who help out pre-event and on-site in executing Flock. Originally, I was requesting four tickets when I started to draft it out, but I felt it was better to group organizers and volunteers. Plus, maybe there will be other forms of contribution that I would want to recognize in this way.

@nb wrote…
If I can find the old speaker list, etc, I can go back and award the 2018 ones.

The unclaimed badge would have been volunteers and organizers in Dresden, I presume. But honestly no idea where that data would be living now. :disappointed:

Hiya folks! I will get to the art or request that one of the current badge design interns gets to it this week after we settle on which badges to create.

I wanted to follow up on the context about the discontinuation of some of the event badges.. and why I think that context is still valid reasons to limit the number of badges for Flock. I haven't counted how many badges are in each category, but from a quick glance at the Badges Explore page it looks like we have more event badges than any other category. In person events are the least accessible thing a Fedora contributor can participate in with restrictions such as time, money, day job, family obligations, distance, inability to gain visas etc. Its a privilege to be able to attend and, although it is work, to contribute as an contributor/organizer/speaker. We also don't want a TON of event badges skewing towards folks who are privileged to travel just because we can make them and not in all of the other areas of the project that are more readily available to contribute to. For these reasons we reduced the badges for DevConf to only be the attendee badge. We kept the badges for Nests limited to two based on this decision for event badges even though contributing/organizing/speaking was more accessible for those virtual events.

Based on all that the two badges I would propose for Flock are:
- Attendee badge
- Social event badge

We kept the social badge because it was a chance for the badge design team to create beautiful designs to commemorate the magic that is the social events of Flock :smile: I don't see any info about the social event in this ticket.. is that something we would still want? Do we have info for the social event for this years Flock confirmed?

Thanks for providing some background @riecatnor!

I think you are making a very valid point. Although, getting each and every badge is not a goal by itself. But I can see why people, otherwise active in the community, feel left out. We should definitely balance event badges with other categories of badges.

On the other hand, organizing an event is something completely different to attending one and it deserves recognition.

With regards to contributor / speaker, couldn't we make that a badge series in the future? You get a badge the first time you speak at an event and then another after 3, 5, 10 talks or whatever is most appropriate. I'm imagining someone on a soap box or a big stage.

For the upcoming Flock, I'm leaving it to you and @jflory7 to decide what badges to provide. But it's definitely something to think about for the future.

Hi everyone! I've created a design for this badge, the files are attached below:

@riecatnor I'd prefer to stick with @jflory7 's original request, but maybe if that is not possible, we can compromise on a Flock badge, an event badge (whenever that is decided), and a contributor badge, and say that the contributor badge is both for speakers and for volunteers/staff. Then it would be less badges, but would still give those that do something to help Flock (speaking or volunteering) could still be recognized.

My goal with the extra badge requests is to provide more recognition and create incentivzes for people who help out in big ways to make Fedora events what they are. I want to better recognize and validate these kinds of contributions as valid contribution pathways in and of themselves.

I am open to decoupling the event contributor and speaker badges from Flock specifically, but I still feel strongly and passionately that we need badges to recognize event contributors and speakers. I want to incentivize this kind of work in a more visible way in the Fedora community. A badge series could apply to both virtual and in-person events, but my one concern is about maintainability. Who then takes responsibility for awarding the badge to any event contributor or event speaker, and what kind of events or presentations are eligible to receive the badges? A badge series comes with added process work and long-term maintenance for something that is constantly ongoing, versus something with a fixed end date. It would make me sad to have an amazing badge series for event contributions and public speaking, but few people know how to get recognition by earning those badges.

However, the timeline is tight with Flock on the horizon next week. I am cautious that planning and launching a new badge series the week before the event would be difficult. This is my 2¢. If not through Fedora Badges, I would seek another way to recognize event contribution and speaking because not only are those contributions that help Fedora, but they also help me incentivize contributions to places where I could use more help as part of my role in Fedora and at Red Hat. But I think Fedora Badges would help me out with my objective in a big way too, because of how treasured Badges are in the community.

Also, specifically for a Flock 2023 contributor badge, I want to award this badge to several people in remote, virtual capacities who are unable to attend Flock, but contributed bits and pieces that pulled it all together. :heart: I see it as a way to make space and be grateful for their contributions to Flock as well.

I know full well that Flock is too close to make the badge series happen before that event. My suggestion was a general one on how we could reduce the number of badges tied to specific events, but still recognize the effort people put into helping organize these.

For the awarding part, since this is a manually awarded badge, we could ask whoever has the information regarding people involved in event organization, to request it be awarded to those people by opening a ticket. I did similar stuff in the past for testing events.

With Badges 2.0 we could look into implementing this in the web UI. If this is not feasible a simple script should work. One way or another, we'll find a way to make this work.

Would I be able to get the QR code for this once it's created for the posters that will be displayed at Flock :)

@ekidney yes, we can get you the QR code as soon as a badge gets pushed.

I was informed there was to be a :ghost: tour for the social! Here's my proposed art:

@smeragoel - can you give a quick review please :D

I pushed the flock-2023-attendee badge.

I pushed the Ghost Tour badge.

https://badges.fedoraproject.org/badge/ghost-tour

I blame any typos on the train shaking... :wink:

@jflory7 and @ekidney have been authorized.

Since we have a bunch of people attending online, would it be an idea to add a slight variation of the attendee badge for folks that attended online? We could award that post event once we have we have a list of people who attended remotely.

That's a great idea, a badge for online attendees.
+1

Since we have a bunch of people attending online, would it be an idea to add a slight variation of the attendee badge for folks that attended online? We could award that post event once we have we have a list of people who attended remotely.

It could be as simple as the main badge with the word Remote or a Letter R on the badge somewhere to signify the difference.

I asked @jflory7 about a badge for remote attendees on the first day, but I knew he was busy with everything else to really focus on it.
https://matrix.to/#/!iXdPsFdJTjXlAHyNHO:matrix.org/$9mmTrvhWDIZ75Jfq-_TV5hBsxsmUKSnSiF1RHQsAUwY?via=libera.chat&via=matrix.org&via=fedora.im

Please be patient. People attending Flock are on their way back home and will need sometime to catch up with their backlogs. It will take some time before this is being worked on.

I would prefer to use the same attendee badge that we used in-person for the folks who attended virtually, versus create something new for the Badges designers. My thinking was to use the Sched.com attendee list as the "pre-requisite" for getting the badge. I have not checked whether I can email everyone in one go, but I am working on it.

I have not checked whether I can email everyone in one go, but I am working on it.

I assume you mean e-mail the link to claim the badge? Not sure how far you've got with that, but if you've got a list of online attendees, I can also manually award the badge using a script on badges-backend01.