= Badge Description =
= Understanding badge =
1) What are those activities?
2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?)
3) Why are they doing them (is this a means to a different end?)
4) When do they do them (every day? once a year?)
5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?)
= Artwork concepts =
= Other discussion =
As of the moment, I don't know if there is a fedmsg hook in place to automate this badge series. If there is, this ticket's concept can be marked as "approved". If not, this ticket should be closed and the badge definition status set to "not yet possible".
Note, this ticket is similar to #434.
I am CCing robyduck and pingou to help advise on this one in terms of whether it is possible.
Yes there is a fedmsg, I uploaded the yml file to ticket #434, just for the first badge but all others are similar. See https://fedorahosted.org/fedora-badges/attachment/ticket/434/long-life-to-pagure-01.yml
Thanks for confirming, robyduck!
Hi! I've made some concepts of the badges, based off of your <optimistic> suggestion </optimistic>. [[Image(http://i.imgur.com/nnk3nRp.png)]] [[Image(http://i.imgur.com/RKDOJu0.png)]] [[Image(http://i.imgur.com/YPziYlT.png)]] [[Image(http://i.imgur.com/QqNm5nF.png)]]
attachment 442 1 v1.svg
attachment 442 10 v1.svg
attachment 442 25 v1.svg
attachment 442 100 v1.svg
Replying to [comment:3 hegataro]:
Hi! I've made some concepts of the badges, based off of your <optimistic> suggestion </optimistic>.
Wow, these look awesome!! Thanks so much for tackling these, hegataro. I'm CCing a few more Design Team members to take a look, and maybe we can move forward on pushing this badge out. :)
I'm still thinking this badge just replies what we have in ticket 434. Being added to as many repos as possible is not really a measurement of contributing. Doing stuff to one or more repos, committing changes and pushing them out is what we should get here IMHO (which is ticket 434, I would not make two series for the same thing).
Replying to [comment:5 robyduck]:
The idea behind this proposal is that it's supposed to fit into an on-boarding series for teams like Fedora Infrastructure especially (and other development-oriented SIGs) to help document the steps for newcomers to get involved. Their progress would be marked with badges as they progress in the levels of contributing.
While you can commit as much as you want to any given Pagure repo(s), being added to other repositories encourages developers to reach out to other projects, find ways to contribute, and after making meaningful contributions, they could be added to another repository. There is a possibility for the commits badge to be awarded for inward contributions (e.g. you are working on a personal project in Pagure), but I believe this one holds its merit as a concept and an idea because it's encouraging people to explore Pagure, find projects that interest them, and make contributions in places they might not have known existed prior.
I'm still +1 to seeing both proposals for #434 and this one become their own series.
Hey hegataro! Great work! One little thing: let's make the outlines thicker to make the graphics stand out. This badge can be an inspiration: [[Image(https://badges.fedoraproject.org/pngs/pkgdb-partners-in-crime.png)]]
Also please check the background color in the badge guidelines, we want to keep them consistent.
Heya! I've thickened the outlines and made the background color more in-tune with the guidelines [[Image(http://i.imgur.com/N3FGw8Z.png)]] [[Image(http://i.imgur.com/toibLLZ.png)]] [[Image(http://i.imgur.com/bHpFnkR.png)]] [[Image(http://i.imgur.com/pJ3RjO2.png)]]
attachment <img alt="442 1 v2.svg.png" src="https://pagure.io/Fedora-Badges/issue/raw/files/d366b9b7dc59d166fe4664007936625315977926bdc658651f894b014f2740dc-442_1_v2.svg.png" />
attachment <img alt="442 1 v2.svg.png" src="//issue/raw/files/d366b9b7dc59d166fe4664007936625315977926bdc658651f894b014f2740dc-442_1_v2.svg.png" />
attachment <img alt="442 10 v2.svg.png" src="https://pagure.io/Fedora-Badges/issue/raw/files/d8de726ed5f5d4f1433e3766635e0e7a63e0936047872e41aa752512569fec16-442_10_v2.svg.png" />
attachment <img alt="442 10 v2.svg.png" src="//issue/raw/files/d8de726ed5f5d4f1433e3766635e0e7a63e0936047872e41aa752512569fec16-442_10_v2.svg.png" />
attachment <img alt="442 25 v2.svg.png" src="//issue/raw/files/9d044ebde873b70ae3d42f7d43d4c93c5878a3d3ca65fa578b4b532083a18e97-442_25_v2.svg.png" />
attachment <img alt="442 25 v2.svg.png" src="https://pagure.io/Fedora-Badges/issue/raw/files/9d044ebde873b70ae3d42f7d43d4c93c5878a3d3ca65fa578b4b532083a18e97-442_25_v2.svg.png" />
attachment <img alt="442 100 v2.svg.png" src="https://pagure.io/Fedora-Badges/issue/raw/files/e374a19cfe6b2ee40b98d3a5cfdcbe60f261f4473f43faa5404356cf5c423176-442_100_v2.svg.png" />
attachment <img alt="442 100 v2.svg.png" src="//issue/raw/files/e374a19cfe6b2ee40b98d3a5cfdcbe60f261f4473f43faa5404356cf5c423176-442_100_v2.svg.png" />
attachment 442 1 v2.svg
attachment 442 10 v2.svg
attachment 442 25 v2.svg
attachment 442 100 v2.svg
For what it's worth, I think this artwork is priceless. :)
attachment licensed-to-push-01.yml
attachment licensed-to-push-02.yml
attachment licensed-to-push-03.yml
attachment licensed-to-push-04.yml
What is the title of the badge referencing? I'm not sure I follow the reference. Either way, from the image you have uploaded I do not think that the artwork proposed is translating to the tail end of a jet.
Ah, ok, it is referencing the Beastie Boys album.. Unfortunately, I still don't think the artwork is translating well. And I am not sure that this reference will come across for a lot of folks. Perhaps we should try another concept for the artwork.
I like the second concept for this one, could be straight forward and allow for a nice series. Would be nice to have the Pagure logo on the card :)
Metadata Update from @jflory7: - Issue assigned to hegataro
Metadata Update from @riecatnor: - Custom field artwork adjusted to None - Custom field concept_review_passed adjusted to None (was: 1) - Custom field has_complete_yaml reset (from None) - Custom field has_description adjusted to on (was: 1) - Custom field has_name adjusted to on (was: 1) - Custom field needs_manual_award reset (from 0) - Custom field triaged adjusted to on (was: 1) - Issue close_status updated to: None - Issue tagged with: artwork-intermediate, artwork-needed, development
Metadata Update from @riecatnor: - Custom field artwork adjusted to needed (was: None) - Custom field has_complete_yaml reset (from false) - Custom field needs_manual_award reset (from false)
@skamath Could you confirm that these badge rules are still up to date?
Metadata Update from @jflory7: - Custom field has_complete_yaml reset (from false) - Custom field needs_manual_award reset (from false)
The yml looks good to me :)
Closing this ticket due to inactivity during Badges virtual hackfest. Please reopen if their is renewed interest. Thanks!
Metadata Update from @riecatnor: - Custom field has_complete_yaml reset (from false) - Custom field needs_manual_award reset (from false) - Issue close_status updated to: declined - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.