#358: Add projects to anitya -------------------------------------+------------------------------------- Reporter: | Owner: pingou | Status: new Type: | Keywords: anitya New badge idea | Has a description: 0 Priority: | Artwork status: None minor | External requirements: Has a name: | Triaged (triagers only): 0 0 | Concept approved (reviewers only): | 0 | Badge definition status: | None | Manually awarded: | 0 | -------------------------------------+------------------------------------- What the badge should be granted for: Adding a project to anitya
Badge description (like "You added a co-maintainer to a package. BFF!"): You added a project to anitya
Anything else we need to know: * Anitya is fedmsg aware * Relates to https://fedorahosted.org/fedora-badges/ticket/357 * Could be made a serie
#358: Add projects to anitya -------------------------------------+------------------------------------- Reporter: pingou | Owner: Type: New badge | Status: idea | new Priority: minor | Resolution: Keywords: anitya | Has a name: Has a description: 0 | 0 Artwork status: None | Concept approved (reviewers only): External requirements: | 0 Triaged (triagers only): 0 | Badge definition status: | None | Manually awarded: | 0 -------------------------------------+-------------------------------------
Comment (by pnemade):
fedmsg is already aware. Can we have badge logo designs here now?
#358: Add projects to anitya -------------------------------------+------------------------------------- Reporter: pingou | Owner: Type: New badge | Status: idea | new Priority: minor | Resolution: Keywords: anitya | Has a name: Has a description: 0 | 0 Artwork status: None | Concept approved (reviewers only): External requirements: | 0 Triaged (triagers only): 0 | Badge definition status: | None | Manually awarded: | 0 -------------------------------------+-------------------------------------
Comment (by riecatnor):
The best way to prepare badge tickets for a designer to work on is to give information.
Ways to expedite the badge design process: - Contribute potential concepts for the artwork - Define what category it will fall under (Categories are content, development, quality, community, events and miscellaneous) - Provide information about what the badge is about and include links. Answering potential questions a designer might have can help provide inspiration for the design. For example: - what is anitya? - what kind of projects get added - how do you add projects?
Providing this info will help get this design done a lot quicker :)
#358: Add projects to anitya -------------------------------------+------------------------------------- Reporter: pingou | Owner: Type: New badge | Status: idea | closed Priority: minor | Resolution: Keywords: anitya | duplicate Has a description: 0 | Has a name: Artwork status: None | 0 External requirements: | Concept approved (reviewers only): Triaged (triagers only): 0 | 0 | Badge definition status: | None | Manually awarded: | 0 -------------------------------------+------------------------------------- Changes (by ralph):
* status: new => closed * resolution: => duplicate
Comment:
riecatnor and I discussed this one yesterday and decided to close it as a duplicate of #358 (even though they're technically separate events). It is quite likely that someone who adds a project to anitya will also map it to Fedora.. so people who get one badge are just going to also get the other. We have other badges that work this way, like tagger votes and tagger adds, but we're trying to cut down on the excess of badges we have for packagers while increasing the badges we have available for non- packager non-developer roles (translations, docs, design, marketing, etc..).
Thanks for the idea!
badges@lists.fedoraproject.org
-
fedora-badges