44 < meta charset ="utf-8 ">
55 < meta http-equiv ="X-UA-Compatible " content ="IE=edge ">
66 < meta name ="viewport " content ="width=device-width, initial-scale=1 ">
7- < meta name ="description " content ="Program It's been a difficult task to create a program, considering we received 40 proposals and time only allows for a maximum of 9 slots. Many promising proposals had to be left out to our ... ">
7+ < meta name ="description " content ="Program 2016 It's been a difficult task to create a program, considering we received 40 proposals and time only allows for a maximum of 9 slots. Many promising proposals had to be left out to our ... ">
88 < meta name ="keywords " content ="">
99 < link rel ="icon " href ="/favicon.ico ">
1010
11- < title > Program - Swiss Python Summit</ title >
11+ < title > Program 2016 - Swiss Python Summit</ title >
1212
1313 <!-- Stylesheets -->
1414 < link href ="/theme/css/bootstrap.min.css " rel ="stylesheet ">
8787 < div class ="row ">
8888 < div class ="col-lg-12 ">
8989 < div class ="header-content ">
90- < h1 class ="header-title text-uppercase "> Program</ h1 >
90+ < h1 class ="header-title text-uppercase "> Program 2016 </ h1 >
9191 < div class ="header-underline "> </ div >
9292 </ div >
9393 </ div >
@@ -102,7 +102,7 @@ <h1 class="header-title text-uppercase">Program</h1>
102102 <!-- Content -->
103103 < div class ="container content ">
104104 < div class ="section " id ="id1 ">
105- < h2 > Program</ h2 >
105+ < h2 > Program 2016 </ h2 >
106106< p > It's been a difficult task to create a program, considering we received 40
107107proposals and time only allows for a maximum of 9 slots. Many promising
108108proposals had to be left out to our regret, but we are certain that we managed
@@ -333,28 +333,6 @@ <h2>Aperitif</h2>
333333< p > Right after the conference we'll have a small aperitif at HSR's cafeteria,
334334sponsored by < a class ="reference external " href ="http://beekeeper.ch/ "> Beekeeper</ a > . There will be soft drinks,
335335water, beer and sandwiches free of charge for all conference attendees.</ p >
336- </ div >
337- < div class ="section " id ="key-signing-event ">
338- < h2 > Key Signing Event</ h2 >
339- < p > During the aperitif we'll also have a key signing party for anyone wanting to
340- expand the web of trust with additional signatures. This is how it will be
341- conducted:</ p >
342- < p > To participate print out your fingerprint before the conference using
343- < a class ="reference external " href ="http://keysheet.net "> http://keysheet.net</ a > for instance and be sure to have a suitable form of
344- identification with you (typically a national ID card, passport or a
345- drivers-license).</ p >
346- < p > During the aperitif we will put up a poster, where anyone interested in
347- getting more signatures can gather around. Typically you will get the
348- fingerprint printout from the other person and give them yours. You then you
349- check the other person's id and then make a note on the fingerprint slip
350- that you have verified it. At the end of the event you should have a collection
351- of these to process at home.</ p >
352- < p > After the event you download the keys of a keyserver, verify the fingerprints
353- you have collected and sign each of the keys. Now you can upload the signature,
354- or if the other party requested it, return it to them via encrypted mail
355- (see < a class ="reference external " href ="https://wiki.debian.org/caff "> https://wiki.debian.org/caff</ a > for automating this).</ p >
356- < p > For more info see < a class ="reference external " href ="https://wiki.debian.org/Keysigning "> https://wiki.debian.org/Keysigning</ a > and the documents
357- linked off that page.</ p >
358336</ div >
359337
360338 </ div >
0 commit comments