Badge description (like "You added a co-maintainer to a package. BFF!"): - You submitted your first happiness packet!
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? - For submitting a happiness packet (https://www.happinesspackets.io/).
2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?) - Everyone who's part of Fedora community
3) Why are they doing them (is this a means to a different end?) - As part of Fedora Appreciation Week 2018 (https://pagure.io/fedora-commops/issue/110), we're trying to encourage people to show their appreciation for fellow contributors. Plus it's part of my GSoC project.
4) When do they do them (every day? once a year?) - Hopefully throughout the year after Fedora Appreciation Week
5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?) - Web interface - We're going to be having our own version of Fedora Happiness Packets where users can send these packets.
Lastly, do you have any ideas for artwork concepts? - Maybe something with little blue hearts
@algogator I love this idea! I adapted a piece of artwork from the link you provided.. What do you think? @mleonova - thoughts?
Metadata Update from @riecatnor: - Custom field artwork adjusted to None - Custom field concept_review_passed adjusted to None
Metadata Update from @riecatnor: - Issue assigned to riecatnor
Metadata Update from @riecatnor: - Issue tagged with: artwork-easy, community, review
Metadata Update from @riecatnor: - Custom field artwork adjusted to has_draft (was: None)
thanks @riecatnor, it looks lovely :)
@riecatnor great start! I feel like it needs a bit more umph =) Blue does not exactly say 'happiness' to me. Maybe yellow? Or the color from the website?
When I hear 'happiness packet' I literally imagine a bag full of happiness, like the one Rowan Atkinson prepares in Love Actually =) Could it be a paper bag with sun shining form it? (an idea)
Let's discuss it at the meeting!
@mleonova @riecatnor We're sticking to blue cos keeping it Fedora themed https://pagure.io/design/issue/600
@algogator since you've created a ticket to change the envelope design, I think we need to wait a bit with this badge - until we have the updated envelope.
@algogator @mleonova yes, agreed. Let's wait until the logo has been established and we can easily create badge artwork based on that :)
@mleonova @riecatnor Ok. Do I need to write the badge rule for this? What is a community badge exactly?
@jflory7 Do we do this after the happiness packet is connected to fedmsg? or is it already done?
@sayanchowdhury We can start working on this, happinesspackets has been hooked up to fedmsg (https://pagure.io/fedora-infrastructure/issue/7053), just have some trouble shooting left
Metadata Update from @mleonova: - Issue assigned to mleonova (was: riecatnor)
So here's an updated version with the logo element:
Metadata Update from @mleonova: - Issue assigned to riecatnor (was: mleonova)
@mleonova :heart_eyes: lovely
@mleonova so cute! Setting to approved :)
Metadata Update from @riecatnor: - Issue tagged with: artwork-approved
Metadata Update from @riecatnor: - Custom field artwork adjusted to approved (was: has_draft)
Hey everyone
I was just wondering what's the process of submitting a YAML rule?
You can clone this very repo. The repo contains a rules directory within then you can create the YAML rule and create a PR.
@sayanchowdhury cool!
Hey @sayanchowdhury could you review this PR #653 for the YAML rule
I see the artwork has been approved. Is this something we can implement? @sayanchowdhury
Hi @riecatnor. This ticket is blocked on technical implementation. The good news is eventually this badge will be possible (reference: fedora-happiness-packets#96). @shraddhaag is currently working on this. The bad news is it will probably be a couple more months before we're ready to implement the badge.
I'm marking this ticket as blocked and assigning it to me for now. Hopefully I will have an update before too long.
Metadata Update from @jflory7: - Custom field concept_review_passed adjusted to not_yet_possible (was: None) - Custom field has_description adjusted to on - Custom field has_name adjusted to on - Custom field triaged adjusted to on - Issue assigned to jflory7 (was: mleonova) - Issue tagged with: blocked, needs-rules
Metadata Update from @jflory7: - Issue untagged with: review
Hi! The technical issues are resolved and we'll deploy Fedora Happiness Packet soon. We can get this one unblocked :)
Since the previous discussion, we have changed our approach on how badges will be awarded. Our present strategy is when a Happiness Packet is sent, both sender and recipient receive badges. For every 1, 5, 10, 25, 50, 100 happiness packets sent/received, badges are awarded. The approach is similar to Pagure badges for clarification.
It'll be awesome if we could start working on the art work for the above mentioned badges :)
Metadata Update from @jflory7: - Assignee reset - Custom field artwork adjusted to has_draft (was: approved) - Custom field concept_review_passed adjusted to passed (was: not_yet_possible) - Issue untagged with: blocked, needs-rules - Issue tagged with: artwork - needed
To follow up on artwork, the Design Team approved a final logo in design#606. The SVG artwork is here.
@shraddhaag For reference, could you upload the YAML rule files you wrote into this ticket for reference? We can keep track of them here for now, and open a PR with the rules once everything is ready and in place. :)
@jflory7 Good idea! I uploaded the rules here for reference. The names of the badges and the description needs some to be revised but the rules are in place.
Metadata Update from @riecatnor: - Issue untagged with: artwork - approved
Metadata Update from @riecatnor: - Issue assigned to smeragoel
@riecatnor hey! so this is my first shot at making the series. I'm going to play around with the size, colour and positioning before making other badges of the series.
I went through the badge guidelines to see if there were any rules regarding the colour of the numbering but didn't find any (except the general do's and don't's), so I browsed the badge index to see other numberings and started off with this pink combination
I like this placement better as it has better clarity (doesn't interfere with the cupcake logo too!)
Yellow is better associated with happiness so I thought I'd experiment with yellow.
Let me know which one works best! I think the last one is the one I'd want to take forward and work upon (better position, colour reflects the theme too)
@smeragoel I like the yellow color too. A couple suggestions for you: - Make the cupcake just a tiny bit smaller, and move it a little to the left to give the number more space - use a number with two digits, instead of 3. Because of the scale of this badge, I doubt we will make one with "100" as a goal. You should be able to scale that up a little bit. - add in another darker stroke behind the numbering you have.. I think there is a dark brown color in the badges extended palette
Thanks!
@riecatnor Something like this?
@smeragoel looks great! Looks they want the following numbering: 1, 5, 10, 25, 50, 100 (guess they are being ambitious ;)
@riecatnor here is the full series! I had to tweak the size and position, because of how different numberings took up space. I hope that's not an issue? Let me know if I need to make any changes!
Hi @smeragoel I opened the first PNG and it was 242x242 pixels(should be 256x256 pixels). Wanna double check the rest and re-upload with correct sizing? Otherwise, they look great! Thanks!!
Fixed! I was exporting it as a drawing not a page, that's why. Oopsies haha
They look great, thanks! Setting to approved :)
Metadata Update from @riecatnor: - Issue untagged with: artwork - needed - Issue tagged with: artwork - approved, ready to push
Issue tagged with: AW: needed
Metadata Update from @riecatnor: - Issue untagged with: AW: needed
This repository has moved over to Fedora Forge. All issue tickets have been transferred in there.
Metadata Update from @t0xic0der: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)