#433: Fedora Developer Portal badges -------------------------------------+------------------------------------- Reporter: phracek | Owner: Type: New badge | phracek@… idea | Status: Priority: minor | new Keywords: | Resolution: Has a description: 0 | Has a name: Artwork status: Concept | 0 External requirements: | Concept approved (reviewers only): Triaged (triagers only): 1 | 1 | Badge definition status: | None | Manually awarded: | 0 -------------------------------------+------------------------------------- Changes (by jflory7):
* cc: ralph, sayan (added) * triaged: 0 => 1 * has_artwork: None => Concept * concept_review_passed: 0 => 1
Comment:
Hi phracek, thanks for submitting this ticket! I'm going through some older ones as part of a triage this morning…
I am curious about if we can automate this one. I know we can publish GitHub repositories to fedmsg. Is it possible for us to extract FAS usernames from GitHub repos on fedmsg? If so, then this should be an easy badge to automate. If $FAS_USERNAME commits to GitHub repo, award badge (or at least, this is how I imagine it). Of course, there is the unavoidable issue where if someone's GitHub username is different from their FAS username, it will not be awarded. But I think we can probably set some of the Fedora Developer Portal team members with awarding privileges to cover those times where it needs to be manually awarded.
I'm CCing Ralph and Sayan to this ticket to see if they could offer a more sound technical description or explanation of whether this badge is possible to automate.