Look at ohloh stats or similar for upstream projects we ship and give a badge for upstream commits.
I'm gonna go out on a limb and assume that this has some kind of 'external requirement' (which is what we're using to say 'something has to be done outside of badges before we can implement this badge') - i.e. we don't actually have the ability to query ohloh in this way yet.
Set triaged to 'yes' for all tickets, as I've hit them all already.
just put types back in, we'll try and handle bugs here too, no new trac.
Note that Ohloh is not the only source to get information about FOSS projects contributions. Not eveyone has as an Ohloh account, but you can see Github or other forges (even independent repositories). Why not make this manual awarded?
Hm, if we did it manually for every user it would get overwhelming for the badges admins (me) I think.
What if we made specific badges for specific projects or groups of projects like we did here: https://badges.fedoraproject.org/badge/badge-off!
For instance, we could have a 'kernel developer' badge or a 'systemd developer' badge. we could periodically do git checkouts of the upstream repos, look for new fedora-based contributors, and award them.
I really like the idea!
A possible list of projects we could track: the ones you just mentioned: kernel systemd some interesting (and listed because of their scope): Python Mozilla OpenStack Drupal Apache (not just the web server) GNU (official GNU software) and a very large etc.
That's the problem I see. There are many great projects. How would we choose which ones to add?
With Fedora Badges in general, my policy has been "if its possible, then let's do it".
Perhaps we close this ticket and create new individual ones for each of the potential upstreams. We then add them whenever someone is able submit artwork for one (and it gets approved by the design-team).
Oh, I guess each one also hinges on the time someone has to code up a script to check for new recipients. We can probably modify this script to work for all of them: http://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/badges-backend/files/cron/award-badges-dev-badge
I think the badge could be just the upstream logo wrapped with a common border.
Checking in on this badge. Is it something we still want/can do? If so please make it clear if we need one badge or if this will be a series. If its possible and I understand this request correctly, my vote is just one badge for all upstream commits.
Metadata Update from @riecatnor: - Custom field artwork adjusted to has_concept - Custom field concept_review_passed adjusted to passed (was: 0) - Custom field has_complete_yaml reset (from Not yet possible) - Custom field has_description reset (from 0) - Custom field has_name adjusted to on (was: 1) - Custom field needs_manual_award reset (from 0) - Custom field triaged adjusted to on (was: 1) - Issue close_status updated to: None
¯_(ツ)_/¯
Metadata Update from @riecatnor: - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field needs_manual_award reset (from false) - Issue tagged with: artwork-intermediate, artwork-needed
Metadata Update from @riecatnor: - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field needs_manual_award reset (from false) - Issue tagged with: development
Flock 2019 badge issue triage, closing old tickets. Please reopen if still relevant. Thanks!
Metadata Update from @riecatnor: - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field needs_manual_award reset (from false)
Metadata Update from @riecatnor: - Custom field external_requirements adjusted to on - Custom field has_complete_yaml adjusted to on (was: false) - Custom field has_description adjusted to on (was: false) - Custom field needs_manual_award adjusted to on (was: false) - Issue close_status updated to: declined - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.