#483: Badge for 389-Directory Server -------------------------------------+------------------------------------- Reporter: | Owner: kamlesh komcy | Status: new Type: | Keywords: New badge idea | 389-Directory Server Priority: | Has a description: 0 minor | Artwork status: Concept Has a name: | External requirements: 1 | Triaged (triagers only): 0 Concept approved (reviewers only): | 0 | Badge definition status: | None | Manually awarded: | 1 | -------------------------------------+------------------------------------- Badge description (like "You added a co-maintainer to a package. BFF!"):
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? Patch submit in 389 2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?) Anyone 3) Why are they doing them (is this a means to a different end?) to grow the Community 4) When do they do them (every day? once a year?) every day 5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?)
Lastly, do you have any ideas for artwork concepts? Nop
#483: Badge for 389-Directory Server -------------------------------------+------------------------------------- Reporter: komcy | Owner: Type: New badge | kamlesh idea | Status: Priority: minor | new Keywords: | Resolution: 389-Directory Server | Has a name: Has a description: 0 | 1 Artwork status: Concept | Concept approved (reviewers only): External requirements: | 0 Triaged (triagers only): 0 | Badge definition status: | None | Manually awarded: | 1 -------------------------------------+-------------------------------------
Comment (by riecatnor):
A concept for this artwork could be a patch like this one: http://www.gfi.com/blog/wp-content/uploads/2011/05/Deploying-a-patch- management-process.jpg with "389" on it
#483: Badge for 389-Directory Server -------------------------------------+------------------------------------- Reporter: komcy | Owner: Type: New badge | kamlesh idea | Status: Priority: minor | new Keywords: | Resolution: Has a description: 0 | Has a name: Artwork status: Concept | 1 External requirements: | Concept approved (reviewers only): Triaged (triagers only): 1 | 1 | Badge definition status: | None | Manually awarded: | 0 -------------------------------------+------------------------------------- Changes (by jflory7):
* keywords: 389-Directory Server => * needs_manual_award: 1 => 0 * triaged: 0 => 1 * concept_review_passed: 0 => 1
Comment:
Hi komcy, I have the same feedback to this ticket as I left in #484. To further clarify, is the 389 repository in Pagure or somewhere else within Fedora's infrastructure? For a badge like this, I think it would be best if it were implemented in an automated way, so we wouldn't have to someone make a mental note to award the badge every time a patch is included. If this repo is in fedmsg, this should be possible, but any technical info you can add to explain where 389 is or where it fits into Fedora Infra would be helpful!
I would advise any future designers to hold off on designing assets here until we are sure if this is a badge we can automatically award.
badges@lists.fedoraproject.org