[Hacker-event-theory] turning feedback from ohm into learning points

[Amran]

>
> Power:
> - - Costly to run generators, every day costs thousands of euros in fuel.
>

how much would a fully paid crew cost to hire with the same ability of your
volunteers? in general, running a low power generator from the get go just
for the crew area would be a boon.

Rolling out power to the whole site is, of course, silly until the event
starts.

Toilets:
> - - For toilets and showers, you need water, power and sewage first.
>

for emf we hired powered heated showers, with a grey-water tank runoff.
they looked like over sized dixies. worked a treat. having one or two,
again, just for the crew area would be amazing.


>
>
> > - event may end on friday, so there are two more days for
> > volunteers without volunteers taking additional days off (initial
> > loss of participants shouldn't be a problem, there are more than
> > enough visitors) - teams should be mixed of NL and DE volunteers,
> > site takes precedence
>
> > - sanitary requirements - sinks to do the dishes should be
> > available (there were some, for sure, but possibly not enough?)
>

you can hire stand pipe affairs with troughs. you just need the water, and
crucially, the grey water disposal. in the uk you can get away with a
'soakway' sometimes. essentially a big hole in the ground you drain water
into. in the NL thats prob not an option

> More general, this should also get some attention:
>
> - Internal communication (as in, between the teams, etc) and
> organisation.

this is as much about having good managers/team leads as it is tools for
comms. ohm had the tools, but perhaps not the right people (and/or not in
the right places).

> We may also have a look at the CCC for this?
>
> There were actually quite some guidelines and policies. The sponsor
> document was quite clear. I believe the best way to go from here is to
> avoid sponsor money as a whole, and accept only sponsoring in natura
> like we do with the up-link and network equipment. Technically you
> have to value those services as well, and pay taxes over them.
>

i like the ccc model for payment


>
> > - Characteristics and quality of the field. For example, it should
> > be compact, but not dense, it should have attractive and distinct
> > landmarks like trees, hangars, etc. Think of additional spaces
> > needed, like parking lots and possibly other designated areas.
>
> The deal (or claim) for the right site should be made more than one
> year before the event, to prevent the best sites being gone already.
> Which means the selection of the site should be started around 1.5
> year before the event.
> We ended up on Geestmerambacht because all other good options failed
> one by one. The Netherlands as only a few areas that are suitable for
> our kind of events, adding additional requirements like sanitation and
> nice scenery brings that number down to a handful.
>
> If we bring the maximum number of people back to say 2500, a lot more
> is possible.
>
> Something to be considered: Pick a good site and stick to it. That way
> you can use the same buildup plans and improve on it, heck, you can
> reuse basically all plans and permit requests. That is how CCC does it.
> Breaks a tradition though. :)
>

im with rop - do it outside of NL. the paper-pushing is just ridiculous here


>
> > - Food. Mostly guidelines only, although availability of vegetarian
> >  food can be a requirement (including diversity) and something on
> > the food for volunteers.
>
> Food for volunteers should be available at large quantities in good
> quality. Budget is not really the issue. The only problem to solve is
> how to make sure only those people who work for it make use of it.
>

thats a wishy washy statement. ohm would get a tick under that statement?
yet it was the single most complained about item.

the team lead ticket system at meal time worked great!

>
>
>
> > - Communication of programm changes. Not sure how to solve this.
> > Low tech would be some kind of announcement boards on a number of
> > fixed locations (near the entrance of each tent, at the infodesk,
> > at the food court, etc). This is something the IFFR has solved
> > this. More high tech solutions are possible as well.
>
> The idea was to have announcement boards displaying a simple website,
> with the program and important announcements. The problem was, nobody
> was available to arrange the required software. All software projects
> should have a deadline at least 3 months before the event. :)
>

i spent time doing this, and leaned on the emf crew to produce an
infoscreen system. it was ready by day 2. its eventual rollout was stopped
by both NOC and info desk refusing to supply enough cat5 and help with
network config.

i think a site like geestmeerambacht wouldve benefited massively from a
jumbotron. cheap to rent, highly visible.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hackerspaces.org/pipermail/hacker-event-theory/attachments/20140404/2e4aeef6/attachment.html>