What the badge should be granted for: Sending a patch to a fedora mailing list Badge description: You sent a patch to a Fedora mailing list! Anything else we need to know: It's considered a rare event in Fedora to have patches sent to (most) public lists. We usually use bugzilla and such, and mailing lists are full of people arguing minor details. Today, a rare event happened and stickster sent a patch to the desktop list. I feel this rare event should be awarded with a special badge :)
Wouldn't that encourage people to do so? Do we want that?
Why wouldn't we want this? Sending patches to lists is common in other FOSS projects, especially big ones like the kernel - it allows the other developers to review your patch, and allows discussion about the patch.
Anything that encourages people to contribute is a thing we want to do, I think.
Possible artwork concepts: Classic looking email envelope. Could have envelope open with a patch sticking out. Email envelope with an eyepatch?
attachment email_list_patch.svg
attachment <img alt="email_list_patch.png" src="https://pagure.io/Fedora-Badges/issue/raw/files/b1d155c5b5481b334e44dbc434d42eb830adde6440b5478bdd1ecf523b9bb6d6-email_list_patch.png" />
attachment <img alt="email_list_patch.png" src="//issue/raw/files/b1d155c5b5481b334e44dbc434d42eb830adde6440b5478bdd1ecf523b9bb6d6-email_list_patch.png" />
[[Image(email_list_patch.png)]]
Cute! Setting to approved :)
Looks good here too :)
We won't be able to implement this one until sometime in late April at the earliest. We should get our mailing list activity hooked into fedmsg sometime around then.
Metadata Update from @elad: - Issue tagged with: hyperkitty
Metadata Update from @riecatnor: - Custom field artwork adjusted to None - Custom field concept_review_passed adjusted to None (was: 0) - Custom field has_complete_yaml reset (from Not yet possible) - Custom field has_description reset (from 0) - Custom field has_name reset (from 0) - Custom field needs_manual_award reset (from 0) - Custom field triaged reset (from 0) - Issue close_status updated to: None - Issue tagged with: artwork-approved, development
Metadata Update from @riecatnor: - Custom field artwork adjusted to approved (was: None) - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Custom field triaged reset (from false)
Metadata Update from @sayanchowdhury: - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Custom field triaged reset (from false) - Issue priority set to: normal (1-2 weeks) - Issue tagged with: not-yet-possible
@elad checking in to see if this badge is now ready to push? thanks!
Metadata Update from @riecatnor: - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Custom field triaged reset (from false)
Metadata Update from @smeragoel: - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Custom field triaged reset (from false) - Issue tagged with: needs-rules
Issue tagged with: AW: needed
Metadata Update from @riecatnor: - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Custom field triaged reset (from false) - Issue untagged with: AW: needed
Login to comment on this ticket.