From: Zak Rogoff Date: Fri, 21 Aug 2015 20:26:29 +0000 (-0400) Subject: Testing a crappy method for removing the border from intros that don't need it. X-Git-Url: https://vcs.fsf.org/?a=commitdiff_plain;h=1dd9bd62cd03f9e790ed77bf7d14945ed78b6a72;p=enc.git Testing a crappy method for removing the border from intros that don't need it. --- diff --git a/en/workshops.html b/en/workshops.html index aa53b2f8..3c4fa3c6 100644 --- a/en/workshops.html +++ b/en/workshops.html @@ -129,12 +129,15 @@ step towards protecting their privacy with free software.
+

#2 Plan The Workshop

Once you've got at least one interested friend, pick a date and start planning out the workshop. Tell participants to bring their computer and ID (for signing each other's keys). Also tell the participants to bring dice (for making passwords), but also bring as many as you can, in case they don't. Make sure the location you select has an easily accessible Internet connection, and make backup plans in case the connection stops working on the day of the workshop. Libraries, coffee shops, and community centers make great locations. Try to get all the participants to set up an Enigmail-compatible email client before the event. Direct them to their email provider's IT department or help page if they run into errors.

Estimate that the workshop will take forty minutes plus ten minutes for each participant, at a minimum. Plan extra time for questions and technical glitches.

The success of the workshop requires understanding and catering to the unique backgrounds and needs of each group of participants. Workshops should stay small, so that each participant receives more individualized instruction. If more than a handful of people want to participate, keep the facilitator to participant ratio low by recruiting more facilitators, or by facilitating multiple workshops. Small workshops among friends work great!

+
+