The Summer Coder badge is given to participants in both GSoC and Outreachy. Yet, the flag on the badge says "GSoC". Plus, Outreachy has both a summer and winter session, making the badge not too appropriate for both seasons.
I think that leaves us with two options: - Option 1: Remove the "GSoC" flag from the Summer Coder badge. This will keep the badge neutral, but won't fix the concern of Outreachy winter sessions. - Option 2: Keep the Summer Coder badge for GSoC only. Then create a new badge for Outreachy.
Badge description for Outreachy badge (like "You added a co-maintainer to a package. BFF!"): You participated (as intern, mentor, or admin) in a Outreachy. Then change the Summer Coder description to be GSoC specific.
Help the badges team understand what this idea is all about. If this badge is awarded for certain kinds of activities:
1) What are those activities? - Making an Outreachy contribution
2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?) - Newcomers
3) Why are they doing them (is this a means to a different end?) - Trying to score an Outreachy internship with the Fedora Project
4) When do they do them (every day? once a year?) - Twice a year
5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?) - IRC, Telegram, Pagure
Lastly, do you have any ideas for artwork concepts? - I'm open to ideas, if this ticket proves relevant :)
@riecatnor What do you think? Is this ticket relevant?
@viv I am not sure why the GSoC one says that, but we do already have an Outreachy badge: https://badges.fedoraproject.org/badge/we-can-do-it%21 thanks for the initiative though :)
Metadata Update from @riecatnor: - Custom field artwork adjusted to None - Custom field concept_review_passed adjusted to None
Metadata Update from @riecatnor: - Custom field external_requirements adjusted to on - Custom field has_complete_yaml adjusted to on - Custom field has_description adjusted to on - Custom field has_name adjusted to on - Custom field needs_manual_award adjusted to on - Custom field triaged adjusted to on - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
@riecatnor Ah, I see. I checked for the Outreachy badge, but missed that! Thanks for clarifying :D
Log in to comment on this ticket.