<p dir="ltr">rejo</p>
<p dir="ltr">have you seen <a href="http://hackerspaces.org/wiki/Hacker_Event_Design_Patterns">http://hackerspaces.org/wiki/Hacker_Event_Design_Patterns</a> yet? </p>
<p dir="ltr">I moved some of our previous discussion points up there. (I've had zero feedback so far) </p>
<p dir="ltr">and that's a lot of feedback. I may comment on it later. some of those are definitely solvable via patterns. </p>
<p dir="ltr">I'm sure car park piet would like to add a pattern for transportation to/from site... </p>
<div class="gmail_quote">On 2 Apr 2014 22:05, "Rejo Zenger" <<a href="mailto:rejo@zenger.nl">rejo@zenger.nl</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi!<br>
<br>
So, I thought of attempting to turn the feedback of OHM into lessons<br>
learned. More difficult than expected, as, for a lot things, I don't<br>
recall the situation at for example the CCC Camp two years ago.<br>
<br>
Some things are very clear:<br>
<br>
- during buildup and teardown<br>
- power should be available during buildup as soon as possible and<br>
during teardown as possible<br>
- toilets (and possibly showers?) should be available during buildup<br>
as soon as possible during teardown as possible<br>
- water should be available during buidup as soon as possible during<br>
teardown as possible<br>
- portacabin should be available during buidup as soon as possible<br>
during teardown as possible<br>
<br>
- volunteer<br>
- volunteer desk should be (in) the center of the camp<br>
- internet should be available during buildup in the vicinity of NOC<br>
only and to NOC-staff only elsewhere<br>
- event may end on friday, so there are two more days for volunteers<br>
without volunteers taking additional days off (initial loss of<br>
participants shouldn't be a problem, there are more than enough<br>
visitors)<br>
- teams should be mixed of NL and DE volunteers, site takes<br>
precedence<br>
<br>
- sanitary requirements<br>
- sinks to do the dishes should be available (there were some, for<br>
sure, but possibly not enough?)<br>
<br>
- financial<br>
- expences made during the event should be registered in a system<br>
right away (preferably, there is a system that allows the volunteer<br>
to enter the details in the system themselves and have the<br>
volunteer attach a scan of the invoice immediatelly)<br>
<br>
More general, this should also get some attention:<br>
<br>
- Internal communication (as in, between the teams, etc) and<br>
organisation.<br>
<br>
- Policy on sponsor deals. Suggestions for the criteria for accepting<br>
deals, no-go's, how to setup a deal (e.g. do you need to put<br>
something on paper), etc.<br>
<br>
At Bits of Freedom we have a policy that may be useful. We do accept<br>
sponsoring in natura if it's something we really need (e.g. hardware<br>
for a server, etc). Nothing is done in return, allthough the donation<br>
may be mentioned in the yearly report. Of course, we accept monetary<br>
donations from companies, but only if i) the donation is small enough<br>
(it shouldn't be a considerable amount of the budget), ii) it's not<br>
from companies that may lead to a lot of discussions (we have turned<br>
down offerings of companies like Fox-IT and Google in the past) and<br>
iii) the donations may not be earmarked. For all monetary donations<br>
we require an agreement to be signed in advance, making sure we<br>
maintain our independency. Donations from companies are mentioned in<br>
the yearly report (only if large enough with logo). Supporting<br>
companies are mentioned on our website, but not prominently.<br>
<br>
We may also have a look at the CCC for this?<br>
<br>
- Characteristics and quality of the field. For example, it should be<br>
compact, but not dense, it should have attractive and distinct<br>
landmarks like trees, hangars, etc. Think of additional spaces<br>
needed, like parking lots and possibly other designated areas.<br>
<br>
- Food. Mostly guidelines only, although availability of vegetarian<br>
food can be a requirement (including diversity) and something on the<br>
food for volunteers.<br>
<br>
- Policy on cars of visitors: cars on terrain, location of parking lot.<br>
<br>
- Transportation between storage at hackerspaces and field should be<br>
better, I can't tell what is needed.<br>
<br>
- Communication of programm changes. Not sure how to solve this. Low<br>
tech would be some kind of announcement boards on a number of fixed<br>
locations (near the entrance of each tent, at the infodesk, at the<br>
food court, etc). This is something the IFFR has solved this. More<br>
high tech solutions are possible as well.<br>
<br>
- Four messages of feedback were mentioning the OHM-coins. Ditch them.<br>
Don't know about the alternative - apart from regular money.<br>
<br>
<br>
--<br>
Rejo Zenger<br>
E <a href="mailto:rejo@zenger.nl">rejo@zenger.nl</a> P <a href="tel:%2B31%280%29639642738" value="+31639642738">+31(0)639642738</a> W <a href="https://rejo.zenger.nl" target="_blank">https://rejo.zenger.nl</a> T @rejozenger<br>
PGP 1FBF 7B37 6537 68B1 2532 A4CB 0994 0946 21DB EFD4<br>
<br>_______________________________________________<br>
Hacker-event-theory mailing list<br>
<a href="mailto:Hacker-event-theory@lists.hackerspaces.org">Hacker-event-theory@lists.hackerspaces.org</a><br>
<a href="http://lists.hackerspaces.org/mailman/listinfo/hacker-event-theory" target="_blank">http://lists.hackerspaces.org/mailman/listinfo/hacker-event-theory</a><br>
<br></blockquote></div>