#433 Fedora Developer Portal badges
Closed: declined 2 years ago by riecatnor. Opened 5 years ago by phracek.

Badge description (like "You added a co-maintainer to a package. BFF!"):

We would like to create a badge or badges for folks who help us with Fedora Developer Portal.

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?
Everybody who create a content should receive a badge for helping with community and developers.
2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?)
The folks who create a content can be packagers, newcomers, veterans, users or everybody who can help other folks for developing on Fedora
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?)
Folks who creates contents do it once a year, I guess.
5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?)
A content can be created via GitHub interface, or editor which is able to write a MarkDown structure.

Lastly, do you have any ideas for artwork concepts?

Fedora Developer Portal is available here: developer.fedoraproject.org
Fedora Developer Portal team is reachable on freenode #developer-portal

May I did not understand some questions.
Do not hesitate to contact us on IRC.

Greetings
Petr


Is there any action needed from Fedora Developer Portal point of view?

Potential Concept: Mash up of this badge: https://fedorahosted.org/fedora-badges/ticket/405 and change what is on the computer to {} or to gears. Take out year and change colors of ring and background.

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.

Metadata Update from @svitek:
- Issue assigned to svitek

4 years ago

Metadata Update from @svitek:
- Custom field artwork adjusted to has_concept
- Custom field concept_review_passed adjusted to passed (was: 1)
- Custom field has_complete_yaml reset (from None)
- Custom field has_description reset (from 0)
- Custom field has_name reset (from 0)
- Custom field needs_manual_award reset (from 0)
- Custom field triaged adjusted to on (was: 1)
- Issue close_status updated to: None

4 years ago

Metadata Update from @svitek:
- Custom field has_complete_yaml reset (from false)
- Custom field has_description reset (from false)
- Custom field has_name reset (from false)
- Custom field needs_manual_award reset (from false)

4 years ago

@phracek I've created a mock-up for your badge. Let me know if it looks okay.

Metadata Update from @svitek:
- Custom field has_complete_yaml reset (from false)
- Custom field has_description reset (from false)
- Custom field has_name reset (from false)
- Custom field needs_manual_award reset (from false)

4 years ago

Metadata Update from @riecatnor:
- Custom field has_complete_yaml reset (from false)
- Custom field has_description reset (from false)
- Custom field has_name reset (from false)
- Custom field needs_manual_award reset (from false)
- Issue tagged with: development, review

4 years ago

Closing this ticket due to inactivity during Badges virtual hackfest. Please reopen if their is renewed interest. Thanks!

Metadata Update from @riecatnor:
- Custom field has_complete_yaml reset (from false)
- Custom field has_description reset (from false)
- Custom field has_name reset (from false)
- Custom field needs_manual_award reset (from false)
- Issue close_status updated to: declined
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Attachments 2
Attached 4 years ago View Comment
Attached 4 years ago View Comment