> On Apr 2, 2017, at 4:28 PM, Sam Ruby <[email protected]> wrote: > > On Sun, Apr 2, 2017 at 7:25 PM, Craig Russell <[email protected]> > wrote: >> Here's what I'd like to do for the next time around. >> >> 1. New whimsy page requires userid login. Pre-fill form with Full Name taken >> from Full Name in iclas.txt, e-mail taken from iclas.txt. >> >> 2. When form is filled, (print) will send a copy to printer and save a file >> in foundation/Meetings/YYYYMMDD/memapp-pending/availid.json >> >> 3. Candidate signs, scans, emails form to secretary@ >> >> 4. Secmail selects memapp and selects candidate from pull-down (just like >> today) >> >> 5. Secmail finds availid.json and pre-fills form fields from json file. >> >> 6. Secretary is so very grateful that he/she does not need to read bad >> handwriting. Just verify signature and we're done. > > Excellent hack-a-thon project idea! :-)
That's what I thought. > >> I'm also open to 2.5 (sign with gpg) button creates a file availid.pdf and >> calls system to sign, creating >> foundation/Meetings/YYYYMMDD/memapp-pending/availid/memapp-received.txt and >> memapp-received.txt.asc >> and then sending email directly to secretary requesting review/approval of >> document. > > Not likely to happen as the web server doesn't (and never should) have > access to the user's gpg private key. Of course, the user can use > either the command line or native tools instead of printing, signing > by hand, and scanning. 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. In order to facilitate digital signature, we (secretary) should add some text to member-app.txt to describe how it should be done. Craig > >> Craig L Russell >> [email protected] > > - Sam Ruby
