#125 Signing another's GPG key
Closed: declined 4 years ago by riecatnor. Opened 10 years ago by sparks.

What the badge should be granted for:
When a contributor signs another contributor's GPG key.

Badge description (like "You added a co-maintainer to a package. BFF!"):
You signed another Fedorian's GPG key. Way to go!

Anything else we need to know:
This would be a manual query from a key server (keys.fedoraproject.org)


So, we could write a cronjob that periodically:

1) goes through the list of people who have gpg key ids in FAS
2) queries the key server for who has signed that key
3) awards the badge to the signer(s) of this person's key.

That sounds pretty computationally expensive (we'll hit duplicates over and over and over again). But it should be possible, and really cool.

Whoah -- could we instrument our new keyserver with fedmsg so when new signatures are uploaded, notifications go out?

Replying to [comment:4 ralph]:

This is the inverse of #237

I just had the idea to maybe make this more stricter and only issues badges for signing other keys if the other key also signed ones own key, so it is more like #237 being done in both directions.

Possible concept for artwork: Pen with key for gpg. Use Crypto Panda (https://badges.fedoraproject.org/badge/crypto-panda) for base. Could have a pen and key crossing with different colored panda paws holding each. Consider creating matching artwork for #237

Replying to [comment:6 riecatnor]:

Possible concept for artwork: Pen with key for gpg. Use Crypto Panda (https://badges.fedoraproject.org/badge/crypto-panda) for base. Could have a pen and key crossing with different colored panda paws holding each. Consider creating matching artwork for #237

This sounds nice. I have the idea for some more related badges:

  • Badge for adding the full fingerprint of ones GPG key to FAS
  • Badge for adding the fedora e-mail address to the GPG key
  • Badge for getting the GPG key signed by cacert (http://www.cacert.org/)
  • Maybe Badge for signing the Fedora release keys

Replying to [comment:7 till]:

I have the idea for some more related badges:

Can you file separate tickets for these?

  • Badge for adding the full fingerprint of ones GPG key to FAS

Let's hold off on this one until FAS3 is written and out the door. We can get
gpg keys "right" there instead of it being kind of flimsy as it is in FAS2.

  • Badge for adding the fedora e-mail address to the GPG key

Yeah, this would work. For artwork concept, we could use some combination of
the panda key and the Fedora logo. Maybe a "keyring" with the panda key on it
and a Fedora logo token hanging on?

Interesting. This one is a little more far-flung from Fedora, but still interesting. Not sure what to do for artwork concept here.

  • Maybe Badge for signing the Fedora release keys

Very interesting, this one. For artwork concept I'm imagining something like a
'saint' walking through a crowd with every reaching out to touch them. Like
this
http://i2.dailyrecord.co.uk/incoming/article1772716.ece/alternates/s1227b/Pope%20Francis%20leans%20out%20to%20touch%20a%20child%27s%20head%20as%20he%20arrives%20in%20Saint%20Peter%27s%20Square%20for%20his%20inaugural%20mass%20at%20the%20Vatican.jpg
except with the people all replaced with keys (a big key with a halo and lots
of little keys positioned lower and around it, somehow pointing at it).
Forgive me if this is ridiculous.

Replying to [comment:8 ralph]:

Replying to [comment:7 till]:

I have the idea for some more related badges:

Can you file separate tickets for these?

  • Badge for adding the full fingerprint of ones GPG key to FAS

Let's hold off on this one until FAS3 is written and out the door. We can get
gpg keys "right" there instead of it being kind of flimsy as it is in FAS2.

yes, probably this is something that should be required anyhow for all the other GPG related badges because otherwise the keys cannot be perfectly identified.

I created tickets for the other ideas:
ticket:343
ticket:344
ticket:345

When the badges are ready, I will create the necessary scripts if needed.

Metadata Update from @riecatnor:
- Custom field artwork adjusted to has_concept
- Custom field concept_review_passed adjusted to None (was: 0)
- Custom field has_complete_yaml reset (from Not yet possible)
- Custom field has_description adjusted to on (was: 1)
- 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

6 years ago

Metadata Update from @riecatnor:
- Custom field has_complete_yaml reset (from false)
- Custom field has_name reset (from false)
- Custom field needs_manual_award reset (from false)
- Issue tagged with: artwork-intermediate

6 years ago

Metadata Update from @riecatnor:
- Custom field has_complete_yaml reset (from false)
- Custom field has_name reset (from false)
- Custom field needs_manual_award reset (from false)
- Issue tagged with: artwork-needed, community

6 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_name reset (from false)
- Custom field needs_manual_award reset (from false)

4 years ago

Metadata Update from @riecatnor:
- Custom field external_requirements adjusted to on
- Custom field has_complete_yaml adjusted to on (was: false)
- Custom field has_name 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)

4 years ago

Login to comment on this ticket.

Metadata