Craig Russell wrote on 4/2/17 7:54 PM: ...snip... > I was thinking that whimsy would be running on the candidate's > computer and it could simply call the command line gpg tool to create > the signature. But if whimsy is running on whimsy.apache.org, signing > would have to be manual.
Unless someone wants to fiddle with OpenPGP.js, the whole actual signing with your key seems to be more work than it's worth, IMO. > > In order to facilitate digital signature, we (secretary) should add > some text to member-app.txt to describe how it should be done. The larger question: is there any standard structure that we can use to create/display/manage documentation for Whimsy bits? We have a lot of different corporate and infra processes that whimsy helps with, but is not necessarily the canonical command line way to do things. Is there some way we can write once, read everywhere the bits of help docs for our processes? 8-) -- - Shane https://www.apache.org/foundation/marks/resources P.S. Working on actually earning committer chops this month...
