#619 New badge request: OSCAL 2018: Mission accomplished!
Closed 5 years ago Opened 5 years ago by jflory7.

Description

During OSCAL 2018 ( #618 ), we want to run a "contribution challenge" for attendees during the conference. We plan to offer "easyfix" bugs or tasks for someone to try and do during OSCAL. The idea is the badge could be a motivator for someone to get involved and make an easy contribution, and hopefully remain engaged after the conference.

If someone makes a contribution and tells us, we will award them with this special badge.

Badge metadata

  • Name: OSCAL 2018: Mission accomplished!
  • Description: You completed the Fedora contribution challenge at OSCAL 2018!
  • Tags: event emea oscal albania

Artwork ideas

This type of idea was done before in the BrickHack 2016 Open Source Winner badge. This badge took the event artwork and made a variant around the event logo in a ring. Perhaps this could be a good precedent to follow for these kinds of badges.

Of course, something more detailed would be awesome, but this badge doesn't have to be complex.


Metadata Update from @mleonova:
- Custom field artwork adjusted to None
- Custom field concept_review_passed adjusted to None

5 years ago

@jflory7 @mleonova this badge does look good :) my only thought is we have been shying away from making any extra event badges besides attendee badges (except flock). We have turned a few requests down. I see the value in how it can help people get involved, but I am not sure we can break the rule for one, but not for others. Thoughts on this?

@mleonova Thanks, this artwork is simple and looks good to me, if we push it.

@riecatnor I didn't know there was a rule about no more event badges other than attendees. I think the original reason to steer away from extra event badges was specific to Flock last year, when @bex asked us to not create speaker badges because the Flock organizing committee wanted to de-emphasize some aspects of speaking at Flock specifically (and it was a lot of work to get a list of the speakers to manually award the badge). I understood this decision as something specific to Flock but I was not aware it was extending to other events.

Originally, we wanted to give away Fedora swag (like t-shirts) for the contribution challenge at OSCAL, but we were unable to make this happen before the event. We wanted to offer something unique and exciting to motivate someone to make a contribution to Fedora.

I see this as a valid exception to the above decision because the previous rule was trying to reduce strain on badge designers for badges that may not have much value other than a small subset of people. We hope to use this badge as a motivator to connect people to the community and motivate them to make a contribution to Fedora (including beginner Fedora Badges tickets :smile: ). I really want to push this badge so we can offer something unique for the contribution challenge. The badge was our last-resort option since the swag option fell through – I'm not sure we will be able to come up with something in time if this badge is not pushed.

What do you all think? I don't want to push this badge up with @mleonova's artwork until there is explicit approval or consent to push this.

Hi @jflory7 - I think this event may have already passed? I am going to close the ticket. As for the validity of the badge or not. I do think the idea has value, and if these types of challenges are recurring, perhaps we should focus on that instead of the event that is hosting it. So "Fedora Challenge" Badges versus an event specific badge. There could be a series of badges based on this, and they could be themed.

There are a few reasons we shy away from event badges beyond just strain on artists. We try to limit them because, 1) We have a ton already (more than content, QA, etc) 2) Travelling to events is something not all Fedorans are able to do on a regular basis, and we would like to focus on badges people can earn without travelling 3) We have turned other people down for badges beyond speaker badges, and beyond Flock.

I hope that helps you understand the position we are in regarding this badge, and I think before the next challenge, we can definitely come up with something that will fall well within guidelines.

Thanks!

Metadata Update from @riecatnor:
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata
Attachments 1