What the badge should be granted for:
Proposing a change to the packaging guidelines which gets accepted.
Badge description (like "You added a co-maintainer to a package. BFF!"):
Can't think of anything cleverer/funnier than "You proposed a change to the packaging guidelines which got accepted."
Anything else we need to know:
Maybe that should be done in the same way as the supplementary wallpaper submissions: one badge for proposing a change to the guidelines, and one badge if the change gets accepted?
For the artwork, maybe some kind of scroll or grimoire, with the word "APPROVED" stamped on it?
attachment package-proposal-approved.svg
attachment <img alt="package-proposal-approved.png" src="https://pagure.io/Fedora-Badges/issue/raw/files/1df6e1aa52c18d931640c239d561879e8fda7aefc56c06a72325324a0717fb45-package-proposal-approved.png" />
attachment <img alt="package-proposal-approved.png" src="//issue/raw/files/1df6e1aa52c18d931640c239d561879e8fda7aefc56c06a72325324a0717fb45-package-proposal-approved.png" />
@bochecha, Hey: here is my artwork proposal for this badge, I think we could make this into a series. I have a few questions for you, before we make the artwork: How often do people propose changes, how much work goes into a proposal and how often do those get accepted?
[[Image(package-proposal-approved.png)]]
@bascht, artwork looks great! I will set to approved once we figure out all the details on numbering and create the badges :) thanks!
Metadata Update from @bochecha: - Issue assigned to bascht
Metadata Update from @riecatnor: - Custom field artwork adjusted to approved - Custom field concept_review_passed adjusted to None (was: 0) - Custom field has_complete_yaml reset (from None) - 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
Any updates here? To finish artwork for this badge we need the following questions addressed: How often do people propose changes, how much work goes into a proposal and how often do those get accepted?
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 @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 tagged with: artwork-approved, development
I'd be happy to help, but I don't know the answers to those questions. :)
How often do people propose changes?
Most of the issues here are guidelines changes:
https://pagure.io/packaging-committee/issues?status=Closed
It's about 5 issues per month.
How much work goes into a proposal?
Depends on the quality and size of the proposal. Can be a one world change, can be a new guidelines for a new programming language. This is very hard question.
How often do those get accepted?
Seems like almost every time a conclusion is made and the change is accepted.
Metadata Update from @churchyard: - 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)
Flock 2019 badge issue triage, closing old tickets. Please reopen if still relevant. Thanks!
Metadata Update from @riecatnor: - Custom field external_requirements adjusted to on - Custom field has_complete_yaml adjusted to on (was: false) - Custom field has_description adjusted to on (was: false) - Custom field has_name adjusted to on (was: false) - Custom field needs_manual_award adjusted to on (was: false) - Custom field triaged adjusted to on (was: false) - Issue close_status updated to: declined - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.