31c3
space (where?)
proposal for three tracks (what?)
1: Documentation
Sharing experiences on How to throw a CryptoParty
Collecting more of the existing documentation (Security in a box etc. but also single blog posts)
Getting this sh|t sorted
Improving on the Handbook
-
Make new issues
One person one issue (assign)
Qn: Status of Handbook mailing list?
improving on the
CSS for the
HTML version
immediate thought at hand: setting up an automated compilation+publication script
Compile:
Publish:
git clone https://github.com/cryptoparty/handbook.git
make install
e.g. Pandoc compiles to HTML and is written here:
${BUILD_DIR}/../cryptoparty-handbook-html
After an update:
cd handbook
git pull
Recurring: crontab entry with git pull
2: Definition
(Guiding Principles, Finding consensus etc.)
… to teach
… for teaching
-
time (when?)
Sat, 27-Dec-2014
Sun, 28-Dec-2014
16:00 Documentation
20:00 Definition
Mon, 29-Dec-2014
12:00 Definition
20:00 Documentation
Tue, 30-Dec-2014
12:00 Documentation wrap-up
14:00 Definition wrap-up
18:00 saying good bye