One of my pet peeve with badges is that we most of the time focus on what we can use as trigger for badges, but not on the result we want to achieve, or the overall benefit for the project.
In order to start making people think about it, I would propose that we change the default template for proposing a badge to ask a question about it. (exact phrasing to be discussed).
For example, what activity do you want to incentivize , what behavior do you want to reward and how does it benefit the project.
For one simple example, using modern ssh keys would be beneficial for security, so having a badge for that could be a good incentive.
Another example of a bad behavior would be "uploaded rpms every day since 1 year", because this would push people to not taking vacation, so that would be a bad badge.
By pushing incentives in the front as a question, I hope this will kickstart a discussion on why we do badges, and move from "this badge can be done" (because there is a message on the bus) to "here is how we want to reward best practice".
Hi @misc I am totally +1 to this idea. Here is an edited version of the template, let me know your thoughts. I added the "badge title" field and question 6
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?
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?)
6) What behavior do you want to incentivize with this badge and how does it benefit the project?
Metadata Update from @riecatnor: - Custom field artwork adjusted to None - Custom field concept_review_passed adjusted to None
@misc @riecatnor Hey, I wanted to say something in this too. As someone who is new to the community, the basic workflow of designing can seem a bit confusing sometimes. I would suggest few more things which could be done to clear the thought process: 1) the person who puts up the issue for the badges, should include a reference link for the topic for which the badge is being made, and a reference artwork also for the kind of posture or positions they expect the characters to be in. 2) differentiate which animal is for which kind of task, for eg- panda for creative community topic, badgers for security, corporate, etc 3) I liked the idea of rewarding badges, we could set up color-coded badges for regular activities especially ones that include monthly or weekly contributions, such as: red for level 1, yellow for level 2, etc or 1 star, 2 stars system, and further on as their contributions increase. 4) the documentation can be improved a bit. it can have direct hyperlinks to the artworks, instead of searching each and every artwork, going straight from the hyperlinks would make it easier. Do tell me if you find these useful. 😁👀
I found this old ticket that could also be relevant to this discussion: https://pagure.io/fedora-badges/issue/498
Log in to comment on this ticket.