Issue #33: Badges-Dev badge - fedora-badges

fedora-badges

#33 Badges-Dev badge

Closed: Pushed None Opened 11 years ago by oddshocks.

Idea is from here: https://github.com/fedora-infra/tahrir/issues/128

It is awarded to anyone with commits in one of the following repos:
Tahrir
Tahrir-API
* Fedbadges

Datanommer and Fedmsg are part of the stack, but are not entirely badges-related, and so commits to these repos would not earn this badge.

Looking for naming suggestions, too. :)

ralph commented 11 years ago

How about "Badge Wizard"

ralph commented 11 years ago

How about "Badge Wizard"

adamwill commented 11 years ago

I'm planning on proposing a badge for reviewing a badge definition, and/or pushing a badge to production. Would they perhaps replace this? It has much the same effect, but it rewards you for doing something rather than being something...

adamwill commented 11 years ago

Set triaged to 'yes' for all tickets, as I've hit them all already.

adamwill commented 11 years ago

Set triaged to 'yes' for all tickets, as I've hit them all already.

adamwill commented 11 years ago

just put types back in, we'll try and handle bugs here too, no new trac.

adamwill commented 11 years ago

just put types back in, we'll try and handle bugs here too, no new trac.

ryanlerch commented 11 years ago

How about "badge engineer" or "badger engineer" or "the society of Engineering Badgers"

the artwork could have our badgerfriend with a hardhat on.

ryanlerch commented 11 years ago

How about "badge engineer" or "badger engineer" or "the society of Engineering Badgers"

the artwork could have our badgerfriend with a hardhat on.

ralph commented 11 years ago

Cool. :)

How about this: We run a cronjob on the badges-backend node that once a night:

pulls down git clones of the three repos (tahrir, tahrir-api, and fedbadges).
Checks the git log to get the email addresses of all committers.
looks up those emails to see if any fas accounts are associated with them.
awards the badge to all those fas accounts it finds.

We could do this someday with a live git-hook from github that pings our servers.. but that might be getting ahead of ourselves.

I'm marking this as "manually awarded" since it doesn't fit into our regular yaml scheme -- it is awarded for activity outside of fedora's infrastructure.

ralph commented 11 years ago

Cool. :)

How about this: We run a cronjob on the badges-backend node that once a night:

pulls down git clones of the three repos (tahrir, tahrir-api, and fedbadges).
Checks the git log to get the email addresses of all committers.
looks up those emails to see if any fas accounts are associated with them.
awards the badge to all those fas accounts it finds.

We could do this someday with a live git-hook from github that pings our servers.. but that might be getting ahead of ourselves.

I'm marking this as "manually awarded" since it doesn't fit into our regular yaml scheme -- it is awarded for activity outside of fedora's infrastructure.