Hurry up and wait!
Oct. 23rd, 2013 05:06 pmI've been away on two weekend trips, and checking in on the progress of the Privacy Handbook re-licensing. I am not optimistic; the FSF doesn't seem impressed by the need to change the document's license.
I was pointed to an old repository of the Handbook that may pre-date the copyright transfer to the FSF, but this is starting to get increasingly archaic -- do I want to assess the even-more-outdated SGML in this old repository and re-convert it?
Frankly, if I'd just started writing a new GnuPG tutorial back in September, I would probably have finished a first draft at this point. So I'm going to start thinking about the outline for a new GnuPG introduction.
Ideas:
Possible outline:
I was pointed to an old repository of the Handbook that may pre-date the copyright transfer to the FSF, but this is starting to get increasingly archaic -- do I want to assess the even-more-outdated SGML in this old repository and re-convert it?
Frankly, if I'd just started writing a new GnuPG tutorial back in September, I would probably have finished a first draft at this point. So I'm going to start thinking about the outline for a new GnuPG introduction.
Ideas:
- Limit conceptual explanation of cryptography to the high-level; don't bother explaining hash functions, symmetric ciphers, etc.
- Try to avoid suggesting overrides to GnuPG's config; instead, we should trust that GnuPG has sensible defaults.
- Encourage people to use mailer integration. Don't try to document the various GUIs; just link to them.
Possible outline:
- Cryptography and GnuPG concepts.
- Generating a key.
- Using GnuPG in your e-mail program.
- Using GnuPG from the command line. (Possibly make this an appendix?)
- Managing your keys.