2026-04-13 20:53 UTC
I'm working with some folks on licensing for a repository that contains:
- Documentation (written by the team, but meant to be shared)
- GPG public keys (which are also replicated on plenty of public key servers around the internet)
I'm thinking the docs should be CC-BY, but that doesn't really make sense for the public keys.
Any advice here?
(I don't really want to get into the weeds as to why they're putting public keys in a git repository)
Replies (1)
-
@patrizia@hachyderm.io 2026-04-13 21:21
@pleia2@floss.social It might be worth checking if encryption keys are copyrightable (I don't think they would be, but that's a non-expert opinion). If they're not, I think you'd be fine to just put them in a CC-BY repo. If they are, it's not uncommon to see a different licence for a different set of files.