WHY2025 wiki - User contributions [en]

Newcomers Guide

2025-08-19T14:51:47Z

Bas: /* Your badge */

<div style="border: 1ex solid #491d88; background: #85c1e9; color: #331a38; padding: 1em; width: 60%; font-size: 120%; margin: 1em">
This page is being actively worked on, and far from complete right now, so if there's some information you think should be here, feel free to add it if you know where to find it, or if not, check back soon.
If you find anything that is not being addressed, you have the following options:
* Jump onto IRC to ask the question in the #why2025 channel
* Join a Online Infodesk session (every day during lunch, https://meet.why2025.org/onlineinfodesk
* In case neither works, use the fallback route to team:info, by sending a mail to: info@why2025.org

</div>

This page is aimed at those who are new to this camp (attending for the first time this year), or to hacker camps in general. If that's you, welcome and here you will find answers you yearn for. Below, you will find information (ranging from "nice to know" to "essential to your experience at WHY2025") about some of the most significant areas of interest of the camp.

The page is quite long. However, all the information is organised into topic sections, arranged loosely in order of importance. You are encouraged to use the Table of Contents below to help you navigate to the sections you need. Each section contains a brief description and some essential information about a topic, as well as a "Further reading" section where you can find links to more in-depth information.

== What even is a hacker camp? ==

A hackercamp is a unique blend of technology conference, outdoor festival, and community gathering that creates a temporary village of tech enthusiasts, creators, and innovators. Unlike traditional tech events, hackercamps take place outdoors, with participants camping in tents across an open field transformed into a vibrant tech ecosystem.

=== The essence of a hacker camp ===

At its core, a hackercamp is a self-organized space where hackers, makers, artists, activists, and technology enthusiasts come together to learn, create, and celebrate technology. The landscape comes alive with colorful LED installations, interactive art, hand-built sculptures, and high-tech experiments happening in every corner.

Key elements that define the hackercamp experience include:

* '''Talks & workshops''', covering topics from cybersecurity and privacy to hardware hacking and creative coding
* '''Villages''', which are self-organized micro-communities that form the social backbone of the camp
* '''Creative exhibitions''', from fire-breathing sculptures and interactive LED installations, to projection mappings, and everything in between
* '''Nighttime spectacles''', like laser shows, light displays, and fire performances
* '''Capture the Flag (CTF)''': Competitive hacking challenges and scavenger hunts
* '''Party areas''' with community-organized music and performances
* '''Family areas''' - spaces where children and parents can explore technology together

=== Who are they for? ===

Hackercamps welcome a diverse community of participants:

* Tech Professionals: Developers, security researchers, and IT specialists
* Makers & Tinkerers: Hardware hackers and DIY enthusiasts
* Artists: Digital creators, light artists, and interactive designers
* Activists: Privacy advocates and digital rights supporters
* Curious Beginners: Anyone interested in learning about technology
* Families: Parents and children exploring tech together

The beauty of hackercamps is that they're designed for both experts and newcomers. You don't need to be a professional hacker or programmer to participate—just bring curiosity and a willingness to engage with technology and the community.

=== Why people attend hacker camps ===

People are drawn to hacker camps for many reasons:

* To connect with like-minded individuals and build community
* To share knowledge and learn through hands-on experiences
* To collaborate on projects with real-world impact
* To experience the unique atmosphere of creativity and innovation
* To discover new passions and potential career paths

At a hacker camp, you don't just observe technology — you actively engage with it alongside others who share your enthusiasm. For many participants, these events become transformative experiences that lead to lasting friendships, collaborations, and new directions in their technological journey.

=== Further reading ===
* [https://why2025.org/post/111 Blog: What does a hackercamp look like?]

== Attending WHY2025 ==

=== Getting a ticket ===
Sorry, but the event has been SOLD OUT as of 10th of july 2025. You can still try to get tickets at the [[TicketSwap]]. <s>It goes without saying, but WHY2025 isn't cheap to setup and run, so if you want to attend, you will need to buy a ticket. You can get one at the [https://tickets.why2025.org/ online ticket shop].</s>

You can also purchase parking for your car <s>or campervan</s>, as well as tents and sweet WHY2025 merch.
There are also options for those who aren't well-off enough to afford a full-price ticket, but these friends tickets are manually validated.

=== What to bring, and what not to bring ===
See the [[What to bring]] page for more detailed information on what exactly you should bring, but generally, here's what you should consider bringing to WHY2025. You may not have, need, or want every item on the list, but they are all worth considering.
* '''Camping equipment''' (tent + mounting, sleeping bag, blanket to sit on etc.)
* '''Your electronics''' (make sure to protect any sensitive data, it's a hacker event after all!) and '''power''' for them (powerbanks, power cords etc.)
* '''A paper copy of your ticket''' (you may not ''need'' it, but it's good to have just in case)
* '''Tools and equipment''' (eating utensils, trash bags, lanterns/flashlights, etc. - just things that are nice to have, check [[What to bring]] for a detailed list)
* '''Hygiene stuff''' (toothbrush + toothpaste, shampoo/shower gel, towel, razor, lotion, deodorant, etc.)
* '''Health/safety stuff''' (sunblock, earplugs, insect repellent, any medication you might need, etc.)
* '''Clothes for both sunny and rainy weather''' (you don't want to be stuck in your tent if it rains!)
* '''A USB-C cable''' for your badge (you'll probably have one if you're bringing your electronics, but it's mentioned here just in case!)
* '''A long power cords''' to connect to your neighbors or the power distribution box, for your power needs.

There are also a few things that are better off being left at home:
* '''Pets (except service animals)''' (as much as we love animals, the camp isn't a pet-friendly space)
* '''Microwave ovens''' (they can disrupt wireless networks)
* '''Exceptionally power-hungry devices''' (the power grid is an issue, so be considerate)
* '''BBQs that run on solid fuel''' (for safety reasons; see [[Team:Safety-Fire]] for more information)

=== Getting to the event site ===
WHY2025 will take place in Geestmerambacht, about 42km north of Amsterdam in the Netherlands. You can get there by car, public transport, or bike. '''Travel by boat is not an option for this event.''' For more information on the specific routes and directions to use, see [[Location]].

=== Getting into and around WHY2025 ===
Once you've reached the WHY2025 site, you will find the [http://map.why2025.org WHY2025 Map] quite useful, as it will help you orient yourself and find out where everything is - from the entrance (which you can also find using signage in the area), to the countless villages and tents with cool stuff all around the event.
You should be able to get a lot of what you need from right within the premises (there is even a supermarket!), but you are free to leave and come back at any time during the camp.

=== Your badge ===
A few attendees of WHY2025 will receive an awesome electronic badge with lots of awesome capabilities and fun stuff to do with it. Originally, badges like this were meant for displaying your name, and while they can be used for that, they grew to become so much more - the badge from the previous camp, MCH2022, had an FPGA, a color screen, and a myriad of sensors on it, among other things. Badges are always a big part of events like this, and it's always really exciting to tinker with them and see what they can do. Specific information about the badge is, as of right now, not available, but [[Team:Badge|Team:Badge's wiki page]] will be the first place to find out about it.

Read more about the WHY2025 Badge in [https://why2025.org/post/494 this article on the website].

=== Further reading ===
* [[Tickets]] - detailed information + FAQ about tickets and buying them
* [[Location]] - details about the different ways to reach the event site
* [[Camping]] - things worth knowing if you plan on camping
* [[What to bring]] - a comprehensive list of things that you should bring, things that you shouldn't bring, and other general considerations
* [[Facilities]] - the facilities and amenities we already provide for you
* [[Team:Safety-Fire]] has a list of regulations on the kinds of gas tanks, cooking equipment, tents etc. you are allowed to have
* [[Team:Badge]] will be updated with new information (specifications etc.) about the badge as it becomes available

== Staying informed ==

=== The WHY2025 Wiki ===
The Wiki (where you are right now) is an extremely valuable resource for staying informed before and during WHY2025. It contains a lot of information about virtually every aspect of the camp, and pages get updated very frequently with additional information.

For help navigating the Wiki, refer to the sidebar on the left of the page which has links to nearly every major page on the Wiki. A lot of them also contain links to other pages, so if you're having trouble finding a specific page, it may be worth checking the sidebar to see if you can find a page that might link to what you're looking for.

If that doesn't prove helpful, there is also a search bar on the top right, where you can search for pages or content by keywords.

=== The Infodesk ===
During the camp, the information desk (or the Infodesk) is the first place to go if you have some sort of issue or question. The Infodesk crew is willing to help out with many different things if you ask nicely.

=== Further reading ===
* [[Welcome#Communication and staying up to date|Staying up to date]] - a list of sources where you can get in touch and stay up to date with WHY2025
* [[Facilities#Infodesk|Infodesk]] - some slightly more in-depth information about what kinds of requests the Infodesk can help with
* [[Special:SpecialPages|Special pages]] - useful links for advanced Wiki navigation

== Keeping yourself, others, and your belongings safe ==

=== General safety guidelines ===

* '''Be respectful and inclusive''' towards all individuals, embracing diversity and ensuring a friendly and welcoming environment. Harassment, discrimination, or aggressive behaviour is not welcome.
* '''Respect personal boundaries''', and if someone tells you you are crossing them, step back.
* '''Ask for clear consent''' before any physical contact, be mindful of personal space, and ensure your attention is welcome.
* '''Practice environmental respect''' by cleaning up after yourself, using provided bins, and taking care of the surroundings.
* '''Be mindful''' of designated quiet zones, accessibility needs, and safe spaces.
* '''Strive for balanced communication''', allowing all voices to be heard and listening actively.
* When taking photos or recordings, '''always ask for clear consent''', and do not touch anyone’s tech or setup without permission. Be mindful of others' privacy before taking recognisable pictures of strangers.
* '''Keep noise levels down''' between 23:00 and 9:00. Camping around the FamilyZone must be quiet from 21:00.
* Open fires (bonfires, barbecues using charcoal or wood) are not allowed due to safety reasons. Gas-powered stoves and barbecue grills are permitted with a fire extinguisher nearby.
* '''Follow electricity safety guidelines''', using outdoor extension cords (IP44), grounded cables/plugs, and keeping indoor equipment dry. Avoid overloading the power supply and do not leave powered equipment unattended. Be aware of morning dew and take precautions for electronic equipment.
* '''Keep emergency routes clear''' and ensure tents do not block entrances/exits of neighbours.
* Use tent pegs that can withstand high wind speeds and use enough guy ropes to secure your tent.
* Drugs (of any kind and any amount) are not allowed.
* As much as possible, take home everything you bring to WHY2025, including larger items.
* Smoking is not allowed in public tents.
* Powder fire extinguishers are strictly prohibited.

=== Taking care of your valuables ===

=== What to do in an emergency ===

* In case of an emergency, contact [[Team:Safety]]. This team will arrive faster than the emergency services.

* '''Contact [[Team:Safety]] via:'''
** Emergency Number: '''+3185234 1111''' (Tip: add this to your phone contacts now)
** DECT phone: '''1111'''
** Handheld radio: ''Talk to anyone with one''
** State the nature of the emergency and the exact location. You can find this location next to each fire extinguisher or on the map.
** The emergency response station can also be visited, it is located next to the Infodesk.

* As a last resort, call directly to '''112''' on your mobile phone. This will connect you directly to local emergency number, NOT team:Safety on the field!

* You can find [[Team:Safety-First-AID]] (EHBO), [[Team:Safety-Fire]], and [[Team:Safety-Security]] at the safety village (see map)

* If anything makes you or someone else uncomfortable and asking them to stop does not work, reach out to a [[Team:Cohesion|cohesion volunteer]] or the designated safety crew.
You can find the contact information for the Cohesion team in the [https://wiki.why2025.org/Code_of_Conduct#Conflict_Resolution Code of Conduct].

=== Further reading ===

== What you can do at WHY2025 ==

=== Non-nerdy stuff ===
* '''Eat delicious food and have a drink or two''' - WHY2025 has a revamped food court and three bars, and there will always be at least one place (but usually several) open where you can get something to eat or drink. Never forge
* '''Meet new people''' - <There are a number of ways in which you can do it - attending workshops, checking out villages, or even just starting conversations with folks around the camp - but there are plenty of opportunities to meet people, have interesting conversations, and make friends.
* '''Sleep''' - Admittedly, it's not exactly the most riveting or exciting thing you can do, but you do need to get some sleep! In fact, that's why there are quiet hours between 01:00 and 07:00 - so you can get some rest after a full day of having fun.
* '''Volunteer''' - Take a look at the [[Angel_Guide|Angel guide]] to see if you can get a volunteering shift. There are shifts of many different kinds - from helping out at the bar, to helping set up cameras and equipment for talks, and everything in between.
* '''Party!''' - WHY2025 has its own party area with great music, cool lighting, and an overall awesome atmosphere! It's a great place to be if you ever just want to groove.

=== Slightly nerdy stuff ===

* '''Attend some talks''' - Talks will be given on a variety of different topics, some more nerdy than others - from climate change to obscure hacking, and everything in between. They are incredibly interesting and fun to listen in on! But if you somehow find one boring, don't worry - you are free to leave a talk at any time. For more info, see [[Newcomers Guide#Talks|Talks]].
* '''Participate in the Secret Token challenge''' - There will be secret tokens hidden all around WHY2025. Secret Tokens are little pieces of text hidden in various places. They look something like this:

<pre>
secret{NewcomerToken}
</pre>

It's a lot of fun to look around for tokens, and some of them are hidden in really interesting places!

=== Very nerdy stuff ===

* '''Join or start a village''' - Villages are groups of people which get together around a shared interest. A lot of them do geeky stuff like hacking, hosting workshops, or setting up cool displays. See [[Newcomers Guide#Villages]] for more information on villages!
* '''Attend a workshop''' - There will be lots of different workshops to attend at WHY2025 about many different topics, in varying levels of geekiness. Previous workshops include a surface-mount soldering guide for beginners, Ubuntu Touch app development, radio broadcasting via commercial satellite, data-mining WhatsApp groups and more.
* '''Tinker with your badge''' - WHY2025 attendees receive an electronic badge that has a lot of cool stuff to play around with! Previous event badges included a variety of different sensors, and the badge from the previous camp had an FPGA on it.
* '''Participate in the CTF''' - CTF stands for '''Capture The Flag'''. Think of it as a 'game' where people compete to be the first to solve hacking puzzles. They range in difficulty from fairly easy to super complex and difficult, and there's something for everyone, no matter your cybersecurity experience.

=== Further reading ===
* [https://why2025.org/programme WHY2025 Programme] - see the programme with all the talks and workshops happening at WHY2025
* [http://map.why2025.org WHY2025 Map] - see all the tents, and see where all the cool stuff is happening, so you can be part of it all
* [[Villages]] - see the list of villages, and find one you might like to get involved in
* [https://ctf.why2025.org/ CTF / Capture The Flag website] - The website for the CTF
* [https://tokens.why2025.org/ Secret Token Game website] - The website for the Secret Token Game

== Volunteering ==

=== The Orga Crew ===
The orga crew refers to everyone who is helping out with organizing WHY2025 before (and during) WHY2025. As a whole, it consists of hundreds of different people, but they are split into small teams, each one tackling a specific aspect of the event (such as decoration, badges, or safety). You can see a list of all the teams on the [[Teams]] page.
Getting involved is easy - check the [[Vacancies]] page to see a list of teams who need additional members, and get in touch with one of them to see how you can help! You may also try to contact teams that are not on the vacancies page, and they might have a spot for you!

=== The Angel System ===
A lot of work during buildup, camp and teardown is done by volunteers. Every visitor that contributes their time to WHY2025 by working one or more shifts is called an angel. During the camp we need hundreds of angels to work thousands of shifts. Angels build up the camp, check tickets, help park cars, pour drinks, organise talks, make video streams and keep us all safe and healthy.
You can read all about it in the [[Angel Guide]], you can learn about Heaven, the Engelsystem and all the perks being an angel can bring.

=== Further reading ===
* [[Volunteering Guide]] - Detailed information on how the WHY2025 organization works and how you can be a part of it
* [[Teams]] - See the list of teams and their contact information, in order to find one you might wanna join

== Camping ==

=== Where to camp at WHY2025 ===
You can camp as part of a village if you're part of one (see [[Newcomers Guide#Villages|Villages]] for more information on villages), or if not, you can place your tent in any of the areas with a white border on [https://map.why2025.org the map]. If you're with a campervan (and have your camping ticket as well) you'll be pre-assigned a spot in one of the areas with a green border.

=== What you need to know if you plan on camping ===
* '''You need a Camper ticket if you want to bring a camper van or similar.''' These are almost always sold out, and the waiting list already has many people on it, so the likelihood of getting one is unlikely.
* '''If you plan on bringing a large tent (larger than 25m2), there are special requirements for these.''' See [[Team:Safety-Fire#Large_Tents]] for the specific rules and regulations involved.
* '''For powering your stuff''', SCHUKO (type F) plugs are available in distribution cabinets all throughout fields. Remember to follow safety rules, be considerate, and keep things dry. See [[Camping#Power on the fields|Power on the fields]] for more information.
* '''Follow the safety rules and regulations.''' These are described and linked above - see [[Newcomers Guide#Keeping yourself, others, and your belongings safe|Keeping yourself, others, and your belongings safe]] for more information.

=== The 6-3-1 rule ===
With so much fun stuff to do, it can be easy to forget to take care of yourself during WHY2025. We have a rule-of-thumb for you to remember during the camp, called the '''6-3-1 rule''', which states that you should do all of these every day:
* Get (at least) '''6''' hours of sleep
* Eat '''3''' meals
* Take (at least) '''1''' shower
Following this rule every day ensures that you're taking care of yourself to an extent - and that means you're making the most of your time too!

=== Further reading ===
* [http://map.why2025.org WHY2025 Map] - to get an idea of how the campsite looks like
* [[FAQ#Camping, buildup & teardown and villages|Camping, buildup & teardown and villages]] - answers to any additional questions you may have (like for special cases) about camping
* [[Camping]] - more details on specific considerations for camping at WHY2025
* [[What to bring]] - detailed information on what you need to bring. Especially useful for camping
* [[Facilities]] - information on what WHY2025 already provides
* [[Team:Safety-Fire]] - the safety regulations you need to follow

== Talks ==

=== What are the talks about? ===
WHY2025 talks can be about pretty much anything - software, hardware, art, climate change, privacy, ethics, you name it.
In previous events, there were hundreds of talks spanning all of these (and more!) subjects, and a great way to get a feel for how diverse the talks are is to check out the talks from past years' events.
* [https://media.ccc.de/c/MCH2022 MCH2022], the previous event, had talks about hacking barcode scanners, climate change, breaking DOOM by changing the value of pi, AI face scanners, and attribution, among many others. Take a look at the full list!
* [https://media.ccc.de/c/SHA2017 SHA2017], the event before MCH2022, had talks about tracking down scam call centers, hacking human DNA, creating escape rooms, biometric ID, and even a talk from an actual NSA whistleblower.
Ultimately, if you have something cool you want to share, it's probably worth giving a talk about!

=== How to attend talks ===
WHY2025 has multiple streams of talks, often that means there is more than one talk going on at the same time. All talks will be live streamed, so if you really wanted to, you could watch them all at once. They'll also be recorded for later viewing, so if you miss a cool talk, no worries!

=== How to submit your own talk ===
Unfortunately, the deadline for submitting a talk has passed :(
If you've already submitted a talk (or just want to read the guidelines), they're at the [http://cfp.why2025.org/ Call for Participation] page.

=== Further reading ===
* [https://why2025.org/post/96 WHY2025 Blog - Should I submit a talk to speak at WHY2025?] - a blog post addressing some objections you might have to giving a talk
* [https://cfp.why2025.org/why2025/cfp WHY2025 Call for Participation] - the page to visit if you want to submit your talk. Contains information about different talk formats, as well as more details on what talks are not allowed.
* [[How can I get reminders for events in the programme?]] - How to mark talks/workshops/entertainment as favourites and get reminders when they're about to start.

== Villages ==

=== What actually is a village? ===
A village is an area of the camp where people with a specific shared interest or goal get together and conduct various different workshops and activities. Essentially, villages are groups of people that want to organize themselves, camp together, collaborate, and sometimes even show off cool stuff like fancy lights or workshop areas.

=== How to get involved in a village (or start your own!) ===
The process of joining a village depends on which village you want to join. Have a look at the [[Villages]] page to see a list of all of them! Once you find one you like, read their page on this wiki - they might have information there on how to join. Otherwise, you could also reach out (many villages have a contact email) and ask how to join. There is a village [[Village:Improvisators|especially aimed at newcomers]] if you're not feeling sure about what type of village you want to get involved in.

As for starting your own village, it ultimately boils down to:
* '''Planning''' - How many people do you want? What will your village be about? What will you do? It's important to get an idea of all of these things first and foremost.
* '''Registering''' - Once you've planned out your village, it's time to register it and give it a home on the Wiki. Fill in the [[Form:Village|village registration form]] to create your village!
* '''Reaching out''' - If you've done the above two steps, you have officially made a village. Congratulations! Now, if you want to do something particularly special or awesome, it's worth reaching out to [[Team:Villages]] and letting them know!

=== Further reading ===
* [[Villages-FAQ]] - more in-depth information about what villages are and how to start one
* [[Villages]] - see a list of all the currently registered villages, and maybe find one you like!

Team:Bar/Mugs

2025-08-18T11:15:36Z

Bas: /* I want one too... */

= Mugs =
There have been reports about the [[Team:Bar/Mugs|Special WHY Mugs]] not reaching expected quality. We are working on the issue and will update you on this page. We thank you all for your patience.

== Issues ==

The print seems not able to resist a dishwasher, and some reports even say a hand wash damaged the print.

Please note that we ordered the mugs to be able to withstand dishwashing.

Another issues, albeit minor, is that we seem to have ordered not enough mugs. Please put your name on the list below if you'd like a mug as well, providing the quality is acceptable this time.

== Solution ==

We are reaching out to our supplier to get to the bottom of this. At this moment we don't have any updates.

== Affected customers ==

We believe that the failure of the print is not an isolated incident, so we'd like a list of customers that have bought this mug. Please add your name (or handle, or other way to contact you) to this list.

* denz, @denz@mastodon.nl, not failed yet
* Johan, @aequitas@mastodon.nl, failed after hand wash, see https://mastodon.nl/@aequitas/115033694380655129
* Marcel Waldvogel, @marcel@waldvogel.family, failed after dishwashing, see https://waldvogel.family/@marcel/115026868577943506
* Christopher Kreitz, @Romses@chaos.social, not failed yet, not yet used/washed
* foosel, @foosel@chaos.social, not failed yet, not yet used but hand washed
* Eisfunke, @eisfunke@inductive.space, not failed yet, used once, hand washed twice
* WoLFjuh, joffrey dash why2025mug at ne2000 dot nl, not failed, not yet washed
* [[User:Dynom]], @dynom@toot.community, not failed, not yet washed on the outside (only hand washed the inside)
* [[User:Thijs]] @thijs@hsnl.social, not failed yet but haven't cleaned the outside yet due to durability concerns
* [[User:Ceres-c]] abstained from washing in dishwasher due to durability concerns
* Snuffel, wendy at snuffel dot net, not washed or used yet.
* Bommlon, why2025mug at bommlon dot com, not yet washed or used
* [[User:Ad]], @CrazyA@mastodon.social, A 15min soak at 60°C (hot tap water) reveals peeling [[File:Mug-ad-after-15-min-soak.jpg|40px]]
* Spacehuhn, @Spacehuhn@chaos.social not failed yet, not yet used/washed
* Rickgeex, m.vangeelen@anovum.nl, washed, affected [[File:Cups_affected_WHY2025_rickgeex_%26_chocolight.jpg|32px]]
* Chocolight, maaike@kujenga.nl, washed, affected [[File:Cups_affected_WHY2025_rickgeex_%26_chocolight.jpg|32px]]
* [[User:Wombat]], @wombat@mendeddrum.org, not failed yet
* [[User:Ricardo]], @ricardo@xirion.net, used, handwashed, not failed yet
* EsteVarda, @GlitterHacker@mastodon.social, used twice, handwashed twice, not failed yet. Did not put in dishwasher because I was warned not to do so during the purchase
* [[User:myzt]], @myzt@mastodon.social, input: 2 why2025 mugs, 2 runs of dishwasher, output: 2 black mugs+microplastics
* [[User:Gapspark]], not failed yet, not yet used/washed. Worried as I put my other emal mugs in the dishwasher without problems.
* [[User:Nomaster]], dishwasher, affected
* [[User:Rad4day]], @rad4day@chaos.social, not failed yet, not used but hand washed
* [[user:bee]], 2 mugs, not used nor damaged yet (slacking paying off once again)
* [[User:Milk]] @catstevenssec@infosec.exchange , not affected but not tried washing yet,
* Mndy: not used yet, not dishwasher-washed yet.
* [[User:Obsidian]] @obsidian@milliways.social, not failed yet, only hand washed twice.
* [[User:Mlijn]] Not used and not washed yet.
* [[User:Mack]], Not used so not failed yet, only rinsed the inside)
* [[User:CH23]], 2 mugs, worried about washing them. Would normally dishwash them.
* [[User:pozorjed]], mug new in box
* [[User:IJskimo]], Some peeling after dishwasing
* [[User:david]], @cosmicsmash@mastadon.social, failed parts peeling, hand-washed (luke warm, soft sponge).
* [[User:Dany]], one regular hand-wash (hot water, dish-washing liquid, brush), not affected yet.
* ... You?

== I want one too... ==

If you still like our mugs, then put your contact info and number of mugs here. If there's enough of demand, and if the new mugs pass our quality control (which will be much more rigorous), we'll order them and contact you regarding payment and delivery. Details will follow.

* kristen+mugsarecool at ikriz dot nl [x1]
* [[user:ReDNaX]] linze_edelsteen.7i [at} icloud (dot] com [1x]
* Iwantadishwasheresetantwhy2025mugaswell@e-bu [dot] de
* achtele at web dot der 1x mug please
* [[user:Mack]] mlombaers at freedom dot nl 2x mug please
* [[user:JuliJane]] why2025mug@my[dot]fqdn[dot]org, would be lovely
* [[user:bengoshi]] would like one mug, too :)
* Bas (team waste), would like a proper one...

== Final thoughts ==

We can't tell you yet what the solution will be, but be sure we'll be working on it.

Feedback

2025-08-18T09:40:26Z

Bas: /* Waste / garbage collection */

'''What Hackers Yearn''' for is to '''Improve'''. This page is dedicated to collecting user feedback related to the execution of WHY2025 as a whole. Constructive feedback is invaluable to the continuous improvement of the project and is welcomed from all participants. Please share your observations and suggestions in a '''clear and respectful manner'''. Your input will help guide enhancements for future generations of the event.

It is also possible to send feedback to [http://mailto:2029@why2025.org 2029@why2025.org]

== IMPORTANT ==

Do '''NOT''' review '''people'''. Any individual interaction you had with a human does not belong here, but should be taken up with [[Team:Cohesion]].

This page is strictly for addressing improvements for the next event. We encourage contributors to maintain a neutral, factual, and calm tone in their feedback.

* GOOD EXAMPLES: "Excessive mud at showers", "Food vendors often refused to accept WHY-voucher", or "Limited drop-off points for luggage shuttle".

* BAD EXAMPLES: "Person XXX was insulting me", "Helpdesk XOC was too busy to help", "frickin hot", "So the story begins on Saturday night at 23:04 when..."

== Feedback List ==

=== General / overall ===

* There should be a clear single method/channel of communication from orga, using the Heaven signal chat or social media for this is not ideal
** +1
* "Communication" in general seems to be the theme of this camp. It was extremely difficult to find reliable information about anything as a visitor/angel, and often you only had the grapevine to go off, and you just had to hope that the necessary information somehow reached you at some point. From what I've heard it wasn't much better between teams either. Documenting things is really important and saves everyone a lot of work having to repeat and figure out the same things over and over again!

=== Arrival / departure / parking / train shuttle / luggage shuttle ===

* On day 0 we queued to drive onto the field. We said said we had stuff for two different villages at opposite ends of the site, named the villages and showed them on map print outs. This information was accepted by a dispatcher. However, the bicycle guide refused to guide us to the second location, claiming it was impossible to get there. This is somewhat surprising, since others had been able to drive to that location before. It seemed there was a informational mismatch between dispatch and bicyle guide. (Both locations were accessible by asphalt roads.)
* train shuttle worked well, good job!

=== Badge ===

* Badge handouts were announced right before they happened which didn't allow people to plan their angel shifts and disrupted talks / workshops. A virtual queue would have fixed this and required less total manhours to organize / manage. +1

* There was an expectation that the badge was and I quote from what I have overheard "included in the price". This is not the case and has never been the case but it’s not clearly communicated. To my understanding there was a surplus at SHA2017 and MCH2022 so there never was a shortage of badges before which may have contributed.
** The above is misinformation: It was in fact communicated in written form that every attendee with a ticket receives a badge. The badge could not be ordered separately and was included in the ticket price.

* During the event (AFAIK) there were no badge angel shifts outside of queue angel. This is a chance from prior events and didn't allow people who normally would have helped to help in the same way.

* Due to the badges not being self-powered nor being distributed at the entrance they failed to function as badges. The SHA2017 badge was designed with having no power yet still being a nametag in mind. The WHY2025 badge did not seem to function as a nametag which should have been its intended design goal.

* At MCH and SHA you had people using the badges at the event itself to make games / hack / learn / teach. It was something which brought people together. There was very little being done / to do with the badge during the camp, not just because of the late arrival and limited distribution but rather because there is no way to get apps on the badge outside of the SD card... or if there is a way of doing so then its not documented on the wiki page as of writing. There was no app store app, no way to use the LORA hardware, and outside the event its impossible to use the badge without reflashing a new wifi SSID.

* You could not sit at the badge tent and solder on your antenna onto the badge or work on projects. At SHA and MCH you could just approach the badge people / angels and even get help with projects.

* Badge still has way too limited documentation to even work on it after the event.

* Team Badge have overworked themselves to get a badge available. Team over Badge next time. Which is also a Team:Cohesion issue.

* Would have been great to have a separate queue for villages that collected tickets and pick up 15+ badges at the same time. This would also have greatly reduced waiting times for individuals picking up badges and sped-up the whole process.

* Not enough badges for all visitors (not even close apparently).

* Badge queues were very long and poorly managed. This made it impossible for some people to collected a badge (for example because they cannot stand that long, require shade, have to take care of children, need to go to their next angel shift, etc.)

* The communication about the badge status was very sparse and lacking. If there is a problem, '''communicate''' about it and tell participants what to expect.

** +1. I am sympathetic to the team scrambling to get stuff done under difficult constraints, but especially in such cases good communication is important. Things like randomly posting a link to a page about the keyboard hardware felt frustrating when we were just waiting for more info about future handouts. In addition, a Signal group was a poor choice of channel for announcements for many reasons - no public access, no history for new joiners, redundant join/leave messages, etc. Keeping updates to a section on the wiki and/or a mailing list would've worked much better.

* During build-up, almost all other teams were scrambling to find a pair of hands to get essential stuff done, while watching lots of people pouring epoxy in the badge tent. Which was, lemme me blunt here, one of the lowest priority of all the things that have been done during build-up.

=== Bars and food court ===

* Menu was much longer and more complex compared to MCH. A lot of items were almost never sold, like nachos and chips.
* Slight differences in the menu between the bars caused customers to ask "Do you have ...?". Also complicates restocking logistics.
* The amount of Rum in the "Tschunk" was '''halved''' without updating the price. They decided it was better to modify the recipe to make it almost non-alcoholic, rather than say "Sorry, we're out."
** +1, the Tschunk contained barely any Rum.
* Bar is not a Merch Store, "Special/Ceremonial Cup" should be sold in Infodesk. It was also badly advertised, only people who "knew" of its existence could buy it. +1
* How was the cup not a deposit... I didn't even realize you wouldn't get any money back. Made it extremely bothersome to buy drinks for other people. +1
* Why wasn't statiegeld/pfand collected? Many glass bins full of mate-bottles. I don't want to know how many plastic bottles and aluminium cans were thrown out. This could have been prevented.
* No Club Mate Beere?
* No normal (0.5L) bottles available on the last day?
* Do we get mate from the source, or a Dutch overprices company?
* No mate during buildup again?
* Not written instructions for angels. The “game of telephone” style handing of incorrect instructions down from one angel to the next caused food to be prepared incorrectly. Written instructions should be posted right at the frier and microwave.
** +1
* Handling of vegan food was bad. Burger stall incorrectly advertised vegetarian burger as "vegan" originally, and could not provide any vegan burger at all because the buns contained milk(!). Fries/snacks stall staff did not know what they were selling or what it contained, and communication was difficult. Only positive note goes to the pasta stall where the food was good, and the operator was highly competent and knew exactly what they were selling (I would like to see them at a next event).
* Bottle collection procedure was very unclear.
* To add to the above: between bar and foodcourt no crates in sight on several days. No crates at any of the waste collection points. No instructions or procedure arranged. So people grabbed the glass-waste bin from the showers and put it in the middle. End result: 24x 240L glass trash bin completely filled to the brim. Assuming roughly around 5000 pfand-bottles (Mate, beer etc) were trashed. And team Waste had a ton of heavy lifting to get all these bins off the field and back to the recycling company. This could have been prevented.
* The same with plastic bottles and cans. Team Waste managed to save a *trailer* full of cans and bottles. About 24 big bags (240L). That could easily have been double. And if people actually organized it, it would have been less work.

=== Cohesion ===
* I like the idea, but not the implementation: Geraffel was put at the arse end of the field (OK fine, epicenter of noise gradient and all that), then got told off for playing music during the day.
* Very little communication/information. People barely knew the team existed and could be contacted, social rules like the Photo Policy were not communicated and very widely ignored. Other events signpost these things all over the site and it does help

=== Content / talks / heralds / speakerdesk / AV / recordings ===

* Party Stage was the perfect location for the "History of Hardcore" talk. More 'serious' talks could be held on the music stages at events going forward.

=== CTF / token game ===

=== Decoration / design ===

* Team did an amazing job. The field felt welcoming and interesting. Thank you so much for all the effort that went in. +1
* Next time we need to find a sponsor to print flags for all visitors, and have it available as merch for purchase. It was sad to see so much deco being liberated too early in the event. We need to also work on the communication around this.

=== Family / kids ===

=== Finance / coins / payments ===

* Like the concept of an anonymous payment card that '''just works'''. Absolutely love the design of the WHY2025 card. And very happy to play with a blank Ultralight AES card afterwards.
** +1, this was set up well! My only feedback would be to maybe have something that you can tap your card against to see the remaining balance (or otherwise instruct angels to communicate the balance upon payment)
* option for payout of remaining funds wasn't communicated properly (even the website claimed it wasn't possible at all). Cash payout would be nice, but would understandably be a big extra thing to manage

=== Information / infodesk / wiki ===

* The wiki seems to have never been updated after the event started. I have attempted to find information about something several times and ''none'' of those times was it on the wiki. Instead everything seemed to be in random Signal groups and wherever else, that I didn't even know about until much later.
* It was very hard to find information on anything (like infrastructure, badge handouts, etc.) in general, and even infodesk angels often didn't have the answers.

=== Merchandise ===
* It would have been nice if the merch that was ordered months ago would have actually been available at the field.
* Flags as preordered merchandise. Would create the possibility for hackerspaces and individuals to bring back home some of them. +2

=== NOC / Network ===
* From buildup, through the event, through teardown: the networks worked!
* It was a pleasure to work together, to deduplicate work and equipment.
* In our location, Wifi coverage was poor although we were next to a Datenklo

=== NUTS / power / water ===

* Showers with adjustable heat (showerheads which mix cold and hot water) to avoid burns.
* Wood pallets outside both showers and toilets to reduce mud. (+1, from day zero would have been helpful)
* Even if not in all bathroom points, more drinking water points other than the one in heaven should have been available from the beginning. +1
* Disable the watertaps at the same time as all the other bathroom facilities. Or communicate when the water is going out. Now villages were only able to fill small containers at the toilets. Or needed to walk all the way to Heaven.
* Slightly more cleaning would have been great. The showers were extremely full of mud even inside at times. Given they only used a hose as far as I saw, should have been possible to also have some angels do this in addition to the cleaning crew.
* Adding hooks to the showers was a very welcome addition, thanks!
* It wasn't clear where to get drinking water during the first few days. This should be communicated better, e.g. with signs and on the map. +1
* I liked the number of toilets: never had to wait +1
* furthermore, the toilets seemed to be cleaned often which is good. +1
* There always was toilet paper available in the stalls, greatly lessens anxiety. +1
* water pressure and temperature in the showers was great! Also: never had to wait, which is great! +1
* There always was plenty of soap available at the sinks, during peak time and at night. +1
* Dedicated dishwashing location. +1
* More drinking water fountains across the terrain
* "upgrading" facilities to "drinking water" is questionable. What of all the potential risks was actually tested and could be guaranteed? Separate 100% clear drinking water spots would be better -1
* Shower temperature constantly fluctuated and never stabilized

=== Off-site logistics ===

=== On-site logistics ===

=== POC / DECT / Fieldphones ===
* micropoc worked just fine: I could easily and quickly register the DECT phones for my village and the network worked whenever I wanted to use it.
* Having the DECT so people can reach my team was as always: amazing. Thank you. Feature request: have a phone number only operational during business hours (and redirect to a prerecorded thing other times). Fixed that ourselves by switching the dect to silent. But would be a cool feature.

=== Productiehuis / C3VOC ===

=== Projectleiding ===

=== ROC ===
* Very clear audio and reception
* Was very happy with radio when the relay was up. During the end of teardown the signal degraded to unintelligible gibberish when going across field.
* Next time, don't do a split service desk in warehouse/ROC.

=== Safety / security / first aid / fire ===

=== Supermarket ===
* Happy friendly people who had the correct stuff on the shelves
* Pricing was for a campsite supermarket 'okay'. Having stuff available on field makes up for a lot.
* Would have loved to be able to purchase anything after 8PM, but i understand that they also need to sleep ;)
* Very resilient, apparently; throughout just about every logistical and infrastructure problem at camp, they seemed to keep operating.
* Would have liked to see tofu in the assortment; a few vegan proteins were available but none were quite as versatile.

=== Sysadmin ===

* Setup "live.why2025.org" as an alias for people to easier find the livestreams next time. Right now you needed to go to "streaming.media.ccc.de/why2025".
* IRC is less popular in new generations of hackers and at least Mastodon+Matrix integrations would have made Signal angel role useful.
* Would like a clear messaging channel from Orga/teams to visitors. live.why2025.org would be good. Better than signal. But have no idea what tool to use.

=== Terrain ===

* Noise gradient should be evaluated better: the main party stage was more audible from the family village than from the Belgian cluster, which was way closer.
* Fridge container orientation: the compressor should point away from campers, it was the single most noisy item from Batavus On tour village point of view.
* Infodesk not located at the entrance like at MCH, causing it to be less visible.
* 4000 people but only a single "Hardware Hacking Tent". It was constantly full, and no other places to sit and solder.
** Plenty villages that'll happily let you use their spaces. It makes sense for this kind of thing to be community-provided (the Hardware Hacking Tent was too - while a official workshop spot, it only exists because of of the HHA team willing to equip and run it)
* "Hackcenter" only had space for 20 people, tiny tent, zero cooling, and no advertisement. Not even a sign... We thought it was someone's Village until day 4.
* No place to party/music all night. It would be cool to have a distant (from tents) area where we're allowed to have music going all night long.
** -1, loud music anywhere on the field travels far and I appreciate being able to sleep. I liked the 23:00 cutoff.
** -1 agreed. "distant" location is not really possible on-site
** +1 AGREE, the noise cutoff was really annoying, other events the music continues until 2am atleast, I don't see why we can't have somewhere on site where we can play music at a reasonable volume. 23:00 is too early for a festival.
** +1, made the event substancially worse, if we have color-coded fields to match volume levels why do we still have to shut the music down completely at 23:00 in the red area?
** -1, i was very happy to have a camp where i could sleep without earplugs. Also it would be impossible due to very strict permits this time around.
*** also this was not followed on the last night after closing in which the angel party continued in the main bar until very late???? have some consistency please. it just feels mean otherwise.

* it was nice that noise rules were followed quite well this time (unlike e.g. MCH where main stages switched to silent disco while sponsors kept blaring music into the silent areas)

* I missed routing signs for bikes coming in. Google Maps got me to the wooden bridge which was fenced off, and nobody there to either let me in or give me a hint. I may have let myself in at that fence, because it was very unclear which detour to take. The climb was only moderately scary.
* Seperate smoking and non-smoking fields, designated smoking areas away from event spaces. A blanket ban on smoking and vaping for the entire event is probably not feasible (unfortunately).

=== Tickets / entrance ===
* Putting the desks on the other side might have looked more welcoming, but all was fine for my check-in.
* Camper tickets were not scanned?

=== Villages ===
* Well done! And it was fun to help out villages doing extra luggage shuttles after we were done doing Waste stuff.

=== Volunteering / angels / heaven===

* Food tickets given to volunteers expiring, without any communication of them doing so.

[[File:Angel Waterbottle Comparison WHY vs MCH.jpg|thumb|Angle Waterbottle Comparison WHY vs MCH]]

* Waterbottle had boring text "'''Thanks For Volunteering'''", instead of WHY wordplay like "'''We Hydrate You'''", "'''Why Hydrate Yourself?'''" or "'''Wet Hackers, Yay!'''".
* Clip/Hook on the waterbootle was 3x smaller, making it unwieldy and difficult to connect. The MCH hook was bigger and easier to quick-connect.
* Drinking part had leak problems, which was not present on the previous bottle.
* The clip caused burn/melt-damage on the waterbottle, as can be seen when zooming in where the clip touches the orange waterbottle.
* No mate during buildup.
* No safe food, or unclear about the contents.
* Severe food safety issues in heaven. Bread toppings (including cheese and meat!) left open on a table outside of a fridge for hours, even overnight, with insects roaming around. No proper cleaning agents or supplies available for cleaning surfaces like tables, only some random supermarket cleaning sprays (this is not good enough for a central eating area!).
* Vegan food availability was unclear and could not be relied on. At times, the "vegan options" were completely inadequate for actually keeping people fed while doing potentially physically intensive volunteer work, with lacking nutritional value. Problem persisted during teardown. "We can't predict what the caterer will deliver" is not good enough for people with dietary restrictions.
* Heaven was too loud. It was almost impossible to communicate with people at the angel desk when there was a meal going on, and you had to practically yell to hear each other. Ideally sound dampening would be installed, but at least the eating area should be separated/insulated from the heaven desk and standby angel area in some way.
* Loved the DasBrot
* Didn't love the utter lack of social hygene during breakfast, lunch and dinner. The proper tools were lacking. Get a cooling gastronorm tray thing for all your meats and cheeses, get the (wasteful) small cups of smears. And have people service it. Dinner handout got fixed with angels doing plating, but was still very haphazard on several days.
* You need more people on the team. You worked your butts off and did not get to enjoy camp enough. I wish better for you all.
* Also get teardown safety vests (or use generic ones for buildup and give a cool one to those tearing down).

=== Warehouse ===
* When Boels screwed up, warehouse delivered us a replacement the same day.
- what did boels screw up?
* I appreciate being able to discuss the underlying requirements instead of automatically being handed a solution. When I asked for a bunch of extension cords, it turned out there was a better solution.
* Delivery service made camp a lot better for me as teamlead. I fixed several problems with one phone call and a happy angel heading out on a bike or gator!
* Purchase generic safety vests for use during shifts. All safety vests with branding were taken by people having done buildup.

=== Waste / garbage collection ===

* I have no knowledge about the state of recycling in NL, but having only separate bins for glass and then ones for everything else felt quite bad. At least separation of paper/carton would have made sense I guess. Also having separate containers where people could "donate" plastic bottles / metal cans which have deposit would have made sense and also could have brought a nice sum of money for the event.
''-> The rules for plastic and metal recycling vary per local municipality, let alone per country. So we decided to not do a plastic/metal sorting bin as it would probably only cause headaches. ''

''-> Paper and food remains were collected seperately at heaven, foodcourt. Agree on extending that to villages.''

''-> Pfand was handled by team bar. Full agree. We saved a trailer full of big bags of bottles and cans.''

* Field was nice and clean until teardown with enough containers to get rid of waste. (+1 for adding at least a paper and deposit container)
* The bins near the villages I was at were always emptied before overflowing, which was nice. On teardown day I saw a big pile of bottles around one of the bins: can't say if glass or deposit ones. Generally the field seemed rather clean.

''-> See above, glass deposit should have been collected. Unclear why it wasn't.''

=== Teardown ===

* "No cars on the gras" policy: Villages that respected the rule of not driving on the grass were effectively disadvantaged. On Wednesday, many cars ignored the rule and drove onto the grass, which meant those villages didn’t have to carry their equipment over long distances. Meanwhile, villages that followed the rule had to transport their gear much farther, which was exhausting given the hot weather. Suggestion: Instead of creating a situation where following the rules feels like a disadvantage, we could reward compliance. For example, check which villages adhere to the rule, and if they do, give them vouchers for a priority ticket queue for the next event.
* Toilets were shut down too early making getting water during the warm teardown harder
* Transporting crates with empty bottles in hand trucks is also very unsafe. If they fall over it would be a mess for barefooted people. Bringing them in and out with cars is much safer.
* Way too many people left a day early. That was a bit sad. For everyone reading this: stay the entire camp ;)
* We should communicate better that flags and other deco is there for the event and should not disappear during the event. Previous events and other events by other parties may have 'trained' our visitors to think they are helping out by removing such decoration early. It was a bit sad to see people rip things of the waste gator. They got told off. But the flags on the main road disappeared on day 2 of camp, and that was entirely unwarranted.
* Remove toilet accessories (paper/soap/brushes) beofore toilets are removed, otherwise they get dumped out on the field.
* Remove zipties of the main tents before tearing the tents down, the tent guys just cut them and leave them on the field.
* Not enough hi-vis vests available, which is especially unsafe when heavy machinery is roaming the site.
* There didn't seem to be any documentation of the teardown procedure for angels, which made it difficult to plan things like food and sleep.

Feedback

2025-08-18T09:39:40Z

Bas: /* Waste / garbage collection */

'''What Hackers Yearn''' for is to '''Improve'''. This page is dedicated to collecting user feedback related to the execution of WHY2025 as a whole. Constructive feedback is invaluable to the continuous improvement of the project and is welcomed from all participants. Please share your observations and suggestions in a '''clear and respectful manner'''. Your input will help guide enhancements for future generations of the event.

It is also possible to send feedback to [http://mailto:2029@why2025.org 2029@why2025.org]

== IMPORTANT ==

Do '''NOT''' review '''people'''. Any individual interaction you had with a human does not belong here, but should be taken up with [[Team:Cohesion]].

This page is strictly for addressing improvements for the next event. We encourage contributors to maintain a neutral, factual, and calm tone in their feedback.

* GOOD EXAMPLES: "Excessive mud at showers", "Food vendors often refused to accept WHY-voucher", or "Limited drop-off points for luggage shuttle".

* BAD EXAMPLES: "Person XXX was insulting me", "Helpdesk XOC was too busy to help", "frickin hot", "So the story begins on Saturday night at 23:04 when..."

== Feedback List ==

=== General / overall ===

* There should be a clear single method/channel of communication from orga, using the Heaven signal chat or social media for this is not ideal
** +1
* "Communication" in general seems to be the theme of this camp. It was extremely difficult to find reliable information about anything as a visitor/angel, and often you only had the grapevine to go off, and you just had to hope that the necessary information somehow reached you at some point. From what I've heard it wasn't much better between teams either. Documenting things is really important and saves everyone a lot of work having to repeat and figure out the same things over and over again!

=== Arrival / departure / parking / train shuttle / luggage shuttle ===

* On day 0 we queued to drive onto the field. We said said we had stuff for two different villages at opposite ends of the site, named the villages and showed them on map print outs. This information was accepted by a dispatcher. However, the bicycle guide refused to guide us to the second location, claiming it was impossible to get there. This is somewhat surprising, since others had been able to drive to that location before. It seemed there was a informational mismatch between dispatch and bicyle guide. (Both locations were accessible by asphalt roads.)
* train shuttle worked well, good job!

=== Badge ===

* Badge handouts were announced right before they happened which didn't allow people to plan their angel shifts and disrupted talks / workshops. A virtual queue would have fixed this and required less total manhours to organize / manage. +1

* There was an expectation that the badge was and I quote from what I have overheard "included in the price". This is not the case and has never been the case but it’s not clearly communicated. To my understanding there was a surplus at SHA2017 and MCH2022 so there never was a shortage of badges before which may have contributed.
** The above is misinformation: It was in fact communicated in written form that every attendee with a ticket receives a badge. The badge could not be ordered separately and was included in the ticket price.

* During the event (AFAIK) there were no badge angel shifts outside of queue angel. This is a chance from prior events and didn't allow people who normally would have helped to help in the same way.

* Due to the badges not being self-powered nor being distributed at the entrance they failed to function as badges. The SHA2017 badge was designed with having no power yet still being a nametag in mind. The WHY2025 badge did not seem to function as a nametag which should have been its intended design goal.

* At MCH and SHA you had people using the badges at the event itself to make games / hack / learn / teach. It was something which brought people together. There was very little being done / to do with the badge during the camp, not just because of the late arrival and limited distribution but rather because there is no way to get apps on the badge outside of the SD card... or if there is a way of doing so then its not documented on the wiki page as of writing. There was no app store app, no way to use the LORA hardware, and outside the event its impossible to use the badge without reflashing a new wifi SSID.

* You could not sit at the badge tent and solder on your antenna onto the badge or work on projects. At SHA and MCH you could just approach the badge people / angels and even get help with projects.

* Badge still has way too limited documentation to even work on it after the event.

* Team Badge have overworked themselves to get a badge available. Team over Badge next time. Which is also a Team:Cohesion issue.

* Would have been great to have a separate queue for villages that collected tickets and pick up 15+ badges at the same time. This would also have greatly reduced waiting times for individuals picking up badges and sped-up the whole process.

* Not enough badges for all visitors (not even close apparently).

* Badge queues were very long and poorly managed. This made it impossible for some people to collected a badge (for example because they cannot stand that long, require shade, have to take care of children, need to go to their next angel shift, etc.)

* The communication about the badge status was very sparse and lacking. If there is a problem, '''communicate''' about it and tell participants what to expect.

** +1. I am sympathetic to the team scrambling to get stuff done under difficult constraints, but especially in such cases good communication is important. Things like randomly posting a link to a page about the keyboard hardware felt frustrating when we were just waiting for more info about future handouts. In addition, a Signal group was a poor choice of channel for announcements for many reasons - no public access, no history for new joiners, redundant join/leave messages, etc. Keeping updates to a section on the wiki and/or a mailing list would've worked much better.

* During build-up, almost all other teams were scrambling to find a pair of hands to get essential stuff done, while watching lots of people pouring epoxy in the badge tent. Which was, lemme me blunt here, one of the lowest priority of all the things that have been done during build-up.

=== Bars and food court ===

* Menu was much longer and more complex compared to MCH. A lot of items were almost never sold, like nachos and chips.
* Slight differences in the menu between the bars caused customers to ask "Do you have ...?". Also complicates restocking logistics.
* The amount of Rum in the "Tschunk" was '''halved''' without updating the price. They decided it was better to modify the recipe to make it almost non-alcoholic, rather than say "Sorry, we're out."
** +1, the Tschunk contained barely any Rum.
* Bar is not a Merch Store, "Special/Ceremonial Cup" should be sold in Infodesk. It was also badly advertised, only people who "knew" of its existence could buy it. +1
* How was the cup not a deposit... I didn't even realize you wouldn't get any money back. Made it extremely bothersome to buy drinks for other people. +1
* Why wasn't statiegeld/pfand collected? Many glass bins full of mate-bottles. I don't want to know how many plastic bottles and aluminium cans were thrown out. This could have been prevented.
* No Club Mate Beere?
* No normal (0.5L) bottles available on the last day?
* Do we get mate from the source, or a Dutch overprices company?
* No mate during buildup again?
* Not written instructions for angels. The “game of telephone” style handing of incorrect instructions down from one angel to the next caused food to be prepared incorrectly. Written instructions should be posted right at the frier and microwave.
** +1
* Handling of vegan food was bad. Burger stall incorrectly advertised vegetarian burger as "vegan" originally, and could not provide any vegan burger at all because the buns contained milk(!). Fries/snacks stall staff did not know what they were selling or what it contained, and communication was difficult. Only positive note goes to the pasta stall where the food was good, and the operator was highly competent and knew exactly what they were selling (I would like to see them at a next event).
* Bottle collection procedure was very unclear.
* To add to the above: between bar and foodcourt no crates in sight on several days. No crates at any of the waste collection points. No instructions or procedure arranged. So people grabbed the glass-waste bin from the showers and put it in the middle. End result: 24x 240L glass trash bin completely filled to the brim. Assuming roughly around 5000 pfand-bottles (Mate, beer etc) were trashed. And team Waste had a ton of heavy lifting to get all these bins off the field and back to the recycling company. This could have been prevented.
* The same with plastic bottles and cans. Team Waste managed to save a *trailer* full of cans and bottles. About 24 big bags (240L). That could easily have been double. And if people actually organized it, it would have been less work.

=== Cohesion ===
* I like the idea, but not the implementation: Geraffel was put at the arse end of the field (OK fine, epicenter of noise gradient and all that), then got told off for playing music during the day.
* Very little communication/information. People barely knew the team existed and could be contacted, social rules like the Photo Policy were not communicated and very widely ignored. Other events signpost these things all over the site and it does help

=== Content / talks / heralds / speakerdesk / AV / recordings ===

* Party Stage was the perfect location for the "History of Hardcore" talk. More 'serious' talks could be held on the music stages at events going forward.

=== CTF / token game ===

=== Decoration / design ===

* Team did an amazing job. The field felt welcoming and interesting. Thank you so much for all the effort that went in. +1
* Next time we need to find a sponsor to print flags for all visitors, and have it available as merch for purchase. It was sad to see so much deco being liberated too early in the event. We need to also work on the communication around this.

=== Family / kids ===

=== Finance / coins / payments ===

* Like the concept of an anonymous payment card that '''just works'''. Absolutely love the design of the WHY2025 card. And very happy to play with a blank Ultralight AES card afterwards.
** +1, this was set up well! My only feedback would be to maybe have something that you can tap your card against to see the remaining balance (or otherwise instruct angels to communicate the balance upon payment)
* option for payout of remaining funds wasn't communicated properly (even the website claimed it wasn't possible at all). Cash payout would be nice, but would understandably be a big extra thing to manage

=== Information / infodesk / wiki ===

* The wiki seems to have never been updated after the event started. I have attempted to find information about something several times and ''none'' of those times was it on the wiki. Instead everything seemed to be in random Signal groups and wherever else, that I didn't even know about until much later.
* It was very hard to find information on anything (like infrastructure, badge handouts, etc.) in general, and even infodesk angels often didn't have the answers.

=== Merchandise ===
* It would have been nice if the merch that was ordered months ago would have actually been available at the field.
* Flags as preordered merchandise. Would create the possibility for hackerspaces and individuals to bring back home some of them. +2

=== NOC / Network ===
* From buildup, through the event, through teardown: the networks worked!
* It was a pleasure to work together, to deduplicate work and equipment.
* In our location, Wifi coverage was poor although we were next to a Datenklo

=== NUTS / power / water ===

* Showers with adjustable heat (showerheads which mix cold and hot water) to avoid burns.
* Wood pallets outside both showers and toilets to reduce mud. (+1, from day zero would have been helpful)
* Even if not in all bathroom points, more drinking water points other than the one in heaven should have been available from the beginning. +1
* Disable the watertaps at the same time as all the other bathroom facilities. Or communicate when the water is going out. Now villages were only able to fill small containers at the toilets. Or needed to walk all the way to Heaven.
* Slightly more cleaning would have been great. The showers were extremely full of mud even inside at times. Given they only used a hose as far as I saw, should have been possible to also have some angels do this in addition to the cleaning crew.
* Adding hooks to the showers was a very welcome addition, thanks!
* It wasn't clear where to get drinking water during the first few days. This should be communicated better, e.g. with signs and on the map. +1
* I liked the number of toilets: never had to wait +1
* furthermore, the toilets seemed to be cleaned often which is good. +1
* There always was toilet paper available in the stalls, greatly lessens anxiety. +1
* water pressure and temperature in the showers was great! Also: never had to wait, which is great! +1
* There always was plenty of soap available at the sinks, during peak time and at night. +1
* Dedicated dishwashing location. +1
* More drinking water fountains across the terrain
* "upgrading" facilities to "drinking water" is questionable. What of all the potential risks was actually tested and could be guaranteed? Separate 100% clear drinking water spots would be better -1
* Shower temperature constantly fluctuated and never stabilized

=== Off-site logistics ===

=== On-site logistics ===

=== POC / DECT / Fieldphones ===
* micropoc worked just fine: I could easily and quickly register the DECT phones for my village and the network worked whenever I wanted to use it.
* Having the DECT so people can reach my team was as always: amazing. Thank you. Feature request: have a phone number only operational during business hours (and redirect to a prerecorded thing other times). Fixed that ourselves by switching the dect to silent. But would be a cool feature.

=== Productiehuis / C3VOC ===

=== Projectleiding ===

=== ROC ===
* Very clear audio and reception
* Was very happy with radio when the relay was up. During the end of teardown the signal degraded to unintelligible gibberish when going across field.
* Next time, don't do a split service desk in warehouse/ROC.

=== Safety / security / first aid / fire ===

=== Supermarket ===
* Happy friendly people who had the correct stuff on the shelves
* Pricing was for a campsite supermarket 'okay'. Having stuff available on field makes up for a lot.
* Would have loved to be able to purchase anything after 8PM, but i understand that they also need to sleep ;)
* Very resilient, apparently; throughout just about every logistical and infrastructure problem at camp, they seemed to keep operating.
* Would have liked to see tofu in the assortment; a few vegan proteins were available but none were quite as versatile.

=== Sysadmin ===

* Setup "live.why2025.org" as an alias for people to easier find the livestreams next time. Right now you needed to go to "streaming.media.ccc.de/why2025".
* IRC is less popular in new generations of hackers and at least Mastodon+Matrix integrations would have made Signal angel role useful.
* Would like a clear messaging channel from Orga/teams to visitors. live.why2025.org would be good. Better than signal. But have no idea what tool to use.

=== Terrain ===

* Noise gradient should be evaluated better: the main party stage was more audible from the family village than from the Belgian cluster, which was way closer.
* Fridge container orientation: the compressor should point away from campers, it was the single most noisy item from Batavus On tour village point of view.
* Infodesk not located at the entrance like at MCH, causing it to be less visible.
* 4000 people but only a single "Hardware Hacking Tent". It was constantly full, and no other places to sit and solder.
** Plenty villages that'll happily let you use their spaces. It makes sense for this kind of thing to be community-provided (the Hardware Hacking Tent was too - while a official workshop spot, it only exists because of of the HHA team willing to equip and run it)
* "Hackcenter" only had space for 20 people, tiny tent, zero cooling, and no advertisement. Not even a sign... We thought it was someone's Village until day 4.
* No place to party/music all night. It would be cool to have a distant (from tents) area where we're allowed to have music going all night long.
** -1, loud music anywhere on the field travels far and I appreciate being able to sleep. I liked the 23:00 cutoff.
** -1 agreed. "distant" location is not really possible on-site
** +1 AGREE, the noise cutoff was really annoying, other events the music continues until 2am atleast, I don't see why we can't have somewhere on site where we can play music at a reasonable volume. 23:00 is too early for a festival.
** +1, made the event substancially worse, if we have color-coded fields to match volume levels why do we still have to shut the music down completely at 23:00 in the red area?
** -1, i was very happy to have a camp where i could sleep without earplugs. Also it would be impossible due to very strict permits this time around.
*** also this was not followed on the last night after closing in which the angel party continued in the main bar until very late???? have some consistency please. it just feels mean otherwise.

* it was nice that noise rules were followed quite well this time (unlike e.g. MCH where main stages switched to silent disco while sponsors kept blaring music into the silent areas)

* I missed routing signs for bikes coming in. Google Maps got me to the wooden bridge which was fenced off, and nobody there to either let me in or give me a hint. I may have let myself in at that fence, because it was very unclear which detour to take. The climb was only moderately scary.
* Seperate smoking and non-smoking fields, designated smoking areas away from event spaces. A blanket ban on smoking and vaping for the entire event is probably not feasible (unfortunately).

=== Tickets / entrance ===
* Putting the desks on the other side might have looked more welcoming, but all was fine for my check-in.
* Camper tickets were not scanned?

=== Villages ===
* Well done! And it was fun to help out villages doing extra luggage shuttles after we were done doing Waste stuff.

=== Volunteering / angels / heaven===

* Food tickets given to volunteers expiring, without any communication of them doing so.

[[File:Angel Waterbottle Comparison WHY vs MCH.jpg|thumb|Angle Waterbottle Comparison WHY vs MCH]]

* Waterbottle had boring text "'''Thanks For Volunteering'''", instead of WHY wordplay like "'''We Hydrate You'''", "'''Why Hydrate Yourself?'''" or "'''Wet Hackers, Yay!'''".
* Clip/Hook on the waterbootle was 3x smaller, making it unwieldy and difficult to connect. The MCH hook was bigger and easier to quick-connect.
* Drinking part had leak problems, which was not present on the previous bottle.
* The clip caused burn/melt-damage on the waterbottle, as can be seen when zooming in where the clip touches the orange waterbottle.
* No mate during buildup.
* No safe food, or unclear about the contents.
* Severe food safety issues in heaven. Bread toppings (including cheese and meat!) left open on a table outside of a fridge for hours, even overnight, with insects roaming around. No proper cleaning agents or supplies available for cleaning surfaces like tables, only some random supermarket cleaning sprays (this is not good enough for a central eating area!).
* Vegan food availability was unclear and could not be relied on. At times, the "vegan options" were completely inadequate for actually keeping people fed while doing potentially physically intensive volunteer work, with lacking nutritional value. Problem persisted during teardown. "We can't predict what the caterer will deliver" is not good enough for people with dietary restrictions.
* Heaven was too loud. It was almost impossible to communicate with people at the angel desk when there was a meal going on, and you had to practically yell to hear each other. Ideally sound dampening would be installed, but at least the eating area should be separated/insulated from the heaven desk and standby angel area in some way.
* Loved the DasBrot
* Didn't love the utter lack of social hygene during breakfast, lunch and dinner. The proper tools were lacking. Get a cooling gastronorm tray thing for all your meats and cheeses, get the (wasteful) small cups of smears. And have people service it. Dinner handout got fixed with angels doing plating, but was still very haphazard on several days.
* You need more people on the team. You worked your butts off and did not get to enjoy camp enough. I wish better for you all.
* Also get teardown safety vests (or use generic ones for buildup and give a cool one to those tearing down).

=== Warehouse ===
* When Boels screwed up, warehouse delivered us a replacement the same day.
- what did boels screw up?
* I appreciate being able to discuss the underlying requirements instead of automatically being handed a solution. When I asked for a bunch of extension cords, it turned out there was a better solution.
* Delivery service made camp a lot better for me as teamlead. I fixed several problems with one phone call and a happy angel heading out on a bike or gator!
* Purchase generic safety vests for use during shifts. All safety vests with branding were taken by people having done buildup.

=== Waste / garbage collection ===

* I have no knowledge about the state of recycling in NL, but having only separate bins for glass and then ones for everything else felt quite bad. At least separation of paper/carton would have made sense I guess. Also having separate containers where people could "donate" plastic bottles / metal cans which have deposit would have made sense and also could have brought a nice sum of money for the event.
''-> The rules for plastic and metal recycling vary per local municipality, let alone per country. So we decided to not do a plastic/metal sorting bin as it would probably only cause headaches.

-> Paper and food remains were collected seperately at heaven, foodcourt. Agree on extending that to villages.

-> Pfand was handled by team bar. Full agree. We saved a trailer full of big bags of bottles and cans.''

* Field was nice and clean until teardown with enough containers to get rid of waste. (+1 for adding at least a paper and deposit container)
* The bins near the villages I was at were always emptied before overflowing, which was nice. On teardown day I saw a big pile of bottles around one of the bins: can't say if glass or deposit ones. Generally the field seemed rather clean.

''-> See above, glass deposit should have been collected. Unclear why it wasn't.
''

=== Teardown ===

* "No cars on the gras" policy: Villages that respected the rule of not driving on the grass were effectively disadvantaged. On Wednesday, many cars ignored the rule and drove onto the grass, which meant those villages didn’t have to carry their equipment over long distances. Meanwhile, villages that followed the rule had to transport their gear much farther, which was exhausting given the hot weather. Suggestion: Instead of creating a situation where following the rules feels like a disadvantage, we could reward compliance. For example, check which villages adhere to the rule, and if they do, give them vouchers for a priority ticket queue for the next event.
* Toilets were shut down too early making getting water during the warm teardown harder
* Transporting crates with empty bottles in hand trucks is also very unsafe. If they fall over it would be a mess for barefooted people. Bringing them in and out with cars is much safer.
* Way too many people left a day early. That was a bit sad. For everyone reading this: stay the entire camp ;)
* We should communicate better that flags and other deco is there for the event and should not disappear during the event. Previous events and other events by other parties may have 'trained' our visitors to think they are helping out by removing such decoration early. It was a bit sad to see people rip things of the waste gator. They got told off. But the flags on the main road disappeared on day 2 of camp, and that was entirely unwarranted.
* Remove toilet accessories (paper/soap/brushes) beofore toilets are removed, otherwise they get dumped out on the field.
* Remove zipties of the main tents before tearing the tents down, the tent guys just cut them and leave them on the field.
* Not enough hi-vis vests available, which is especially unsafe when heavy machinery is roaming the site.
* There didn't seem to be any documentation of the teardown procedure for angels, which made it difficult to plan things like food and sleep.

Feedback

2025-08-18T09:39:07Z

Bas: /* Waste / garbage collection */

'''What Hackers Yearn''' for is to '''Improve'''. This page is dedicated to collecting user feedback related to the execution of WHY2025 as a whole. Constructive feedback is invaluable to the continuous improvement of the project and is welcomed from all participants. Please share your observations and suggestions in a '''clear and respectful manner'''. Your input will help guide enhancements for future generations of the event.

It is also possible to send feedback to [http://mailto:2029@why2025.org 2029@why2025.org]

== IMPORTANT ==

Do '''NOT''' review '''people'''. Any individual interaction you had with a human does not belong here, but should be taken up with [[Team:Cohesion]].

This page is strictly for addressing improvements for the next event. We encourage contributors to maintain a neutral, factual, and calm tone in their feedback.

* GOOD EXAMPLES: "Excessive mud at showers", "Food vendors often refused to accept WHY-voucher", or "Limited drop-off points for luggage shuttle".

* BAD EXAMPLES: "Person XXX was insulting me", "Helpdesk XOC was too busy to help", "frickin hot", "So the story begins on Saturday night at 23:04 when..."

== Feedback List ==

=== General / overall ===

* There should be a clear single method/channel of communication from orga, using the Heaven signal chat or social media for this is not ideal
** +1
* "Communication" in general seems to be the theme of this camp. It was extremely difficult to find reliable information about anything as a visitor/angel, and often you only had the grapevine to go off, and you just had to hope that the necessary information somehow reached you at some point. From what I've heard it wasn't much better between teams either. Documenting things is really important and saves everyone a lot of work having to repeat and figure out the same things over and over again!

=== Arrival / departure / parking / train shuttle / luggage shuttle ===

* On day 0 we queued to drive onto the field. We said said we had stuff for two different villages at opposite ends of the site, named the villages and showed them on map print outs. This information was accepted by a dispatcher. However, the bicycle guide refused to guide us to the second location, claiming it was impossible to get there. This is somewhat surprising, since others had been able to drive to that location before. It seemed there was a informational mismatch between dispatch and bicyle guide. (Both locations were accessible by asphalt roads.)
* train shuttle worked well, good job!

=== Badge ===

* Badge handouts were announced right before they happened which didn't allow people to plan their angel shifts and disrupted talks / workshops. A virtual queue would have fixed this and required less total manhours to organize / manage. +1

* There was an expectation that the badge was and I quote from what I have overheard "included in the price". This is not the case and has never been the case but it’s not clearly communicated. To my understanding there was a surplus at SHA2017 and MCH2022 so there never was a shortage of badges before which may have contributed.
** The above is misinformation: It was in fact communicated in written form that every attendee with a ticket receives a badge. The badge could not be ordered separately and was included in the ticket price.

* During the event (AFAIK) there were no badge angel shifts outside of queue angel. This is a chance from prior events and didn't allow people who normally would have helped to help in the same way.

* Due to the badges not being self-powered nor being distributed at the entrance they failed to function as badges. The SHA2017 badge was designed with having no power yet still being a nametag in mind. The WHY2025 badge did not seem to function as a nametag which should have been its intended design goal.

* At MCH and SHA you had people using the badges at the event itself to make games / hack / learn / teach. It was something which brought people together. There was very little being done / to do with the badge during the camp, not just because of the late arrival and limited distribution but rather because there is no way to get apps on the badge outside of the SD card... or if there is a way of doing so then its not documented on the wiki page as of writing. There was no app store app, no way to use the LORA hardware, and outside the event its impossible to use the badge without reflashing a new wifi SSID.

* You could not sit at the badge tent and solder on your antenna onto the badge or work on projects. At SHA and MCH you could just approach the badge people / angels and even get help with projects.

* Badge still has way too limited documentation to even work on it after the event.

* Team Badge have overworked themselves to get a badge available. Team over Badge next time. Which is also a Team:Cohesion issue.

* Would have been great to have a separate queue for villages that collected tickets and pick up 15+ badges at the same time. This would also have greatly reduced waiting times for individuals picking up badges and sped-up the whole process.

* Not enough badges for all visitors (not even close apparently).

* Badge queues were very long and poorly managed. This made it impossible for some people to collected a badge (for example because they cannot stand that long, require shade, have to take care of children, need to go to their next angel shift, etc.)

* The communication about the badge status was very sparse and lacking. If there is a problem, '''communicate''' about it and tell participants what to expect.

** +1. I am sympathetic to the team scrambling to get stuff done under difficult constraints, but especially in such cases good communication is important. Things like randomly posting a link to a page about the keyboard hardware felt frustrating when we were just waiting for more info about future handouts. In addition, a Signal group was a poor choice of channel for announcements for many reasons - no public access, no history for new joiners, redundant join/leave messages, etc. Keeping updates to a section on the wiki and/or a mailing list would've worked much better.

* During build-up, almost all other teams were scrambling to find a pair of hands to get essential stuff done, while watching lots of people pouring epoxy in the badge tent. Which was, lemme me blunt here, one of the lowest priority of all the things that have been done during build-up.

=== Bars and food court ===

* Menu was much longer and more complex compared to MCH. A lot of items were almost never sold, like nachos and chips.
* Slight differences in the menu between the bars caused customers to ask "Do you have ...?". Also complicates restocking logistics.
* The amount of Rum in the "Tschunk" was '''halved''' without updating the price. They decided it was better to modify the recipe to make it almost non-alcoholic, rather than say "Sorry, we're out."
** +1, the Tschunk contained barely any Rum.
* Bar is not a Merch Store, "Special/Ceremonial Cup" should be sold in Infodesk. It was also badly advertised, only people who "knew" of its existence could buy it. +1
* How was the cup not a deposit... I didn't even realize you wouldn't get any money back. Made it extremely bothersome to buy drinks for other people. +1
* Why wasn't statiegeld/pfand collected? Many glass bins full of mate-bottles. I don't want to know how many plastic bottles and aluminium cans were thrown out. This could have been prevented.
* No Club Mate Beere?
* No normal (0.5L) bottles available on the last day?
* Do we get mate from the source, or a Dutch overprices company?
* No mate during buildup again?
* Not written instructions for angels. The “game of telephone” style handing of incorrect instructions down from one angel to the next caused food to be prepared incorrectly. Written instructions should be posted right at the frier and microwave.
** +1
* Handling of vegan food was bad. Burger stall incorrectly advertised vegetarian burger as "vegan" originally, and could not provide any vegan burger at all because the buns contained milk(!). Fries/snacks stall staff did not know what they were selling or what it contained, and communication was difficult. Only positive note goes to the pasta stall where the food was good, and the operator was highly competent and knew exactly what they were selling (I would like to see them at a next event).
* Bottle collection procedure was very unclear.
* To add to the above: between bar and foodcourt no crates in sight on several days. No crates at any of the waste collection points. No instructions or procedure arranged. So people grabbed the glass-waste bin from the showers and put it in the middle. End result: 24x 240L glass trash bin completely filled to the brim. Assuming roughly around 5000 pfand-bottles (Mate, beer etc) were trashed. And team Waste had a ton of heavy lifting to get all these bins off the field and back to the recycling company. This could have been prevented.
* The same with plastic bottles and cans. Team Waste managed to save a *trailer* full of cans and bottles. About 24 big bags (240L). That could easily have been double. And if people actually organized it, it would have been less work.

=== Cohesion ===
* I like the idea, but not the implementation: Geraffel was put at the arse end of the field (OK fine, epicenter of noise gradient and all that), then got told off for playing music during the day.
* Very little communication/information. People barely knew the team existed and could be contacted, social rules like the Photo Policy were not communicated and very widely ignored. Other events signpost these things all over the site and it does help

=== Content / talks / heralds / speakerdesk / AV / recordings ===

* Party Stage was the perfect location for the "History of Hardcore" talk. More 'serious' talks could be held on the music stages at events going forward.

=== CTF / token game ===

=== Decoration / design ===

* Team did an amazing job. The field felt welcoming and interesting. Thank you so much for all the effort that went in. +1
* Next time we need to find a sponsor to print flags for all visitors, and have it available as merch for purchase. It was sad to see so much deco being liberated too early in the event. We need to also work on the communication around this.

=== Family / kids ===

=== Finance / coins / payments ===

* Like the concept of an anonymous payment card that '''just works'''. Absolutely love the design of the WHY2025 card. And very happy to play with a blank Ultralight AES card afterwards.
** +1, this was set up well! My only feedback would be to maybe have something that you can tap your card against to see the remaining balance (or otherwise instruct angels to communicate the balance upon payment)
* option for payout of remaining funds wasn't communicated properly (even the website claimed it wasn't possible at all). Cash payout would be nice, but would understandably be a big extra thing to manage

=== Information / infodesk / wiki ===

* The wiki seems to have never been updated after the event started. I have attempted to find information about something several times and ''none'' of those times was it on the wiki. Instead everything seemed to be in random Signal groups and wherever else, that I didn't even know about until much later.
* It was very hard to find information on anything (like infrastructure, badge handouts, etc.) in general, and even infodesk angels often didn't have the answers.

=== Merchandise ===
* It would have been nice if the merch that was ordered months ago would have actually been available at the field.
* Flags as preordered merchandise. Would create the possibility for hackerspaces and individuals to bring back home some of them. +2

=== NOC / Network ===
* From buildup, through the event, through teardown: the networks worked!
* It was a pleasure to work together, to deduplicate work and equipment.
* In our location, Wifi coverage was poor although we were next to a Datenklo

=== NUTS / power / water ===

* Showers with adjustable heat (showerheads which mix cold and hot water) to avoid burns.
* Wood pallets outside both showers and toilets to reduce mud. (+1, from day zero would have been helpful)
* Even if not in all bathroom points, more drinking water points other than the one in heaven should have been available from the beginning. +1
* Disable the watertaps at the same time as all the other bathroom facilities. Or communicate when the water is going out. Now villages were only able to fill small containers at the toilets. Or needed to walk all the way to Heaven.
* Slightly more cleaning would have been great. The showers were extremely full of mud even inside at times. Given they only used a hose as far as I saw, should have been possible to also have some angels do this in addition to the cleaning crew.
* Adding hooks to the showers was a very welcome addition, thanks!
* It wasn't clear where to get drinking water during the first few days. This should be communicated better, e.g. with signs and on the map. +1
* I liked the number of toilets: never had to wait +1
* furthermore, the toilets seemed to be cleaned often which is good. +1
* There always was toilet paper available in the stalls, greatly lessens anxiety. +1
* water pressure and temperature in the showers was great! Also: never had to wait, which is great! +1
* There always was plenty of soap available at the sinks, during peak time and at night. +1
* Dedicated dishwashing location. +1
* More drinking water fountains across the terrain
* "upgrading" facilities to "drinking water" is questionable. What of all the potential risks was actually tested and could be guaranteed? Separate 100% clear drinking water spots would be better -1
* Shower temperature constantly fluctuated and never stabilized

=== Off-site logistics ===

=== On-site logistics ===

=== POC / DECT / Fieldphones ===
* micropoc worked just fine: I could easily and quickly register the DECT phones for my village and the network worked whenever I wanted to use it.
* Having the DECT so people can reach my team was as always: amazing. Thank you. Feature request: have a phone number only operational during business hours (and redirect to a prerecorded thing other times). Fixed that ourselves by switching the dect to silent. But would be a cool feature.

=== Productiehuis / C3VOC ===

=== Projectleiding ===

=== ROC ===
* Very clear audio and reception
* Was very happy with radio when the relay was up. During the end of teardown the signal degraded to unintelligible gibberish when going across field.
* Next time, don't do a split service desk in warehouse/ROC.

=== Safety / security / first aid / fire ===

=== Supermarket ===
* Happy friendly people who had the correct stuff on the shelves
* Pricing was for a campsite supermarket 'okay'. Having stuff available on field makes up for a lot.
* Would have loved to be able to purchase anything after 8PM, but i understand that they also need to sleep ;)
* Very resilient, apparently; throughout just about every logistical and infrastructure problem at camp, they seemed to keep operating.
* Would have liked to see tofu in the assortment; a few vegan proteins were available but none were quite as versatile.

=== Sysadmin ===

* Setup "live.why2025.org" as an alias for people to easier find the livestreams next time. Right now you needed to go to "streaming.media.ccc.de/why2025".
* IRC is less popular in new generations of hackers and at least Mastodon+Matrix integrations would have made Signal angel role useful.
* Would like a clear messaging channel from Orga/teams to visitors. live.why2025.org would be good. Better than signal. But have no idea what tool to use.

=== Terrain ===

* Noise gradient should be evaluated better: the main party stage was more audible from the family village than from the Belgian cluster, which was way closer.
* Fridge container orientation: the compressor should point away from campers, it was the single most noisy item from Batavus On tour village point of view.
* Infodesk not located at the entrance like at MCH, causing it to be less visible.
* 4000 people but only a single "Hardware Hacking Tent". It was constantly full, and no other places to sit and solder.
** Plenty villages that'll happily let you use their spaces. It makes sense for this kind of thing to be community-provided (the Hardware Hacking Tent was too - while a official workshop spot, it only exists because of of the HHA team willing to equip and run it)
* "Hackcenter" only had space for 20 people, tiny tent, zero cooling, and no advertisement. Not even a sign... We thought it was someone's Village until day 4.
* No place to party/music all night. It would be cool to have a distant (from tents) area where we're allowed to have music going all night long.
** -1, loud music anywhere on the field travels far and I appreciate being able to sleep. I liked the 23:00 cutoff.
** -1 agreed. "distant" location is not really possible on-site
** +1 AGREE, the noise cutoff was really annoying, other events the music continues until 2am atleast, I don't see why we can't have somewhere on site where we can play music at a reasonable volume. 23:00 is too early for a festival.
** +1, made the event substancially worse, if we have color-coded fields to match volume levels why do we still have to shut the music down completely at 23:00 in the red area?
** -1, i was very happy to have a camp where i could sleep without earplugs. Also it would be impossible due to very strict permits this time around.
*** also this was not followed on the last night after closing in which the angel party continued in the main bar until very late???? have some consistency please. it just feels mean otherwise.

* it was nice that noise rules were followed quite well this time (unlike e.g. MCH where main stages switched to silent disco while sponsors kept blaring music into the silent areas)

* I missed routing signs for bikes coming in. Google Maps got me to the wooden bridge which was fenced off, and nobody there to either let me in or give me a hint. I may have let myself in at that fence, because it was very unclear which detour to take. The climb was only moderately scary.
* Seperate smoking and non-smoking fields, designated smoking areas away from event spaces. A blanket ban on smoking and vaping for the entire event is probably not feasible (unfortunately).

=== Tickets / entrance ===
* Putting the desks on the other side might have looked more welcoming, but all was fine for my check-in.
* Camper tickets were not scanned?

=== Villages ===
* Well done! And it was fun to help out villages doing extra luggage shuttles after we were done doing Waste stuff.

=== Volunteering / angels / heaven===

* Food tickets given to volunteers expiring, without any communication of them doing so.

[[File:Angel Waterbottle Comparison WHY vs MCH.jpg|thumb|Angle Waterbottle Comparison WHY vs MCH]]

* Waterbottle had boring text "'''Thanks For Volunteering'''", instead of WHY wordplay like "'''We Hydrate You'''", "'''Why Hydrate Yourself?'''" or "'''Wet Hackers, Yay!'''".
* Clip/Hook on the waterbootle was 3x smaller, making it unwieldy and difficult to connect. The MCH hook was bigger and easier to quick-connect.
* Drinking part had leak problems, which was not present on the previous bottle.
* The clip caused burn/melt-damage on the waterbottle, as can be seen when zooming in where the clip touches the orange waterbottle.
* No mate during buildup.
* No safe food, or unclear about the contents.
* Severe food safety issues in heaven. Bread toppings (including cheese and meat!) left open on a table outside of a fridge for hours, even overnight, with insects roaming around. No proper cleaning agents or supplies available for cleaning surfaces like tables, only some random supermarket cleaning sprays (this is not good enough for a central eating area!).
* Vegan food availability was unclear and could not be relied on. At times, the "vegan options" were completely inadequate for actually keeping people fed while doing potentially physically intensive volunteer work, with lacking nutritional value. Problem persisted during teardown. "We can't predict what the caterer will deliver" is not good enough for people with dietary restrictions.
* Heaven was too loud. It was almost impossible to communicate with people at the angel desk when there was a meal going on, and you had to practically yell to hear each other. Ideally sound dampening would be installed, but at least the eating area should be separated/insulated from the heaven desk and standby angel area in some way.
* Loved the DasBrot
* Didn't love the utter lack of social hygene during breakfast, lunch and dinner. The proper tools were lacking. Get a cooling gastronorm tray thing for all your meats and cheeses, get the (wasteful) small cups of smears. And have people service it. Dinner handout got fixed with angels doing plating, but was still very haphazard on several days.
* You need more people on the team. You worked your butts off and did not get to enjoy camp enough. I wish better for you all.
* Also get teardown safety vests (or use generic ones for buildup and give a cool one to those tearing down).

=== Warehouse ===
* When Boels screwed up, warehouse delivered us a replacement the same day.
- what did boels screw up?
* I appreciate being able to discuss the underlying requirements instead of automatically being handed a solution. When I asked for a bunch of extension cords, it turned out there was a better solution.
* Delivery service made camp a lot better for me as teamlead. I fixed several problems with one phone call and a happy angel heading out on a bike or gator!
* Purchase generic safety vests for use during shifts. All safety vests with branding were taken by people having done buildup.

=== Waste / garbage collection ===

* I have no knowledge about the state of recycling in NL, but having only separate bins for glass and then ones for everything else felt quite bad. At least separation of paper/carton would have made sense I guess. Also having separate containers where people could "donate" plastic bottles / metal cans which have deposit would have made sense and also could have brought a nice sum of money for the event.
-> The rules for plastic and metal recycling vary per local municipality, let alone per country. So we decided to not do a plastic/metal sorting bin as it would probably only cause headaches.
-> Paper and food remains were collected seperately at heaven, foodcourt. Agree on extending that to villages.
-> Pfand was handled by team bar. Full agree. We saved a trailer full of big bags of bottles and cans.

* Field was nice and clean until teardown with enough containers to get rid of waste. (+1 for adding at least a paper and deposit container)
* The bins near the villages I was at were always emptied before overflowing, which was nice. On teardown day I saw a big pile of bottles around one of the bins: can't say if glass or deposit ones. Generally the field seemed rather clean.
-> See above, glass deposit should have been collected. Unclear why it wasn't.

=== Teardown ===

* "No cars on the gras" policy: Villages that respected the rule of not driving on the grass were effectively disadvantaged. On Wednesday, many cars ignored the rule and drove onto the grass, which meant those villages didn’t have to carry their equipment over long distances. Meanwhile, villages that followed the rule had to transport their gear much farther, which was exhausting given the hot weather. Suggestion: Instead of creating a situation where following the rules feels like a disadvantage, we could reward compliance. For example, check which villages adhere to the rule, and if they do, give them vouchers for a priority ticket queue for the next event.
* Toilets were shut down too early making getting water during the warm teardown harder
* Transporting crates with empty bottles in hand trucks is also very unsafe. If they fall over it would be a mess for barefooted people. Bringing them in and out with cars is much safer.
* Way too many people left a day early. That was a bit sad. For everyone reading this: stay the entire camp ;)
* We should communicate better that flags and other deco is there for the event and should not disappear during the event. Previous events and other events by other parties may have 'trained' our visitors to think they are helping out by removing such decoration early. It was a bit sad to see people rip things of the waste gator. They got told off. But the flags on the main road disappeared on day 2 of camp, and that was entirely unwarranted.
* Remove toilet accessories (paper/soap/brushes) beofore toilets are removed, otherwise they get dumped out on the field.
* Remove zipties of the main tents before tearing the tents down, the tent guys just cut them and leave them on the field.
* Not enough hi-vis vests available, which is especially unsafe when heavy machinery is roaming the site.
* There didn't seem to be any documentation of the teardown procedure for angels, which made it difficult to plan things like food and sleep.

Feedback

2025-08-18T09:23:22Z

Bas: /* Volunteering / angels / heaven */

'''What Hackers Yearn''' for is to '''Improve'''. This page is dedicated to collecting user feedback related to the execution of WHY2025 as a whole. Constructive feedback is invaluable to the continuous improvement of the project and is welcomed from all participants. Please share your observations and suggestions in a '''clear and respectful manner'''. Your input will help guide enhancements for future generations of the event.

It is also possible to send feedback to [http://mailto:2029@why2025.org 2029@why2025.org]

== IMPORTANT ==

Do '''NOT''' review '''people'''. Any individual interaction you had with a human does not belong here, but should be taken up with [[Team:Cohesion]].

This page is strictly for addressing improvements for the next event. We encourage contributors to maintain a neutral, factual, and calm tone in their feedback.

* GOOD EXAMPLES: "Excessive mud at showers", "Food vendors often refused to accept WHY-voucher", or "Limited drop-off points for luggage shuttle".

* BAD EXAMPLES: "Person XXX was insulting me", "Helpdesk XOC was too busy to help", "frickin hot", "So the story begins on Saturday night at 23:04 when..."

== Feedback List ==

=== General / overall ===

* There should be a clear single method/channel of communication from orga, using the Heaven signal chat or social media for this is not ideal
** +1

=== Arrival / departure / parking / train shuttle / luggage shuttle ===

* On day 0 we queued to drive onto the field. We said said we had stuff for two different villages at opposite ends of the site, named the villages and showed them on map print outs. This information was accepted by a dispatcher. However, the bicycle guide refused to guide us to the second location, claiming it was impossible to get there. This is somewhat surprising, since others had been able to drive to that location before. It seemed there was a informational mismatch between dispatch and bicyle guide. (Both locations were accessible by asphalt roads.)
* train shuttle worked well, good job!

=== Badge ===

* Badge handouts were announced right before they happened which didn't allow people to plan their angel shifts and disrupted talks / workshops. A virtual queue would have fixed this and required less total manhours to organize / manage. +1

* There was an expectation that the badge was and I quote from what I have overheard "included in the price". This is not the case and has never been the case but it’s not clearly communicated. To my understanding there was a surplus at SHA2017 and MCH2022 so there never was a shortage of badges before which may have contributed.
** The above is misinformation: It was in fact communicated in written form that every attendee with a ticket receives a badge. The badge could not be ordered separately and was included in the ticket price.

* During the event (AFAIK) there were no badge angel shifts outside of queue angel. This is a chance from prior events and didn't allow people who normally would have helped to help in the same way.

* Due to the badges not being self-powered nor being distributed at the entrance they failed to function as badges. The SHA2017 badge was designed with having no power yet still being a nametag in mind. The WHY2025 badge did not seem to function as a nametag which should have been its intended design goal.

* At MCH and SHA you had people using the badges at the event itself to make games / hack / learn / teach. It was something which brought people together. There was very little being done / to do with the badge during the camp, not just because of the late arrival and limited distribution but rather because there is no way to get apps on the badge outside of the SD card... or if there is a way of doing so then its not documented on the wiki page as of writing. There was no app store app, no way to use the LORA hardware, and outside the event its impossible to use the badge without reflashing a new wifi SSID.

* You could not sit at the badge tent and solder on your antenna onto the badge or work on projects. At SHA and MCH you could just approach the badge people / angels and even get help with projects.

* Badge still has way too limited documentation to even work on it after the event.

* Team Badge have overworked themselves to get a badge available. Team over Badge next time. Which is also a Team:Cohesion issue.

* Would have been great to have a separate queue for villages that collected tickets and pick up 15+ badges at the same time. This would also have greatly reduced waiting times for individuals picking up badges and sped-up the whole process.

* Not enough badges for all visitors (not even close apparently).

* Badge queues were very long and poorly managed. This made it impossible for some people to collected a badge (for example because they cannot stand that long, require shade, have to take care of children, need to go to their next angel shift, etc.)

* The communication about the badge status was very sparse and lacking. If there is a problem, '''communicate''' about it and tell participants what to expect.

** +1. I am sympathetic to the team scrambling to get stuff done under difficult constraints, but especially in such cases good communication is important. Things like randomly posting a link to a page about the keyboard hardware felt frustrating when we were just waiting for more info about future handouts. In addition, a Signal group was a poor choice of channel for announcements for many reasons - no public access, no history for new joiners, redundant join/leave messages, etc. Keeping updates to a section on the wiki and/or a mailing list would've worked much better.

* During build-up, almost all other teams were scrambling to find a pair of hands to get essential stuff done, while watching lots of people pouring epoxy in the badge tent. Which was, lemme me blunt here, one of the lowest priority of all the things that have been done during build-up.

=== Bars and food court ===

* Menu was much longer and more complex compared to MCH. A lot of items were almost never sold, like nachos and chips.
* Slight differences in the menu between the bars caused customers to ask "Do you have ...?". Also complicates restocking logistics.
* The amount of Rum in the "Tschunk" was '''halved''' without updating the price. They decided it was better to modify the recipe to make it almost non-alcoholic, rather than say "Sorry, we're out."
** +1, the Tschunk contained barely any Rum.
* Bar is not a Merch Store, "Special/Ceremonial Cup" should be sold in Infodesk. It was also badly advertised, only people who "knew" of its existence could buy it. +1
* How was the cup not a deposit... I didn't even realize you wouldn't get any money back. Made it extremely bothersome to buy drinks for other people. +1
* Why wasn't statiegeld/pfand collected? Many glass bins full of mate-bottles. I don't want to know how many plastic bottles and aluminium cans were thrown out. This could have been prevented.
* No Club Mate Beere?
* No normal (0.5L) bottles available on the last day?
* Do we get mate from the source, or a Dutch overprices company?
* No mate during buildup again?
* Not written instructions for angels. The “game of telephone” style handing of incorrect instructions down from one angel to the next caused food to be prepared incorrectly. Written instructions should be posted right at the frier and microwave.
** +1
* Handling of vegan food was bad. Burger stall incorrectly advertised vegetarian burger as "vegan" originally, and could not provide any vegan burger at all because the buns contained milk(!). Fries/snacks stall staff did not know what they were selling or what it contained, and communication was difficult. Only positive note goes to the pasta stall where the food was good, and the operator was highly competent and knew exactly what they were selling (I would like to see them at a next event).
* Bottle collection procedure was very unclear.
* To add to the above: between bar and foodcourt no crates in sight on several days. No crates at any of the waste collection points. No instructions or procedure arranged. So people grabbed the glass-waste bin from the showers and put it in the middle. End result: 24x 240L glass trash bin completely filled to the brim. Assuming roughly around 5000 pfand-bottles (Mate, beer etc) were trashed. And team Waste had a ton of heavy lifting to get all these bins off the field and back to the recycling company. This could have been prevented.
* The same with plastic bottles and cans. Team Waste managed to save a *trailer* full of cans and bottles. About 24 big bags (240L). That could easily have been double. And if people actually organized it, it would have been less work.

=== Cohesion ===
* I like the idea, but not the implementation: Geraffel was put at the arse end of the field (OK fine, epicenter of noise gradient and all that), then got told off for playing music during the day.
* Very little communication/information. People barely knew the team existed and could be contacted, social rules like the Photo Policy were not communicated and very widely ignored. Other events signpost these things all over the site and it does help

=== Content / talks / heralds / speakerdesk / AV / recordings ===

* Party Stage was the perfect location for the "History of Hardcore" talk. More 'serious' talks could be held on the music stages at events going forward.

=== CTF / token game ===

=== Decoration / design ===

* Team did an amazing job. The field felt welcoming and interesting. Thank you so much for all the effort that went in. +1
* Next time we need to find a sponsor to print flags for all visitors, and have it available as merch for purchase. It was sad to see so much deco being liberated too early in the event. We need to also work on the communication around this.

=== Family / kids ===

=== Finance / coins / payments ===

* Like the concept of an anonymous payment card that '''just works'''. Absolutely love the design of the WHY2025 card. And very happy to play with a blank Ultralight AES card afterwards.
** +1, this was set up well! My only feedback would be to maybe have something that you can tap your card against to see the remaining balance (or otherwise instruct angels to communicate the balance upon payment)
* option for payout of remaining funds wasn't communicated properly (even the website claimed it wasn't possible at all). Cash payout would be nice, but would understandably be a big extra thing to manage

=== Information / infodesk / wiki ===

* The wiki seems to have never been updated after the event started. I have attempted to find information about something several times and ''none'' of those times was it on the wiki. Instead everything seemed to be in random Signal groups and wherever else, that I didn't even know about until much later.
* It was very hard to find information on anything (like infrastructure, badge handouts, etc.) in general, and even infodesk angels often didn't have the answers.

=== Merchandise ===
* It would have been nice if the merch that was ordered months ago would have actually been available at the field.
* Flags as preordered merchandise. Would create the possibility for hackerspaces and individuals to bring back home some of them. +2

=== NOC / Network ===
* From buildup, through the event, through teardown: the networks worked!
* It was a pleasure to work together, to deduplicate work and equipment.
* In our location, Wifi coverage was poor although we were next to a Datenklo

=== NUTS / power / water ===

* Showers with adjustable heat (showerheads which mix cold and hot water) to avoid burns.
* Wood pallets outside both showers and toilets to reduce mud. (+1, from day zero would have been helpful)
* Even if not in all bathroom points, more drinking water points other than the one in heaven should have been available from the beginning. +1
* Disable the watertaps at the same time as all the other bathroom facilities. Or communicate when the water is going out. Now villages were only able to fill small containers at the toilets. Or needed to walk all the way to Heaven.
* Slightly more cleaning would have been great. The showers were extremely full of mud even inside at times. Given they only used a hose as far as I saw, should have been possible to also have some angels do this in addition to the cleaning crew.
* Adding hooks to the showers was a very welcome addition, thanks!
* It wasn't clear where to get drinking water during the first few days. This should be communicated better, e.g. with signs and on the map. +1
* I liked the number of toilets: never had to wait +1
* furthermore, the toilets seemed to be cleaned often which is good. +1
* There always was toilet paper available in the stalls, greatly lessens anxiety. +1
* water pressure and temperature in the showers was great! Also: never had to wait, which is great! +1
* There always was plenty of soap available at the sinks, during peak time and at night. +1
* Dedicated dishwashing location. +1
* More drinking water fountains across the terrain
* "upgrading" facilities to "drinking water" is questionable. What of all the potential risks was actually tested and could be guaranteed? Separate 100% clear drinking water spots would be better -1
* Shower temperature constantly fluctuated and never stabilized

=== Off-site logistics ===

=== On-site logistics ===

=== POC / DECT / Fieldphones ===
* micropoc worked just fine: I could easily and quickly register the DECT phones for my village and the network worked whenever I wanted to use it.
* Having the DECT so people can reach my team was as always: amazing. Thank you. Feature request: have a phone number only operational during business hours (and redirect to a prerecorded thing other times). Fixed that ourselves by switching the dect to silent. But would be a cool feature.

=== Productiehuis / C3VOC ===

=== Projectleiding ===

=== ROC ===
* Very clear audio and reception
* Was very happy with radio when the relay was up. During the end of teardown the signal degraded to unintelligible gibberish when going across field.
* Next time, don't do a split service desk in warehouse/ROC.

=== Safety / security / first aid / fire ===

=== Supermarket ===
* Happy friendly people who had the correct stuff on the shelves
* Pricing was for a campsite supermarket 'okay'. Having stuff available on field makes up for a lot.
* Would have loved to be able to purchase anything after 8PM, but i understand that they also need to sleep ;)
* Very resilient, apparently; throughout just about every logistical and infrastructure problem at camp, they seemed to keep operating.
* Would have liked to see tofu in the assortment; a few vegan proteins were available but none were quite as versatile.

=== Sysadmin ===

* Setup "live.why2025.org" as an alias for people to easier find the livestreams next time. Right now you needed to go to "streaming.media.ccc.de/why2025".
* IRC is less popular in new generations of hackers and at least Mastodon+Matrix integrations would have made Signal angel role useful.
* Would like a clear messaging channel from Orga/teams to visitors. live.why2025.org would be good. Better than signal. But have no idea what tool to use.

=== Terrain ===

* Noise gradient should be evaluated better: the main party stage was more audible from the family village than from the Belgian cluster, which was way closer.
* Fridge container orientation: the compressor should point away from campers, it was the single most noisy item from Batavus On tour village point of view.
* Infodesk not located at the entrance like at MCH, causing it to be less visible.
* 4000 people but only a single "Hardware Hacking Tent". It was constantly full, and no other places to sit and solder.
** Plenty villages that'll happily let you use their spaces. It makes sense for this kind of thing to be community-provided (the Hardware Hacking Tent was too - while a official workshop spot, it only exists because of of the HHA team willing to equip and run it)
* "Hackcenter" only had space for 20 people, tiny tent, zero cooling, and no advertisement. Not even a sign... We thought it was someone's Village until day 4.
* No place to party/music all night. It would be cool to have a distant (from tents) area where we're allowed to have music going all night long.
** -1, loud music anywhere on the field travels far and I appreciate being able to sleep. I liked the 23:00 cutoff.
** -1 agreed. "distant" location is not really possible on-site
** +1 AGREE, the noise cutoff was really annoying, other events the music continues until 2am atleast, I don't see why we can't have somewhere on site where we can play music at a reasonable volume. 23:00 is too early for a festival.
** +1, made the event substancially worse, if we have color-coded fields to match volume levels why do we still have to shut the music down completely at 23:00 in the red area?
** -1, i was very happy to have a camp where i could sleep without earplugs. Also it would be impossible due to very strict permits this time around.
*** also this was not followed on the last night after closing in which the angel party continued in the main bar until very late???? have some consistency please. it just feels mean otherwise.

* it was nice that noise rules were followed quite well this time (unlike e.g. MCH where main stages switched to silent disco while sponsors kept blaring music into the silent areas)

* I missed routing signs for bikes coming in. Google Maps got me to the wooden bridge which was fenced off, and nobody there to either let me in or give me a hint. I may have let myself in at that fence, because it was very unclear which detour to take. The climb was only moderately scary.
* Seperate smoking and non-smoking fields, designated smoking areas away from event spaces. A blanket ban on smoking and vaping for the entire event is probably not feasible (unfortunately).

=== Tickets / entrance ===
* Putting the desks on the other side might have looked more welcoming, but all was fine for my check-in.
* Camper tickets were not scanned?

=== Villages ===
* Well done! And it was fun to help out villages doing extra luggage shuttles after we were done doing Waste stuff.

=== Volunteering / angels / heaven===

* Food tickets given to volunteers expiring, without any communication of them doing so.

[[File:Angel Waterbottle Comparison WHY vs MCH.jpg|thumb|Angle Waterbottle Comparison WHY vs MCH]]

* Waterbottle had boring text "'''Thanks For Volunteering'''", instead of WHY wordplay like "'''We Hydrate You'''", "'''Why Hydrate Yourself?'''" or "'''Wet Hackers, Yay!'''".
* Clip/Hook on the waterbootle was 3x smaller, making it unwieldy and difficult to connect. The MCH hook was bigger and easier to quick-connect.
* Drinking part had leak problems, which was not present on the previous bottle.
* The clip caused burn/melt-damage on the waterbottle, as can be seen when zooming in where the clip touches the orange waterbottle.
* No mate during buildup.
* No safe food, or unclear about the contents.
* Severe food safety issues in heaven. Bread toppings (including cheese and meat!) left open on a table outside of a fridge for hours, even overnight, with insects roaming around. No proper cleaning agents or supplies available for cleaning surfaces like tables, only some random supermarket cleaning sprays (this is not good enough for a central eating area!).
* Vegan food availability was unclear and could not be relied on. At times, the "vegan options" were completely inadequate for actually keeping people fed while doing potentially physically intensive volunteer work, with lacking nutritional value. Problem persisted during teardown. "We can't predict what the caterer will deliver" is not good enough for people with dietary restrictions.
* Heaven was too loud. It was almost impossible to communicate with people at the angel desk when there was a meal going on, and you had to practically yell to hear each other. Ideally sound dampening would be installed, but at least the eating area should be separated/insulated from the heaven desk and standby angel area in some way.
* Loved the DasBrot
* Didn't love the utter lack of social hygene during breakfast, lunch and dinner. The proper tools were lacking. Get a cooling gastronorm tray thing for all your meats and cheeses, get the (wasteful) small cups of smears. And have people service it. Dinner handout got fixed with angels doing plating, but was still very haphazard on several days.
* You need more people on the team. You worked your butts off and did not get to enjoy camp enough. I wish better for you all.
* Also get teardown safety vests (or use generic ones for buildup and give a cool one to those tearing down).

=== Warehouse ===
* When Boels screwed up, warehouse delivered us a replacement the same day.
- what did boels screw up?
* I appreciate being able to discuss the underlying requirements instead of automatically being handed a solution. When I asked for a bunch of extension cords, it turned out there was a better solution.
* Delivery service made camp a lot better for me as teamlead. I fixed several problems with one phone call and a happy angel heading out on a bike or gator!
* Purchase generic safety vests for use during shifts. All safety vests with branding were taken by people having done buildup.

=== Waste / garbage collection ===

* I have no knowledge about the state of recycling in NL, but having only separate bins for glass and then ones for everything else felt quite bad. At least separation of paper/carton would have made sense I guess. Also having separate containers where people could "donate" plastic bottles / metal cans which have deposit would have made sense and also could have brought a nice sum of money for the event.
* Field was nice and clean until teardown with enough containers to get rid of waste. (+1 for adding at least a paper and deposit container)
* The bins near the villages I was at were always emptied before overflowing, which was nice.
* on teardown day I saw a big pile of bottles around one of the bins: can't say if glass or deposit ones
* generally the field seemed rather clean

=== Teardown ===

* "No cars on the gras" policy: Villages that respected the rule of not driving on the grass were effectively disadvantaged. On Wednesday, many cars ignored the rule and drove onto the grass, which meant those villages didn’t have to carry their equipment over long distances. Meanwhile, villages that followed the rule had to transport their gear much farther, which was exhausting given the hot weather. Suggestion: Instead of creating a situation where following the rules feels like a disadvantage, we could reward compliance. For example, check which villages adhere to the rule, and if they do, give them vouchers for a priority ticket queue for the next event.
* Toilets were shut down too early making getting water during the warm teardown harder
* Transporting crates with empty bottles in hand trucks is also very unsafe. If they fall over it would be a mess for barefooted people. Bringing them in and out with cars is much safer.
* Way too many people left a day early. That was a bit sad. For everyone reading this: stay the entire camp ;)
* We should communicate better that flags and other deco is there for the event and should not disappear during the event. Previous events and other events by other parties may have 'trained' our visitors to think they are helping out by removing such decoration early. It was a bit sad to see people rip things of the waste gator. They got told off. But the flags on the main road disappeared on day 2 of camp, and that was entirely unwarranted.
* Remove toilet accessories (paper/soap/brushes) beofore toilets are removed, otherwise they get dumped out on the field.
* Remove zipties of the main tents before tearing the tents down, the tent guys just cut them and leave them on the field.
* Not enough hi-vis vests available, which is especially unsafe when heavy machinery is roaming the site.
* There didn't seem to be any documentation of the teardown procedure for angels, which made it difficult to plan things like food and sleep.

Feedback

2025-08-18T09:18:46Z

Bas: /* Warehouse */

'''What Hackers Yearn''' for is to '''Improve'''. This page is dedicated to collecting user feedback related to the execution of WHY2025 as a whole. Constructive feedback is invaluable to the continuous improvement of the project and is welcomed from all participants. Please share your observations and suggestions in a '''clear and respectful manner'''. Your input will help guide enhancements for future generations of the event.

It is also possible to send feedback to [http://mailto:2029@why2025.org 2029@why2025.org]

== IMPORTANT ==

Do '''NOT''' review '''people'''. Any individual interaction you had with a human does not belong here, but should be taken up with [[Team:Cohesion]].

This page is strictly for addressing improvements for the next event. We encourage contributors to maintain a neutral, factual, and calm tone in their feedback.

* GOOD EXAMPLES: "Excessive mud at showers", "Food vendors often refused to accept WHY-voucher", or "Limited drop-off points for luggage shuttle".

* BAD EXAMPLES: "Person XXX was insulting me", "Helpdesk XOC was too busy to help", "frickin hot", "So the story begins on Saturday night at 23:04 when..."

== Feedback List ==

=== General / overall ===

* There should be a clear single method/channel of communication from orga, using the Heaven signal chat or social media for this is not ideal
** +1

=== Arrival / departure / parking / train shuttle / luggage shuttle ===

* On day 0 we queued to drive onto the field. We said said we had stuff for two different villages at opposite ends of the site, named the villages and showed them on map print outs. This information was accepted by a dispatcher. However, the bicycle guide refused to guide us to the second location, claiming it was impossible to get there. This is somewhat surprising, since others had been able to drive to that location before. It seemed there was a informational mismatch between dispatch and bicyle guide. (Both locations were accessible by asphalt roads.)
* train shuttle worked well, good job!

=== Badge ===

* Badge handouts were announced right before they happened which didn't allow people to plan their angel shifts and disrupted talks / workshops. A virtual queue would have fixed this and required less total manhours to organize / manage. +1

* There was an expectation that the badge was and I quote from what I have overheard "included in the price". This is not the case and has never been the case but it’s not clearly communicated. To my understanding there was a surplus at SHA2017 and MCH2022 so there never was a shortage of badges before which may have contributed.
** The above is misinformation: It was in fact communicated in written form that every attendee with a ticket receives a badge. The badge could not be ordered separately and was included in the ticket price.

* During the event (AFAIK) there were no badge angel shifts outside of queue angel. This is a chance from prior events and didn't allow people who normally would have helped to help in the same way.

* Due to the badges not being self-powered nor being distributed at the entrance they failed to function as badges. The SHA2017 badge was designed with having no power yet still being a nametag in mind. The WHY2025 badge did not seem to function as a nametag which should have been its intended design goal.

* At MCH and SHA you had people using the badges at the event itself to make games / hack / learn / teach. It was something which brought people together. There was very little being done / to do with the badge during the camp, not just because of the late arrival and limited distribution but rather because there is no way to get apps on the badge outside of the SD card... or if there is a way of doing so then its not documented on the wiki page as of writing. There was no app store app, no way to use the LORA hardware, and outside the event its impossible to use the badge without reflashing a new wifi SSID.

* You could not sit at the badge tent and solder on your antenna onto the badge or work on projects. At SHA and MCH you could just approach the badge people / angels and even get help with projects.

* Badge still has way too limited documentation to even work on it after the event.

* Team Badge have overworked themselves to get a badge available. Team over Badge next time. Which is also a Team:Cohesion issue.

* Would have been great to have a separate queue for villages that collected tickets and pick up 15+ badges at the same time. This would also have greatly reduced waiting times for individuals picking up badges and sped-up the whole process.

* Not enough badges for all visitors (not even close apparently).

* Badge queues were very long and poorly managed. This made it impossible for some people to collected a badge (for example because they cannot stand that long, require shade, have to take care of children, need to go to their next angel shift, etc.)

* The communication about the badge status was very sparse and lacking. If there is a problem, '''communicate''' about it and tell participants what to expect.

** +1. I am sympathetic to the team scrambling to get stuff done under difficult constraints, but especially in such cases good communication is important. Things like randomly posting a link to a page about the keyboard hardware felt frustrating when we were just waiting for more info about future handouts. In addition, a Signal group was a poor choice of channel for announcements for many reasons - no public access, no history for new joiners, redundant join/leave messages, etc. Keeping updates to a section on the wiki and/or a mailing list would've worked much better.

* During build-up, almost all other teams were scrambling to find a pair of hands to get essential stuff done, while watching lots of people pouring epoxy in the badge tent. Which was, lemme me blunt here, one of the lowest priority of all the things that have been done during build-up.

=== Bars and food court ===

* Menu was much longer and more complex compared to MCH. A lot of items were almost never sold, like nachos and chips.
* Slight differences in the menu between the bars caused customers to ask "Do you have ...?". Also complicates restocking logistics.
* The amount of Rum in the "Tschunk" was '''halved''' without updating the price. They decided it was better to modify the recipe to make it almost non-alcoholic, rather than say "Sorry, we're out."
** +1, the Tschunk contained barely any Rum.
* Bar is not a Merch Store, "Special/Ceremonial Cup" should be sold in Infodesk. It was also badly advertised, only people who "knew" of its existence could buy it. +1
* How was the cup not a deposit... I didn't even realize you wouldn't get any money back. Made it extremely bothersome to buy drinks for other people. +1
* Why wasn't statiegeld/pfand collected? Many glass bins full of mate-bottles. I don't want to know how many plastic bottles and aluminium cans were thrown out. This could have been prevented.
* No Club Mate Beere?
* No normal (0.5L) bottles available on the last day?
* Do we get mate from the source, or a Dutch overprices company?
* No mate during buildup again?
* Not written instructions for angels. The “game of telephone” style handing of incorrect instructions down from one angel to the next caused food to be prepared incorrectly. Written instructions should be posted right at the frier and microwave.
** +1
* Handling of vegan food was bad. Burger stall incorrectly advertised vegetarian burger as "vegan" originally, and could not provide any vegan burger at all because the buns contained milk(!). Fries/snacks stall staff did not know what they were selling or what it contained, and communication was difficult. Only positive note goes to the pasta stall where the food was good, and the operator was highly competent and knew exactly what they were selling (I would like to see them at a next event).
* Bottle collection procedure was very unclear.
* To add to the above: between bar and foodcourt no crates in sight on several days. No crates at any of the waste collection points. No instructions or procedure arranged. So people grabbed the glass-waste bin from the showers and put it in the middle. End result: 24x 240L glass trash bin completely filled to the brim. Assuming roughly around 5000 pfand-bottles (Mate, beer etc) were trashed. And team Waste had a ton of heavy lifting to get all these bins off the field and back to the recycling company. This could have been prevented.
* The same with plastic bottles and cans. Team Waste managed to save a *trailer* full of cans and bottles. About 24 big bags (240L). That could easily have been double. And if people actually organized it, it would have been less work.

=== Cohesion ===
* I like the idea, but not the implementation: Geraffel was put at the arse end of the field (OK fine, epicenter of noise gradient and all that), then got told off for playing music during the day.
* Very little communication/information. People barely knew the team existed and could be contacted, social rules like the Photo Policy were not communicated and very widely ignored. Other events signpost these things all over the site and it does help

=== Content / talks / heralds / speakerdesk / AV / recordings ===

* Party Stage was the perfect location for the "History of Hardcore" talk. More 'serious' talks could be held on the music stages at events going forward.

=== CTF / token game ===

=== Decoration / design ===

* Team did an amazing job. The field felt welcoming and interesting. Thank you so much for all the effort that went in. +1
* Next time we need to find a sponsor to print flags for all visitors, and have it available as merch for purchase. It was sad to see so much deco being liberated too early in the event. We need to also work on the communication around this.

=== Family / kids ===

=== Finance / coins / payments ===

* Like the concept of an anonymous payment card that '''just works'''. Absolutely love the design of the WHY2025 card. And very happy to play with a blank Ultralight AES card afterwards.
* option for payout of remaining funds wasn't communicated properly (even the website claimed it wasn't possible at all). Cash payout would be nice, but would understandably be a big extra thing to manage

=== Information / infodesk / wiki ===

* The wiki seems to have never been updated after the event started. I have attempted to find information about something several times and ''none'' of those times was it on the wiki. Instead everything seemed to be in random Signal groups and wherever else, that I didn't even know about until much later.
* It was very hard to find information on anything (like infrastructure, badge handouts, etc.) in general, and even infodesk angels often didn't have the answers.

=== Merchandise ===
* It would have been nice if the merch that was ordered months ago would have actually been available at the field.
* Flags as preordered merchandise. Would create the possibility for hackerspaces and individuals to bring back home some of them. +2

=== NOC / Network ===
* From buildup, through the event, through teardown: the networks worked!
* It was a pleasure to work together, to deduplicate work and equipment.
* In our location, Wifi coverage was poor although we were next to a Datenklo

=== NUTS / power / water ===

* Showers with adjustable heat (showerheads which mix cold and hot water) to avoid burns.
* Wood pallets outside both showers and toilets to reduce mud. (+1, from day zero would have been helpful)
* Even if not in all bathroom points, more drinking water points other than the one in heaven should have been available from the beginning. +1
* Disable the watertaps at the same time as all the other bathroom facilities. Or communicate when the water is going out. Now villages were only able to fill small containers at the toilets. Or needed to walk all the way to Heaven.
* Slightly more cleaning would have been great. The showers were extremely full of mud even inside at times. Given they only used a hose as far as I saw, should have been possible to also have some angels do this in addition to the cleaning crew.
* Adding hooks to the showers was a very welcome addition, thanks!
* It wasn't clear where to get drinking water during the first few days. This should be communicated better, e.g. with signs and on the map. +1
* I liked the number of toilets: never had to wait +1
* furthermore, the toilets seemed to be cleaned often which is good. +1
* There always was toilet paper available in the stalls, greatly lessens anxiety. +1
* water pressure and temperature in the showers was great! Also: never had to wait, which is great! +1
* There always was plenty of soap available at the sinks, during peak time and at night. +1
* Dedicated dishwashing location. +1
* More drinking water fountains across the terrain
* "upgrading" facilities to "drinking water" is questionable. What of all the potential risks was actually tested and could be guaranteed? Separate 100% clear drinking water spots would be better -1
* Shower temperature constantly fluctuated and never stabilized

=== Off-site logistics ===

=== On-site logistics ===

=== POC / DECT / Fieldphones ===
* micropoc worked just fine: I could easily and quickly register the DECT phones for my village and the network worked whenever I wanted to use it.
* Having the DECT so people can reach my team was as always: amazing. Thank you. Feature request: have a phone number only operational during business hours (and redirect to a prerecorded thing other times). Fixed that ourselves by switching the dect to silent. But would be a cool feature.

=== Productiehuis / C3VOC ===

=== Projectleiding ===

=== ROC ===
* Very clear audio and reception
* Was very happy with radio when the relay was up. During the end of teardown the signal degraded to unintelligible gibberish when going across field.
* Next time, don't do a split service desk in warehouse/ROC.

=== Safety / security / first aid / fire ===

=== Supermarket ===
* Happy friendly people who had the correct stuff on the shelves
* Pricing was for a campsite supermarket 'okay'. Having stuff available on field makes up for a lot.
* Would have loved to be able to purchase anything after 8PM, but i understand that they also need to sleep ;)
* Very resilient, apparently; throughout just about every logistical and infrastructure problem at camp, they seemed to keep operating.
* Would have liked to see tofu in the assortment; a few vegan proteins were available but none were quite as versatile.

=== Sysadmin ===

* Setup "live.why2025.org" as an alias for people to easier find the livestreams next time. Right now you needed to go to "streaming.media.ccc.de/why2025".
* IRC is less popular in new generations of hackers and at least Mastodon+Matrix integrations would have made Signal angel role useful.
* Would like a clear messaging channel from Orga/teams to visitors. live.why2025.org would be good. Better than signal. But have no idea what tool to use.

=== Terrain ===

* Noise gradient should be evaluated better: the main party stage was more audible from the family village than from the Belgian cluster, which was way closer.
* Fridge container orientation: the compressor should point away from campers, it was the single most noisy item from Batavus On tour village point of view.
* Infodesk not located at the entrance like at MCH, causing it to be less visible.
* 4000 people but only a single "Hardware Hacking Tent". It was constantly full, and no other places to sit and solder.
** Plenty villages that'll happily let you use their spaces. It makes sense for this kind of thing to be community-provided (the Hardware Hacking Tent was too - while a official workshop spot, it only exists because of of the HHA team willing to equip and run it)
* "Hackcenter" only had space for 20 people, tiny tent, zero cooling, and no advertisement. Not even a sign... We thought it was someone's Village until day 4.
* No place to party/music all night. It would be cool to have a distant (from tents) area where we're allowed to have music going all night long.
** -1, loud music anywhere on the field travels far and I appreciate being able to sleep. I liked the 23:00 cutoff.
** -1 agreed. "distant" location is not really possible on-site
** +1 AGREE, the noise cutoff was really annoying, other events the music continues until 2am atleast, I don't see why we can't have somewhere on site where we can play music at a reasonable volume. 23:00 is too early for a festival.
** +1, made the event substancially worse, if we have color-coded fields to match volume levels why do we still have to shut the music down completely at 23:00 in the red area?
** -1, i was very happy to have a camp where i could sleep without earplugs. Also it would be impossible due to very strict permits this time around.
*** also this was not followed on the last night after closing in which the angel party continued in the main bar until very late???? have some consistency please. it just feels mean otherwise.

* it was nice that noise rules were followed quite well this time (unlike e.g. MCH where main stages switched to silent disco while sponsors kept blaring music into the silent areas)

* I missed routing signs for bikes coming in. Google Maps got me to the wooden bridge which was fenced off, and nobody there to either let me in or give me a hint. I may have let myself in at that fence, because it was very unclear which detour to take. The climb was only moderately scary.
* Seperate smoking and non-smoking fields, designated smoking areas away from event spaces. A blanket ban on smoking and vaping for the entire event is probably not feasible (unfortunately).

=== Tickets / entrance ===
* Putting the desks on the other side might have looked more welcoming, but all was fine for my check-in.
* Camper tickets were not scanned?

=== Villages ===
* Well done! And it was fun to help out villages doing extra luggage shuttles after we were done doing Waste stuff.

=== Volunteering / angels / heaven===

* Food tickets given to volunteers expiring, without any communication of them doing so.

[[File:Angel Waterbottle Comparison WHY vs MCH.jpg|thumb|Angle Waterbottle Comparison WHY vs MCH]]

* Waterbottle had boring text "'''Thanks For Volunteering'''", instead of WHY wordplay like "'''We Hydrate You'''", "'''Why Hydrate Yourself?'''" or "'''Wet Hackers, Yay!'''".
* Clip/Hook on the waterbootle was 3x smaller, making it unwieldy and difficult to connect. The MCH hook was bigger and easier to quick-connect.
* Drinking part had leak problems, which was not present on the previous bottle.
* The clip caused burn/melt-damage on the waterbottle, as can be seen when zooming in where the clip touches the orange waterbottle.
* No mate during buildup.
* No safe food, or unclear about the contents.
* Severe food safety issues in heaven. Bread toppings (including cheese and meat!) left open on a table outside of a fridge for hours, even overnight, with insects roaming around. No proper cleaning agents or supplies available for cleaning surfaces like tables, only some random supermarket cleaning sprays (this is not good enough for a central eating area!).
* Vegan food availability was unclear and could not be relied on. At times, the "vegan options" were completely inadequate for actually keeping people fed while doing potentially physically intensive volunteer work, with lacking nutritional value. Problem persisted during teardown. "We can't predict what the caterer will deliver" is not good enough for people with dietary restrictions.
* Heaven was too loud. It was almost impossible to communicate with people at the angel desk when there was a meal going on, and you had to practically yell to hear each other. Ideally sound dampening would be installed, but at least the eating area should be separated/insulated from the heaven desk and standby angel area in some way.

=== Warehouse ===
* When Boels screwed up, warehouse delivered us a replacement the same day.
- what did boels screw up?
* I appreciate being able to discuss the underlying requirements instead of automatically being handed a solution. When I asked for a bunch of extension cords, it turned out there was a better solution.
* Delivery service made camp a lot better for me as teamlead. I fixed several problems with one phone call and a happy angel heading out on a bike or gator!
* Purchase generic safety vests for use during shifts. All safety vests with branding were taken by people having done buildup.

=== Waste / garbage collection ===

* I have no knowledge about the state of recycling in NL, but having only separate bins for glass and then ones for everything else felt quite bad. At least separation of paper/carton would have made sense I guess. Also having separate containers where people could "donate" plastic bottles / metal cans which have deposit would have made sense and also could have brought a nice sum of money for the event.
* Field was nice and clean until teardown with enough containers to get rid of waste. (+1 for adding at least a paper and deposit container)

=== Teardown ===

* "No cars on the gras" policy: Villages that respected the rule of not driving on the grass were effectively disadvantaged. On Wednesday, many cars ignored the rule and drove onto the grass, which meant those villages didn’t have to carry their equipment over long distances. Meanwhile, villages that followed the rule had to transport their gear much farther, which was exhausting given the hot weather. Suggestion: Instead of creating a situation where following the rules feels like a disadvantage, we could reward compliance. For example, check which villages adhere to the rule, and if they do, give them vouchers for a priority ticket queue for the next event.
* Toilets were shut down too early making getting water during the warm teardown harder
* Transporting crates with empty bottles in hand trucks is also very unsafe. If they fall over it would be a mess for barefooted people. Bringing them in and out with cars is much safer.
* Way too many people left a day early. That was a bit sad. For everyone reading this: stay the entire camp ;)
* We should communicate better that flags and other deco is there for the event and should not disappear during the event. Previous events and other events by other parties may have 'trained' our visitors to think they are helping out by removing such decoration early. It was a bit sad to see people rip things of the waste gator. They got told off. But the flags on the main road disappeared on day 2 of camp, and that was entirely unwarranted.
* Remove toilet accessories (paper/soap/brushes) beofore toilets are removed, otherwise they get dumped out on the field.
* Remove zipties of the main tents before tearing the tents down, the tent guys just cut them and leave them on the field.
* Not enough hi-vis vests available, which is especially unsafe when heavy machinery is roaming the site.
* There didn't seem to be any documentation of the teardown procedure for angels, which made it difficult to plan things like food and sleep.

Feedback

2025-08-18T09:17:20Z

Bas: /* Sysadmin */

'''What Hackers Yearn''' for is to '''Improve'''. This page is dedicated to collecting user feedback related to the execution of WHY2025 as a whole. Constructive feedback is invaluable to the continuous improvement of the project and is welcomed from all participants. Please share your observations and suggestions in a '''clear and respectful manner'''. Your input will help guide enhancements for future generations of the event.

It is also possible to send feedback to [http://mailto:2029@why2025.org 2029@why2025.org]

== IMPORTANT ==

Do '''NOT''' review '''people'''. Any individual interaction you had with a human does not belong here, but should be taken up with [[Team:Cohesion]].

This page is strictly for addressing improvements for the next event. We encourage contributors to maintain a neutral, factual, and calm tone in their feedback.

* GOOD EXAMPLES: "Excessive mud at showers", "Food vendors often refused to accept WHY-voucher", or "Limited drop-off points for luggage shuttle".

* BAD EXAMPLES: "Person XXX was insulting me", "Helpdesk XOC was too busy to help", "frickin hot", "So the story begins on Saturday night at 23:04 when..."

== Feedback List ==

=== General / overall ===

* There should be a clear single method/channel of communication from orga, using the Heaven signal chat or social media for this is not ideal
** +1

=== Arrival / departure / parking / train shuttle / luggage shuttle ===

* On day 0 we queued to drive onto the field. We said said we had stuff for two different villages at opposite ends of the site, named the villages and showed them on map print outs. This information was accepted by a dispatcher. However, the bicycle guide refused to guide us to the second location, claiming it was impossible to get there. This is somewhat surprising, since others had been able to drive to that location before. It seemed there was a informational mismatch between dispatch and bicyle guide. (Both locations were accessible by asphalt roads.)
* train shuttle worked well, good job!

=== Badge ===

* Badge handouts were announced right before they happened which didn't allow people to plan their angel shifts and disrupted talks / workshops. A virtual queue would have fixed this and required less total manhours to organize / manage. +1

* There was an expectation that the badge was and I quote from what I have overheard "included in the price". This is not the case and has never been the case but it’s not clearly communicated. To my understanding there was a surplus at SHA2017 and MCH2022 so there never was a shortage of badges before which may have contributed.
** The above is misinformation: It was in fact communicated in written form that every attendee with a ticket receives a badge. The badge could not be ordered separately and was included in the ticket price.

* During the event (AFAIK) there were no badge angel shifts outside of queue angel. This is a chance from prior events and didn't allow people who normally would have helped to help in the same way.

* Due to the badges not being self-powered nor being distributed at the entrance they failed to function as badges. The SHA2017 badge was designed with having no power yet still being a nametag in mind. The WHY2025 badge did not seem to function as a nametag which should have been its intended design goal.

* At MCH and SHA you had people using the badges at the event itself to make games / hack / learn / teach. It was something which brought people together. There was very little being done / to do with the badge during the camp, not just because of the late arrival and limited distribution but rather because there is no way to get apps on the badge outside of the SD card... or if there is a way of doing so then its not documented on the wiki page as of writing. There was no app store app, no way to use the LORA hardware, and outside the event its impossible to use the badge without reflashing a new wifi SSID.

* You could not sit at the badge tent and solder on your antenna onto the badge or work on projects. At SHA and MCH you could just approach the badge people / angels and even get help with projects.

* Badge still has way too limited documentation to even work on it after the event.

* Team Badge have overworked themselves to get a badge available. Team over Badge next time. Which is also a Team:Cohesion issue.

* Would have been great to have a separate queue for villages that collected tickets and pick up 15+ badges at the same time. This would also have greatly reduced waiting times for individuals picking up badges and sped-up the whole process.

* Not enough badges for all visitors (not even close apparently).

* Badge queues were very long and poorly managed. This made it impossible for some people to collected a badge (for example because they cannot stand that long, require shade, have to take care of children, need to go to their next angel shift, etc.)

* The communication about the badge status was very sparse and lacking. If there is a problem, '''communicate''' about it and tell participants what to expect.

** +1. I am sympathetic to the team scrambling to get stuff done under difficult constraints, but especially in such cases good communication is important. Things like randomly posting a link to a page about the keyboard hardware felt frustrating when we were just waiting for more info about future handouts. In addition, a Signal group was a poor choice of channel for announcements for many reasons - no public access, no history for new joiners, redundant join/leave messages, etc. Keeping updates to a section on the wiki and/or a mailing list would've worked much better.

* During build-up, almost all other teams were scrambling to find a pair of hands to get essential stuff done, while watching lots of people pouring epoxy in the badge tent. Which was, lemme me blunt here, one of the lowest priority of all the things that have been done during build-up.

=== Bars and food court ===

* Menu was much longer and more complex compared to MCH. A lot of items were almost never sold, like nachos and chips.
* Slight differences in the menu between the bars caused customers to ask "Do you have ...?". Also complicates restocking logistics.
* The amount of Rum in the "Tschunk" was '''halved''' without updating the price. They decided it was better to modify the recipe to make it almost non-alcoholic, rather than say "Sorry, we're out."
** +1, the Tschunk contained barely any Rum.
* Bar is not a Merch Store, "Special/Ceremonial Cup" should be sold in Infodesk. It was also badly advertised, only people who "knew" of its existence could buy it. +1
* How was the cup not a deposit... I didn't even realize you wouldn't get any money back. Made it extremely bothersome to buy drinks for other people. +1
* Why wasn't statiegeld/pfand collected? Many glass bins full of mate-bottles. I don't want to know how many plastic bottles and aluminium cans were thrown out. This could have been prevented.
* No Club Mate Beere?
* No normal (0.5L) bottles available on the last day?
* Do we get mate from the source, or a Dutch overprices company?
* No mate during buildup again?
* Not written instructions for angels. The “game of telephone” style handing of incorrect instructions down from one angel to the next caused food to be prepared incorrectly. Written instructions should be posted right at the frier and microwave.
** +1
* Handling of vegan food was bad. Burger stall incorrectly advertised vegetarian burger as "vegan" originally, and could not provide any vegan burger at all because the buns contained milk(!). Fries/snacks stall staff did not know what they were selling or what it contained, and communication was difficult. Only positive note goes to the pasta stall where the food was good, and the operator was highly competent and knew exactly what they were selling (I would like to see them at a next event).
* Bottle collection procedure was very unclear.
* To add to the above: between bar and foodcourt no crates in sight on several days. No crates at any of the waste collection points. No instructions or procedure arranged. So people grabbed the glass-waste bin from the showers and put it in the middle. End result: 24x 240L glass trash bin completely filled to the brim. Assuming roughly around 5000 pfand-bottles (Mate, beer etc) were trashed. And team Waste had a ton of heavy lifting to get all these bins off the field and back to the recycling company. This could have been prevented.
* The same with plastic bottles and cans. Team Waste managed to save a *trailer* full of cans and bottles. About 24 big bags (240L). That could easily have been double. And if people actually organized it, it would have been less work.

=== Cohesion ===
* I like the idea, but not the implementation: Geraffel was put at the arse end of the field (OK fine, epicenter of noise gradient and all that), then got told off for playing music during the day.
* Very little communication/information. People barely knew the team existed and could be contacted, social rules like the Photo Policy were not communicated and very widely ignored. Other events signpost these things all over the site and it does help

=== Content / talks / heralds / speakerdesk / AV / recordings ===

* Party Stage was the perfect location for the "History of Hardcore" talk. More 'serious' talks could be held on the music stages at events going forward.

=== CTF / token game ===

=== Decoration / design ===

* Team did an amazing job. The field felt welcoming and interesting. Thank you so much for all the effort that went in. +1
* Next time we need to find a sponsor to print flags for all visitors, and have it available as merch for purchase. It was sad to see so much deco being liberated too early in the event. We need to also work on the communication around this.

=== Family / kids ===

=== Finance / coins / payments ===

* Like the concept of an anonymous payment card that '''just works'''. Absolutely love the design of the WHY2025 card. And very happy to play with a blank Ultralight AES card afterwards.
* option for payout of remaining funds wasn't communicated properly (even the website claimed it wasn't possible at all). Cash payout would be nice, but would understandably be a big extra thing to manage

=== Information / infodesk / wiki ===

* The wiki seems to have never been updated after the event started. I have attempted to find information about something several times and ''none'' of those times was it on the wiki. Instead everything seemed to be in random Signal groups and wherever else, that I didn't even know about until much later.
* It was very hard to find information on anything (like infrastructure, badge handouts, etc.) in general, and even infodesk angels often didn't have the answers.

=== Merchandise ===
* It would have been nice if the merch that was ordered months ago would have actually been available at the field.
* Flags as preordered merchandise. Would create the possibility for hackerspaces and individuals to bring back home some of them. +2

=== NOC / Network ===
* From buildup, through the event, through teardown: the networks worked!
* It was a pleasure to work together, to deduplicate work and equipment.
* In our location, Wifi coverage was poor although we were next to a Datenklo

=== NUTS / power / water ===

* Showers with adjustable heat (showerheads which mix cold and hot water) to avoid burns.
* Wood pallets outside both showers and toilets to reduce mud. (+1, from day zero would have been helpful)
* Even if not in all bathroom points, more drinking water points other than the one in heaven should have been available from the beginning. +1
* Disable the watertaps at the same time as all the other bathroom facilities. Or communicate when the water is going out. Now villages were only able to fill small containers at the toilets. Or needed to walk all the way to Heaven.
* Slightly more cleaning would have been great. The showers were extremely full of mud even inside at times. Given they only used a hose as far as I saw, should have been possible to also have some angels do this in addition to the cleaning crew.
* Adding hooks to the showers was a very welcome addition, thanks!
* It wasn't clear where to get drinking water during the first few days. This should be communicated better, e.g. with signs and on the map. +1
* I liked the number of toilets: never had to wait +1
* furthermore, the toilets seemed to be cleaned often which is good. +1
* There always was toilet paper available in the stalls, greatly lessens anxiety. +1
* water pressure and temperature in the showers was great! Also: never had to wait, which is great! +1
* There always was plenty of soap available at the sinks, during peak time and at night. +1
* Dedicated dishwashing location. +1
* More drinking water fountains across the terrain
* "upgrading" facilities to "drinking water" is questionable. What of all the potential risks was actually tested and could be guaranteed? Separate 100% clear drinking water spots would be better -1
* Shower temperature constantly fluctuated and never stabilized

=== Off-site logistics ===

=== On-site logistics ===

=== POC / DECT / Fieldphones ===
* micropoc worked just fine: I could easily and quickly register the DECT phones for my village and the network worked whenever I wanted to use it.
* Having the DECT so people can reach my team was as always: amazing. Thank you. Feature request: have a phone number only operational during business hours (and redirect to a prerecorded thing other times). Fixed that ourselves by switching the dect to silent. But would be a cool feature.

=== Productiehuis / C3VOC ===

=== Projectleiding ===

=== ROC ===
* Very clear audio and reception
* Was very happy with radio when the relay was up. During the end of teardown the signal degraded to unintelligible gibberish when going across field.
* Next time, don't do a split service desk in warehouse/ROC.

=== Safety / security / first aid / fire ===

=== Supermarket ===
* Happy friendly people who had the correct stuff on the shelves
* Pricing was for a campsite supermarket 'okay'. Having stuff available on field makes up for a lot.
* Would have loved to be able to purchase anything after 8PM, but i understand that they also need to sleep ;)

=== Sysadmin ===

* Setup "live.why2025.org" as an alias for people to easier find the livestreams next time. Right now you needed to go to "streaming.media.ccc.de/why2025".
* IRC is less popular in new generations of hackers and at least Mastodon+Matrix integrations would have made Signal angel role useful.
* Would like a clear messaging channel from Orga/teams to visitors. live.why2025.org would be good. Better than signal. But have no idea what tool to use.

=== Terrain ===

* Noise gradient should be evaluated better: the main party stage was more audible from the family village than from the Belgian cluster, which was way closer.
* Fridge container orientation: the compressor should point away from campers, it was the single most noisy item from Batavus On tour village point of view.
* Infodesk not located at the entrance like at MCH, causing it to be less visible.
* 4000 people but only a single "Hardware Hacking Tent". It was constantly full, and no other places to sit and solder.
** Plenty villages that'll happily let you use their spaces. It makes sense for this kind of thing to be community-provided (the Hardware Hacking Tent was too - while a official workshop spot, it only exists because of of the HHA team willing to equip and run it)
* "Hackcenter" only had space for 20 people, tiny tent, zero cooling, and no advertisement. Not even a sign... We thought it was someone's Village until day 4.
* No place to party/music all night. It would be cool to have a distant (from tents) area where we're allowed to have music going all night long.
** -1, loud music anywhere on the field travels far and I appreciate being able to sleep. I liked the 23:00 cutoff.
** -1 agreed. "distant" location is not really possible on-site
** +1 AGREE, the noise cutoff was really annoying, other events the music continues until 2am atleast, I don't see why we can't have somewhere on site where we can play music at a reasonable volume. 23:00 is too early for a festival.
** +1, made the event substancially worse, if we have color-coded fields to match volume levels why do we still have to shut the music down completely at 23:00 in the red area?
** -1, i was very happy to have a camp where i could sleep without earplugs. Also it would be impossible due to very strict permits this time around.
*** also this was not followed on the last night after closing in which the angel party continued in the main bar until very late???? have some consistency please. it just feels mean otherwise.

* it was nice that noise rules were followed quite well this time (unlike e.g. MCH where main stages switched to silent disco while sponsors kept blaring music into the silent areas)

* I missed routing signs for bikes coming in. Google Maps got me to the wooden bridge which was fenced off, and nobody there to either let me in or give me a hint. I may have let myself in at that fence, because it was very unclear which detour to take. The climb was only moderately scary.
* Seperate smoking and non-smoking fields, designated smoking areas away from event spaces. A blanket ban on smoking and vaping for the entire event is probably not feasible (unfortunately).

=== Tickets / entrance ===
* Putting the desks on the other side might have looked more welcoming, but all was fine for my check-in.
* Camper tickets were not scanned?

=== Villages ===
* Well done! And it was fun to help out villages doing extra luggage shuttles after we were done doing Waste stuff.

=== Volunteering / angels / heaven===

* Food tickets given to volunteers expiring, without any communication of them doing so.

[[File:Angel Waterbottle Comparison WHY vs MCH.jpg|thumb|Angle Waterbottle Comparison WHY vs MCH]]

* Waterbottle had boring text "'''Thanks For Volunteering'''", instead of WHY wordplay like "'''We Hydrate You'''", "'''Why Hydrate Yourself?'''" or "'''Wet Hackers, Yay!'''".
* Clip/Hook on the waterbootle was 3x smaller, making it unwieldy and difficult to connect. The MCH hook was bigger and easier to quick-connect.
* Drinking part had leak problems, which was not present on the previous bottle.
* The clip caused burn/melt-damage on the waterbottle, as can be seen when zooming in where the clip touches the orange waterbottle.
* No mate during buildup.
* No safe food, or unclear about the contents.
* Severe food safety issues in heaven. Bread toppings (including cheese and meat!) left open on a table outside of a fridge for hours, even overnight, with insects roaming around. No proper cleaning agents or supplies available for cleaning surfaces like tables, only some random supermarket cleaning sprays (this is not good enough for a central eating area!).
* Vegan food availability was unclear and could not be relied on. At times, the "vegan options" were completely inadequate for actually keeping people fed while doing potentially physically intensive volunteer work, with lacking nutritional value. Problem persisted during teardown. "We can't predict what the caterer will deliver" is not good enough for people with dietary restrictions.
* Heaven was too loud. It was almost impossible to communicate with people at the angel desk when there was a meal going on, and you had to practically yell to hear each other. Ideally sound dampening would be installed, but at least the eating area should be separated/insulated from the heaven desk and standby angel area in some way.

=== Warehouse ===
* When Boels screwed up, warehouse delivered us a replacement the same day.
- what did boels screw up?
* I appreciate being able to discuss the underlying requirements instead of automatically being handed a solution. When I asked for a bunch of extension cords, it turned out there was a better solution.
* Delivery service made camp a lot better for me as teamlead. I fixed several problems with one phone call and a happy angel heading out on a bike or gator!

=== Waste / garbage collection ===

* I have no knowledge about the state of recycling in NL, but having only separate bins for glass and then ones for everything else felt quite bad. At least separation of paper/carton would have made sense I guess. Also having separate containers where people could "donate" plastic bottles / metal cans which have deposit would have made sense and also could have brought a nice sum of money for the event.
* Field was nice and clean until teardown with enough containers to get rid of waste. (+1 for adding at least a paper and deposit container)

=== Teardown ===

* "No cars on the gras" policy: Villages that respected the rule of not driving on the grass were effectively disadvantaged. On Wednesday, many cars ignored the rule and drove onto the grass, which meant those villages didn’t have to carry their equipment over long distances. Meanwhile, villages that followed the rule had to transport their gear much farther, which was exhausting given the hot weather. Suggestion: Instead of creating a situation where following the rules feels like a disadvantage, we could reward compliance. For example, check which villages adhere to the rule, and if they do, give them vouchers for a priority ticket queue for the next event.
* Toilets were shut down too early making getting water during the warm teardown harder
* Transporting crates with empty bottles in hand trucks is also very unsafe. If they fall over it would be a mess for barefooted people. Bringing them in and out with cars is much safer.
* Way too many people left a day early. That was a bit sad. For everyone reading this: stay the entire camp ;)
* We should communicate better that flags and other deco is there for the event and should not disappear during the event. Previous events and other events by other parties may have 'trained' our visitors to think they are helping out by removing such decoration early. It was a bit sad to see people rip things of the waste gator. They got told off. But the flags on the main road disappeared on day 2 of camp, and that was entirely unwarranted.
* Remove toilet accessories (paper/soap/brushes) beofore toilets are removed, otherwise they get dumped out on the field.
* Remove zipties of the main tents before tearing the tents down, the tent guys just cut them and leave them on the field.
* Not enough hi-vis vests available, which is especially unsafe when heavy machinery is roaming the site.
* There didn't seem to be any documentation of the teardown procedure for angels, which made it difficult to plan things like food and sleep.

Feedback

2025-08-18T09:16:14Z

Bas: /* Supermarket */

'''What Hackers Yearn''' for is to '''Improve'''. This page is dedicated to collecting user feedback related to the execution of WHY2025 as a whole. Constructive feedback is invaluable to the continuous improvement of the project and is welcomed from all participants. Please share your observations and suggestions in a '''clear and respectful manner'''. Your input will help guide enhancements for future generations of the event.

It is also possible to send feedback to [http://mailto:2029@why2025.org 2029@why2025.org]

== IMPORTANT ==

Do '''NOT''' review '''people'''. Any individual interaction you had with a human does not belong here, but should be taken up with [[Team:Cohesion]].

This page is strictly for addressing improvements for the next event. We encourage contributors to maintain a neutral, factual, and calm tone in their feedback.

* GOOD EXAMPLES: "Excessive mud at showers", "Food vendors often refused to accept WHY-voucher", or "Limited drop-off points for luggage shuttle".

* BAD EXAMPLES: "Person XXX was insulting me", "Helpdesk XOC was too busy to help", "frickin hot", "So the story begins on Saturday night at 23:04 when..."

== Feedback List ==

=== General / overall ===

* There should be a clear single method/channel of communication from orga, using the Heaven signal chat or social media for this is not ideal
** +1

=== Arrival / departure / parking / train shuttle / luggage shuttle ===

* On day 0 we queued to drive onto the field. We said said we had stuff for two different villages at opposite ends of the site, named the villages and showed them on map print outs. This information was accepted by a dispatcher. However, the bicycle guide refused to guide us to the second location, claiming it was impossible to get there. This is somewhat surprising, since others had been able to drive to that location before. It seemed there was a informational mismatch between dispatch and bicyle guide. (Both locations were accessible by asphalt roads.)
* train shuttle worked well, good job!

=== Badge ===

* Badge handouts were announced right before they happened which didn't allow people to plan their angel shifts and disrupted talks / workshops. A virtual queue would have fixed this and required less total manhours to organize / manage. +1

* There was an expectation that the badge was and I quote from what I have overheard "included in the price". This is not the case and has never been the case but it’s not clearly communicated. To my understanding there was a surplus at SHA2017 and MCH2022 so there never was a shortage of badges before which may have contributed.
** The above is misinformation: It was in fact communicated in written form that every attendee with a ticket receives a badge. The badge could not be ordered separately and was included in the ticket price.

* During the event (AFAIK) there were no badge angel shifts outside of queue angel. This is a chance from prior events and didn't allow people who normally would have helped to help in the same way.

* Due to the badges not being self-powered nor being distributed at the entrance they failed to function as badges. The SHA2017 badge was designed with having no power yet still being a nametag in mind. The WHY2025 badge did not seem to function as a nametag which should have been its intended design goal.

* At MCH and SHA you had people using the badges at the event itself to make games / hack / learn / teach. It was something which brought people together. There was very little being done / to do with the badge during the camp, not just because of the late arrival and limited distribution but rather because there is no way to get apps on the badge outside of the SD card... or if there is a way of doing so then its not documented on the wiki page as of writing. There was no app store app, no way to use the LORA hardware, and outside the event its impossible to use the badge without reflashing a new wifi SSID.

* You could not sit at the badge tent and solder on your antenna onto the badge or work on projects. At SHA and MCH you could just approach the badge people / angels and even get help with projects.

* Badge still has way too limited documentation to even work on it after the event.

* Team Badge have overworked themselves to get a badge available. Team over Badge next time. Which is also a Team:Cohesion issue.

* Would have been great to have a separate queue for villages that collected tickets and pick up 15+ badges at the same time. This would also have greatly reduced waiting times for individuals picking up badges and sped-up the whole process.

* Not enough badges for all visitors (not even close apparently).

* Badge queues were very long and poorly managed. This made it impossible for some people to collected a badge (for example because they cannot stand that long, require shade, have to take care of children, need to go to their next angel shift, etc.)

* The communication about the badge status was very sparse and lacking. If there is a problem, '''communicate''' about it and tell participants what to expect.

** +1. I am sympathetic to the team scrambling to get stuff done under difficult constraints, but especially in such cases good communication is important. Things like randomly posting a link to a page about the keyboard hardware felt frustrating when we were just waiting for more info about future handouts. In addition, a Signal group was a poor choice of channel for announcements for many reasons - no public access, no history for new joiners, redundant join/leave messages, etc. Keeping updates to a section on the wiki and/or a mailing list would've worked much better.

* During build-up, almost all other teams were scrambling to find a pair of hands to get essential stuff done, while watching lots of people pouring epoxy in the badge tent. Which was, lemme me blunt here, one of the lowest priority of all the things that have been done during build-up.

=== Bars and food court ===

* Menu was much longer and more complex compared to MCH. A lot of items were almost never sold, like nachos and chips.
* Slight differences in the menu between the bars caused customers to ask "Do you have ...?". Also complicates restocking logistics.
* The amount of Rum in the "Tschunk" was '''halved''' without updating the price. They decided it was better to modify the recipe to make it almost non-alcoholic, rather than say "Sorry, we're out."
** +1, the Tschunk contained barely any Rum.
* Bar is not a Merch Store, "Special/Ceremonial Cup" should be sold in Infodesk. It was also badly advertised, only people who "knew" of its existence could buy it. +1
* How was the cup not a deposit... I didn't even realize you wouldn't get any money back. Made it extremely bothersome to buy drinks for other people. +1
* Why wasn't statiegeld/pfand collected? Many glass bins full of mate-bottles. I don't want to know how many plastic bottles and aluminium cans were thrown out. This could have been prevented.
* No Club Mate Beere?
* No normal (0.5L) bottles available on the last day?
* Do we get mate from the source, or a Dutch overprices company?
* No mate during buildup again?
* Not written instructions for angels. The “game of telephone” style handing of incorrect instructions down from one angel to the next caused food to be prepared incorrectly. Written instructions should be posted right at the frier and microwave.
** +1
* Handling of vegan food was bad. Burger stall incorrectly advertised vegetarian burger as "vegan" originally, and could not provide any vegan burger at all because the buns contained milk(!). Fries/snacks stall staff did not know what they were selling or what it contained, and communication was difficult. Only positive note goes to the pasta stall where the food was good, and the operator was highly competent and knew exactly what they were selling (I would like to see them at a next event).
* Bottle collection procedure was very unclear.
* To add to the above: between bar and foodcourt no crates in sight on several days. No crates at any of the waste collection points. No instructions or procedure arranged. So people grabbed the glass-waste bin from the showers and put it in the middle. End result: 24x 240L glass trash bin completely filled to the brim. Assuming roughly around 5000 pfand-bottles (Mate, beer etc) were trashed. And team Waste had a ton of heavy lifting to get all these bins off the field and back to the recycling company. This could have been prevented.
* The same with plastic bottles and cans. Team Waste managed to save a *trailer* full of cans and bottles. About 24 big bags (240L). That could easily have been double. And if people actually organized it, it would have been less work.

=== Cohesion ===
* I like the idea, but not the implementation: Geraffel was put at the arse end of the field (OK fine, epicenter of noise gradient and all that), then got told off for playing music during the day.
* Very little communication/information. People barely knew the team existed and could be contacted, social rules like the Photo Policy were not communicated and very widely ignored. Other events signpost these things all over the site and it does help

=== Content / talks / heralds / speakerdesk / AV / recordings ===

* Party Stage was the perfect location for the "History of Hardcore" talk. More 'serious' talks could be held on the music stages at events going forward.

=== CTF / token game ===

=== Decoration / design ===

* Team did an amazing job. The field felt welcoming and interesting. Thank you so much for all the effort that went in. +1
* Next time we need to find a sponsor to print flags for all visitors, and have it available as merch for purchase. It was sad to see so much deco being liberated too early in the event. We need to also work on the communication around this.

=== Family / kids ===

=== Finance / coins / payments ===

* Like the concept of an anonymous payment card that '''just works'''. Absolutely love the design of the WHY2025 card. And very happy to play with a blank Ultralight AES card afterwards.
* option for payout of remaining funds wasn't communicated properly (even the website claimed it wasn't possible at all). Cash payout would be nice, but would understandably be a big extra thing to manage

=== Information / infodesk / wiki ===

* The wiki seems to have never been updated after the event started. I have attempted to find information about something several times and ''none'' of those times was it on the wiki. Instead everything seemed to be in random Signal groups and wherever else, that I didn't even know about until much later.
* It was very hard to find information on anything (like infrastructure, badge handouts, etc.) in general, and even infodesk angels often didn't have the answers.

=== Merchandise ===
* It would have been nice if the merch that was ordered months ago would have actually been available at the field.
* Flags as preordered merchandise. Would create the possibility for hackerspaces and individuals to bring back home some of them. +2

=== NOC / Network ===
* From buildup, through the event, through teardown: the networks worked!
* It was a pleasure to work together, to deduplicate work and equipment.
* In our location, Wifi coverage was poor although we were next to a Datenklo

=== NUTS / power / water ===

* Showers with adjustable heat (showerheads which mix cold and hot water) to avoid burns.
* Wood pallets outside both showers and toilets to reduce mud. (+1, from day zero would have been helpful)
* Even if not in all bathroom points, more drinking water points other than the one in heaven should have been available from the beginning. +1
* Disable the watertaps at the same time as all the other bathroom facilities. Or communicate when the water is going out. Now villages were only able to fill small containers at the toilets. Or needed to walk all the way to Heaven.
* Slightly more cleaning would have been great. The showers were extremely full of mud even inside at times. Given they only used a hose as far as I saw, should have been possible to also have some angels do this in addition to the cleaning crew.
* Adding hooks to the showers was a very welcome addition, thanks!
* It wasn't clear where to get drinking water during the first few days. This should be communicated better, e.g. with signs and on the map. +1
* I liked the number of toilets: never had to wait +1
* furthermore, the toilets seemed to be cleaned often which is good. +1
* There always was toilet paper available in the stalls, greatly lessens anxiety. +1
* water pressure and temperature in the showers was great! Also: never had to wait, which is great! +1
* There always was plenty of soap available at the sinks, during peak time and at night. +1
* Dedicated dishwashing location. +1
* More drinking water fountains across the terrain
* "upgrading" facilities to "drinking water" is questionable. What of all the potential risks was actually tested and could be guaranteed? Separate 100% clear drinking water spots would be better -1
* Shower temperature constantly fluctuated and never stabilized

=== Off-site logistics ===

=== On-site logistics ===

=== POC / DECT / Fieldphones ===
* micropoc worked just fine: I could easily and quickly register the DECT phones for my village and the network worked whenever I wanted to use it.
* Having the DECT so people can reach my team was as always: amazing. Thank you. Feature request: have a phone number only operational during business hours (and redirect to a prerecorded thing other times). Fixed that ourselves by switching the dect to silent. But would be a cool feature.

=== Productiehuis / C3VOC ===

=== Projectleiding ===

=== ROC ===
* Very clear audio and reception
* Was very happy with radio when the relay was up. During the end of teardown the signal degraded to unintelligible gibberish when going across field.
* Next time, don't do a split service desk in warehouse/ROC.

=== Safety / security / first aid / fire ===

=== Supermarket ===
* Happy friendly people who had the correct stuff on the shelves
* Pricing was for a campsite supermarket 'okay'. Having stuff available on field makes up for a lot.
* Would have loved to be able to purchase anything after 8PM, but i understand that they also need to sleep ;)

=== Sysadmin ===

* Setup "live.why2025.org" as an alias for people to easier find the livestreams next time. Right now you needed to go to "streaming.media.ccc.de/why2025".
* IRC is less popular in new generations of hackers and at least Mastodon+Matrix integrations would have made Signal angel role useful.

=== Terrain ===

* Noise gradient should be evaluated better: the main party stage was more audible from the family village than from the Belgian cluster, which was way closer.
* Fridge container orientation: the compressor should point away from campers, it was the single most noisy item from Batavus On tour village point of view.
* Infodesk not located at the entrance like at MCH, causing it to be less visible.
* 4000 people but only a single "Hardware Hacking Tent". It was constantly full, and no other places to sit and solder.
** Plenty villages that'll happily let you use their spaces. It makes sense for this kind of thing to be community-provided (the Hardware Hacking Tent was too - while a official workshop spot, it only exists because of of the HHA team willing to equip and run it)
* "Hackcenter" only had space for 20 people, tiny tent, zero cooling, and no advertisement. Not even a sign... We thought it was someone's Village until day 4.
* No place to party/music all night. It would be cool to have a distant (from tents) area where we're allowed to have music going all night long.
** -1, loud music anywhere on the field travels far and I appreciate being able to sleep. I liked the 23:00 cutoff.
** -1 agreed. "distant" location is not really possible on-site
** +1 AGREE, the noise cutoff was really annoying, other events the music continues until 2am atleast, I don't see why we can't have somewhere on site where we can play music at a reasonable volume. 23:00 is too early for a festival.
** +1, made the event substancially worse, if we have color-coded fields to match volume levels why do we still have to shut the music down completely at 23:00 in the red area?
** -1, i was very happy to have a camp where i could sleep without earplugs. Also it would be impossible due to very strict permits this time around.
*** also this was not followed on the last night after closing in which the angel party continued in the main bar until very late???? have some consistency please. it just feels mean otherwise.

* it was nice that noise rules were followed quite well this time (unlike e.g. MCH where main stages switched to silent disco while sponsors kept blaring music into the silent areas)

* I missed routing signs for bikes coming in. Google Maps got me to the wooden bridge which was fenced off, and nobody there to either let me in or give me a hint. I may have let myself in at that fence, because it was very unclear which detour to take. The climb was only moderately scary.
* Seperate smoking and non-smoking fields, designated smoking areas away from event spaces. A blanket ban on smoking and vaping for the entire event is probably not feasible (unfortunately).

=== Tickets / entrance ===
* Putting the desks on the other side might have looked more welcoming, but all was fine for my check-in.
* Camper tickets were not scanned?

=== Villages ===
* Well done! And it was fun to help out villages doing extra luggage shuttles after we were done doing Waste stuff.

=== Volunteering / angels / heaven===

* Food tickets given to volunteers expiring, without any communication of them doing so.

[[File:Angel Waterbottle Comparison WHY vs MCH.jpg|thumb|Angle Waterbottle Comparison WHY vs MCH]]

* Waterbottle had boring text "'''Thanks For Volunteering'''", instead of WHY wordplay like "'''We Hydrate You'''", "'''Why Hydrate Yourself?'''" or "'''Wet Hackers, Yay!'''".
* Clip/Hook on the waterbootle was 3x smaller, making it unwieldy and difficult to connect. The MCH hook was bigger and easier to quick-connect.
* Drinking part had leak problems, which was not present on the previous bottle.
* The clip caused burn/melt-damage on the waterbottle, as can be seen when zooming in where the clip touches the orange waterbottle.
* No mate during buildup.
* No safe food, or unclear about the contents.
* Severe food safety issues in heaven. Bread toppings (including cheese and meat!) left open on a table outside of a fridge for hours, even overnight, with insects roaming around. No proper cleaning agents or supplies available for cleaning surfaces like tables, only some random supermarket cleaning sprays (this is not good enough for a central eating area!).
* Vegan food availability was unclear and could not be relied on. At times, the "vegan options" were completely inadequate for actually keeping people fed while doing potentially physically intensive volunteer work, with lacking nutritional value. Problem persisted during teardown. "We can't predict what the caterer will deliver" is not good enough for people with dietary restrictions.
* Heaven was too loud. It was almost impossible to communicate with people at the angel desk when there was a meal going on, and you had to practically yell to hear each other. Ideally sound dampening would be installed, but at least the eating area should be separated/insulated from the heaven desk and standby angel area in some way.

=== Warehouse ===
* When Boels screwed up, warehouse delivered us a replacement the same day.
- what did boels screw up?
* I appreciate being able to discuss the underlying requirements instead of automatically being handed a solution. When I asked for a bunch of extension cords, it turned out there was a better solution.
* Delivery service made camp a lot better for me as teamlead. I fixed several problems with one phone call and a happy angel heading out on a bike or gator!

=== Waste / garbage collection ===

* I have no knowledge about the state of recycling in NL, but having only separate bins for glass and then ones for everything else felt quite bad. At least separation of paper/carton would have made sense I guess. Also having separate containers where people could "donate" plastic bottles / metal cans which have deposit would have made sense and also could have brought a nice sum of money for the event.
* Field was nice and clean until teardown with enough containers to get rid of waste. (+1 for adding at least a paper and deposit container)

=== Teardown ===

* "No cars on the gras" policy: Villages that respected the rule of not driving on the grass were effectively disadvantaged. On Wednesday, many cars ignored the rule and drove onto the grass, which meant those villages didn’t have to carry their equipment over long distances. Meanwhile, villages that followed the rule had to transport their gear much farther, which was exhausting given the hot weather. Suggestion: Instead of creating a situation where following the rules feels like a disadvantage, we could reward compliance. For example, check which villages adhere to the rule, and if they do, give them vouchers for a priority ticket queue for the next event.
* Toilets were shut down too early making getting water during the warm teardown harder
* Transporting crates with empty bottles in hand trucks is also very unsafe. If they fall over it would be a mess for barefooted people. Bringing them in and out with cars is much safer.
* Way too many people left a day early. That was a bit sad. For everyone reading this: stay the entire camp ;)
* We should communicate better that flags and other deco is there for the event and should not disappear during the event. Previous events and other events by other parties may have 'trained' our visitors to think they are helping out by removing such decoration early. It was a bit sad to see people rip things of the waste gator. They got told off. But the flags on the main road disappeared on day 2 of camp, and that was entirely unwarranted.
* Remove toilet accessories (paper/soap/brushes) beofore toilets are removed, otherwise they get dumped out on the field.
* Remove zipties of the main tents before tearing the tents down, the tent guys just cut them and leave them on the field.
* Not enough hi-vis vests available, which is especially unsafe when heavy machinery is roaming the site.
* There didn't seem to be any documentation of the teardown procedure for angels, which made it difficult to plan things like food and sleep.

Feedback

2025-08-18T09:14:17Z

Bas: /* ROC */

'''What Hackers Yearn''' for is to '''Improve'''. This page is dedicated to collecting user feedback related to the execution of WHY2025 as a whole. Constructive feedback is invaluable to the continuous improvement of the project and is welcomed from all participants. Please share your observations and suggestions in a '''clear and respectful manner'''. Your input will help guide enhancements for future generations of the event.

It is also possible to send feedback to [http://mailto:2029@why2025.org 2029@why2025.org]

== IMPORTANT ==

Do '''NOT''' review '''people'''. Any individual interaction you had with a human does not belong here, but should be taken up with [[Team:Cohesion]].

This page is strictly for addressing improvements for the next event. We encourage contributors to maintain a neutral, factual, and calm tone in their feedback.

* GOOD EXAMPLES: "Excessive mud at showers", "Food vendors often refused to accept WHY-voucher", or "Limited drop-off points for luggage shuttle".

* BAD EXAMPLES: "Person XXX was insulting me", "Helpdesk XOC was too busy to help", "frickin hot", "So the story begins on Saturday night at 23:04 when..."

== Feedback List ==

=== General / overall ===

* There should be a clear single method/channel of communication from orga, using the Heaven signal chat or social media for this is not ideal
** +1

=== Arrival / departure / parking / train shuttle / luggage shuttle ===

* On day 0 we queued to drive onto the field. We said said we had stuff for two different villages at opposite ends of the site, named the villages and showed them on map print outs. This information was accepted by a dispatcher. However, the bicycle guide refused to guide us to the second location, claiming it was impossible to get there. This is somewhat surprising, since others had been able to drive to that location before. It seemed there was a informational mismatch between dispatch and bicyle guide. (Both locations were accessible by asphalt roads.)
* train shuttle worked well, good job!

=== Badge ===

* Badge handouts were announced right before they happened which didn't allow people to plan their angel shifts and disrupted talks / workshops. A virtual queue would have fixed this and required less total manhours to organize / manage. +1

* There was an expectation that the badge was and I quote from what I have overheard "included in the price". This is not the case and has never been the case but it’s not clearly communicated. To my understanding there was a surplus at SHA2017 and MCH2022 so there never was a shortage of badges before which may have contributed.
** The above is misinformation: It was in fact communicated in written form that every attendee with a ticket receives a badge. The badge could not be ordered separately and was included in the ticket price.

* During the event (AFAIK) there were no badge angel shifts outside of queue angel. This is a chance from prior events and didn't allow people who normally would have helped to help in the same way.

* Due to the badges not being self-powered nor being distributed at the entrance they failed to function as badges. The SHA2017 badge was designed with having no power yet still being a nametag in mind. The WHY2025 badge did not seem to function as a nametag which should have been its intended design goal.

* At MCH and SHA you had people using the badges at the event itself to make games / hack / learn / teach. It was something which brought people together. There was very little being done / to do with the badge during the camp, not just because of the late arrival and limited distribution but rather because there is no way to get apps on the badge outside of the SD card... or if there is a way of doing so then its not documented on the wiki page as of writing. There was no app store app, no way to use the LORA hardware, and outside the event its impossible to use the badge without reflashing a new wifi SSID.

* You could not sit at the badge tent and solder on your antenna onto the badge or work on projects. At SHA and MCH you could just approach the badge people / angels and even get help with projects.

* Badge still has way too limited documentation to even work on it after the event.

* Team Badge have overworked themselves to get a badge available. Team over Badge next time. Which is also a Team:Cohesion issue.

* Would have been great to have a separate queue for villages that collected tickets and pick up 15+ badges at the same time. This would also have greatly reduced waiting times for individuals picking up badges and sped-up the whole process.

* Not enough badges for all visitors (not even close apparently).

* Badge queues were very long and poorly managed. This made it impossible for some people to collected a badge (for example because they cannot stand that long, require shade, have to take care of children, need to go to their next angel shift, etc.)

* The communication about the badge status was very sparse and lacking. If there is a problem, '''communicate''' about it and tell participants what to expect.

** +1. I am sympathetic to the team scrambling to get stuff done under difficult constraints, but especially in such cases good communication is important. Things like randomly posting a link to a page about the keyboard hardware felt frustrating when we were just waiting for more info about future handouts. In addition, a Signal group was a poor choice of channel for announcements for many reasons - no public access, no history for new joiners, redundant join/leave messages, etc. Keeping updates to a section on the wiki and/or a mailing list would've worked much better.

* During build-up, almost all other teams were scrambling to find a pair of hands to get essential stuff done, while watching lots of people pouring epoxy in the badge tent. Which was, lemme me blunt here, one of the lowest priority of all the things that have been done during build-up.

=== Bars and food court ===

* Menu was much longer and more complex compared to MCH. A lot of items were almost never sold, like nachos and chips.
* Slight differences in the menu between the bars caused customers to ask "Do you have ...?". Also complicates restocking logistics.
* The amount of Rum in the "Tschunk" was '''halved''' without updating the price. They decided it was better to modify the recipe to make it almost non-alcoholic, rather than say "Sorry, we're out."
** +1, the Tschunk contained barely any Rum.
* Bar is not a Merch Store, "Special/Ceremonial Cup" should be sold in Infodesk. It was also badly advertised, only people who "knew" of its existence could buy it. +1
* How was the cup not a deposit... I didn't even realize you wouldn't get any money back. Made it extremely bothersome to buy drinks for other people. +1
* Why wasn't statiegeld/pfand collected? Many glass bins full of mate-bottles. I don't want to know how many plastic bottles and aluminium cans were thrown out. This could have been prevented.
* No Club Mate Beere?
* No normal (0.5L) bottles available on the last day?
* Do we get mate from the source, or a Dutch overprices company?
* No mate during buildup again?
* Not written instructions for angels. The “game of telephone” style handing of incorrect instructions down from one angel to the next caused food to be prepared incorrectly. Written instructions should be posted right at the frier and microwave.
** +1
* Handling of vegan food was bad. Burger stall incorrectly advertised vegetarian burger as "vegan" originally, and could not provide any vegan burger at all because the buns contained milk(!). Fries/snacks stall staff did not know what they were selling or what it contained, and communication was difficult. Only positive note goes to the pasta stall where the food was good, and the operator was highly competent and knew exactly what they were selling (I would like to see them at a next event).
* Bottle collection procedure was very unclear.
* To add to the above: between bar and foodcourt no crates in sight on several days. No crates at any of the waste collection points. No instructions or procedure arranged. So people grabbed the glass-waste bin from the showers and put it in the middle. End result: 24x 240L glass trash bin completely filled to the brim. Assuming roughly around 5000 pfand-bottles (Mate, beer etc) were trashed. And team Waste had a ton of heavy lifting to get all these bins off the field and back to the recycling company. This could have been prevented.
* The same with plastic bottles and cans. Team Waste managed to save a *trailer* full of cans and bottles. About 24 big bags (240L). That could easily have been double. And if people actually organized it, it would have been less work.

=== Cohesion ===
* I like the idea, but not the implementation: Geraffel was put at the arse end of the field (OK fine, epicenter of noise gradient and all that), then got told off for playing music during the day.
* Very little communication/information. People barely knew the team existed and could be contacted, social rules like the Photo Policy were not communicated and very widely ignored. Other events signpost these things all over the site and it does help

=== Content / talks / heralds / speakerdesk / AV / recordings ===

* Party Stage was the perfect location for the "History of Hardcore" talk. More 'serious' talks could be held on the music stages at events going forward.

=== CTF / token game ===

=== Decoration / design ===

* Team did an amazing job. The field felt welcoming and interesting. Thank you so much for all the effort that went in. +1
* Next time we need to find a sponsor to print flags for all visitors, and have it available as merch for purchase. It was sad to see so much deco being liberated too early in the event. We need to also work on the communication around this.

=== Family / kids ===

=== Finance / coins / payments ===

* Like the concept of an anonymous payment card that '''just works'''. Absolutely love the design of the WHY2025 card. And very happy to play with a blank Ultralight AES card afterwards.
* option for payout of remaining funds wasn't communicated properly (even the website claimed it wasn't possible at all). Cash payout would be nice, but would understandably be a big extra thing to manage

=== Information / infodesk / wiki ===

* The wiki seems to have never been updated after the event started. I have attempted to find information about something several times and ''none'' of those times was it on the wiki. Instead everything seemed to be in random Signal groups and wherever else, that I didn't even know about until much later.
* It was very hard to find information on anything (like infrastructure, badge handouts, etc.) in general, and even infodesk angels often didn't have the answers.

=== Merchandise ===
* It would have been nice if the merch that was ordered months ago would have actually been available at the field.
* Flags as preordered merchandise. Would create the possibility for hackerspaces and individuals to bring back home some of them. +2

=== NOC / Network ===
* From buildup, through the event, through teardown: the networks worked!
* It was a pleasure to work together, to deduplicate work and equipment.
* In our location, Wifi coverage was poor although we were next to a Datenklo

=== NUTS / power / water ===

* Showers with adjustable heat (showerheads which mix cold and hot water) to avoid burns.
* Wood pallets outside both showers and toilets to reduce mud. (+1, from day zero would have been helpful)
* Even if not in all bathroom points, more drinking water points other than the one in heaven should have been available from the beginning. +1
* Disable the watertaps at the same time as all the other bathroom facilities. Or communicate when the water is going out. Now villages were only able to fill small containers at the toilets. Or needed to walk all the way to Heaven.
* Slightly more cleaning would have been great. The showers were extremely full of mud even inside at times. Given they only used a hose as far as I saw, should have been possible to also have some angels do this in addition to the cleaning crew.
* Adding hooks to the showers was a very welcome addition, thanks!
* It wasn't clear where to get drinking water during the first few days. This should be communicated better, e.g. with signs and on the map. +1
* I liked the number of toilets: never had to wait +1
* furthermore, the toilets seemed to be cleaned often which is good. +1
* There always was toilet paper available in the stalls, greatly lessens anxiety. +1
* water pressure and temperature in the showers was great! Also: never had to wait, which is great! +1
* There always was plenty of soap available at the sinks, during peak time and at night. +1
* Dedicated dishwashing location. +1
* More drinking water fountains across the terrain
* "upgrading" facilities to "drinking water" is questionable. What of all the potential risks was actually tested and could be guaranteed? Separate 100% clear drinking water spots would be better -1
* Shower temperature constantly fluctuated and never stabilized

=== Off-site logistics ===

=== On-site logistics ===

=== POC / DECT / Fieldphones ===
* micropoc worked just fine: I could easily and quickly register the DECT phones for my village and the network worked whenever I wanted to use it.
* Having the DECT so people can reach my team was as always: amazing. Thank you. Feature request: have a phone number only operational during business hours (and redirect to a prerecorded thing other times). Fixed that ourselves by switching the dect to silent. But would be a cool feature.

=== Productiehuis / C3VOC ===

=== Projectleiding ===

=== ROC ===
* Very clear audio and reception
* Was very happy with radio when the relay was up. During the end of teardown the signal degraded to unintelligible gibberish when going across field.
* Next time, don't do a split service desk in warehouse/ROC.

=== Safety / security / first aid / fire ===

=== Supermarket ===

=== Sysadmin ===

* Setup "live.why2025.org" as an alias for people to easier find the livestreams next time. Right now you needed to go to "streaming.media.ccc.de/why2025".
* IRC is less popular in new generations of hackers and at least Mastodon+Matrix integrations would have made Signal angel role useful.

=== Terrain ===

* Noise gradient should be evaluated better: the main party stage was more audible from the family village than from the Belgian cluster, which was way closer.
* Fridge container orientation: the compressor should point away from campers, it was the single most noisy item from Batavus On tour village point of view.
* Infodesk not located at the entrance like at MCH, causing it to be less visible.
* 4000 people but only a single "Hardware Hacking Tent". It was constantly full, and no other places to sit and solder.
** Plenty villages that'll happily let you use their spaces. It makes sense for this kind of thing to be community-provided (the Hardware Hacking Tent was too - while a official workshop spot, it only exists because of of the HHA team willing to equip and run it)
* "Hackcenter" only had space for 20 people, tiny tent, zero cooling, and no advertisement. Not even a sign... We thought it was someone's Village until day 4.
* No place to party/music all night. It would be cool to have a distant (from tents) area where we're allowed to have music going all night long.
** -1, loud music anywhere on the field travels far and I appreciate being able to sleep. I liked the 23:00 cutoff.
** -1 agreed. "distant" location is not really possible on-site
** +1 AGREE, the noise cutoff was really annoying, other events the music continues until 2am atleast, I don't see why we can't have somewhere on site where we can play music at a reasonable volume. 23:00 is too early for a festival.
** +1, made the event substancially worse, if we have color-coded fields to match volume levels why do we still have to shut the music down completely at 23:00 in the red area?
** -1, i was very happy to have a camp where i could sleep without earplugs. Also it would be impossible due to very strict permits this time around.
*** also this was not followed on the last night after closing in which the angel party continued in the main bar until very late???? have some consistency please. it just feels mean otherwise.

* it was nice that noise rules were followed quite well this time (unlike e.g. MCH where main stages switched to silent disco while sponsors kept blaring music into the silent areas)

* I missed routing signs for bikes coming in. Google Maps got me to the wooden bridge which was fenced off, and nobody there to either let me in or give me a hint. I may have let myself in at that fence, because it was very unclear which detour to take. The climb was only moderately scary.
* Seperate smoking and non-smoking fields, designated smoking areas away from event spaces. A blanket ban on smoking and vaping for the entire event is probably not feasible (unfortunately).

=== Tickets / entrance ===
* Putting the desks on the other side might have looked more welcoming, but all was fine for my check-in.
* Camper tickets were not scanned?

=== Villages ===
* Well done! And it was fun to help out villages doing extra luggage shuttles after we were done doing Waste stuff.

=== Volunteering / angels / heaven===

* Food tickets given to volunteers expiring, without any communication of them doing so.

[[File:Angel Waterbottle Comparison WHY vs MCH.jpg|thumb|Angle Waterbottle Comparison WHY vs MCH]]

* Waterbottle had boring text "'''Thanks For Volunteering'''", instead of WHY wordplay like "'''We Hydrate You'''", "'''Why Hydrate Yourself?'''" or "'''Wet Hackers, Yay!'''".
* Clip/Hook on the waterbootle was 3x smaller, making it unwieldy and difficult to connect. The MCH hook was bigger and easier to quick-connect.
* Drinking part had leak problems, which was not present on the previous bottle.
* The clip caused burn/melt-damage on the waterbottle, as can be seen when zooming in where the clip touches the orange waterbottle.
* No mate during buildup.
* No safe food, or unclear about the contents.
* Severe food safety issues in heaven. Bread toppings (including cheese and meat!) left open on a table outside of a fridge for hours, even overnight, with insects roaming around. No proper cleaning agents or supplies available for cleaning surfaces like tables, only some random supermarket cleaning sprays (this is not good enough for a central eating area!).
* Vegan food availability was unclear and could not be relied on. At times, the "vegan options" were completely inadequate for actually keeping people fed while doing potentially physically intensive volunteer work, with lacking nutritional value. Problem persisted during teardown. "We can't predict what the caterer will deliver" is not good enough for people with dietary restrictions.
* Heaven was too loud. It was almost impossible to communicate with people at the angel desk when there was a meal going on, and you had to practically yell to hear each other. Ideally sound dampening would be installed, but at least the eating area should be separated/insulated from the heaven desk and standby angel area in some way.

=== Warehouse ===
* When Boels screwed up, warehouse delivered us a replacement the same day.
- what did boels screw up?
* I appreciate being able to discuss the underlying requirements instead of automatically being handed a solution. When I asked for a bunch of extension cords, it turned out there was a better solution.
* Delivery service made camp a lot better for me as teamlead. I fixed several problems with one phone call and a happy angel heading out on a bike or gator!

=== Waste / garbage collection ===

* I have no knowledge about the state of recycling in NL, but having only separate bins for glass and then ones for everything else felt quite bad. At least separation of paper/carton would have made sense I guess. Also having separate containers where people could "donate" plastic bottles / metal cans which have deposit would have made sense and also could have brought a nice sum of money for the event.
* Field was nice and clean until teardown with enough containers to get rid of waste. (+1 for adding at least a paper and deposit container)

=== Teardown ===

* "No cars on the gras" policy: Villages that respected the rule of not driving on the grass were effectively disadvantaged. On Wednesday, many cars ignored the rule and drove onto the grass, which meant those villages didn’t have to carry their equipment over long distances. Meanwhile, villages that followed the rule had to transport their gear much farther, which was exhausting given the hot weather. Suggestion: Instead of creating a situation where following the rules feels like a disadvantage, we could reward compliance. For example, check which villages adhere to the rule, and if they do, give them vouchers for a priority ticket queue for the next event.
* Toilets were shut down too early making getting water during the warm teardown harder
* Transporting crates with empty bottles in hand trucks is also very unsafe. If they fall over it would be a mess for barefooted people. Bringing them in and out with cars is much safer.
* Way too many people left a day early. That was a bit sad. For everyone reading this: stay the entire camp ;)
* We should communicate better that flags and other deco is there for the event and should not disappear during the event. Previous events and other events by other parties may have 'trained' our visitors to think they are helping out by removing such decoration early. It was a bit sad to see people rip things of the waste gator. They got told off. But the flags on the main road disappeared on day 2 of camp, and that was entirely unwarranted.
* Remove toilet accessories (paper/soap/brushes) beofore toilets are removed, otherwise they get dumped out on the field.
* Remove zipties of the main tents before tearing the tents down, the tent guys just cut them and leave them on the field.
* Not enough hi-vis vests available, which is especially unsafe when heavy machinery is roaming the site.

Feedback

2025-08-18T09:13:01Z

Bas: /* POC / DECT / Fieldphones */

'''What Hackers Yearn''' for is to '''Improve'''. This page is dedicated to collecting user feedback related to the execution of WHY2025 as a whole. Constructive feedback is invaluable to the continuous improvement of the project and is welcomed from all participants. Please share your observations and suggestions in a '''clear and respectful manner'''. Your input will help guide enhancements for future generations of the event.

It is also possible to send feedback to [http://mailto:2029@why2025.org 2029@why2025.org]

== IMPORTANT ==

Do '''NOT''' review '''people'''. Any individual interaction you had with a human does not belong here, but should be taken up with [[Team:Cohesion]].

This page is strictly for addressing improvements for the next event. We encourage contributors to maintain a neutral, factual, and calm tone in their feedback.

* GOOD EXAMPLES: "Excessive mud at showers", "Food vendors often refused to accept WHY-voucher", or "Limited drop-off points for luggage shuttle".

* BAD EXAMPLES: "Person XXX was insulting me", "Helpdesk XOC was too busy to help", "frickin hot", "So the story begins on Saturday night at 23:04 when..."

== Feedback List ==

=== General / overall ===

* There should be a clear single method/channel of communication from orga, using the Heaven signal chat or social media for this is not ideal
** +1

=== Arrival / departure / parking / train shuttle / luggage shuttle ===

* On day 0 we queued to drive onto the field. We said said we had stuff for two different villages at opposite ends of the site, named the villages and showed them on map print outs. This information was accepted by a dispatcher. However, the bicycle guide refused to guide us to the second location, claiming it was impossible to get there. This is somewhat surprising, since others had been able to drive to that location before. It seemed there was a informational mismatch between dispatch and bicyle guide. (Both locations were accessible by asphalt roads.)
* train shuttle worked well, good job!

=== Badge ===

* Badge handouts were announced right before they happened which didn't allow people to plan their angel shifts and disrupted talks / workshops. A virtual queue would have fixed this and required less total manhours to organize / manage. +1

* There was an expectation that the badge was and I quote from what I have overheard "included in the price". This is not the case and has never been the case but it’s not clearly communicated. To my understanding there was a surplus at SHA2017 and MCH2022 so there never was a shortage of badges before which may have contributed.
** The above is misinformation: It was in fact communicated in written form that every attendee with a ticket receives a badge. The badge could not be ordered separately and was included in the ticket price.

* During the event (AFAIK) there were no badge angel shifts outside of queue angel. This is a chance from prior events and didn't allow people who normally would have helped to help in the same way.

* Due to the badges not being self-powered nor being distributed at the entrance they failed to function as badges. The SHA2017 badge was designed with having no power yet still being a nametag in mind. The WHY2025 badge did not seem to function as a nametag which should have been its intended design goal.

* At MCH and SHA you had people using the badges at the event itself to make games / hack / learn / teach. It was something which brought people together. There was very little being done / to do with the badge during the camp, not just because of the late arrival and limited distribution but rather because there is no way to get apps on the badge outside of the SD card... or if there is a way of doing so then its not documented on the wiki page as of writing. There was no app store app, no way to use the LORA hardware, and outside the event its impossible to use the badge without reflashing a new wifi SSID.

* You could not sit at the badge tent and solder on your antenna onto the badge or work on projects. At SHA and MCH you could just approach the badge people / angels and even get help with projects.

* Badge still has way too limited documentation to even work on it after the event.

* Team Badge have overworked themselves to get a badge available. Team over Badge next time. Which is also a Team:Cohesion issue.

* Would have been great to have a separate queue for villages that collected tickets and pick up 15+ badges at the same time. This would also have greatly reduced waiting times for individuals picking up badges and sped-up the whole process.

* Not enough badges for all visitors (not even close apparently).

* Badge queues were very long and poorly managed. This made it impossible for some people to collected a badge (for example because they cannot stand that long, require shade, have to take care of children, need to go to their next angel shift, etc.)

* The communication about the badge status was very sparse and lacking. If there is a problem, '''communicate''' about it and tell participants what to expect.

** +1. I am sympathetic to the team scrambling to get stuff done under difficult constraints, but especially in such cases good communication is important. Things like randomly posting a link to a page about the keyboard hardware felt frustrating when we were just waiting for more info about future handouts. In addition, a Signal group was a poor choice of channel for announcements for many reasons - no public access, no history for new joiners, redundant join/leave messages, etc. Keeping updates to a section on the wiki and/or a mailing list would've worked much better.

* During build-up, almost all other teams were scrambling to find a pair of hands to get essential stuff done, while watching lots of people pouring epoxy in the badge tent. Which was, lemme me blunt here, one of the lowest priority of all the things that have been done during build-up.

=== Bars and food court ===

* Menu was much longer and more complex compared to MCH. A lot of items were almost never sold, like nachos and chips.
* Slight differences in the menu between the bars caused customers to ask "Do you have ...?". Also complicates restocking logistics.
* The amount of Rum in the "Tschunk" was '''halved''' without updating the price. They decided it was better to modify the recipe to make it almost non-alcoholic, rather than say "Sorry, we're out."
** +1, the Tschunk contained barely any Rum.
* Bar is not a Merch Store, "Special/Ceremonial Cup" should be sold in Infodesk. It was also badly advertised, only people who "knew" of its existence could buy it. +1
* How was the cup not a deposit... I didn't even realize you wouldn't get any money back. Made it extremely bothersome to buy drinks for other people. +1
* Why wasn't statiegeld/pfand collected? Many glass bins full of mate-bottles. I don't want to know how many plastic bottles and aluminium cans were thrown out. This could have been prevented.
* No Club Mate Beere?
* No normal (0.5L) bottles available on the last day?
* Do we get mate from the source, or a Dutch overprices company?
* No mate during buildup again?
* Not written instructions for angels. The “game of telephone” style handing of incorrect instructions down from one angel to the next caused food to be prepared incorrectly. Written instructions should be posted right at the frier and microwave.
** +1
* Handling of vegan food was bad. Burger stall incorrectly advertised vegetarian burger as "vegan" originally, and could not provide any vegan burger at all because the buns contained milk(!). Fries/snacks stall staff did not know what they were selling or what it contained, and communication was difficult. Only positive note goes to the pasta stall where the food was good, and the operator was highly competent and knew exactly what they were selling (I would like to see them at a next event).
* Bottle collection procedure was very unclear.
* To add to the above: between bar and foodcourt no crates in sight on several days. No crates at any of the waste collection points. No instructions or procedure arranged. So people grabbed the glass-waste bin from the showers and put it in the middle. End result: 24x 240L glass trash bin completely filled to the brim. Assuming roughly around 5000 pfand-bottles (Mate, beer etc) were trashed. And team Waste had a ton of heavy lifting to get all these bins off the field and back to the recycling company. This could have been prevented.
* The same with plastic bottles and cans. Team Waste managed to save a *trailer* full of cans and bottles. About 24 big bags (240L). That could easily have been double. And if people actually organized it, it would have been less work.

=== Cohesion ===
* I like the idea, but not the implementation: Geraffel was put at the arse end of the field (OK fine, epicenter of noise gradient and all that), then got told off for playing music during the day.
* Very little communication/information. People barely knew the team existed and could be contacted, social rules like the Photo Policy were not communicated and very widely ignored. Other events signpost these things all over the site and it does help

=== Content / talks / heralds / speakerdesk / AV / recordings ===

* Party Stage was the perfect location for the "History of Hardcore" talk. More 'serious' talks could be held on the music stages at events going forward.

=== CTF / token game ===

=== Decoration / design ===

* Team did an amazing job. The field felt welcoming and interesting. Thank you so much for all the effort that went in. +1
* Next time we need to find a sponsor to print flags for all visitors, and have it available as merch for purchase. It was sad to see so much deco being liberated too early in the event. We need to also work on the communication around this.

=== Family / kids ===

=== Finance / coins / payments ===

* Like the concept of an anonymous payment card that '''just works'''. Absolutely love the design of the WHY2025 card. And very happy to play with a blank Ultralight AES card afterwards.
* option for payout of remaining funds wasn't communicated properly (even the website claimed it wasn't possible at all). Cash payout would be nice, but would understandably be a big extra thing to manage

=== Information / infodesk / wiki ===

* The wiki seems to have never been updated after the event started. I have attempted to find information about something several times and ''none'' of those times was it on the wiki. Instead everything seemed to be in random Signal groups and wherever else, that I didn't even know about until much later.
* It was very hard to find information on anything (like infrastructure, badge handouts, etc.) in general, and even infodesk angels often didn't have the answers.

=== Merchandise ===
* It would have been nice if the merch that was ordered months ago would have actually been available at the field.
* Flags as preordered merchandise. Would create the possibility for hackerspaces and individuals to bring back home some of them. +2

=== NOC / Network ===
* From buildup, through the event, through teardown: the networks worked!
* It was a pleasure to work together, to deduplicate work and equipment.
* In our location, Wifi coverage was poor although we were next to a Datenklo

=== NUTS / power / water ===

* Showers with adjustable heat (showerheads which mix cold and hot water) to avoid burns.
* Wood pallets outside both showers and toilets to reduce mud. (+1, from day zero would have been helpful)
* Even if not in all bathroom points, more drinking water points other than the one in heaven should have been available from the beginning. +1
* Disable the watertaps at the same time as all the other bathroom facilities. Or communicate when the water is going out. Now villages were only able to fill small containers at the toilets. Or needed to walk all the way to Heaven.
* Slightly more cleaning would have been great. The showers were extremely full of mud even inside at times. Given they only used a hose as far as I saw, should have been possible to also have some angels do this in addition to the cleaning crew.
* Adding hooks to the showers was a very welcome addition, thanks!
* It wasn't clear where to get drinking water during the first few days. This should be communicated better, e.g. with signs and on the map. +1
* I liked the number of toilets: never had to wait +1
* furthermore, the toilets seemed to be cleaned often which is good. +1
* There always was toilet paper available in the stalls, greatly lessens anxiety. +1
* water pressure and temperature in the showers was great! Also: never had to wait, which is great! +1
* There always was plenty of soap available at the sinks, during peak time and at night. +1
* Dedicated dishwashing location. +1
* More drinking water fountains across the terrain
* "upgrading" facilities to "drinking water" is questionable. What of all the potential risks was actually tested and could be guaranteed? Separate 100% clear drinking water spots would be better -1
* Shower temperature constantly fluctuated and never stabilized

=== Off-site logistics ===

=== On-site logistics ===

=== POC / DECT / Fieldphones ===
* micropoc worked just fine: I could easily and quickly register the DECT phones for my village and the network worked whenever I wanted to use it.
* Having the DECT so people can reach my team was as always: amazing. Thank you. Feature request: have a phone number only operational during business hours (and redirect to a prerecorded thing other times). Fixed that ourselves by switching the dect to silent. But would be a cool feature.

=== Productiehuis / C3VOC ===

=== Projectleiding ===

=== ROC ===
* Very clear audio and reception

=== Safety / security / first aid / fire ===

=== Supermarket ===

=== Sysadmin ===

* Setup "live.why2025.org" as an alias for people to easier find the livestreams next time. Right now you needed to go to "streaming.media.ccc.de/why2025".
* IRC is less popular in new generations of hackers and at least Mastodon+Matrix integrations would have made Signal angel role useful.

=== Terrain ===

* Noise gradient should be evaluated better: the main party stage was more audible from the family village than from the Belgian cluster, which was way closer.
* Fridge container orientation: the compressor should point away from campers, it was the single most noisy item from Batavus On tour village point of view.
* Infodesk not located at the entrance like at MCH, causing it to be less visible.
* 4000 people but only a single "Hardware Hacking Tent". It was constantly full, and no other places to sit and solder.
** Plenty villages that'll happily let you use their spaces. It makes sense for this kind of thing to be community-provided (the Hardware Hacking Tent was too - while a official workshop spot, it only exists because of of the HHA team willing to equip and run it)
* "Hackcenter" only had space for 20 people, tiny tent, zero cooling, and no advertisement. Not even a sign... We thought it was someone's Village until day 4.
* No place to party/music all night. It would be cool to have a distant (from tents) area where we're allowed to have music going all night long.
** -1, loud music anywhere on the field travels far and I appreciate being able to sleep. I liked the 23:00 cutoff.
** -1 agreed. "distant" location is not really possible on-site
** +1 AGREE, the noise cutoff was really annoying, other events the music continues until 2am atleast, I don't see why we can't have somewhere on site where we can play music at a reasonable volume. 23:00 is too early for a festival.
** +1, made the event substancially worse, if we have color-coded fields to match volume levels why do we still have to shut the music down completely at 23:00 in the red area?
** -1, i was very happy to have a camp where i could sleep without earplugs. Also it would be impossible due to very strict permits this time around.
*** also this was not followed on the last night after closing in which the angel party continued in the main bar until very late???? have some consistency please. it just feels mean otherwise.

* it was nice that noise rules were followed quite well this time (unlike e.g. MCH where main stages switched to silent disco while sponsors kept blaring music into the silent areas)

* I missed routing signs for bikes coming in. Google Maps got me to the wooden bridge which was fenced off, and nobody there to either let me in or give me a hint. I may have let myself in at that fence, because it was very unclear which detour to take. The climb was only moderately scary.
* Seperate smoking and non-smoking fields, designated smoking areas away from event spaces. A blanket ban on smoking and vaping for the entire event is probably not feasible (unfortunately).

=== Tickets / entrance ===
* Putting the desks on the other side might have looked more welcoming, but all was fine for my check-in.
* Camper tickets were not scanned?

=== Villages ===
* Well done! And it was fun to help out villages doing extra luggage shuttles after we were done doing Waste stuff.

=== Volunteering / angels / heaven===

* Food tickets given to volunteers expiring, without any communication of them doing so.

[[File:Angel Waterbottle Comparison WHY vs MCH.jpg|thumb|Angle Waterbottle Comparison WHY vs MCH]]

* Waterbottle had boring text "'''Thanks For Volunteering'''", instead of WHY wordplay like "'''We Hydrate You'''", "'''Why Hydrate Yourself?'''" or "'''Wet Hackers, Yay!'''".
* Clip/Hook on the waterbootle was 3x smaller, making it unwieldy and difficult to connect. The MCH hook was bigger and easier to quick-connect.
* Drinking part had leak problems, which was not present on the previous bottle.
* The clip caused burn/melt-damage on the waterbottle, as can be seen when zooming in where the clip touches the orange waterbottle.
* No mate during buildup.
* No safe food, or unclear about the contents.
* Severe food safety issues in heaven. Bread toppings (including cheese and meat!) left open on a table outside of a fridge for hours, even overnight, with insects roaming around. No proper cleaning agents or supplies available for cleaning surfaces like tables, only some random supermarket cleaning sprays (this is not good enough for a central eating area!).
* Vegan food availability was unclear and could not be relied on. At times, the "vegan options" were completely inadequate for actually keeping people fed while doing potentially physically intensive volunteer work, with lacking nutritional value. Problem persisted during teardown. "We can't predict what the caterer will deliver" is not good enough for people with dietary restrictions.
* Heaven was too loud. It was almost impossible to communicate with people at the angel desk when there was a meal going on, and you had to practically yell to hear each other. Ideally sound dampening would be installed, but at least the eating area should be separated/insulated from the heaven desk and standby angel area in some way.

=== Warehouse ===
* When Boels screwed up, warehouse delivered us a replacement the same day.
- what did boels screw up?
* I appreciate being able to discuss the underlying requirements instead of automatically being handed a solution. When I asked for a bunch of extension cords, it turned out there was a better solution.
* Delivery service made camp a lot better for me as teamlead. I fixed several problems with one phone call and a happy angel heading out on a bike or gator!

=== Waste / garbage collection ===

* I have no knowledge about the state of recycling in NL, but having only separate bins for glass and then ones for everything else felt quite bad. At least separation of paper/carton would have made sense I guess. Also having separate containers where people could "donate" plastic bottles / metal cans which have deposit would have made sense and also could have brought a nice sum of money for the event.
* Field was nice and clean until teardown with enough containers to get rid of waste. (+1 for adding at least a paper and deposit container)

=== Teardown ===

* "No cars on the gras" policy: Villages that respected the rule of not driving on the grass were effectively disadvantaged. On Wednesday, many cars ignored the rule and drove onto the grass, which meant those villages didn’t have to carry their equipment over long distances. Meanwhile, villages that followed the rule had to transport their gear much farther, which was exhausting given the hot weather. Suggestion: Instead of creating a situation where following the rules feels like a disadvantage, we could reward compliance. For example, check which villages adhere to the rule, and if they do, give them vouchers for a priority ticket queue for the next event.
* Toilets were shut down too early making getting water during the warm teardown harder
* Transporting crates with empty bottles in hand trucks is also very unsafe. If they fall over it would be a mess for barefooted people. Bringing them in and out with cars is much safer.
* Way too many people left a day early. That was a bit sad. For everyone reading this: stay the entire camp ;)
* We should communicate better that flags and other deco is there for the event and should not disappear during the event. Previous events and other events by other parties may have 'trained' our visitors to think they are helping out by removing such decoration early. It was a bit sad to see people rip things of the waste gator. They got told off. But the flags on the main road disappeared on day 2 of camp, and that was entirely unwarranted.
* Remove toilet accessories (paper/soap/brushes) beofore toilets are removed, otherwise they get dumped out on the field.
* Remove zipties of the main tents before tearing the tents down, the tent guys just cut them and leave them on the field.

Feedback

2025-08-18T09:11:33Z

Bas: /* Warehouse */

'''What Hackers Yearn''' for is to '''Improve'''. This page is dedicated to collecting user feedback related to the execution of WHY2025 as a whole. Constructive feedback is invaluable to the continuous improvement of the project and is welcomed from all participants. Please share your observations and suggestions in a '''clear and respectful manner'''. Your input will help guide enhancements for future generations of the event.

It is also possible to send feedback to [http://mailto:2029@why2025.org 2029@why2025.org]

== IMPORTANT ==

Do '''NOT''' review '''people'''. Any individual interaction you had with a human does not belong here, but should be taken up with [[Team:Cohesion]].

This page is strictly for addressing improvements for the next event. We encourage contributors to maintain a neutral, factual, and calm tone in their feedback.

* GOOD EXAMPLES: "Excessive mud at showers", "Food vendors often refused to accept WHY-voucher", or "Limited drop-off points for luggage shuttle".

* BAD EXAMPLES: "Person XXX was insulting me", "Helpdesk XOC was too busy to help", "frickin hot", "So the story begins on Saturday night at 23:04 when..."

== Feedback List ==

=== General / overall ===

* There should be a clear single method/channel of communication from orga, using the Heaven signal chat or social media for this is not ideal
** +1

=== Arrival / departure / parking / train shuttle / luggage shuttle ===

* On day 0 we queued to drive onto the field. We said said we had stuff for two different villages at opposite ends of the site, named the villages and showed them on map print outs. This information was accepted by a dispatcher. However, the bicycle guide refused to guide us to the second location, claiming it was impossible to get there. This is somewhat surprising, since others had been able to drive to that location before. It seemed there was a informational mismatch between dispatch and bicyle guide. (Both locations were accessible by asphalt roads.)
* train shuttle worked well, good job!

=== Badge ===

* Badge handouts were announced right before they happened which didn't allow people to plan their angel shifts and disrupted talks / workshops. A virtual queue would have fixed this and required less total manhours to organize / manage. +1

* There was an expectation that the badge was and I quote from what I have overheard "included in the price". This is not the case and has never been the case but it’s not clearly communicated. To my understanding there was a surplus at SHA2017 and MCH2022 so there never was a shortage of badges before which may have contributed.
** The above is misinformation: It was in fact communicated in written form that every attendee with a ticket receives a badge. The badge could not be ordered separately and was included in the ticket price.

* During the event (AFAIK) there were no badge angel shifts outside of queue angel. This is a chance from prior events and didn't allow people who normally would have helped to help in the same way.

* Due to the badges not being self-powered nor being distributed at the entrance they failed to function as badges. The SHA2017 badge was designed with having no power yet still being a nametag in mind. The WHY2025 badge did not seem to function as a nametag which should have been its intended design goal.

* At MCH and SHA you had people using the badges at the event itself to make games / hack / learn / teach. It was something which brought people together. There was very little being done / to do with the badge during the camp, not just because of the late arrival and limited distribution but rather because there is no way to get apps on the badge outside of the SD card... or if there is a way of doing so then its not documented on the wiki page as of writing. There was no app store app, no way to use the LORA hardware, and outside the event its impossible to use the badge without reflashing a new wifi SSID.

* You could not sit at the badge tent and solder on your antenna onto the badge or work on projects. At SHA and MCH you could just approach the badge people / angels and even get help with projects.

* Badge still has way too limited documentation to even work on it after the event.

* Team Badge have overworked themselves to get a badge available. Team over Badge next time. Which is also a Team:Cohesion issue.

* Would have been great to have a separate queue for villages that collected tickets and pick up 15+ badges at the same time. This would also have greatly reduced waiting times for individuals picking up badges and sped-up the whole process.

* Not enough badges for all visitors (not even close apparently).

* Badge queues were very long and poorly managed. This made it impossible for some people to collected a badge (for example because they cannot stand that long, require shade, have to take care of children, need to go to their next angel shift, etc.)

* The communication about the badge status was very sparse and lacking. If there is a problem, '''communicate''' about it and tell participants what to expect.

** +1. I am sympathetic to the team scrambling to get stuff done under difficult constraints, but especially in such cases good communication is important. Things like randomly posting a link to a page about the keyboard hardware felt frustrating when we were just waiting for more info about future handouts. In addition, a Signal group was a poor choice of channel for announcements for many reasons - no public access, no history for new joiners, redundant join/leave messages, etc. Keeping updates to a section on the wiki and/or a mailing list would've worked much better.

* During build-up, almost all other teams were scrambling to find a pair of hands to get essential stuff done, while watching lots of people pouring epoxy in the badge tent. Which was, lemme me blunt here, one of the lowest priority of all the things that have been done during build-up.

=== Bars and food court ===

* Menu was much longer and more complex compared to MCH. A lot of items were almost never sold, like nachos and chips.
* Slight differences in the menu between the bars caused customers to ask "Do you have ...?". Also complicates restocking logistics.
* The amount of Rum in the "Tschunk" was '''halved''' without updating the price. They decided it was better to modify the recipe to make it almost non-alcoholic, rather than say "Sorry, we're out."
** +1, the Tschunk contained barely any Rum.
* Bar is not a Merch Store, "Special/Ceremonial Cup" should be sold in Infodesk. It was also badly advertised, only people who "knew" of its existence could buy it. +1
* How was the cup not a deposit... I didn't even realize you wouldn't get any money back. Made it extremely bothersome to buy drinks for other people. +1
* Why wasn't statiegeld/pfand collected? Many glass bins full of mate-bottles. I don't want to know how many plastic bottles and aluminium cans were thrown out. This could have been prevented.
* No Club Mate Beere?
* No normal (0.5L) bottles available on the last day?
* Do we get mate from the source, or a Dutch overprices company?
* No mate during buildup again?
* Not written instructions for angels. The “game of telephone” style handing of incorrect instructions down from one angel to the next caused food to be prepared incorrectly. Written instructions should be posted right at the frier and microwave.
** +1
* Handling of vegan food was bad. Burger stall incorrectly advertised vegetarian burger as "vegan" originally, and could not provide any vegan burger at all because the buns contained milk(!). Fries/snacks stall staff did not know what they were selling or what it contained, and communication was difficult. Only positive note goes to the pasta stall where the food was good, and the operator was highly competent and knew exactly what they were selling (I would like to see them at a next event).
* Bottle collection procedure was very unclear.
* To add to the above: between bar and foodcourt no crates in sight on several days. No crates at any of the waste collection points. No instructions or procedure arranged. So people grabbed the glass-waste bin from the showers and put it in the middle. End result: 24x 240L glass trash bin completely filled to the brim. Assuming roughly around 5000 pfand-bottles (Mate, beer etc) were trashed. And team Waste had a ton of heavy lifting to get all these bins off the field and back to the recycling company. This could have been prevented.
* The same with plastic bottles and cans. Team Waste managed to save a *trailer* full of cans and bottles. About 24 big bags (240L). That could easily have been double. And if people actually organized it, it would have been less work.

=== Cohesion ===
* I like the idea, but not the implementation: Geraffel was put at the arse end of the field (OK fine, epicenter of noise gradient and all that), then got told off for playing music during the day.
* Very little communication/information. People barely knew the team existed and could be contacted, social rules like the Photo Policy were not communicated and very widely ignored. Other events signpost these things all over the site and it does help

=== Content / talks / heralds / speakerdesk / AV / recordings ===

* Party Stage was the perfect location for the "History of Hardcore" talk. More 'serious' talks could be held on the music stages at events going forward.

=== CTF / token game ===

=== Decoration / design ===

* Team did an amazing job. The field felt welcoming and interesting. Thank you so much for all the effort that went in. +1
* Next time we need to find a sponsor to print flags for all visitors, and have it available as merch for purchase. It was sad to see so much deco being liberated too early in the event. We need to also work on the communication around this.

=== Family / kids ===

=== Finance / coins / payments ===

* Like the concept of an anonymous payment card that '''just works'''. Absolutely love the design of the WHY2025 card. And very happy to play with a blank Ultralight AES card afterwards.
* option for payout of remaining funds wasn't communicated properly (even the website claimed it wasn't possible at all). Cash payout would be nice, but would understandably be a big extra thing to manage

=== Information / infodesk / wiki ===

* The wiki seems to have never been updated after the event started. I have attempted to find information about something several times and ''none'' of those times was it on the wiki. Instead everything seemed to be in random Signal groups and wherever else, that I didn't even know about until much later.
* It was very hard to find information on anything (like infrastructure, badge handouts, etc.) in general, and even infodesk angels often didn't have the answers.

=== Merchandise ===
* It would have been nice if the merch that was ordered months ago would have actually been available at the field.
* Flags as preordered merchandise. Would create the possibility for hackerspaces and individuals to bring back home some of them. +2

=== NOC / Network ===
* From buildup, through the event, through teardown: the networks worked!
* It was a pleasure to work together, to deduplicate work and equipment.
* In our location, Wifi coverage was poor although we were next to a Datenklo

=== NUTS / power / water ===

* Showers with adjustable heat (showerheads which mix cold and hot water) to avoid burns.
* Wood pallets outside both showers and toilets to reduce mud. (+1, from day zero would have been helpful)
* Even if not in all bathroom points, more drinking water points other than the one in heaven should have been available from the beginning. +1
* Disable the watertaps at the same time as all the other bathroom facilities. Or communicate when the water is going out. Now villages were only able to fill small containers at the toilets. Or needed to walk all the way to Heaven.
* Slightly more cleaning would have been great. The showers were extremely full of mud even inside at times. Given they only used a hose as far as I saw, should have been possible to also have some angels do this in addition to the cleaning crew.
* Adding hooks to the showers was a very welcome addition, thanks!
* It wasn't clear where to get drinking water during the first few days. This should be communicated better, e.g. with signs and on the map. +1
* I liked the number of toilets: never had to wait +1
* furthermore, the toilets seemed to be cleaned often which is good. +1
* There always was toilet paper available in the stalls, greatly lessens anxiety. +1
* water pressure and temperature in the showers was great! Also: never had to wait, which is great! +1
* There always was plenty of soap available at the sinks, during peak time and at night. +1
* Dedicated dishwashing location. +1
* More drinking water fountains across the terrain
* "upgrading" facilities to "drinking water" is questionable. What of all the potential risks was actually tested and could be guaranteed? Separate 100% clear drinking water spots would be better -1
* Shower temperature constantly fluctuated and never stabilized

=== Off-site logistics ===

=== On-site logistics ===

=== POC / DECT / Fieldphones ===
* micropoc worked just fine: I could easily and quickly register the DECT phones for my village and the network worked whenever I wanted to use it.

=== Productiehuis / C3VOC ===

=== Projectleiding ===

=== ROC ===
* Very clear audio and reception

=== Safety / security / first aid / fire ===

=== Supermarket ===

=== Sysadmin ===

* Setup "live.why2025.org" as an alias for people to easier find the livestreams next time. Right now you needed to go to "streaming.media.ccc.de/why2025".
* IRC is less popular in new generations of hackers and at least Mastodon+Matrix integrations would have made Signal angel role useful.

=== Terrain ===

* Noise gradient should be evaluated better: the main party stage was more audible from the family village than from the Belgian cluster, which was way closer.
* Fridge container orientation: the compressor should point away from campers, it was the single most noisy item from Batavus On tour village point of view.
* Infodesk not located at the entrance like at MCH, causing it to be less visible.
* 4000 people but only a single "Hardware Hacking Tent". It was constantly full, and no other places to sit and solder.
** Plenty villages that'll happily let you use their spaces. It makes sense for this kind of thing to be community-provided (the Hardware Hacking Tent was too - while a official workshop spot, it only exists because of of the HHA team willing to equip and run it)
* "Hackcenter" only had space for 20 people, tiny tent, zero cooling, and no advertisement. Not even a sign... We thought it was someone's Village until day 4.
* No place to party/music all night. It would be cool to have a distant (from tents) area where we're allowed to have music going all night long.
** -1, loud music anywhere on the field travels far and I appreciate being able to sleep. I liked the 23:00 cutoff.
** -1 agreed. "distant" location is not really possible on-site
** +1 AGREE, the noise cutoff was really annoying, other events the music continues until 2am atleast, I don't see why we can't have somewhere on site where we can play music at a reasonable volume. 23:00 is too early for a festival.
** +1, made the event substancially worse, if we have color-coded fields to match volume levels why do we still have to shut the music down completely at 23:00 in the red area?
** -1, i was very happy to have a camp where i could sleep without earplugs. Also it would be impossible due to very strict permits this time around.
*** also this was not followed on the last night after closing in which the angel party continued in the main bar until very late???? have some consistency please. it just feels mean otherwise.

* it was nice that noise rules were followed quite well this time (unlike e.g. MCH where main stages switched to silent disco while sponsors kept blaring music into the silent areas)

* I missed routing signs for bikes coming in. Google Maps got me to the wooden bridge which was fenced off, and nobody there to either let me in or give me a hint. I may have let myself in at that fence, because it was very unclear which detour to take. The climb was only moderately scary.
* Seperate smoking and non-smoking fields, designated smoking areas away from event spaces. A blanket ban on smoking and vaping for the entire event is probably not feasible (unfortunately).

=== Tickets / entrance ===
* Putting the desks on the other side might have looked more welcoming, but all was fine for my check-in.
* Camper tickets were not scanned?

=== Villages ===
* Well done! And it was fun to help out villages doing extra luggage shuttles after we were done doing Waste stuff.

=== Volunteering / angels / heaven===

* Food tickets given to volunteers expiring, without any communication of them doing so.

[[File:Angel Waterbottle Comparison WHY vs MCH.jpg|thumb|Angle Waterbottle Comparison WHY vs MCH]]

* Waterbottle had boring text "'''Thanks For Volunteering'''", instead of WHY wordplay like "'''We Hydrate You'''", "'''Why Hydrate Yourself?'''" or "'''Wet Hackers, Yay!'''".
* Clip/Hook on the waterbootle was 3x smaller, making it unwieldy and difficult to connect. The MCH hook was bigger and easier to quick-connect.
* Drinking part had leak problems, which was not present on the previous bottle.
* The clip caused burn/melt-damage on the waterbottle, as can be seen when zooming in where the clip touches the orange waterbottle.
* No mate during buildup.
* No safe food, or unclear about the contents.
* Severe food safety issues in heaven. Bread toppings (including cheese and meat!) left open on a table outside of a fridge for hours, even overnight, with insects roaming around. No proper cleaning agents or supplies available for cleaning surfaces like tables, only some random supermarket cleaning sprays (this is not good enough for a central eating area!).
* Vegan food availability was unclear and could not be relied on. At times, the "vegan options" were completely inadequate for actually keeping people fed while doing potentially physically intensive volunteer work, with lacking nutritional value. Problem persisted during teardown. "We can't predict what the caterer will deliver" is not good enough for people with dietary restrictions.

=== Warehouse ===
* When Boels screwed up, warehouse delivered us a replacement the same day.
- what did boels screw up?
* I appreciate being able to discuss the underlying requirements instead of automatically being handed a solution. When I asked for a bunch of extension cords, it turned out there was a better solution.
* Delivery service made camp a lot better for me as teamlead. I fixed several problems with one phone call and a happy angel heading out on a bike or gator!

=== Waste / garbage collection ===

* I have no knowledge about the state of recycling in NL, but having only separate bins for glass and then ones for everything else felt quite bad. At least separation of paper/carton would have made sense I guess. Also having separate containers where people could "donate" plastic bottles / metal cans which have deposit would have made sense and also could have brought a nice sum of money for the event.
* Field was nice and clean until teardown with enough containers to get rid of waste. (+1 for adding at least a paper and deposit container)

=== Teardown ===

* "No cars on the gras" policy: Villages that respected the rule of not driving on the grass were effectively disadvantaged. On Wednesday, many cars ignored the rule and drove onto the grass, which meant those villages didn’t have to carry their equipment over long distances. Meanwhile, villages that followed the rule had to transport their gear much farther, which was exhausting given the hot weather. Suggestion: Instead of creating a situation where following the rules feels like a disadvantage, we could reward compliance. For example, check which villages adhere to the rule, and if they do, give them vouchers for a priority ticket queue for the next event.
* Toilets were shut down too early making getting water during the warm teardown harder
* Transporting crates with empty bottles in hand trucks is also very unsafe. If they fall over it would be a mess for barefooted people. Bringing them in and out with cars is much safer.
* Way too many people left a day early. That was a bit sad. For everyone reading this: stay the entire camp ;)
* We should communicate better that flags and other deco is there for the event and should not disappear during the event. Previous events and other events by other parties may have 'trained' our visitors to think they are helping out by removing such decoration early. It was a bit sad to see people rip things of the waste gator. They got told off. But the flags on the main road disappeared on day 2 of camp, and that was entirely unwarranted.

Feedback

2025-08-18T09:10:16Z

Bas: /* Bars and food court */

'''What Hackers Yearn''' for is to '''Improve'''. This page is dedicated to collecting user feedback related to the execution of WHY2025 as a whole. Constructive feedback is invaluable to the continuous improvement of the project and is welcomed from all participants. Please share your observations and suggestions in a '''clear and respectful manner'''. Your input will help guide enhancements for future generations of the event.

It is also possible to send feedback to [http://mailto:2029@why2025.org 2029@why2025.org]

== IMPORTANT ==

Do '''NOT''' review '''people'''. Any individual interaction you had with a human does not belong here, but should be taken up with [[Team:Cohesion]].

This page is strictly for addressing improvements for the next event. We encourage contributors to maintain a neutral, factual, and calm tone in their feedback.

* GOOD EXAMPLES: "Excessive mud at showers", "Food vendors often refused to accept WHY-voucher", or "Limited drop-off points for luggage shuttle".

* BAD EXAMPLES: "Person XXX was insulting me", "Helpdesk XOC was too busy to help", "frickin hot", "So the story begins on Saturday night at 23:04 when..."

== Feedback List ==

=== General / overall ===

* There should be a clear single method/channel of communication from orga, using the Heaven signal chat or social media for this is not ideal
** +1

=== Arrival / departure / parking / train shuttle / luggage shuttle ===

* On day 0 we queued to drive onto the field. We said said we had stuff for two different villages at opposite ends of the site, named the villages and showed them on map print outs. This information was accepted by a dispatcher. However, the bicycle guide refused to guide us to the second location, claiming it was impossible to get there. This is somewhat surprising, since others had been able to drive to that location before. It seemed there was a informational mismatch between dispatch and bicyle guide. (Both locations were accessible by asphalt roads.)
* train shuttle worked well, good job!

=== Badge ===

* Badge handouts were announced right before they happened which didn't allow people to plan their angel shifts and disrupted talks / workshops. A virtual queue would have fixed this and required less total manhours to organize / manage. +1

* There was an expectation that the badge was and I quote from what I have overheard "included in the price". This is not the case and has never been the case but it’s not clearly communicated. To my understanding there was a surplus at SHA2017 and MCH2022 so there never was a shortage of badges before which may have contributed.
** The above is misinformation: It was in fact communicated in written form that every attendee with a ticket receives a badge. The badge could not be ordered separately and was included in the ticket price.

* During the event (AFAIK) there were no badge angel shifts outside of queue angel. This is a chance from prior events and didn't allow people who normally would have helped to help in the same way.

* Due to the badges not being self-powered nor being distributed at the entrance they failed to function as badges. The SHA2017 badge was designed with having no power yet still being a nametag in mind. The WHY2025 badge did not seem to function as a nametag which should have been its intended design goal.

* At MCH and SHA you had people using the badges at the event itself to make games / hack / learn / teach. It was something which brought people together. There was very little being done / to do with the badge during the camp, not just because of the late arrival and limited distribution but rather because there is no way to get apps on the badge outside of the SD card... or if there is a way of doing so then its not documented on the wiki page as of writing. There was no app store app, no way to use the LORA hardware, and outside the event its impossible to use the badge without reflashing a new wifi SSID.

* You could not sit at the badge tent and solder on your antenna onto the badge or work on projects. At SHA and MCH you could just approach the badge people / angels and even get help with projects.

* Badge still has way too limited documentation to even work on it after the event.

* Team Badge have overworked themselves to get a badge available. Team over Badge next time. Which is also a Team:Cohesion issue.

* Would have been great to have a separate queue for villages that collected tickets and pick up 15+ badges at the same time. This would also have greatly reduced waiting times for individuals picking up badges and sped-up the whole process.

* Not enough badges for all visitors (not even close apparently).

* Badge queues were very long and poorly managed. This made it impossible for some people to collected a badge (for example because they cannot stand that long, require shade, have to take care of children, need to go to their next angel shift, etc.)

* The communication about the badge status was very sparse and lacking. If there is a problem, '''communicate''' about it and tell participants what to expect.

** +1. I am sympathetic to the team scrambling to get stuff done under difficult constraints, but especially in such cases good communication is important. Things like randomly posting a link to a page about the keyboard hardware felt frustrating when we were just waiting for more info about future handouts. In addition, a Signal group was a poor choice of channel for announcements for many reasons - no public access, no history for new joiners, redundant join/leave messages, etc. Keeping updates to a section on the wiki and/or a mailing list would've worked much better.

* During build-up, almost all other teams were scrambling to find a pair of hands to get essential stuff done, while watching lots of people pouring epoxy in the badge tent. Which was, lemme me blunt here, one of the lowest priority of all the things that have been done during build-up.

=== Bars and food court ===

* Menu was much longer and more complex compared to MCH. A lot of items were almost never sold, like nachos and chips.
* Slight differences in the menu between the bars caused customers to ask "Do you have ...?". Also complicates restocking logistics.
* The amount of Rum in the "Tschunk" was '''halved''' without updating the price. They decided it was better to modify the recipe to make it almost non-alcoholic, rather than say "Sorry, we're out."
** +1, the Tschunk contained barely any Rum.
* Bar is not a Merch Store, "Special/Ceremonial Cup" should be sold in Infodesk. It was also badly advertised, only people who "knew" of its existence could buy it. +1
* How was the cup not a deposit... I didn't even realize you wouldn't get any money back. Made it extremely bothersome to buy drinks for other people. +1
* Why wasn't statiegeld/pfand collected? Many glass bins full of mate-bottles. I don't want to know how many plastic bottles and aluminium cans were thrown out. This could have been prevented.
* No Club Mate Beere?
* No normal (0.5L) bottles available on the last day?
* Do we get mate from the source, or a Dutch overprices company?
* No mate during buildup again?
* Not written instructions for angels. The “game of telephone” style handing of incorrect instructions down from one angel to the next caused food to be prepared incorrectly. Written instructions should be posted right at the frier and microwave.
** +1
* Handling of vegan food was bad. Burger stall incorrectly advertised vegetarian burger as "vegan" originally, and could not provide any vegan burger at all because the buns contained milk(!). Fries/snacks stall staff did not know what they were selling or what it contained, and communication was difficult. Only positive note goes to the pasta stall where the food was good, and the operator was highly competent and knew exactly what they were selling (I would like to see them at a next event).
* Bottle collection procedure was very unclear.
* To add to the above: between bar and foodcourt no crates in sight on several days. No crates at any of the waste collection points. No instructions or procedure arranged. So people grabbed the glass-waste bin from the showers and put it in the middle. End result: 24x 240L glass trash bin completely filled to the brim. Assuming roughly around 5000 pfand-bottles (Mate, beer etc) were trashed. And team Waste had a ton of heavy lifting to get all these bins off the field and back to the recycling company. This could have been prevented.
* The same with plastic bottles and cans. Team Waste managed to save a *trailer* full of cans and bottles. About 24 big bags (240L). That could easily have been double. And if people actually organized it, it would have been less work.

=== Cohesion ===
* I like the idea, but not the implementation: Geraffel was put at the arse end of the field (OK fine, epicenter of noise gradient and all that), then got told off for playing music during the day.
* Very little communication/information. People barely knew the team existed and could be contacted, social rules like the Photo Policy were not communicated and very widely ignored. Other events signpost these things all over the site and it does help

=== Content / talks / heralds / speakerdesk / AV / recordings ===

* Party Stage was the perfect location for the "History of Hardcore" talk. More 'serious' talks could be held on the music stages at events going forward.

=== CTF / token game ===

=== Decoration / design ===

* Team did an amazing job. The field felt welcoming and interesting. Thank you so much for all the effort that went in. +1
* Next time we need to find a sponsor to print flags for all visitors, and have it available as merch for purchase. It was sad to see so much deco being liberated too early in the event. We need to also work on the communication around this.

=== Family / kids ===

=== Finance / coins / payments ===

* Like the concept of an anonymous payment card that '''just works'''. Absolutely love the design of the WHY2025 card. And very happy to play with a blank Ultralight AES card afterwards.
* option for payout of remaining funds wasn't communicated properly (even the website claimed it wasn't possible at all). Cash payout would be nice, but would understandably be a big extra thing to manage

=== Information / infodesk / wiki ===

* The wiki seems to have never been updated after the event started. I have attempted to find information about something several times and ''none'' of those times was it on the wiki. Instead everything seemed to be in random Signal groups and wherever else, that I didn't even know about until much later.
* It was very hard to find information on anything (like infrastructure, badge handouts, etc.) in general, and even infodesk angels often didn't have the answers.

=== Merchandise ===
* It would have been nice if the merch that was ordered months ago would have actually been available at the field.
* Flags as preordered merchandise. Would create the possibility for hackerspaces and individuals to bring back home some of them. +2

=== NOC / Network ===
* From buildup, through the event, through teardown: the networks worked!
* It was a pleasure to work together, to deduplicate work and equipment.
* In our location, Wifi coverage was poor although we were next to a Datenklo

=== NUTS / power / water ===

* Showers with adjustable heat (showerheads which mix cold and hot water) to avoid burns.
* Wood pallets outside both showers and toilets to reduce mud. (+1, from day zero would have been helpful)
* Even if not in all bathroom points, more drinking water points other than the one in heaven should have been available from the beginning. +1
* Disable the watertaps at the same time as all the other bathroom facilities. Or communicate when the water is going out. Now villages were only able to fill small containers at the toilets. Or needed to walk all the way to Heaven.
* Slightly more cleaning would have been great. The showers were extremely full of mud even inside at times. Given they only used a hose as far as I saw, should have been possible to also have some angels do this in addition to the cleaning crew.
* Adding hooks to the showers was a very welcome addition, thanks!
* It wasn't clear where to get drinking water during the first few days. This should be communicated better, e.g. with signs and on the map. +1
* I liked the number of toilets: never had to wait +1
* furthermore, the toilets seemed to be cleaned often which is good. +1
* There always was toilet paper available in the stalls, greatly lessens anxiety. +1
* water pressure and temperature in the showers was great! Also: never had to wait, which is great! +1
* There always was plenty of soap available at the sinks, during peak time and at night. +1
* Dedicated dishwashing location. +1
* More drinking water fountains across the terrain
* "upgrading" facilities to "drinking water" is questionable. What of all the potential risks was actually tested and could be guaranteed? Separate 100% clear drinking water spots would be better -1
* Shower temperature constantly fluctuated and never stabilized

=== Off-site logistics ===

=== On-site logistics ===

=== POC / DECT / Fieldphones ===
* micropoc worked just fine: I could easily and quickly register the DECT phones for my village and the network worked whenever I wanted to use it.

=== Productiehuis / C3VOC ===

=== Projectleiding ===

=== ROC ===
* Very clear audio and reception

=== Safety / security / first aid / fire ===

=== Supermarket ===

=== Sysadmin ===

* Setup "live.why2025.org" as an alias for people to easier find the livestreams next time. Right now you needed to go to "streaming.media.ccc.de/why2025".
* IRC is less popular in new generations of hackers and at least Mastodon+Matrix integrations would have made Signal angel role useful.

=== Terrain ===

* Noise gradient should be evaluated better: the main party stage was more audible from the family village than from the Belgian cluster, which was way closer.
* Fridge container orientation: the compressor should point away from campers, it was the single most noisy item from Batavus On tour village point of view.
* Infodesk not located at the entrance like at MCH, causing it to be less visible.
* 4000 people but only a single "Hardware Hacking Tent". It was constantly full, and no other places to sit and solder.
** Plenty villages that'll happily let you use their spaces. It makes sense for this kind of thing to be community-provided (the Hardware Hacking Tent was too - while a official workshop spot, it only exists because of of the HHA team willing to equip and run it)
* "Hackcenter" only had space for 20 people, tiny tent, zero cooling, and no advertisement. Not even a sign... We thought it was someone's Village until day 4.
* No place to party/music all night. It would be cool to have a distant (from tents) area where we're allowed to have music going all night long.
** -1, loud music anywhere on the field travels far and I appreciate being able to sleep. I liked the 23:00 cutoff.
** -1 agreed. "distant" location is not really possible on-site
** +1 AGREE, the noise cutoff was really annoying, other events the music continues until 2am atleast, I don't see why we can't have somewhere on site where we can play music at a reasonable volume. 23:00 is too early for a festival.
** +1, made the event substancially worse, if we have color-coded fields to match volume levels why do we still have to shut the music down completely at 23:00 in the red area?
** -1, i was very happy to have a camp where i could sleep without earplugs. Also it would be impossible due to very strict permits this time around.
*** also this was not followed on the last night after closing in which the angel party continued in the main bar until very late???? have some consistency please. it just feels mean otherwise.

* it was nice that noise rules were followed quite well this time (unlike e.g. MCH where main stages switched to silent disco while sponsors kept blaring music into the silent areas)

* I missed routing signs for bikes coming in. Google Maps got me to the wooden bridge which was fenced off, and nobody there to either let me in or give me a hint. I may have let myself in at that fence, because it was very unclear which detour to take. The climb was only moderately scary.
* Seperate smoking and non-smoking fields, designated smoking areas away from event spaces. A blanket ban on smoking and vaping for the entire event is probably not feasible (unfortunately).

=== Tickets / entrance ===
* Putting the desks on the other side might have looked more welcoming, but all was fine for my check-in.
* Camper tickets were not scanned?

=== Villages ===
* Well done! And it was fun to help out villages doing extra luggage shuttles after we were done doing Waste stuff.

=== Volunteering / angels / heaven===

* Food tickets given to volunteers expiring, without any communication of them doing so.

[[File:Angel Waterbottle Comparison WHY vs MCH.jpg|thumb|Angle Waterbottle Comparison WHY vs MCH]]

* Waterbottle had boring text "'''Thanks For Volunteering'''", instead of WHY wordplay like "'''We Hydrate You'''", "'''Why Hydrate Yourself?'''" or "'''Wet Hackers, Yay!'''".
* Clip/Hook on the waterbootle was 3x smaller, making it unwieldy and difficult to connect. The MCH hook was bigger and easier to quick-connect.
* Drinking part had leak problems, which was not present on the previous bottle.
* The clip caused burn/melt-damage on the waterbottle, as can be seen when zooming in where the clip touches the orange waterbottle.
* No mate during buildup.
* No safe food, or unclear about the contents.
* Severe food safety issues in heaven. Bread toppings (including cheese and meat!) left open on a table outside of a fridge for hours, even overnight, with insects roaming around. No proper cleaning agents or supplies available for cleaning surfaces like tables, only some random supermarket cleaning sprays (this is not good enough for a central eating area!).
* Vegan food availability was unclear and could not be relied on. At times, the "vegan options" were completely inadequate for actually keeping people fed while doing potentially physically intensive volunteer work, with lacking nutritional value. Problem persisted during teardown. "We can't predict what the caterer will deliver" is not good enough for people with dietary restrictions.

=== Warehouse ===
* When Boels screwed up, warehouse delivered us a replacement the same day.
- what did boels screw up?
* I appreciate being able to discuss the underlying requirements instead of automatically being handed a solution. When I asked for a bunch of extension cords, it turned out there was a better solution.

=== Waste / garbage collection ===

* I have no knowledge about the state of recycling in NL, but having only separate bins for glass and then ones for everything else felt quite bad. At least separation of paper/carton would have made sense I guess. Also having separate containers where people could "donate" plastic bottles / metal cans which have deposit would have made sense and also could have brought a nice sum of money for the event.
* Field was nice and clean until teardown with enough containers to get rid of waste. (+1 for adding at least a paper and deposit container)

=== Teardown ===

* "No cars on the gras" policy: Villages that respected the rule of not driving on the grass were effectively disadvantaged. On Wednesday, many cars ignored the rule and drove onto the grass, which meant those villages didn’t have to carry their equipment over long distances. Meanwhile, villages that followed the rule had to transport their gear much farther, which was exhausting given the hot weather. Suggestion: Instead of creating a situation where following the rules feels like a disadvantage, we could reward compliance. For example, check which villages adhere to the rule, and if they do, give them vouchers for a priority ticket queue for the next event.
* Toilets were shut down too early making getting water during the warm teardown harder
* Transporting crates with empty bottles in hand trucks is also very unsafe. If they fall over it would be a mess for barefooted people. Bringing them in and out with cars is much safer.
* Way too many people left a day early. That was a bit sad. For everyone reading this: stay the entire camp ;)
* We should communicate better that flags and other deco is there for the event and should not disappear during the event. Previous events and other events by other parties may have 'trained' our visitors to think they are helping out by removing such decoration early. It was a bit sad to see people rip things of the waste gator. They got told off. But the flags on the main road disappeared on day 2 of camp, and that was entirely unwarranted.

Feedback

2025-08-18T09:09:38Z

Bas: /* Bars and food court */

'''What Hackers Yearn''' for is to '''Improve'''. This page is dedicated to collecting user feedback related to the execution of WHY2025 as a whole. Constructive feedback is invaluable to the continuous improvement of the project and is welcomed from all participants. Please share your observations and suggestions in a '''clear and respectful manner'''. Your input will help guide enhancements for future generations of the event.

It is also possible to send feedback to [http://mailto:2029@why2025.org 2029@why2025.org]

== IMPORTANT ==

Do '''NOT''' review '''people'''. Any individual interaction you had with a human does not belong here, but should be taken up with [[Team:Cohesion]].

This page is strictly for addressing improvements for the next event. We encourage contributors to maintain a neutral, factual, and calm tone in their feedback.

* GOOD EXAMPLES: "Excessive mud at showers", "Food vendors often refused to accept WHY-voucher", or "Limited drop-off points for luggage shuttle".

* BAD EXAMPLES: "Person XXX was insulting me", "Helpdesk XOC was too busy to help", "frickin hot", "So the story begins on Saturday night at 23:04 when..."

== Feedback List ==

=== General / overall ===

* There should be a clear single method/channel of communication from orga, using the Heaven signal chat or social media for this is not ideal
** +1

=== Arrival / departure / parking / train shuttle / luggage shuttle ===

* On day 0 we queued to drive onto the field. We said said we had stuff for two different villages at opposite ends of the site, named the villages and showed them on map print outs. This information was accepted by a dispatcher. However, the bicycle guide refused to guide us to the second location, claiming it was impossible to get there. This is somewhat surprising, since others had been able to drive to that location before. It seemed there was a informational mismatch between dispatch and bicyle guide. (Both locations were accessible by asphalt roads.)
* train shuttle worked well, good job!

=== Badge ===

* Badge handouts were announced right before they happened which didn't allow people to plan their angel shifts and disrupted talks / workshops. A virtual queue would have fixed this and required less total manhours to organize / manage. +1

* There was an expectation that the badge was and I quote from what I have overheard "included in the price". This is not the case and has never been the case but it’s not clearly communicated. To my understanding there was a surplus at SHA2017 and MCH2022 so there never was a shortage of badges before which may have contributed.
** The above is misinformation: It was in fact communicated in written form that every attendee with a ticket receives a badge. The badge could not be ordered separately and was included in the ticket price.

* During the event (AFAIK) there were no badge angel shifts outside of queue angel. This is a chance from prior events and didn't allow people who normally would have helped to help in the same way.

* Due to the badges not being self-powered nor being distributed at the entrance they failed to function as badges. The SHA2017 badge was designed with having no power yet still being a nametag in mind. The WHY2025 badge did not seem to function as a nametag which should have been its intended design goal.

* At MCH and SHA you had people using the badges at the event itself to make games / hack / learn / teach. It was something which brought people together. There was very little being done / to do with the badge during the camp, not just because of the late arrival and limited distribution but rather because there is no way to get apps on the badge outside of the SD card... or if there is a way of doing so then its not documented on the wiki page as of writing. There was no app store app, no way to use the LORA hardware, and outside the event its impossible to use the badge without reflashing a new wifi SSID.

* You could not sit at the badge tent and solder on your antenna onto the badge or work on projects. At SHA and MCH you could just approach the badge people / angels and even get help with projects.

* Badge still has way too limited documentation to even work on it after the event.

* Team Badge have overworked themselves to get a badge available. Team over Badge next time. Which is also a Team:Cohesion issue.

* Would have been great to have a separate queue for villages that collected tickets and pick up 15+ badges at the same time. This would also have greatly reduced waiting times for individuals picking up badges and sped-up the whole process.

* Not enough badges for all visitors (not even close apparently).

* Badge queues were very long and poorly managed. This made it impossible for some people to collected a badge (for example because they cannot stand that long, require shade, have to take care of children, need to go to their next angel shift, etc.)

* The communication about the badge status was very sparse and lacking. If there is a problem, '''communicate''' about it and tell participants what to expect.

** +1. I am sympathetic to the team scrambling to get stuff done under difficult constraints, but especially in such cases good communication is important. Things like randomly posting a link to a page about the keyboard hardware felt frustrating when we were just waiting for more info about future handouts. In addition, a Signal group was a poor choice of channel for announcements for many reasons - no public access, no history for new joiners, redundant join/leave messages, etc. Keeping updates to a section on the wiki and/or a mailing list would've worked much better.

* During build-up, almost all other teams were scrambling to find a pair of hands to get essential stuff done, while watching lots of people pouring epoxy in the badge tent. Which was, lemme me blunt here, one of the lowest priority of all the things that have been done during build-up.

=== Bars and food court ===

* Menu was much longer and more complex compared to MCH. A lot of items were almost never sold, like nachos and chips.
* Slight differences in the menu between the bars caused customers to ask "Do you have ...?". Also complicates restocking logistics.
* The amount of Rum in the "Tschunk" was '''halved''' without updating the price. They decided it was better to modify the recipe to make it almost non-alcoholic, rather than say "Sorry, we're out."
** +1, the Tschunk contained barely any Rum.
* Bar is not a Merch Store, "Special/Ceremonial Cup" should be sold in Infodesk. It was also badly advertised, only people who "knew" of its existence could buy it. +1
* How was the cup not a deposit... I didn't even realize you wouldn't get any money back. Made it extremely bothersome to buy drinks for other people. +1
* Why wasn't statiegeld/pfand collected? Many glass bins full of mate-bottles. I don't want to know how many plastic bottles and aluminium cans were thrown out. This could have been prevented.
* No Club Mate Beere?
* No normal (0.5L) bottles available on the last day?
* Do we get mate from the source, or a Dutch overprices company?
* No mate during buildup again?
* Not written instructions for angels. The “game of telephone” style handing of incorrect instructions down from one angel to the next caused food to be prepared incorrectly. Written instructions should be posted right at the frier and microwave.
** +1
* Handling of vegan food was bad. Burger stall incorrectly advertised vegetarian burger as "vegan" originally, and could not provide any vegan burger at all because the buns contained milk(!). Fries/snacks stall staff did not know what they were selling or what it contained, and communication was difficult. Only positive note goes to the pasta stall where the food was good, and the operator was highly competent and knew exactly what they were selling (I would like to see them at a next event).
* Bottle collection procedure was very unclear.
* To add to the above: between bar and foodcourt no crates in sight on several days. No instructions or procedure arranged. So people grabbed the glass-waste bin from the showers and put it in the middle. End result: 24x 240L glass trash bin completely filled to the brim. Assuming roughly around 5000 pfand-bottles (Mate, beer etc) were trashed. And team Waste had a ton of heavy lifting to get all these bins off the field and back to the recycling company. This could have been prevented.
* The same with plastic bottles and cans. Team Waste managed to save a *trailer* full of cans and bottles. About 24 big bags (240L). That could easily have been double. And if people actually organized it, it would have been less work.

=== Cohesion ===
* I like the idea, but not the implementation: Geraffel was put at the arse end of the field (OK fine, epicenter of noise gradient and all that), then got told off for playing music during the day.
* Very little communication/information. People barely knew the team existed and could be contacted, social rules like the Photo Policy were not communicated and very widely ignored. Other events signpost these things all over the site and it does help

=== Content / talks / heralds / speakerdesk / AV / recordings ===

* Party Stage was the perfect location for the "History of Hardcore" talk. More 'serious' talks could be held on the music stages at events going forward.

=== CTF / token game ===

=== Decoration / design ===

* Team did an amazing job. The field felt welcoming and interesting. Thank you so much for all the effort that went in. +1
* Next time we need to find a sponsor to print flags for all visitors, and have it available as merch for purchase. It was sad to see so much deco being liberated too early in the event. We need to also work on the communication around this.

=== Family / kids ===

=== Finance / coins / payments ===

* Like the concept of an anonymous payment card that '''just works'''. Absolutely love the design of the WHY2025 card. And very happy to play with a blank Ultralight AES card afterwards.
* option for payout of remaining funds wasn't communicated properly (even the website claimed it wasn't possible at all). Cash payout would be nice, but would understandably be a big extra thing to manage

=== Information / infodesk / wiki ===

* The wiki seems to have never been updated after the event started. I have attempted to find information about something several times and ''none'' of those times was it on the wiki. Instead everything seemed to be in random Signal groups and wherever else, that I didn't even know about until much later.
* It was very hard to find information on anything (like infrastructure, badge handouts, etc.) in general, and even infodesk angels often didn't have the answers.

=== Merchandise ===
* It would have been nice if the merch that was ordered months ago would have actually been available at the field.
* Flags as preordered merchandise. Would create the possibility for hackerspaces and individuals to bring back home some of them. +2

=== NOC / Network ===
* From buildup, through the event, through teardown: the networks worked!
* It was a pleasure to work together, to deduplicate work and equipment.
* In our location, Wifi coverage was poor although we were next to a Datenklo

=== NUTS / power / water ===

* Showers with adjustable heat (showerheads which mix cold and hot water) to avoid burns.
* Wood pallets outside both showers and toilets to reduce mud. (+1, from day zero would have been helpful)
* Even if not in all bathroom points, more drinking water points other than the one in heaven should have been available from the beginning. +1
* Disable the watertaps at the same time as all the other bathroom facilities. Or communicate when the water is going out. Now villages were only able to fill small containers at the toilets. Or needed to walk all the way to Heaven.
* Slightly more cleaning would have been great. The showers were extremely full of mud even inside at times. Given they only used a hose as far as I saw, should have been possible to also have some angels do this in addition to the cleaning crew.
* Adding hooks to the showers was a very welcome addition, thanks!
* It wasn't clear where to get drinking water during the first few days. This should be communicated better, e.g. with signs and on the map. +1
* I liked the number of toilets: never had to wait +1
* furthermore, the toilets seemed to be cleaned often which is good. +1
* There always was toilet paper available in the stalls, greatly lessens anxiety. +1
* water pressure and temperature in the showers was great! Also: never had to wait, which is great! +1
* There always was plenty of soap available at the sinks, during peak time and at night. +1
* Dedicated dishwashing location. +1
* More drinking water fountains across the terrain
* "upgrading" facilities to "drinking water" is questionable. What of all the potential risks was actually tested and could be guaranteed? Separate 100% clear drinking water spots would be better -1
* Shower temperature constantly fluctuated and never stabilized

=== Off-site logistics ===

=== On-site logistics ===

=== POC / DECT / Fieldphones ===
* micropoc worked just fine: I could easily and quickly register the DECT phones for my village and the network worked whenever I wanted to use it.

=== Productiehuis / C3VOC ===

=== Projectleiding ===

=== ROC ===
* Very clear audio and reception

=== Safety / security / first aid / fire ===

=== Supermarket ===

=== Sysadmin ===

* Setup "live.why2025.org" as an alias for people to easier find the livestreams next time. Right now you needed to go to "streaming.media.ccc.de/why2025".
* IRC is less popular in new generations of hackers and at least Mastodon+Matrix integrations would have made Signal angel role useful.

=== Terrain ===

* Noise gradient should be evaluated better: the main party stage was more audible from the family village than from the Belgian cluster, which was way closer.
* Fridge container orientation: the compressor should point away from campers, it was the single most noisy item from Batavus On tour village point of view.
* Infodesk not located at the entrance like at MCH, causing it to be less visible.
* 4000 people but only a single "Hardware Hacking Tent". It was constantly full, and no other places to sit and solder.
** Plenty villages that'll happily let you use their spaces. It makes sense for this kind of thing to be community-provided (the Hardware Hacking Tent was too - while a official workshop spot, it only exists because of of the HHA team willing to equip and run it)
* "Hackcenter" only had space for 20 people, tiny tent, zero cooling, and no advertisement. Not even a sign... We thought it was someone's Village until day 4.
* No place to party/music all night. It would be cool to have a distant (from tents) area where we're allowed to have music going all night long.
** -1, loud music anywhere on the field travels far and I appreciate being able to sleep. I liked the 23:00 cutoff.
** -1 agreed. "distant" location is not really possible on-site
** +1 AGREE, the noise cutoff was really annoying, other events the music continues until 2am atleast, I don't see why we can't have somewhere on site where we can play music at a reasonable volume. 23:00 is too early for a festival.
** +1, made the event substancially worse, if we have color-coded fields to match volume levels why do we still have to shut the music down completely at 23:00 in the red area?
** -1, i was very happy to have a camp where i could sleep without earplugs. Also it would be impossible due to very strict permits this time around.
*** also this was not followed on the last night after closing in which the angel party continued in the main bar until very late???? have some consistency please. it just feels mean otherwise.

* it was nice that noise rules were followed quite well this time (unlike e.g. MCH where main stages switched to silent disco while sponsors kept blaring music into the silent areas)

* I missed routing signs for bikes coming in. Google Maps got me to the wooden bridge which was fenced off, and nobody there to either let me in or give me a hint. I may have let myself in at that fence, because it was very unclear which detour to take. The climb was only moderately scary.
* Seperate smoking and non-smoking fields, designated smoking areas away from event spaces. A blanket ban on smoking and vaping for the entire event is probably not feasible (unfortunately).

=== Tickets / entrance ===
* Putting the desks on the other side might have looked more welcoming, but all was fine for my check-in.
* Camper tickets were not scanned?

=== Villages ===
* Well done! And it was fun to help out villages doing extra luggage shuttles after we were done doing Waste stuff.

=== Volunteering / angels / heaven===

* Food tickets given to volunteers expiring, without any communication of them doing so.

[[File:Angel Waterbottle Comparison WHY vs MCH.jpg|thumb|Angle Waterbottle Comparison WHY vs MCH]]

* Waterbottle had boring text "'''Thanks For Volunteering'''", instead of WHY wordplay like "'''We Hydrate You'''", "'''Why Hydrate Yourself?'''" or "'''Wet Hackers, Yay!'''".
* Clip/Hook on the waterbootle was 3x smaller, making it unwieldy and difficult to connect. The MCH hook was bigger and easier to quick-connect.
* Drinking part had leak problems, which was not present on the previous bottle.
* The clip caused burn/melt-damage on the waterbottle, as can be seen when zooming in where the clip touches the orange waterbottle.
* No mate during buildup.
* No safe food, or unclear about the contents.
* Severe food safety issues in heaven. Bread toppings (including cheese and meat!) left open on a table outside of a fridge for hours, even overnight, with insects roaming around. No proper cleaning agents or supplies available for cleaning surfaces like tables, only some random supermarket cleaning sprays (this is not good enough for a central eating area!).
* Vegan food availability was unclear and could not be relied on. At times, the "vegan options" were completely inadequate for actually keeping people fed while doing potentially physically intensive volunteer work, with lacking nutritional value. Problem persisted during teardown. "We can't predict what the caterer will deliver" is not good enough for people with dietary restrictions.

=== Warehouse ===
* When Boels screwed up, warehouse delivered us a replacement the same day.
- what did boels screw up?
* I appreciate being able to discuss the underlying requirements instead of automatically being handed a solution. When I asked for a bunch of extension cords, it turned out there was a better solution.

=== Waste / garbage collection ===

* I have no knowledge about the state of recycling in NL, but having only separate bins for glass and then ones for everything else felt quite bad. At least separation of paper/carton would have made sense I guess. Also having separate containers where people could "donate" plastic bottles / metal cans which have deposit would have made sense and also could have brought a nice sum of money for the event.
* Field was nice and clean until teardown with enough containers to get rid of waste. (+1 for adding at least a paper and deposit container)

=== Teardown ===

* "No cars on the gras" policy: Villages that respected the rule of not driving on the grass were effectively disadvantaged. On Wednesday, many cars ignored the rule and drove onto the grass, which meant those villages didn’t have to carry their equipment over long distances. Meanwhile, villages that followed the rule had to transport their gear much farther, which was exhausting given the hot weather. Suggestion: Instead of creating a situation where following the rules feels like a disadvantage, we could reward compliance. For example, check which villages adhere to the rule, and if they do, give them vouchers for a priority ticket queue for the next event.
* Toilets were shut down too early making getting water during the warm teardown harder
* Transporting crates with empty bottles in hand trucks is also very unsafe. If they fall over it would be a mess for barefooted people. Bringing them in and out with cars is much safer.
* Way too many people left a day early. That was a bit sad. For everyone reading this: stay the entire camp ;)
* We should communicate better that flags and other deco is there for the event and should not disappear during the event. Previous events and other events by other parties may have 'trained' our visitors to think they are helping out by removing such decoration early. It was a bit sad to see people rip things of the waste gator. They got told off. But the flags on the main road disappeared on day 2 of camp, and that was entirely unwarranted.

Feedback

2025-08-18T08:56:00Z

Bas: /* Villages */

'''What Hackers Yearn''' for is to '''Improve'''. This page is dedicated to collecting user feedback related to the execution of WHY2025 as a whole. Constructive feedback is invaluable to the continuous improvement of the project and is welcomed from all participants. Please share your observations and suggestions in a '''clear and respectful manner'''. Your input will help guide enhancements for future generations of the event.

It is also possible to send feedback to [http://mailto:2029@why2025.org 2029@why2025.org]

== IMPORTANT ==

Do '''NOT''' review '''people'''. Any individual interaction you had with a human does not belong here, but should be taken up with [[Team:Cohesion]].

This page is strictly for addressing improvements for the next event. We encourage contributors to maintain a neutral, factual, and calm tone in their feedback.

* GOOD EXAMPLES: "Excessive mud at showers", "Food vendors often refused to accept WHY-voucher", or "Limited drop-off points for luggage shuttle".

* BAD EXAMPLES: "Person XXX was insulting me", "Helpdesk XOC was too busy to help", "frickin hot", "So the story begins on Saturday night at 23:04 when..."

== Feedback List ==

=== General / overall ===

* There should be a clear single method/channel of communication from orga, using the Heaven signal chat or social media for this is not ideal
** +1

=== Arrival / departure / parking / train shuttle / luggage shuttle ===

* On day 0 we queued to drive onto the field. We said said we had stuff for two different villages at opposite ends of the site, named the villages and showed them on map print outs. This information was accepted by a dispatcher. However, the bicycle guide refused to guide us to the second location, claiming it was impossible to get there. This is somewhat surprising, since others had been able to drive to that location before. It seemed there was a informational mismatch between dispatch and bicyle guide. (Both locations were accessible by asphalt roads.)
* train shuttle worked well, good job!

=== Badge ===

* Badge handouts were announced right before they happened which didn't allow people to plan their angel shifts and disrupted talks / workshops. A virtual queue would have fixed this and required less total manhours to organize / manage. +1

* There was an expectation that the badge was and I quote from what I have overheard "included in the price". This is not the case and has never been the case but it’s not clearly communicated. To my understanding there was a surplus at SHA2017 and MCH2022 so there never was a shortage of badges before which may have contributed.
** The above is misinformation: It was in fact communicated in written form that every attendee with a ticket receives a badge. The badge could not be ordered separately and was included in the ticket price.

* During the event (AFAIK) there were no badge angel shifts outside of queue angel. This is a chance from prior events and didn't allow people who normally would have helped to help in the same way.

* Due to the badges not being self-powered nor being distributed at the entrance they failed to function as badges. The SHA2017 badge was designed with having no power yet still being a nametag in mind. The WHY2025 badge did not seem to function as a nametag which should have been its intended design goal.

* At MCH and SHA you had people using the badges at the event itself to make games / hack / learn / teach. It was something which brought people together. There was very little being done / to do with the badge during the camp, not just because of the late arrival and limited distribution but rather because there is no way to get apps on the badge outside of the SD card... or if there is a way of doing so then its not documented on the wiki page as of writing. There was no app store app, no way to use the LORA hardware, and outside the event its impossible to use the badge without reflashing a new wifi SSID.

* You could not sit at the badge tent and solder on your antenna onto the badge or work on projects. At SHA and MCH you could just approach the badge people / angels and even get help with projects.

* Badge still has way too limited documentation to even work on it after the event.

* Team Badge have overworked themselves to get a badge available. Team over Badge next time. Which is also a Team:Cohesion issue.

* Would have been great to have a separate queue for villages that collected tickets and pick up 15+ badges at the same time. This would also have greatly reduced waiting times for individuals picking up badges and sped-up the whole process.

* Not enough badges for all visitors (not even close apparently).

* Badge queues were very long and poorly managed. This made it impossible for some people to collected a badge (for example because they cannot stand that long, require shade, have to take care of children, need to go to their next angel shift, etc.)

* The communication about the badge status was very sparse and lacking. If there is a problem, '''communicate''' about it and tell participants what to expect.

** +1. I am sympathetic to the team scrambling to get stuff done under difficult constraints, but especially in such cases good communication is important. Things like randomly posting a link to a page about the keyboard hardware felt frustrating when we were just waiting for more info about future handouts. In addition, a Signal group was a poor choice of channel for announcements for many reasons - no public access, no history for new joiners, redundant join/leave messages, etc. Keeping updates to a section on the wiki and/or a mailing list would've worked much better.

* During build-up, almost all other teams were scrambling to find a pair of hands to get essential stuff done, while watching lots of people pouring epoxy in the badge tent. Which was, lemme me blunt here, one of the lowest priority of all the things that have been done during build-up.

=== Bars and food court ===

* Menu was much longer and more complex compared to MCH. A lot of items were almost never sold, like nachos and chips.
* Slight differences in the menu between the bars caused customers to ask "Do you have ...?". Also complicates restocking logistics.
* The amount of Rum in the "Tschunk" was '''halved''' without updating the price. They decided it was better to modify the recipe to make it almost non-alcoholic, rather than say "Sorry, we're out."
** +1, the Tschunk contained barely any Rum.
* Bar is not a Merch Store, "Special/Ceremonial Cup" should be sold in Infodesk. It was also badly advertised, only people who "knew" of its existence could buy it. +1
* How was the cup not a deposit... I didn't even realize you wouldn't get any money back. Made it extremely bothersome to buy drinks for other people. +1
* Why wasn't statiegeld/pfand collected? Many glass bins full of mate-bottles. I don't want to know how many plastic bottles and aluminium cans were thrown out. This could have been prevented.
* No Club Mate Beere?
* No normal (0.5L) bottles available on the last day?
* Do we get mate from the source, or a Dutch overprices company?
* No mate during buildup again?
* Not written instructions for angels. The “game of telephone” style handing of incorrect instructions down from one angel to the next caused food to be prepared incorrectly. Written instructions should be posted right at the frier and microwave.
** +1
* Handling of vegan food was bad. Burger stall incorrectly advertised vegetarian burger as "vegan" originally, and could not provide any vegan burger at all because the buns contained milk(!). Fries/snacks stall staff did not know what they were selling or what it contained, and communication was difficult. Only positive note goes to the pasta stall where the food was good, and the operator was highly competent and knew exactly what they were selling (I would like to see them at a next event).
* Bottle collection procedure was very unclear.

=== Cohesion ===
* I like the idea, but not the implementation: Geraffel was put at the arse end of the field (OK fine, epicenter of noise gradient and all that), then got told off for playing music during the day.
* Very little communication/information. People barely knew the team existed and could be contacted, social rules like the Photo Policy were not communicated and very widely ignored. Other events signpost these things all over the site and it does help

=== Content / talks / heralds / speakerdesk / AV / recordings ===

* Party Stage was the perfect location for the "History of Hardcore" talk. More 'serious' talks could be held on the music stages at events going forward.

=== CTF / token game ===

=== Decoration / design ===

* Team did an amazing job. The field felt welcoming and interesting. Thank you so much for all the effort that went in. +1
* Next time we need to find a sponsor to print flags for all visitors, and have it available as merch for purchase. It was sad to see so much deco being liberated too early in the event. We need to also work on the communication around this.

=== Family / kids ===

=== Finance / coins / payments ===

* Like the concept of an anonymous payment card that '''just works'''. Absolutely love the design of the WHY2025 card. And very happy to play with a blank Ultralight AES card afterwards.
* option for payout of remaining funds wasn't communicated properly (even the website claimed it wasn't possible at all). Cash payout would be nice, but would understandably be a big extra thing to manage

=== Information / infodesk / wiki ===

=== Merchandise ===
* It would have been nice if the merch that was ordered months ago would have actually been available at the field.
* Flags as preordered merchandise. Would create the possibility for hackerspaces and individuals to bring back home some of them. +2

=== NOC / Network ===
* From buildup, through the event, through teardown: the networks worked!
* It was a pleasure to work together, to deduplicate work and equipment.
* In our location, Wifi coverage was poor although we were next to a Datenklo

=== NUTS / power / water ===

* Showers with adjustable heat (showerheads which mix cold and hot water) to avoid burns.
* Wood pallets outside both showers and toilets to reduce mud. (+1, from day zero would have been helpful)
* Even if not in all bathroom points, more drinking water points other than the one in heaven should have been available from the beginning. +1
* Disable the watertaps at the same time as all the other bathroom facilities. Or communicate when the water is going out. Now villages were only able to fill small containers at the toilets. Or needed to walk all the way to Heaven.
* Slightly more cleaning would have been great. The showers were extremely full of mud even inside at times. Given they only used a hose as far as I saw, should have been possible to also have some angels do this in addition to the cleaning crew.
* Adding hooks to the showers was a very welcome addition, thanks!
* It wasn't clear where to get drinking water during the first few days. This should be communicated better, e.g. with signs and on the map. +1
* I liked the number of toilets: never had to wait +1
* furthermore, the toilets seemed to be cleaned often which is good. +1
* There always was toilet paper available in the stalls, greatly lessens anxiety. +1
* water pressure and temperature in the showers was great! Also: never had to wait, which is great! +1
* There always was plenty of soap available at the sinks, during peak time and at night. +1
* Dedicated dishwashing location. +1
* More drinking water fountains across the terrain
* "upgrading" facilities to "drinking water" is questionable. What of all the potential risks was actually tested and could be guaranteed? Separate 100% clear drinking water spots would be better -1

=== Off-site logistics ===

=== On-site logistics ===

=== POC / DECT / Fieldphones ===
* micropoc worked just fine: I could easily and quickly register the DECT phones for my village and the network worked whenever I wanted to use it.

=== Productiehuis / C3VOC ===

=== Projectleiding ===

=== ROC ===
* Very clear audio and reception

=== Safety / security / first aid / fire ===

=== Supermarket ===

=== Sysadmin ===

* Setup "live.why2025.org" as an alias for people to easier find the livestreams next time. Right now you needed to go to "streaming.media.ccc.de/why2025".
* IRC is less popular in new generations of hackers and at least Mastodon+Matrix integrations would have made Signal angel role useful.

=== Terrain ===

* Noise gradient should be evaluated better: the main party stage was more audible from the family village than from the Belgian cluster, which was way closer.
* Fridge container orientation: the compressor should point away from campers, it was the single most noisy item from Batavus On tour village point of view.
* Infodesk not located at the entrance like at MCH, causing it to be less visible.
* 4000 people but only a single "Hardware Hacking Tent". It was constantly full, and no other places to sit and solder.
** Plenty villages that'll happily let you use their spaces. It makes sense for this kind of thing to be community-provided (the Hardware Hacking Tent was too - while a official workshop spot, it only exists because of of the HHA team willing to equip and run it)
* "Hackcenter" only had space for 20 people, tiny tent, zero cooling, and no advertisement. Not even a sign... We thought it was someone's Village until day 4.
* No place to party/music all night. It would be cool to have a distant (from tents) area where we're allowed to have music going all night long.
** -1, loud music anywhere on the field travels far and I appreciate being able to sleep. I liked the 23:00 cutoff.
** -1 agreed. "distant" location is not really possible on-site
** +1 AGREE, the noise cutoff was really annoying, other events the music continues until 2am atleast, I don't see why we can't have somewhere on site where we can play music at a reasonable volume. 23:00 is too early for a festival.
** +1, made the event substancially worse, if we have color-coded fields to match volume levels why do we still have to shut the music down completely at 23:00 in the red area?
** -1, i was very happy to have a camp where i could sleep without earplugs. Also it would be impossible due to very strict permits this time around.
*** also this was not followed on the last night after closing in which the angel party continued in the main bar until very late???? have some consistency please. it just feels mean otherwise.

* it was nice that noise rules were followed quite well this time (unlike e.g. MCH where main stages switched to silent disco while sponsors kept blaring music into the silent areas)

* I missed routing signs for bikes coming in. Google Maps got me to the wooden bridge which was fenced off, and nobody there to either let me in or give me a hint. I may have let myself in at that fence, because it was very unclear which detour to take. The climb was only moderately scary.

=== Tickets / entrance ===
* Putting the desks on the other side might have looked more welcoming, but all was fine for my check-in.
* Camper tickets were not scanned?

=== Villages ===
* Well done! And it was fun to help out villages doing extra luggage shuttles after we were done doing Waste stuff.

=== Volunteering / angels / heaven===

* Food tickets given to volunteers expiring, without any communication of them doing so.

[[File:Angel Waterbottle Comparison WHY vs MCH.jpg|thumb|Angle Waterbottle Comparison WHY vs MCH]]

* Waterbottle had boring text "'''Thanks For Volunteering'''", instead of WHY wordplay like "'''We Hydrate You'''", "'''Why Hydrate Yourself?'''" or "'''Wet Hackers, Yay!'''".
* Clip/Hook on the waterbootle was 3x smaller, making it unwieldy and difficult to connect. The MCH hook was bigger and easier to quick-connect.
* Drinking part had leak problems, which was not present on the previous bottle.
* The clip caused burn/melt-damage on the waterbottle, as can be seen when zooming in where the clip touches the orange waterbottle.
* No mate during buildup.
* No safe food, or unclear about the contents.

=== Warehouse ===
* When Boels screwed up, warehouse delivered us a replacement the same day.
- what did boels screw up?
* I appreciate being able to discuss the underlying requirements instead of automatically being handed a solution. When I asked for a bunch of extension cords, it turned out there was a better solution.

=== Waste / garbage collection ===

=== Teardown ===

* "No cars on the gras" policy: Villages that respected the rule of not driving on the grass were effectively disadvantaged. On Wednesday, many cars ignored the rule and drove onto the grass, which meant those villages didn’t have to carry their equipment over long distances. Meanwhile, villages that followed the rule had to transport their gear much farther, which was exhausting given the hot weather. Suggestion: Instead of creating a situation where following the rules feels like a disadvantage, we could reward compliance. For example, check which villages adhere to the rule, and if they do, give them vouchers for a priority ticket queue for the next event.
* Toilets were shut down too early making getting water during the warm teardown harder
* Transporting crates with empty bottles in hand trucks is also very unsafe. If they fall over it would be a mess for barefooted people. Bringing them in and out with cars is much safer.
* Way too many people left a day early. That was a bit sad. For everyone reading this: stay the entire camp ;)
* We should communicate better that flags and other deco is there for the event and should not disappear during the event. Previous events and other events by other parties may have 'trained' our visitors to think they are helping out by removing such decoration early. It was a bit sad to see people rip things of the waste gator. They got told off. But the flags on the main road disappeared on day 2 of camp, and that was entirely unwarranted.

Badge Issues

2025-08-18T08:51:29Z

Bas: /* [4] screen is not turning on at all. */

== Please edit this page ==

'''Please edit this page to add your issue or increase the interest counter
'''

The ''[number]'' in front of each question is the interest counter. Increase it by one if you have the same question.

== Badge Hardware Questions/Issues ==
=== Answered ===
==== [1] After reflash and exiting the intial sponsors screen, the screen stays blue ====
* => Reflash the badge using the web flasher. (https://why-prog.heplaphon.com/). Use the USB socket on the left side for flashing. After the update unplug/replug the USB. Make sure to use a good cable as the badge is power hungry.
==== [2] How do I reset the badge on battery? ====
* => Applying usb power will reset the badge
==== [4] Batteries ar being held firmly (maybe a bit too firmly) in place in the battery holder. How can I safely remove the batteries? What tool to use for this without damaging the batteries or the PCB? ====
* => Try gripping it with rubber gloves on.
* => For future handling, add strong tape around it, so that you'll have a lid to pull on for extra support

==== [3] The badge suddenly stopped working. Serial shows boot-loop with message <pre>Cannot connect to target. Error: TIMEOUT </pre> ====
* => Reseating the ESP daughterboard (fitted with a screw) helped here.
* => M.2 socket of ESP daughterboard can break off without being immediately visible. This also leads to this error. [https://chaos.social/@xro/115011118785473303 Re-soldering fixed it.]
Trace of boot-loop:
<pre>
./idf.py monitor
W (1098) fatfs-sd: SD card not mounted
E (1108) device: The device does not exist SD0
Cannot connect to target. Error: TIMEOUT
Check if the host and the target are properly connected.
E (4828) sdmmc_common: sdmmc_init_ocr: send_op_cond (1) returned 0x107
HINT: Please reboot the board and then try again
E (4828) sdio_wrapper: sdmmc_card_init failed
E (4828) H_SDIO_DRV: sdio card init failed
Crashing in ESP-IDF task
Guru Meditation Error: Core 1 panic'ed (Instruction access fault). Exception was unhandled.

--- Stack dump detected
Core 1 register dump:
MEPC : 0x00000000 RA : 0x00000000 SP : 0x4ff278c0 GP : 0x4ff18580
TP : 0x4ff278e0 T0 : 0x4ff0f4a6 T1 : 0x4ff120a8 T2 : 0xffffffff
--- 0x4ff0f4a6: spinlock_release at /home/bernhard/source/why2025-badge-firmware/components/esp_hw_support/include/spinlock.h:181
</pre>
==== [5] Some keys (the `w` key in my case) don't register. I've tried with the nametag app and with the new System Settings app, and it didn't work on either. ====
[[User:Bytefighter|bytefighter]] ([[User_talk:Bytefighter|talk]]) 01:24, 14 August 2025 (CEST)
* => Check for [https://chaos.social/@edronik/115027350958230845 crusty stuff under the metal membrane]
==== [8] The antenna isn't connected yet. Can I use the device without damaging anything? ====
* The antenna is used by the LoRa radio. At the moment of writing there is no badge firmware available that uses the LoRa radio. This means that for now the device can safely be used without the antenna (socket) attached.
* As soon as you do start using the LoRa radio, there is a potential for damage when the badge is used without the antenna. Attaching the antenna requires some extra precautions. See the instructions on attaching the socket further down on this wiki page for tips and tricks.
** (Can not include link as the HTTP anchor contains square brackets)

==== [2] Where/how to solder the antenna socket/connector? ====

[[File:Badge back antenna socket holes.jpg|thumb]]
[[File:Badge front antenna socket details.jpg|thumb]]
[[File:Badge front kapton tape.jpg|thumb]]

Before soldering on the antenna socket, consider if you really need to. The section of the wiki about using the badge without the antenna attached has some important information.

Steps for soldering:
It's recommended to read through these steps first before you get going.

* Shut down badge. Remove batteries or other power sources.
* Take the badge apart by unscrewing all four screws, removing the front plate and the 3D printed spacer(s).
** The best fitting bit is a J0/JIS0, some iFixit kits have them. A PH0/00 may work but be careful to not strip the screw or poke in to your hand while applying pressure for unscrewing.
* Location: in the top right corner tightly along side the screen, you should now see 5 holes marked as "J5". (See image)
* Check if your 3D printed spacer has holes in that spot. The socket will be inserted in these holes from the back of the badge. The legs will stick through on the front side of the badge. Once they are soldered the spacer needs to allow some room for the pins to poke through it. If the spacer won't fit, a quick fix would be to widen the holes with you soldering iron, or use a drill to increase the size.
* The center hole of the pattern is for the signal. The surrounding 4 holes are connected to ground and provide points to strengthen the connection between the socket and the PCB. (See image)
* Insert the socket from the back of the PCB. The component should be on the back of the badge where the battery holders are. The legs should stick out on the screen side of the badge.

Note: some of the holes for soldering on the socket are very close to the side of the screen. The screen is delicate and will take damage from the heat of your soldering iron. How to deal with this? (See image)

* Easy:
** Keep your iron away from the side of the screen.
** Solder only the two pins on the outside of the PCB for rigidity, and the center pin for signal. This gives you less than half a centimeter to work with. Be careful with the antenna and socket as
* Expert:
** Put one or more layers of true Kapton tape (M3 5413) on the side of the screen, all the way down to the PCB to protect the screen from heat. (See image)
** Still make sure your soldering iron stays away from the screen as much as possible at all times.
** Solder the four outside pins for maximum rigidity and the center pin for signal.
* Possibly hard to execute:
** Ideally you take the screen of which can be done with some dental floss, although this could damage the screen.

=== Unanswered ===
* Got a question that is already listed but not answered yet? The ''[number]'' in front of each question is the interest counter. Edit this wiki and increase the counter by one if you have the same question. This allows us to prioritize. Thank you!
* Got an answer? Please edit the wiki, add your answer and move the question to the Answered section. Thank you for your contribution!
==== [4] Screen flickers sometimes. Is this a defect? I tried looking at the screen ribbon cable, it seems OK. ====
* => (bend the board -> more flicker?)
* => I had to resolder the m.2 connector (use flux and touch every pin with soldering iron)

==== [4] screen is not turning on at all. ====
* => I had to resolder the m.2 connector (use flux and touch every pin with soldering iron)
* => extreme case: (https://chaos.social/@xro/115011118785473303)
* => https://wiki.why2025.org/Badge#m.2_connector

==== [7] Can not turn off badge while charging. ====
Yet to be answered.
==== [9] One battery holder has a big blob of epoxy where it should contact the battery. Is there a good way to remove it? ====
Yet to be answered.
==== [10] Badge updates apps after starting an app that isn't the updater ====
Yet to be answered.
==== [11] Sponsor screen replays (unskippable) after every flash ====

[[User:RobotJoosen|robotjoosen]] 22:11, 14 August 2025 (GMT)

<s>=> Press `fn + x` to skip sponsor screen</s>

[[User:Tielemans.jorim|Tielemans.jorim]] 14:13, 16 August 2025 (CEST)

`fn + x` should not be used as this force closes the sponsors app. You need to wait for it to at least play once and use the `esc` key once shown on screen. Terminating the sponsors app early might result in not being able to open other apps.

==== [12] Double-tapping the power button doesn't shut down the badge ====
Yet to be answered.
==== [13] Where do we get the badge now that the event is over? The lines were huge or the stand was closed. Can we pay for shipping to get them later? ====
Yet to be answered.
==== [14] Is it possible to insert an SD card without removing the daughter board (with cells installed)? ====

[[User:RobotJoosen|robotjoosen]] 22:13, 14 August 2025 (GMT)

=> No, there is not physical space to insert a SD card without bending/breaking it. It is also not possible without the cells.

==== [1] Flashing to `BadgeVMS post_event` might work fine, until a reboot. This appears to happen only on devices with an SD-card installed, it will result in the error `Could not open APPS:[badgevms_launcher]badgevms_launcher.elf` [https://pastebin.com/zMr45zHT pastebin] ====
Yet to be answered.

* Addendum, See also: [https://gitlab.com/why2025/team-badge/firmware/-/issues?show=eyJpaWQiOiI5IiwiZnVsbF9wYXRoIjoid2h5MjAyNS90ZWFtLWJhZGdlL2Zpcm13YXJlIiwiaWQiOjE3MTg4NzgyNX0%3D Boot is stuck, when fitted with an SD card]

==== [2] Damaged wrapping of an 18650 battery, is this an issue? ====
* Is this an issue? (see picture) [[File:Badge 18650 with a small mark.jpg|thumb]]

==== [1] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
Yet to be answered.
==== [1] Screen wobbles horizontal (X-Axis) with random amount. (Allready flashed newest firmware (Badge VMS post_event) without any changes). Wobble gets worse the longer the device is on. Starts after about 3 Minutes. Slight wobble can be triggert by pressing a button keyboard ====
Yet to be answered.

==== [1] Screen has yellowish pixel failures [[File:PXL 20250815 195829061.jpg|thumb]] Screen also wobbles horizontal after few minutes (see topic above) ====
Yet to be answered.

==== [1] I'd like to remove the 18650 cell holders but the epoxy is holding them in a bit too well. Has anyone managed to find a non-destructive way to do this? ====

Unofficial answer from the OP... I was able to pry the cell holders loose using a craft knife and a little force. However, this revealed some pools of uncured epoxy, as shown in the photo. The Internet suggests leaving the badge outside for a bit of sunbathing, as the solar UV will help the epoxy to set.

[[File:Badge-post-op.jpg|thumb|alt=WHY badge which has had the cell holders removed using a craft knife. Along the long edge of each cell holder there is some pooling of uncured epoxy.|WHY badge with cell holders removed - showing uncured epoxy]]

==== [1] I'd like to power the badge using a conventional LiPo pouch, but I don't see a header anywhere that I could solder a JST connector to. Has anyone else achieved this? ====
Yet to be answered.

==== [1] There's a header (LS1) between the M.2 board and one of the cell holders which seems (from the schematics) to be for a speaker. Has anyone got this working? What parts did you use? ====
Yet to be answered.

==== [1] Badge shows yellow screen randomly (seems related to daughter M.2 board) ====

Randomly the badge display turns yellow.

What I tried:
* Swapped the daughter M.2 ESP board with another badge → the yellow screen issue followed the daughterboard, not the main board.
* Serial log shows no errors at the moment the display turns yellow.
* Tried many different firmwares, currently running the post event firmware.

This suggests the issue is related to the M.2 daughterboard, likely power instability under load.

Yet to be answered.

== Badge User Questions/Issues ==
=== Answered ===
==== [1] Inside program “c64emu” v1 trying Shift+{number} prints the number to console and not the symbol. This behaviour works in “crackme” v3. ====
* Thank you for reporting this, I've fixed this and released a new version with improved keyboard handling (v2.0.1). --[[User:Wallaby|Wallaby]] ([[User talk:Wallaby|talk]]) 14:37, 11 August 2025 (CEST)
==== [5] WHY2025 OTA updater is not reacting. ====
* => We are working on this. For now, don't touch it and instead just wait at least 30 seconds.
** => This didn't work for me; I had to re-flash the firmware. [[User:Bytefighter|bytefighter]] ([[User_talk:Bytefighter|talk]]) 08:53, 13 August 2025 (CEST)
** => Any update on this? "OTA" and "Hello" app don't do anything. Not even an error message. Is there a hidden Wifi settings menu or something for the "over the air" part? Maybe a USB-C to Ethernet dongle?
==== [3] There is a stripe and/or "HD3" stamp on my screen ====
* Test if you see these when the badge is off.
* There is a protective cellophane sheet attached to the screen for protection against scratches and dirt. Remove the cellophane sheet by peeling it off. There's a tab to peel in the lower right corner. This tab may be under the front cover or the spacer.
* I saw at least one device where the sticky tape area was '''under''' the front cover. --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:03, 11 August 2025 (CEST)
** Assemblers of the spacer/keyboard/front cover were at some point instructed to keep the tab to peel of the protective layer under the spacer. Reason for this: unknown. Perhaps to reduce the change of them coming off while the badges were still being assembled. --[[User:44x|44x]] 23:33, 14 August 2025 (CEST)
==== [2] Could do one update, then three updates and then BadgeVMS Firmware Version 4. Now I a offered this update on every boot and can do nothing else, even though I have installed it already ====
* reboot fixes this.
==== [3] My Badge is showing a yellow screen. Its starting with a blue screen and shows the Menu for a few seconds an then turns yellow. What does this indicate? ====
* The v5 firmware had this bug. Reflash with a newer to fix.
==== [11] I’m finally home! How do I connect the badge to my local Wi-Fi? ====
* Lazy, hacky method: Create an open Wi-Fi network with the SSID "WHY2025-open" (the O not as a capital letter) and run the OTA update app.
* Easy method: Use the [https://why-prog.heplaphon.com/ WHY badge flasher] to install the "BadgeVMS post_event" firmware which includes an app called System Settings which allows you to connect to your home Wi-Fi network.
** This requires a desktop Google Chrome or Microsoft Edge. Firefox is not supported.
** The USB cable must be in the socket on the side. Not the bottom.
** The correct COM port is named "USB Serial". Not "USB Jtag/Serial" or "CDC"
?? What if "USB Serial is not showing up ??
* Developer method:
** Clone the badge firmware repository.
** Edit `wifi_config` in `badgevms/drivers/wifi.c`.
** Change `.ssid` to your network name.
** Directly below `.ssid` add a line with `.password = "your network password",`.
** Then build/flash the firmware: `idf.py build flash`.
* Dev-in-a-hurry:
** Collect the latest firmware here: https://gitlab.com/why2025/team-badge/firmware/-/releases
** use esptool.py -p /dev/cu.wch* write_flash 0 firmware_81d7cdf7.bin
** use the System Settings which allows you to connect to your home Wi-Fi network.

==== There's sticky transparent stuff on my badge, what should I do? ====
* The sticky stuff is UV epoxy that is not fully cured.
* It is very much recommended to fully cure the epoxy first.
** If you have touched the sticky epoxy, wash your hands.
** ⚠️ Note that according to the interwebz some people can be allergic to uncured epoxy. It is not ruled out you may see an allergic reaction. Always contact a medical professional if you see effects and have questions.
* Where can I expect epoxy on my badge?
** Epoxy should have been applied to the ends of the battery holders, where the holders are soldered onto the PCB. There are 4 spots in total. In some cases epoxy may not cover the area that needs protecting.
** You may however also observe epoxy in other spots, such as:
*** The back side near the bottom USB-C port and the screw holes, preventing screws from going through.
*** The front side of the badge near the keyboard, which may prevent the keyboard from fully functioning. This includes the area under the white membrane layer. [https://chaos.social/@edronik/115027350958230845 More information from someone who has experienced this].
*** Basically any place liquid could have flowed to from the location the epoxy was applied since the epoxy was runny when it was applied.
* How to cure the epoxy?
** The epoxy is cured by exposing it to UV light. A popular source of UV light is the sun. Even if it is cloudy or somewhat later in the afternoon, UV light is still present so you don't need to put the badge in the scorching sun to cure the epoxy.
** 1. Shut down badge, remove batteries or any other power source. Do not expose those to the hot sun.
** 2. Place your badge outside in daylight. Make sure all spots that have UV resin on them are exposed. In direct sunlight it is recommended to cover other components.
** 3. Leave for 30 to 60 minutes.
** 4. Regularly check and leave exposed to daylight until all blobs of epoxy have fully cured and are no longer sticky at all. Wash hands after every check.

=== Unanswered ===
* Got a question that is already listed but not answered yet? The ''[number]'' in front of each question is the interest counter. Edit this wiki and increase the counter by one if you have the same question. This allows us to prioritize. Thank you!
* Got an answer? Please edit the wiki, add your answer and move the question to the Answered section. Thank you for your contribution!
==== [4] OTA update screen appears on first boot, after pressing space bar, blue screen with nothing happening for over an hour. ====
* Have the same problem after first OTA update. Update started but the device stuck on bluescreen for an hour or so before I removed power. After flashing a new firmware using the [https://why-prog.heplaphon.com web updater] it works again (use the USB slot on the side, otherwise you get an error message "Your ESP C6 chip is unsupported"). [https://pastebin.com/VjMA5ZZA Logfiles] --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:03, 11 August 2025 (CEST)
** No, it doesn't. It displayed the sponsors page once but returned to the bluescreen afterwards. [https://pastebin.com/cCKejKCk Logs from the side USB port]. --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:18, 11 August 2025 (CEST)
** Uploaded another log containing the complete first boot after flashing the new firmware: https://pastebin.com/3NiSRncL (edit: see below). Note the exception at the end: "Task 4 caused an unhandled exception, Cerberos will deal with it". After that, no new entries appear and the display stays blue. --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:25, 11 August 2025 (CEST)
** Was wrong about that again. There were more log entries while I wrote the previous comments. Here is the complete log: https://pastebin.com/KMQwhBPv --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:34, 11 August 2025 (CEST)
* Anyone managed to fix that errpr and getting the Bagde running again? --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 13:16, 13 August 2025 (CEST)
==== [7] Blue screen. Nothing happening. ====
* => Not official answer: What helped for me was reflashing the badge via the flash station at the badge tent.
* Might be missing symbols, ota might work. Flash, don't reboot yet and ota first.
* Might be because of a known issue regarding the sd card, if you have this issue with an sd card inserted, try again when removing it. See also: [https://gitlab.com/why2025/team-badge/firmware/-/issues?show=eyJpaWQiOiI5IiwiZnVsbF9wYXRoIjoid2h5MjAyNS90ZWFtLWJhZGdlL2Zpcm13YXJlIiwiaWQiOjE3MTg4NzgyNX0%3D Boot is stuck, when fitted with an SD card]

==== [1] Cannot build the firmware from https://gitlab.com/why2025/team-badge/firmware/. Tried to build main and flashed_at_first_handout - both fail because of the following error: https://pastebin.com/H4xwPLhC ====
* Do you have the latest ESP-IDF installed? (Version 5.5)
==== [1] stuck at do_http(https://badge.why2025.org/api/v3/projects/why2025_firmware_ota_c6/rev4/files/version.txt) error: server response: '{"reason":"No app with slug 'why2025_firmware_ota_c6' and revision '4' found"}' ====

==== [5] The badge is not detect on my mac when I connect it by side port: ====
* '''Don't''' use brew, it has been reported not to work.
* Follow these instructions: [[Badge/MacOS_Drivers]]
==== [1] I can't flash the badge - it says the board is incompatible ====
* => Use the USB-C port on the side of the board, not the one on the bottom
==== [1] The letter "a' is represented by a horizontal dash in the nametag app ====
Yet to be answered.
==== [1] The launcher says that "Enter" will launch an app while it really launches when pressing "Space". ====
Yet to be answered.
==== [1] The settings app does react veeeee*ry slowly, sometimes I have to press Enter multiple times to get to the list of WiFi networks (and sometimes, one of those keypresses instantly selects a network) ====
Yet to be answered.

==== [1] How to get the missing apps after reflashing the badge? ====
I have two badges. Badge 1 flashed at the event, and Badge 2 reflashed with "BadgeVMS post-event" using "WHY2025-Open" SSID at home and the web flasher https://why-prog.heplaphon.com/.

Badge 1 shows 11 Applications Available: Game of Life v1, Eat Cheese v1, crackme v3, DOOM Shareware v1, MicroPython v1.0.1, Celeste Classic v1.1, c64emu v2, why2025_sponsors v1, WHY 2025 OTA updater v3, SNAKE! v3, hello v5.

Badge 2 shows 6 Applications Available: WHY2025 Sponsors v1, WHY 2025 OTA updater v4, Name tag v6, SNAKE! v3, hello v5, System settings v1.

How to get the missing apps on the post-event firmware?

[Solved] : Ensure the WIFI and DHCP works...

== Badge Firmware Development related Questions/Issues ==
==== [2] Flashing takes forever (>40 seconds) for a trivial application. Can I speed this up? ====
Yet to be answered.
==== [1] After installing OTA update, application updates AND System Update "BadgeVMS Firmware, Version 4, Main Badge Firmware" the system restarts showing System Updates => "Updates available 1" => "BadgeVMS Firmware, Version 4, Main Badge Firmware". Selecting it, installing it and autorstarting leads back to this same screen. I seem to be stuck in a loop of the update process. ====
* => Shut down your badge by double tapping the power button. Restart. You should now see the application WHY Application Launcher.
** => But double-tapping the power button doesn't shut down the badge...
*** hold ot down for 13+ seconds for a hard reboot.

== BadgeHub related Questions/Issues ==
==== [2] How do I get apps from the BadgeHub onto the Badge? Is it possible without an SD card (I don't have one). I can build apps and flash the firmware, but I have no idea how to get pre-compiled ELFs on there. ====
* => If you have a SD card (if not, the mysteryhack village has a vending machine): Create the folder stucture ./BADGEVMS/APPS on there. In there, create a folder named like the badge hub project name. Download and put the .elf in there. Create a json file with the project name next to the folder and put the key/values for name, unique_identifier, version and binary_path in there. binary_path is just the full name of the .elf file.
** => the mysteryhack village vending machine has been out of SD cards since day 0 or 1

Feedback

2025-08-18T08:49:03Z

Bas: /* Decoration / design */

Feedback

2025-08-18T08:46:37Z

Bas: /* Decoration / design */

Feedback

2025-08-18T08:45:01Z

Bas: /* Teardown */

Feedback

2025-08-18T08:42:18Z

Bas: /* Terrain */

Feedback

2025-08-18T08:39:56Z

Bas: /* Terrain */

Memories

2025-08-18T08:38:22Z

Bas: /* De geit is gemolken */

This is a place to write share and save memories from WHY2025. The fun anecdotes, the shenanigans you pulled, the questionable solutions you hacked together, they weird things you overheard and more. Put photos on snaps.why2025.org and record all the awesomeness that was WHY2025 for the history books.

== Overheard ==
Stuff you heard people say.

==== Drag Race ====
On the Safety-Cala radio channel, the hired security guards in a very serious an professional tone: "There are people on the main road driving with excessive speeds on small vehicles. Not wearing any protective gear. We will intervene" Turns out all the home build carts were racing each other on the Gina Straße and a speed camera was actively used to enforce speed limits.

==== Spritz ====
"Would you mind spritzing on my calves?" 
"Sure, I can rub it in too if you want." 
(It was aftersun spray)

== Etherdiscipline ==
Radio shenanigans, and all things you are not really supposed to do in radio communication.

==== Radio test ====
In the Safety signal app between WD-40 and Central Post: "Geez the Orga radio channel is very quiet. I almost wondering if my radio is broken."
Over the radio on Orga channel: 
"CP to WD-40, CP to WD-40" 
"WD-40 is listening." 
"This is a radio test." 
"WD-40 has clear reception. Thank you!"

==== De geit is gemolken ====
On the Orga channel, out of nowhere, a message was shared: 
''"De geit is gemolken"'' 
Someone chimed in with: 
''"De soep is op"'' 
As a call back to the origin of "de geit is gemolken" someone asked: 
''"De slager is een wat!?"'' 
Not entirely sure what came after that.. '''please add'''! 
After these very silly remarks the channel was quiet, which was the exact right amount of shenanigans without cluttering the channel

It ended at least one time with a PL member saying 'De Maat is VOL'. Which was perfect in line with the joke, well done.

== Making Camp Happen ==
The things we did to make the event work

==== Gate Sign Soldering ====
The WHY2025 sign on top of the gate had +3000 LEDs left to be soldered during buildup. This was done over the course of 3(?) days by over 5 different volunteers. Our interactions went mostly as follows:
* "Don't think. Just solder"

==== Operation Light Bulb ====
Team:Nuts delivered 7000 light bulbs to heaven for the strings of lights lighting up the terrain. Every bulb individually packed in a cardboard box. Without any organization people started helping out unpacking bulbs. Tables were rearranged to lay out out the light strings, put in a rubber gland in each of the 7000 sockets, screw in a light bulb, test the string, roll it up and put back in a crate for distribution around the field. All that happened in about two hours. The happening included multiple hackers diving into the waste paper skip compacting the little boxes and everyone having a good time.

== Numbers ==
The numbers of (fun) things happend. Most of them correct, some guestimated.

* 1 geocache on the terrain
* 8 crocodiles were killed by the Kroko Killer, 1 was spotted in the wild
* 1 purple crocodile survied (again, for 3 camps now)
* 2 shitty floods happend
* 1 hill flooded
* 3 rickrolls happend to all DECTs
* 165 post it's on PLs kanban board
* 52 picturesn on the photowall @ PL
* 1 car yeeted of the terrain by on-site logistics
* 2 rainbows spotted (4 if you count the doormats @ warehouse & PL aswel)
* 35 WHY signal groups per person
* 150 floppies got stickerd
* 1337 ice creams bought
* 1 human secret token
* 1 spelling error was found on the official traffic signs (WYH2025) [[File:Bordje-WYH2025.jpg|16px]]
* 1 rivierkreeftje spotted
* 1 pallet pi(ii)ndakaas was lifted out of a rooftop tent
* 1 speedcamera spotted on the terrain
* 3 birthdays
* 2 blajhajs cought joyriding
* 3 tents wooshed or crashed during WAAI2025
* 1 villagetent crashed by the 5 min super rain during Windy Hackers Yearn 2025
* [x] times bullshit was shouted during the cyber debat with politics
* 1 poweroutage
* 3 flat tires (1 gator, twice of a the same persons car)
* 1 early buildup village blown to pieces (storm)
* 550 liters of soup made by 1 woman
* 1 near miss of drone reversing into a tent peak
* 1x ice cream was made with fire extinguishers
* 210+ Tetra radios on the field
* 154(?) Tetra radios were online at the same time.
* 35km away, Dimitri's laser was spotted
* ....

Badge

2025-08-18T07:37:01Z

Bas: /* m.2 connector */

{{whybox|title=WHY2025 Badge|content=
'''Warning'''
* ⚠️ [[Badge/Fire hazard|Fire Hazard]]
* ⚠️ [https://hsnl.social/@m@martinh.net/115043789003085726 Uncured epoxy] [https://martinh.net/@m/115043788673993241 second link] - wear gloves.

'''Articles'''
* [https://why2025.org/post/494 Blogpost 01] - A First Look at the WHY2025 Badge: Prototyping Complete
* [https://why2025.org/post/697 Blogpost 02] - Build With Us: The WHY2025 Badge and the Last‑Mile Push
* [https://www.youtube.com/watch?v=-uMUSUYVGkU WHYCast Episode41]
* [https://tweakers.net/geek/237414/dit-is-de-why2025-badge-met-twee-esp32s-en-een-loramodule.html Tweakers article] (Dutch) - Dit is de WHY2025-badge met twee ESP32's en een loramodule

'''Documentation'''
* [https://badge.why2025.org/ BadgeHub] and its [https://badge.why2025.org/api-docs/ API Docs]
* [https://gitlab.com/why2025/team-badge Team:Badge GitLab repo] (files + documentation)
* Flash your badge with the BadgeVMS firmware at [https://why-prog.heplaphon.com/ WHY2025 Badge Web Flasher]
* Report your [[Badge Issues]]
* Report your [[Badge App Requests]]
* [[How to develop an app]]
* [[Badge/MacOS_Drivers]]
}}

<hr>

== Reflash your badge ==

You're home and the badge won't update over WiFi anymore?

Use the [https://why-prog.heplaphon.com/ WHY badge flasher] (requires Chrome or Edge browser).

Select "BadgeVMS post_event" for a firmware supporting WiFi setup.

If you don't want to install Chrome or Edge on your machine, you can compile the current firmware version yourself, using the instructions on [[How to develop an app]]. The updated firmware will automatically add the new settings app to your badge.

== Hardware repair ==
=== m.2 connector ===
If the m.2 connection is flaky, the system will probably boot-loop. Symptoms: serial output with hard crashes every few seconds, no backlight/picture. Bas' connector broke off entirely.

* https://hsnl.social/@bas/115048503119046256

[[File:Badge-broken-m2.jpg|thumb]]

Rework the connector with a bit of flux, solder etc and it should be back to normal. Recommended for everyone is to put two *small* drops of self-curing epoxy or a glue on either side of the connector to improve mechanical strength. A user recommended E6000 glue and to let it cure for 24hrs.

A soldering tutorial might appear within a week.

== Batteries ==

* Beware of the [[Badge/Fire hazard]] warning before you use batteries in the device.
* insert Cell Positive (+) side, which is the 'middle' of the badge, first, and Cell Minus (-), near the 'edge' of the badge, second.
* don't forget to take it out when not in use because of https://why2025.org/post/822
* you can flash with the batteries in, for charging you can use any of the two ports.

== Badge Case Info ==

Currently cases are designed around the prototype PCBs. The final boards might be slightly different, so best advise is currently to wait until (after) the camp with printing one - the badges will be usable without a case. Instead, maybe help with printing the 3mm full-frame spaces (see above).

• Designing your own case? Use the existing screw holes on the badge.
• Bring M2 screws, up to 15 mm in length depending on your case design.
• Badges function fully without a case.
• Note: Cases take much longer to print than spacers.

Case Examples by the community:
 
* [https://www.printables.com/model/1372316-why2025-badge-case Semi-official case] by @Dynom
* [https://www.printables.com/model/1376706-why-2025-badge-case-remix Remix of above for printing without supports]
* [https://www.printables.com/model/1377822-why2025-transparent-case Other case design which allows for transparent cases]
* [https://www.printables.com/model/1387194-slim-case-for-why2025-event-badge]
* [https://momakemore.com/micropages/why2025/ Two Case Designs by @MoMakeMore] (based on the cutouts by @Dynom)
** HEAVY - The Camp Case. Full feature, Heavy Duty.
** SLIM - After Camp: Minimal Design, minimal breakouts + Lora, no 18650 support
* [https://www.printables.com/model/1380554-why2025-badge-case-speedy-print-the-boat-hull Speedy Print Case by @MattGrayYes], which can print in under an hour on a Prusa MK4
* [https://www.thingiverse.com/thing:7118590 Top cover for the "semi-official case" by Shmuma (with and without logo versions)]

== Installing apps from BadgeHub via microSD Card ==
You need a microSD card for this.

# 1. Create the folder stucture ./BADGEVMS/APPS on there.
# 2. In the APPS folder, create a folder named like the badge hub project name.
# 3. Download the app from [https://badge.why2025.org/ BadgeHub] and put the .elf in there.
# 4. Create a json file with the project name next to the folder
# 5. Put the key/values for name, unique_identifier, version and binary_path (full name of the .elf file) in that json file.

== ℹ️🪛 Update! State of "Not assembled" Badges ==
For the badges that were handed out in an unassembled state, please make sure to follow this guide for assembly:

2 variants spacers were added to the white bags that were handed out with your badge:
* 1 variant has a fully printed frame with holes on each corner.
** This one needs to be placed between the badge carrier PCB and the front plate and will cover all electronics on the side.

* the other variant has (at least) 4 small black plastic cilinders. The cilinders look like the following:

[[File:Badge with small spacers.jpg|300px|alt=Badge with small spacers]]

Please make sure to install them between the badge and the front plate like this:

[[File:Spacers on badge.jpg|300px|alt=spacers on badge]]
[[File:Screenshot 2025-08-12 at 20.03.55.png|300px|alt=Badge with small spacer installed and front plate screwed.]]

You have installed these correctly if you can see a clear gap between the badge carrier PCB and the front plate like in the picture above.

== Badge Assembly at BadgeTent ==

We aim to conduct the full-scale assembly during the whole day of Friday, which will involve a maximum of 30 volunteers working in the 15*15 meters BadgeTent.

Assembly involves screwing everything together.

Assembling your first '''WHY2025''' badge might feel overwhelming, that’s okay.

Take your time, explore the parts, and build confidence.

With repetition:
* 1st time = You're learning. -> Instructions on how to handle the components will be provided.
* 5th time = You gain confidence by knowing your tools and how to grab them the best way.
* 500th time = Congratulations, you have accomplished the assembly and will have a Foxconn recruiter on the line.

Parts to assemble:
* CarrierBoard
* Keyboard Dome Layer
* Keyboard Silicon Layer
* 3mm Spacers
* 4x M2 Screws
* Front Panel PCB

If you want to help out in the Badge Assembly on Friday during the day -> then join this Signal group.

[https://signal.group/#CjQKIIORCgY9yjX3a834iz-RQeOQu80fIZtg-i3G56EYqnaQEhBaRn9aHmtLggM6oH7dWXC5 Badge Assembly - Signal group].

=== Lessons Learned during Badge Assembly ===

We encountered a small number of badges (three in total) where the Keyboard Dome Layer was slightly misaligned, leading to a few non-responsive keys. Thanks to our initial test-flashing process, we were able to detect these issues early and have since improved our application method for the Dome Layer.

To ensure quality, every badge will undergo a final quality control check, including a visual inspection of the epoxy and final firmware flashing, so that everyone receives a fully functional badge.

== LoRa Details ==

• The LoRa connector will not be pre-soldered but will be handed out as a compontent separately.
• You’ll also receive a screw-on LoRa antenna.

If you want to use another antenna, use a 868MHz antenna with a SMA connector.

Have a look in here:
https://github.com/n0p/mesthastic-fw-why-badge/tree/why2025-badge

https://github.com/n0p/mesthastic-fw-why-badge/blob/why2025-badge/variants/why_badge/variant.h

== SAO's ==
Simple Add-Ons.

* https://github.com/a-little-wifi/WHY2025-SAOadapter

== Photo Sections ==

Pictures of 3D printed Full-frame Spacers:

[[File:Signal-2025-08-04-11-10-44-889.jpg|300px]]

[[File:Geraffel printed.jpg|300px]]

Pictures of WHY2025 Badge Cases:

[[File:Signal-2025-08-03-15-22-08-679.jpg|300px]]

[[File:Signal-2025-08-03-15-22-15-031.jpg|300px]]

[[File:20250804_140303.jpg|300px]]

Pictures of Final WHY2025 Badges with LoRa Antenna:

Martin has build and flashed Doom and the badge is now running Doom. See also [[Badge_Doom_how_to]].

[[File:Doom-Why-Badge.jpg|300px]]

== Replacement parts ==

* Keyboard (buttons) -- https://www.solder.party/keeb/

== 3mm Full-frame Spacer Status ==

* [https://gitlab.com/why2025/team-badge/Hardware/-/blob/main/Spacer/3d_print/Full_Spacer_with_LoRa_Antenna_WHY2025.stl Original spacer]
* [https://www.printables.com/model/1385989-why2025-badge-spacer-with-more-space-for-lora-ante Slightly modified spacer with added space for the LoRa antenna solder joint]

=== Current Contributors ===
{| class="wikitable"
|+ Full-frame Spacer Contributors
|-
! Number
! Credits to
! Printer
! Layer
|-
| 783 || [[Village:Geraffel]] [[File:Geraffel 3D black.jpg|80px|thumb]] || YES, MANY ||
|-
| 343 || Sander {{UserLink|Jar0d}} || BambuLab H2D & X1C ||
|-
| 200 || Klaas ({{UserLink|KlaasYK}}) & Harry & Ilja || Prusa Mk4 & Mk3S and a big thank you to DJO Groningen! ||
|-
| 174 || {{UserLink|krekr}} (Gregor) || Creality K1 Max || 0.2mm
|-
| 105 || Michael ({{UserLink|MikeS}}) || Prusa MK3.9 and two dusted off MK2.5's ||
|-
| 100 || {{UserLink|rick}} || Prusa MK4S|| 0.20mm
|-
| 86 || {{UserLink|Edwinm}} || Prusa MK3 || 0.20mm
|-
|71 || {{UserLink|Sndrsmnk}} || Bambu Lab P1S || 0.20mm
|-
| 68 || {{UserLink|Dude77}} || Bambu Lab P1S || 0.20mm
|-
| >60 || Henri ({{UserLink|Fashice}}) | already at badge tent| ||
|-
| 60 || {{UserLink|Renssies}} || - Bambu Lab X1C 2x (1 @ home, 1 @ work) - Bambu Lab A1 (@ Pixelbar, now @ Village) || 0.20mm
|-
|60 || {{userLink|ScoutHack42}} and buurman || Bambu Lab A1 || 0.20mm
|-
| 58 || Wouter ({{UserLink|Pa3weg}}) || Bambu LAN P1S || 0.20mm
|-
| 50 || Jan-Willem ({{UserLink|jwrm22}}) || Bambu Lab P1S || 0.20mm, suport material stacks
|-
| 46 || Saskia ({{UserLink|Sassy}}) || Prusa MK4S || 0.20mm
|-
| >45 || Alex ({{UserLink|Tinyledmatrix}}) || Prusa MK2, Bambulab A1 Mini, Qidi X-Smart3 ||
|-
|45 || {{userLink|kap}} || Bambu Lab X1C || 0.20 mm
|-
| 42 || {{UserLink|Jelmo2}} || ||
|-
|40 || {{UserLink|Willow}} || Bambu Lab P1S || 0.20mm
|-
|32 || {{UserLink|LordGaav}} || Voron V2.4 (V2.4523) || 0.20mm
|-
| 30 || Fabian || ||
|-
|30 || {{UserLink|Jap}} || Bambu Lab P1S || 0.20mm
|-
| 28 || NinjaLikesCheeze || ||
|-
|21 || {{UserLink|Iikkak}} || Ender 3 S1 pro || 0.20mm
|-
|20 || {{UserLink|MagicalDuck}} || Ender 3 || 0.24mm
|-
|13 || {{userLink|Tijnoz}} || Prusa Mk3.9 || 0.20 mm
|-
|11 || {{UserLink|Bx}} || Bambu Lab X1C || 0.20mm
|-
|11 || {{UserLink|Galactum}} || Bambu Lab A1 || 0.20mm
|-
|>10 || {{UserLink|Habbie}} || Bambu Lab A1 || 0.20mm
|-
| 10 || Frankkie || ||
|-
|10 || {{userLink|Stare}} || Creality CR10 ||
|-
|10> || {{userLink|Jayblue}} || Flashforge Adventurer 5M || 0.20mm
|-
|9 || {{UserLink|q3k}} || MK3S+ || 0.20mm
|-
|8 || {{userLink|fmurodov}} || Bambu Lab A1Mini || 0.20 mm
|-
|6 || {{userLink|FrancisD}} || GEEETECH A20 || 0.20mm
|-
|6 || {{UserLink|Foorschtbar}} || Prusa XL || 0.20mm
|-
| 5 || {{UserLink|Luxim}} || Ender 3 v3 KE || 0.20mm
|-
|5 || {{userLink|PHiAX}} || Creality Ender3 S1 || 0.20 mm
|-
|4 || {{UserLink|Xylitol}} || CR-10S Pro || 0.20mm
|-
| 3 || Wouter || ||
|-
|2 || {{userLink|Miizix}} || Ender 3 || 0.20mm
|-
}

Current total: '''>2702''' units printed / 3500 needed (76.1%)

Add your amount and name to this list. Thank you.

Badge

2025-08-18T07:32:18Z

Bas: /* Hardware repair */

{{whybox|title=WHY2025 Badge|content=
'''Warning'''
* ⚠️ [[Badge/Fire hazard|Fire Hazard]]
* ⚠️ [https://hsnl.social/@m@martinh.net/115043789003085726 Uncured epoxy] [https://martinh.net/@m/115043788673993241 second link] - wear gloves.

'''Articles'''
* [https://why2025.org/post/494 Blogpost 01] - A First Look at the WHY2025 Badge: Prototyping Complete
* [https://why2025.org/post/697 Blogpost 02] - Build With Us: The WHY2025 Badge and the Last‑Mile Push
* [https://www.youtube.com/watch?v=-uMUSUYVGkU WHYCast Episode41]
* [https://tweakers.net/geek/237414/dit-is-de-why2025-badge-met-twee-esp32s-en-een-loramodule.html Tweakers article] (Dutch) - Dit is de WHY2025-badge met twee ESP32's en een loramodule

'''Documentation'''
* [https://badge.why2025.org/ BadgeHub] and its [https://badge.why2025.org/api-docs/ API Docs]
* [https://gitlab.com/why2025/team-badge Team:Badge GitLab repo] (files + documentation)
* Flash your badge with the BadgeVMS firmware at [https://why-prog.heplaphon.com/ WHY2025 Badge Web Flasher]
* Report your [[Badge Issues]]
* Report your [[Badge App Requests]]
* [[How to develop an app]]
* [[Badge/MacOS_Drivers]]
}}

<hr>

== Reflash your badge ==

You're home and the badge won't update over WiFi anymore?

Use the [https://why-prog.heplaphon.com/ WHY badge flasher] (requires Chrome or Edge browser).

Select "BadgeVMS post_event" for a firmware supporting WiFi setup.

If you don't want to install Chrome or Edge on your machine, you can compile the current firmware version yourself, using the instructions on [[How to develop an app]]. The updated firmware will automatically add the new settings app to your badge.

== Hardware repair ==
=== m.2 connector ===
If the m.2 connection is flaky, the system will probably boot-loop. Symptoms: serial output with hard crashes every few seconds, no backlight/picture. Bas' connector broke off entirely.

* https://hsnl.social/@bas/115048503119046256

[[File:Badge-broken-m2.jpg|thumb]]

Rework the connector with a bit of flux, solder etc and it should be back to normal. Recommended for everyone is to put two *small* drops of self-curing epoxy or a glue on either side of the connector to improve mechanical strength.

A soldering tutorial might appear within a week.

== Batteries ==

* Beware of the [[Badge/Fire hazard]] warning before you use batteries in the device.
* insert Cell Positive (+) side, which is the 'middle' of the badge, first, and Cell Minus (-), near the 'edge' of the badge, second.
* don't forget to take it out when not in use because of https://why2025.org/post/822
* you can flash with the batteries in, for charging you can use any of the two ports.

== Badge Case Info ==

Currently cases are designed around the prototype PCBs. The final boards might be slightly different, so best advise is currently to wait until (after) the camp with printing one - the badges will be usable without a case. Instead, maybe help with printing the 3mm full-frame spaces (see above).

• Designing your own case? Use the existing screw holes on the badge.
• Bring M2 screws, up to 15 mm in length depending on your case design.
• Badges function fully without a case.
• Note: Cases take much longer to print than spacers.

Case Examples by the community:
 
* [https://www.printables.com/model/1372316-why2025-badge-case Semi-official case] by @Dynom
* [https://www.printables.com/model/1376706-why-2025-badge-case-remix Remix of above for printing without supports]
* [https://www.printables.com/model/1377822-why2025-transparent-case Other case design which allows for transparent cases]
* [https://www.printables.com/model/1387194-slim-case-for-why2025-event-badge]
* [https://momakemore.com/micropages/why2025/ Two Case Designs by @MoMakeMore] (based on the cutouts by @Dynom)
** HEAVY - The Camp Case. Full feature, Heavy Duty.
** SLIM - After Camp: Minimal Design, minimal breakouts + Lora, no 18650 support
* [https://www.printables.com/model/1380554-why2025-badge-case-speedy-print-the-boat-hull Speedy Print Case by @MattGrayYes], which can print in under an hour on a Prusa MK4
* [https://www.thingiverse.com/thing:7118590 Top cover for the "semi-official case" by Shmuma (with and without logo versions)]

== Installing apps from BadgeHub via microSD Card ==
You need a microSD card for this.

# 1. Create the folder stucture ./BADGEVMS/APPS on there.
# 2. In the APPS folder, create a folder named like the badge hub project name.
# 3. Download the app from [https://badge.why2025.org/ BadgeHub] and put the .elf in there.
# 4. Create a json file with the project name next to the folder
# 5. Put the key/values for name, unique_identifier, version and binary_path (full name of the .elf file) in that json file.

== ℹ️🪛 Update! State of "Not assembled" Badges ==
For the badges that were handed out in an unassembled state, please make sure to follow this guide for assembly:

2 variants spacers were added to the white bags that were handed out with your badge:
* 1 variant has a fully printed frame with holes on each corner.
** This one needs to be placed between the badge carrier PCB and the front plate and will cover all electronics on the side.

* the other variant has (at least) 4 small black plastic cilinders. The cilinders look like the following:

[[File:Badge with small spacers.jpg|300px|alt=Badge with small spacers]]

Please make sure to install them between the badge and the front plate like this:

[[File:Spacers on badge.jpg|300px|alt=spacers on badge]]
[[File:Screenshot 2025-08-12 at 20.03.55.png|300px|alt=Badge with small spacer installed and front plate screwed.]]

You have installed these correctly if you can see a clear gap between the badge carrier PCB and the front plate like in the picture above.

== Badge Assembly at BadgeTent ==

We aim to conduct the full-scale assembly during the whole day of Friday, which will involve a maximum of 30 volunteers working in the 15*15 meters BadgeTent.

Assembly involves screwing everything together.

Assembling your first '''WHY2025''' badge might feel overwhelming, that’s okay.

Take your time, explore the parts, and build confidence.

With repetition:
* 1st time = You're learning. -> Instructions on how to handle the components will be provided.
* 5th time = You gain confidence by knowing your tools and how to grab them the best way.
* 500th time = Congratulations, you have accomplished the assembly and will have a Foxconn recruiter on the line.

Parts to assemble:
* CarrierBoard
* Keyboard Dome Layer
* Keyboard Silicon Layer
* 3mm Spacers
* 4x M2 Screws
* Front Panel PCB

If you want to help out in the Badge Assembly on Friday during the day -> then join this Signal group.

[https://signal.group/#CjQKIIORCgY9yjX3a834iz-RQeOQu80fIZtg-i3G56EYqnaQEhBaRn9aHmtLggM6oH7dWXC5 Badge Assembly - Signal group].

=== Lessons Learned during Badge Assembly ===

We encountered a small number of badges (three in total) where the Keyboard Dome Layer was slightly misaligned, leading to a few non-responsive keys. Thanks to our initial test-flashing process, we were able to detect these issues early and have since improved our application method for the Dome Layer.

To ensure quality, every badge will undergo a final quality control check, including a visual inspection of the epoxy and final firmware flashing, so that everyone receives a fully functional badge.

== LoRa Details ==

• The LoRa connector will not be pre-soldered but will be handed out as a compontent separately.
• You’ll also receive a screw-on LoRa antenna.

If you want to use another antenna, use a 868MHz antenna with a SMA connector.

Have a look in here:
https://github.com/n0p/mesthastic-fw-why-badge/tree/why2025-badge

https://github.com/n0p/mesthastic-fw-why-badge/blob/why2025-badge/variants/why_badge/variant.h

== SAO's ==
Simple Add-Ons.

* https://github.com/a-little-wifi/WHY2025-SAOadapter

== Photo Sections ==

Pictures of 3D printed Full-frame Spacers:

[[File:Signal-2025-08-04-11-10-44-889.jpg|300px]]

[[File:Geraffel printed.jpg|300px]]

Pictures of WHY2025 Badge Cases:

[[File:Signal-2025-08-03-15-22-08-679.jpg|300px]]

[[File:Signal-2025-08-03-15-22-15-031.jpg|300px]]

[[File:20250804_140303.jpg|300px]]

Pictures of Final WHY2025 Badges with LoRa Antenna:

Martin has build and flashed Doom and the badge is now running Doom. See also [[Badge_Doom_how_to]].

[[File:Doom-Why-Badge.jpg|300px]]

== Replacement parts ==

* Keyboard (buttons) -- https://www.solder.party/keeb/

== 3mm Full-frame Spacer Status ==

* [https://gitlab.com/why2025/team-badge/Hardware/-/blob/main/Spacer/3d_print/Full_Spacer_with_LoRa_Antenna_WHY2025.stl Original spacer]
* [https://www.printables.com/model/1385989-why2025-badge-spacer-with-more-space-for-lora-ante Slightly modified spacer with added space for the LoRa antenna solder joint]

=== Current Contributors ===
{| class="wikitable"
|+ Full-frame Spacer Contributors
|-
! Number
! Credits to
! Printer
! Layer
|-
| 783 || [[Village:Geraffel]] [[File:Geraffel 3D black.jpg|80px|thumb]] || YES, MANY ||
|-
| 343 || Sander {{UserLink|Jar0d}} || BambuLab H2D & X1C ||
|-
| 200 || Klaas ({{UserLink|KlaasYK}}) & Harry & Ilja || Prusa Mk4 & Mk3S and a big thank you to DJO Groningen! ||
|-
| 174 || {{UserLink|krekr}} (Gregor) || Creality K1 Max || 0.2mm
|-
| 105 || Michael ({{UserLink|MikeS}}) || Prusa MK3.9 and two dusted off MK2.5's ||
|-
| 100 || {{UserLink|rick}} || Prusa MK4S|| 0.20mm
|-
| 86 || {{UserLink|Edwinm}} || Prusa MK3 || 0.20mm
|-
|71 || {{UserLink|Sndrsmnk}} || Bambu Lab P1S || 0.20mm
|-
| 68 || {{UserLink|Dude77}} || Bambu Lab P1S || 0.20mm
|-
| >60 || Henri ({{UserLink|Fashice}}) | already at badge tent| ||
|-
| 60 || {{UserLink|Renssies}} || - Bambu Lab X1C 2x (1 @ home, 1 @ work) - Bambu Lab A1 (@ Pixelbar, now @ Village) || 0.20mm
|-
|60 || {{userLink|ScoutHack42}} and buurman || Bambu Lab A1 || 0.20mm
|-
| 58 || Wouter ({{UserLink|Pa3weg}}) || Bambu LAN P1S || 0.20mm
|-
| 50 || Jan-Willem ({{UserLink|jwrm22}}) || Bambu Lab P1S || 0.20mm, suport material stacks
|-
| 46 || Saskia ({{UserLink|Sassy}}) || Prusa MK4S || 0.20mm
|-
| >45 || Alex ({{UserLink|Tinyledmatrix}}) || Prusa MK2, Bambulab A1 Mini, Qidi X-Smart3 ||
|-
|45 || {{userLink|kap}} || Bambu Lab X1C || 0.20 mm
|-
| 42 || {{UserLink|Jelmo2}} || ||
|-
|40 || {{UserLink|Willow}} || Bambu Lab P1S || 0.20mm
|-
|32 || {{UserLink|LordGaav}} || Voron V2.4 (V2.4523) || 0.20mm
|-
| 30 || Fabian || ||
|-
|30 || {{UserLink|Jap}} || Bambu Lab P1S || 0.20mm
|-
| 28 || NinjaLikesCheeze || ||
|-
|21 || {{UserLink|Iikkak}} || Ender 3 S1 pro || 0.20mm
|-
|20 || {{UserLink|MagicalDuck}} || Ender 3 || 0.24mm
|-
|13 || {{userLink|Tijnoz}} || Prusa Mk3.9 || 0.20 mm
|-
|11 || {{UserLink|Bx}} || Bambu Lab X1C || 0.20mm
|-
|11 || {{UserLink|Galactum}} || Bambu Lab A1 || 0.20mm
|-
|>10 || {{UserLink|Habbie}} || Bambu Lab A1 || 0.20mm
|-
| 10 || Frankkie || ||
|-
|10 || {{userLink|Stare}} || Creality CR10 ||
|-
|10> || {{userLink|Jayblue}} || Flashforge Adventurer 5M || 0.20mm
|-
|9 || {{UserLink|q3k}} || MK3S+ || 0.20mm
|-
|8 || {{userLink|fmurodov}} || Bambu Lab A1Mini || 0.20 mm
|-
|6 || {{userLink|FrancisD}} || GEEETECH A20 || 0.20mm
|-
|6 || {{UserLink|Foorschtbar}} || Prusa XL || 0.20mm
|-
| 5 || {{UserLink|Luxim}} || Ender 3 v3 KE || 0.20mm
|-
|5 || {{userLink|PHiAX}} || Creality Ender3 S1 || 0.20 mm
|-
|4 || {{UserLink|Xylitol}} || CR-10S Pro || 0.20mm
|-
| 3 || Wouter || ||
|-
|2 || {{userLink|Miizix}} || Ender 3 || 0.20mm
|-
}

Current total: '''>2702''' units printed / 3500 needed (76.1%)

Add your amount and name to this list. Thank you.

Badge

2025-08-18T07:29:28Z

Bas: /* Hardware repair */

{{whybox|title=WHY2025 Badge|content=
'''Warning'''
* ⚠️ [[Badge/Fire hazard|Fire Hazard]]
* ⚠️ [https://hsnl.social/@m@martinh.net/115043789003085726 Uncured epoxy] [https://martinh.net/@m/115043788673993241 second link] - wear gloves.

'''Articles'''
* [https://why2025.org/post/494 Blogpost 01] - A First Look at the WHY2025 Badge: Prototyping Complete
* [https://why2025.org/post/697 Blogpost 02] - Build With Us: The WHY2025 Badge and the Last‑Mile Push
* [https://www.youtube.com/watch?v=-uMUSUYVGkU WHYCast Episode41]
* [https://tweakers.net/geek/237414/dit-is-de-why2025-badge-met-twee-esp32s-en-een-loramodule.html Tweakers article] (Dutch) - Dit is de WHY2025-badge met twee ESP32's en een loramodule

'''Documentation'''
* [https://badge.why2025.org/ BadgeHub] and its [https://badge.why2025.org/api-docs/ API Docs]
* [https://gitlab.com/why2025/team-badge Team:Badge GitLab repo] (files + documentation)
* Flash your badge with the BadgeVMS firmware at [https://why-prog.heplaphon.com/ WHY2025 Badge Web Flasher]
* Report your [[Badge Issues]]
* Report your [[Badge App Requests]]
* [[How to develop an app]]
* [[Badge/MacOS_Drivers]]
}}

<hr>

== Reflash your badge ==

You're home and the badge won't update over WiFi anymore?

Use the [https://why-prog.heplaphon.com/ WHY badge flasher] (requires Chrome or Edge browser).

Select "BadgeVMS post_event" for a firmware supporting WiFi setup.

If you don't want to install Chrome or Edge on your machine, you can compile the current firmware version yourself, using the instructions on [[How to develop an app]]. The updated firmware will automatically add the new settings app to your badge.

== Hardware repair ==
=== m.2 connector ===
If the m.2 connection is flaky, the system will probably boot-loop. Symptoms: serial output with hard crashes every few seconds, no backlight/picture. Bas' connector broke off entirely.

* https://hsnl.social/@bas/115048503119046256

[[File:Badge-broken-m2.jpg|thumb]]

Rework the connector with a bit of flux, solder etc and it should be back to normal. A soldering tutorial might appear within a week.

== Batteries ==

* Beware of the [[Badge/Fire hazard]] warning before you use batteries in the device.
* insert Cell Positive (+) side, which is the 'middle' of the badge, first, and Cell Minus (-), near the 'edge' of the badge, second.
* don't forget to take it out when not in use because of https://why2025.org/post/822
* you can flash with the batteries in, for charging you can use any of the two ports.

== Badge Case Info ==

Currently cases are designed around the prototype PCBs. The final boards might be slightly different, so best advise is currently to wait until (after) the camp with printing one - the badges will be usable without a case. Instead, maybe help with printing the 3mm full-frame spaces (see above).

• Designing your own case? Use the existing screw holes on the badge.
• Bring M2 screws, up to 15 mm in length depending on your case design.
• Badges function fully without a case.
• Note: Cases take much longer to print than spacers.

Case Examples by the community:
 
* [https://www.printables.com/model/1372316-why2025-badge-case Semi-official case] by @Dynom
* [https://www.printables.com/model/1376706-why-2025-badge-case-remix Remix of above for printing without supports]
* [https://www.printables.com/model/1377822-why2025-transparent-case Other case design which allows for transparent cases]
* [https://www.printables.com/model/1387194-slim-case-for-why2025-event-badge]
* [https://momakemore.com/micropages/why2025/ Two Case Designs by @MoMakeMore] (based on the cutouts by @Dynom)
** HEAVY - The Camp Case. Full feature, Heavy Duty.
** SLIM - After Camp: Minimal Design, minimal breakouts + Lora, no 18650 support
* [https://www.printables.com/model/1380554-why2025-badge-case-speedy-print-the-boat-hull Speedy Print Case by @MattGrayYes], which can print in under an hour on a Prusa MK4
* [https://www.thingiverse.com/thing:7118590 Top cover for the "semi-official case" by Shmuma (with and without logo versions)]

== Installing apps from BadgeHub via microSD Card ==
You need a microSD card for this.

# 1. Create the folder stucture ./BADGEVMS/APPS on there.
# 2. In the APPS folder, create a folder named like the badge hub project name.
# 3. Download the app from [https://badge.why2025.org/ BadgeHub] and put the .elf in there.
# 4. Create a json file with the project name next to the folder
# 5. Put the key/values for name, unique_identifier, version and binary_path (full name of the .elf file) in that json file.

== ℹ️🪛 Update! State of "Not assembled" Badges ==
For the badges that were handed out in an unassembled state, please make sure to follow this guide for assembly:

2 variants spacers were added to the white bags that were handed out with your badge:
* 1 variant has a fully printed frame with holes on each corner.
** This one needs to be placed between the badge carrier PCB and the front plate and will cover all electronics on the side.

* the other variant has (at least) 4 small black plastic cilinders. The cilinders look like the following:

[[File:Badge with small spacers.jpg|300px|alt=Badge with small spacers]]

Please make sure to install them between the badge and the front plate like this:

[[File:Spacers on badge.jpg|300px|alt=spacers on badge]]
[[File:Screenshot 2025-08-12 at 20.03.55.png|300px|alt=Badge with small spacer installed and front plate screwed.]]

You have installed these correctly if you can see a clear gap between the badge carrier PCB and the front plate like in the picture above.

== Badge Assembly at BadgeTent ==

We aim to conduct the full-scale assembly during the whole day of Friday, which will involve a maximum of 30 volunteers working in the 15*15 meters BadgeTent.

Assembly involves screwing everything together.

Assembling your first '''WHY2025''' badge might feel overwhelming, that’s okay.

Take your time, explore the parts, and build confidence.

With repetition:
* 1st time = You're learning. -> Instructions on how to handle the components will be provided.
* 5th time = You gain confidence by knowing your tools and how to grab them the best way.
* 500th time = Congratulations, you have accomplished the assembly and will have a Foxconn recruiter on the line.

Parts to assemble:
* CarrierBoard
* Keyboard Dome Layer
* Keyboard Silicon Layer
* 3mm Spacers
* 4x M2 Screws
* Front Panel PCB

If you want to help out in the Badge Assembly on Friday during the day -> then join this Signal group.

[https://signal.group/#CjQKIIORCgY9yjX3a834iz-RQeOQu80fIZtg-i3G56EYqnaQEhBaRn9aHmtLggM6oH7dWXC5 Badge Assembly - Signal group].

=== Lessons Learned during Badge Assembly ===

We encountered a small number of badges (three in total) where the Keyboard Dome Layer was slightly misaligned, leading to a few non-responsive keys. Thanks to our initial test-flashing process, we were able to detect these issues early and have since improved our application method for the Dome Layer.

To ensure quality, every badge will undergo a final quality control check, including a visual inspection of the epoxy and final firmware flashing, so that everyone receives a fully functional badge.

== LoRa Details ==

• The LoRa connector will not be pre-soldered but will be handed out as a compontent separately.
• You’ll also receive a screw-on LoRa antenna.

If you want to use another antenna, use a 868MHz antenna with a SMA connector.

Have a look in here:
https://github.com/n0p/mesthastic-fw-why-badge/tree/why2025-badge

https://github.com/n0p/mesthastic-fw-why-badge/blob/why2025-badge/variants/why_badge/variant.h

== SAO's ==
Simple Add-Ons.

* https://github.com/a-little-wifi/WHY2025-SAOadapter

== Photo Sections ==

Pictures of 3D printed Full-frame Spacers:

[[File:Signal-2025-08-04-11-10-44-889.jpg|300px]]

[[File:Geraffel printed.jpg|300px]]

Pictures of WHY2025 Badge Cases:

[[File:Signal-2025-08-03-15-22-08-679.jpg|300px]]

[[File:Signal-2025-08-03-15-22-15-031.jpg|300px]]

[[File:20250804_140303.jpg|300px]]

Pictures of Final WHY2025 Badges with LoRa Antenna:

Martin has build and flashed Doom and the badge is now running Doom. See also [[Badge_Doom_how_to]].

[[File:Doom-Why-Badge.jpg|300px]]

== Replacement parts ==

* Keyboard (buttons) -- https://www.solder.party/keeb/

== 3mm Full-frame Spacer Status ==

* [https://gitlab.com/why2025/team-badge/Hardware/-/blob/main/Spacer/3d_print/Full_Spacer_with_LoRa_Antenna_WHY2025.stl Original spacer]
* [https://www.printables.com/model/1385989-why2025-badge-spacer-with-more-space-for-lora-ante Slightly modified spacer with added space for the LoRa antenna solder joint]

=== Current Contributors ===
{| class="wikitable"
|+ Full-frame Spacer Contributors
|-
! Number
! Credits to
! Printer
! Layer
|-
| 783 || [[Village:Geraffel]] [[File:Geraffel 3D black.jpg|80px|thumb]] || YES, MANY ||
|-
| 343 || Sander {{UserLink|Jar0d}} || BambuLab H2D & X1C ||
|-
| 200 || Klaas ({{UserLink|KlaasYK}}) & Harry & Ilja || Prusa Mk4 & Mk3S and a big thank you to DJO Groningen! ||
|-
| 174 || {{UserLink|krekr}} (Gregor) || Creality K1 Max || 0.2mm
|-
| 105 || Michael ({{UserLink|MikeS}}) || Prusa MK3.9 and two dusted off MK2.5's ||
|-
| 100 || {{UserLink|rick}} || Prusa MK4S|| 0.20mm
|-
| 86 || {{UserLink|Edwinm}} || Prusa MK3 || 0.20mm
|-
|71 || {{UserLink|Sndrsmnk}} || Bambu Lab P1S || 0.20mm
|-
| 68 || {{UserLink|Dude77}} || Bambu Lab P1S || 0.20mm
|-
| >60 || Henri ({{UserLink|Fashice}}) | already at badge tent| ||
|-
| 60 || {{UserLink|Renssies}} || - Bambu Lab X1C 2x (1 @ home, 1 @ work) - Bambu Lab A1 (@ Pixelbar, now @ Village) || 0.20mm
|-
|60 || {{userLink|ScoutHack42}} and buurman || Bambu Lab A1 || 0.20mm
|-
| 58 || Wouter ({{UserLink|Pa3weg}}) || Bambu LAN P1S || 0.20mm
|-
| 50 || Jan-Willem ({{UserLink|jwrm22}}) || Bambu Lab P1S || 0.20mm, suport material stacks
|-
| 46 || Saskia ({{UserLink|Sassy}}) || Prusa MK4S || 0.20mm
|-
| >45 || Alex ({{UserLink|Tinyledmatrix}}) || Prusa MK2, Bambulab A1 Mini, Qidi X-Smart3 ||
|-
|45 || {{userLink|kap}} || Bambu Lab X1C || 0.20 mm
|-
| 42 || {{UserLink|Jelmo2}} || ||
|-
|40 || {{UserLink|Willow}} || Bambu Lab P1S || 0.20mm
|-
|32 || {{UserLink|LordGaav}} || Voron V2.4 (V2.4523) || 0.20mm
|-
| 30 || Fabian || ||
|-
|30 || {{UserLink|Jap}} || Bambu Lab P1S || 0.20mm
|-
| 28 || NinjaLikesCheeze || ||
|-
|21 || {{UserLink|Iikkak}} || Ender 3 S1 pro || 0.20mm
|-
|20 || {{UserLink|MagicalDuck}} || Ender 3 || 0.24mm
|-
|13 || {{userLink|Tijnoz}} || Prusa Mk3.9 || 0.20 mm
|-
|11 || {{UserLink|Bx}} || Bambu Lab X1C || 0.20mm
|-
|11 || {{UserLink|Galactum}} || Bambu Lab A1 || 0.20mm
|-
|>10 || {{UserLink|Habbie}} || Bambu Lab A1 || 0.20mm
|-
| 10 || Frankkie || ||
|-
|10 || {{userLink|Stare}} || Creality CR10 ||
|-
|10> || {{userLink|Jayblue}} || Flashforge Adventurer 5M || 0.20mm
|-
|9 || {{UserLink|q3k}} || MK3S+ || 0.20mm
|-
|8 || {{userLink|fmurodov}} || Bambu Lab A1Mini || 0.20 mm
|-
|6 || {{userLink|FrancisD}} || GEEETECH A20 || 0.20mm
|-
|6 || {{UserLink|Foorschtbar}} || Prusa XL || 0.20mm
|-
| 5 || {{UserLink|Luxim}} || Ender 3 v3 KE || 0.20mm
|-
|5 || {{userLink|PHiAX}} || Creality Ender3 S1 || 0.20 mm
|-
|4 || {{UserLink|Xylitol}} || CR-10S Pro || 0.20mm
|-
| 3 || Wouter || ||
|-
|2 || {{userLink|Miizix}} || Ender 3 || 0.20mm
|-
}

Current total: '''>2702''' units printed / 3500 needed (76.1%)

Add your amount and name to this list. Thank you.

Badge

2025-08-18T07:29:03Z

Bas:

{{whybox|title=WHY2025 Badge|content=
'''Warning'''
* ⚠️ [[Badge/Fire hazard|Fire Hazard]]
* ⚠️ [https://hsnl.social/@m@martinh.net/115043789003085726 Uncured epoxy] [https://martinh.net/@m/115043788673993241 second link] - wear gloves.

'''Articles'''
* [https://why2025.org/post/494 Blogpost 01] - A First Look at the WHY2025 Badge: Prototyping Complete
* [https://why2025.org/post/697 Blogpost 02] - Build With Us: The WHY2025 Badge and the Last‑Mile Push
* [https://www.youtube.com/watch?v=-uMUSUYVGkU WHYCast Episode41]
* [https://tweakers.net/geek/237414/dit-is-de-why2025-badge-met-twee-esp32s-en-een-loramodule.html Tweakers article] (Dutch) - Dit is de WHY2025-badge met twee ESP32's en een loramodule

'''Documentation'''
* [https://badge.why2025.org/ BadgeHub] and its [https://badge.why2025.org/api-docs/ API Docs]
* [https://gitlab.com/why2025/team-badge Team:Badge GitLab repo] (files + documentation)
* Flash your badge with the BadgeVMS firmware at [https://why-prog.heplaphon.com/ WHY2025 Badge Web Flasher]
* Report your [[Badge Issues]]
* Report your [[Badge App Requests]]
* [[How to develop an app]]
* [[Badge/MacOS_Drivers]]
}}

<hr>

== Reflash your badge ==

You're home and the badge won't update over WiFi anymore?

Use the [https://why-prog.heplaphon.com/ WHY badge flasher] (requires Chrome or Edge browser).

Select "BadgeVMS post_event" for a firmware supporting WiFi setup.

If you don't want to install Chrome or Edge on your machine, you can compile the current firmware version yourself, using the instructions on [[How to develop an app]]. The updated firmware will automatically add the new settings app to your badge.

== Hardware repair ==

If the m.2 connection is flaky, the system will probably boot-loop. Symptoms: serial output with hard crashes every few seconds, no backlight/picture. Bas' connector broke off entirely.

* https://hsnl.social/@bas/115048503119046256

[[File:Badge-broken-m2.jpg|thumb]]

Rework the connector with a bit of flux, solder etc and it should be back to normal. A soldering tutorial might appear within a week.

== Batteries ==

* Beware of the [[Badge/Fire hazard]] warning before you use batteries in the device.
* insert Cell Positive (+) side, which is the 'middle' of the badge, first, and Cell Minus (-), near the 'edge' of the badge, second.
* don't forget to take it out when not in use because of https://why2025.org/post/822
* you can flash with the batteries in, for charging you can use any of the two ports.

== Badge Case Info ==

Currently cases are designed around the prototype PCBs. The final boards might be slightly different, so best advise is currently to wait until (after) the camp with printing one - the badges will be usable without a case. Instead, maybe help with printing the 3mm full-frame spaces (see above).

• Designing your own case? Use the existing screw holes on the badge.
• Bring M2 screws, up to 15 mm in length depending on your case design.
• Badges function fully without a case.
• Note: Cases take much longer to print than spacers.

Case Examples by the community:
 
* [https://www.printables.com/model/1372316-why2025-badge-case Semi-official case] by @Dynom
* [https://www.printables.com/model/1376706-why-2025-badge-case-remix Remix of above for printing without supports]
* [https://www.printables.com/model/1377822-why2025-transparent-case Other case design which allows for transparent cases]
* [https://www.printables.com/model/1387194-slim-case-for-why2025-event-badge]
* [https://momakemore.com/micropages/why2025/ Two Case Designs by @MoMakeMore] (based on the cutouts by @Dynom)
** HEAVY - The Camp Case. Full feature, Heavy Duty.
** SLIM - After Camp: Minimal Design, minimal breakouts + Lora, no 18650 support
* [https://www.printables.com/model/1380554-why2025-badge-case-speedy-print-the-boat-hull Speedy Print Case by @MattGrayYes], which can print in under an hour on a Prusa MK4
* [https://www.thingiverse.com/thing:7118590 Top cover for the "semi-official case" by Shmuma (with and without logo versions)]

== Installing apps from BadgeHub via microSD Card ==
You need a microSD card for this.

# 1. Create the folder stucture ./BADGEVMS/APPS on there.
# 2. In the APPS folder, create a folder named like the badge hub project name.
# 3. Download the app from [https://badge.why2025.org/ BadgeHub] and put the .elf in there.
# 4. Create a json file with the project name next to the folder
# 5. Put the key/values for name, unique_identifier, version and binary_path (full name of the .elf file) in that json file.

== ℹ️🪛 Update! State of "Not assembled" Badges ==
For the badges that were handed out in an unassembled state, please make sure to follow this guide for assembly:

2 variants spacers were added to the white bags that were handed out with your badge:
* 1 variant has a fully printed frame with holes on each corner.
** This one needs to be placed between the badge carrier PCB and the front plate and will cover all electronics on the side.

* the other variant has (at least) 4 small black plastic cilinders. The cilinders look like the following:

[[File:Badge with small spacers.jpg|300px|alt=Badge with small spacers]]

Please make sure to install them between the badge and the front plate like this:

[[File:Spacers on badge.jpg|300px|alt=spacers on badge]]
[[File:Screenshot 2025-08-12 at 20.03.55.png|300px|alt=Badge with small spacer installed and front plate screwed.]]

You have installed these correctly if you can see a clear gap between the badge carrier PCB and the front plate like in the picture above.

== Badge Assembly at BadgeTent ==

We aim to conduct the full-scale assembly during the whole day of Friday, which will involve a maximum of 30 volunteers working in the 15*15 meters BadgeTent.

Assembly involves screwing everything together.

Assembling your first '''WHY2025''' badge might feel overwhelming, that’s okay.

Take your time, explore the parts, and build confidence.

With repetition:
* 1st time = You're learning. -> Instructions on how to handle the components will be provided.
* 5th time = You gain confidence by knowing your tools and how to grab them the best way.
* 500th time = Congratulations, you have accomplished the assembly and will have a Foxconn recruiter on the line.

Parts to assemble:
* CarrierBoard
* Keyboard Dome Layer
* Keyboard Silicon Layer
* 3mm Spacers
* 4x M2 Screws
* Front Panel PCB

If you want to help out in the Badge Assembly on Friday during the day -> then join this Signal group.

[https://signal.group/#CjQKIIORCgY9yjX3a834iz-RQeOQu80fIZtg-i3G56EYqnaQEhBaRn9aHmtLggM6oH7dWXC5 Badge Assembly - Signal group].

=== Lessons Learned during Badge Assembly ===

We encountered a small number of badges (three in total) where the Keyboard Dome Layer was slightly misaligned, leading to a few non-responsive keys. Thanks to our initial test-flashing process, we were able to detect these issues early and have since improved our application method for the Dome Layer.

To ensure quality, every badge will undergo a final quality control check, including a visual inspection of the epoxy and final firmware flashing, so that everyone receives a fully functional badge.

== LoRa Details ==

• The LoRa connector will not be pre-soldered but will be handed out as a compontent separately.
• You’ll also receive a screw-on LoRa antenna.

If you want to use another antenna, use a 868MHz antenna with a SMA connector.

Have a look in here:
https://github.com/n0p/mesthastic-fw-why-badge/tree/why2025-badge

https://github.com/n0p/mesthastic-fw-why-badge/blob/why2025-badge/variants/why_badge/variant.h

== SAO's ==
Simple Add-Ons.

* https://github.com/a-little-wifi/WHY2025-SAOadapter

== Photo Sections ==

Pictures of 3D printed Full-frame Spacers:

[[File:Signal-2025-08-04-11-10-44-889.jpg|300px]]

[[File:Geraffel printed.jpg|300px]]

Pictures of WHY2025 Badge Cases:

[[File:Signal-2025-08-03-15-22-08-679.jpg|300px]]

[[File:Signal-2025-08-03-15-22-15-031.jpg|300px]]

[[File:20250804_140303.jpg|300px]]

Pictures of Final WHY2025 Badges with LoRa Antenna:

Martin has build and flashed Doom and the badge is now running Doom. See also [[Badge_Doom_how_to]].

[[File:Doom-Why-Badge.jpg|300px]]

== Replacement parts ==

* Keyboard (buttons) -- https://www.solder.party/keeb/

== 3mm Full-frame Spacer Status ==

* [https://gitlab.com/why2025/team-badge/Hardware/-/blob/main/Spacer/3d_print/Full_Spacer_with_LoRa_Antenna_WHY2025.stl Original spacer]
* [https://www.printables.com/model/1385989-why2025-badge-spacer-with-more-space-for-lora-ante Slightly modified spacer with added space for the LoRa antenna solder joint]

=== Current Contributors ===
{| class="wikitable"
|+ Full-frame Spacer Contributors
|-
! Number
! Credits to
! Printer
! Layer
|-
| 783 || [[Village:Geraffel]] [[File:Geraffel 3D black.jpg|80px|thumb]] || YES, MANY ||
|-
| 343 || Sander {{UserLink|Jar0d}} || BambuLab H2D & X1C ||
|-
| 200 || Klaas ({{UserLink|KlaasYK}}) & Harry & Ilja || Prusa Mk4 & Mk3S and a big thank you to DJO Groningen! ||
|-
| 174 || {{UserLink|krekr}} (Gregor) || Creality K1 Max || 0.2mm
|-
| 105 || Michael ({{UserLink|MikeS}}) || Prusa MK3.9 and two dusted off MK2.5's ||
|-
| 100 || {{UserLink|rick}} || Prusa MK4S|| 0.20mm
|-
| 86 || {{UserLink|Edwinm}} || Prusa MK3 || 0.20mm
|-
|71 || {{UserLink|Sndrsmnk}} || Bambu Lab P1S || 0.20mm
|-
| 68 || {{UserLink|Dude77}} || Bambu Lab P1S || 0.20mm
|-
| >60 || Henri ({{UserLink|Fashice}}) | already at badge tent| ||
|-
| 60 || {{UserLink|Renssies}} || - Bambu Lab X1C 2x (1 @ home, 1 @ work) - Bambu Lab A1 (@ Pixelbar, now @ Village) || 0.20mm
|-
|60 || {{userLink|ScoutHack42}} and buurman || Bambu Lab A1 || 0.20mm
|-
| 58 || Wouter ({{UserLink|Pa3weg}}) || Bambu LAN P1S || 0.20mm
|-
| 50 || Jan-Willem ({{UserLink|jwrm22}}) || Bambu Lab P1S || 0.20mm, suport material stacks
|-
| 46 || Saskia ({{UserLink|Sassy}}) || Prusa MK4S || 0.20mm
|-
| >45 || Alex ({{UserLink|Tinyledmatrix}}) || Prusa MK2, Bambulab A1 Mini, Qidi X-Smart3 ||
|-
|45 || {{userLink|kap}} || Bambu Lab X1C || 0.20 mm
|-
| 42 || {{UserLink|Jelmo2}} || ||
|-
|40 || {{UserLink|Willow}} || Bambu Lab P1S || 0.20mm
|-
|32 || {{UserLink|LordGaav}} || Voron V2.4 (V2.4523) || 0.20mm
|-
| 30 || Fabian || ||
|-
|30 || {{UserLink|Jap}} || Bambu Lab P1S || 0.20mm
|-
| 28 || NinjaLikesCheeze || ||
|-
|21 || {{UserLink|Iikkak}} || Ender 3 S1 pro || 0.20mm
|-
|20 || {{UserLink|MagicalDuck}} || Ender 3 || 0.24mm
|-
|13 || {{userLink|Tijnoz}} || Prusa Mk3.9 || 0.20 mm
|-
|11 || {{UserLink|Bx}} || Bambu Lab X1C || 0.20mm
|-
|11 || {{UserLink|Galactum}} || Bambu Lab A1 || 0.20mm
|-
|>10 || {{UserLink|Habbie}} || Bambu Lab A1 || 0.20mm
|-
| 10 || Frankkie || ||
|-
|10 || {{userLink|Stare}} || Creality CR10 ||
|-
|10> || {{userLink|Jayblue}} || Flashforge Adventurer 5M || 0.20mm
|-
|9 || {{UserLink|q3k}} || MK3S+ || 0.20mm
|-
|8 || {{userLink|fmurodov}} || Bambu Lab A1Mini || 0.20 mm
|-
|6 || {{userLink|FrancisD}} || GEEETECH A20 || 0.20mm
|-
|6 || {{UserLink|Foorschtbar}} || Prusa XL || 0.20mm
|-
| 5 || {{UserLink|Luxim}} || Ender 3 v3 KE || 0.20mm
|-
|5 || {{userLink|PHiAX}} || Creality Ender3 S1 || 0.20 mm
|-
|4 || {{UserLink|Xylitol}} || CR-10S Pro || 0.20mm
|-
| 3 || Wouter || ||
|-
|2 || {{userLink|Miizix}} || Ender 3 || 0.20mm
|-
}

Current total: '''>2702''' units printed / 3500 needed (76.1%)

Add your amount and name to this list. Thank you.

File:Badge-broken-m2.jpg

2025-08-18T07:27:39Z

Bas:

A badge with a broken off m.2 connector.

FAQ

2025-08-05T08:55:50Z

Bas: /* How is waste-disposal arranged? */

[[Category:FAQ]]
'''WHY2025''' is approaching quickly, and you might have questions about the event, planning, or facilities.

We’ve gathered common questions from past camps and this year’s preparations in this '''FAQ'''.

While we’re still finalizing many details, please note that the information here may change or require confirmation.

Have a question that’s not covered on this page?

Feel free to mail '''[mailto:info@why2025.org the Infodesk]'''

= Useful links=

* Do you have a question about tickets? See [[Tickets]]
* Are you an (aspiring) speaker? Check the [[Speaker FAQ]]
* Do you have a question about volunteering? See [[Volunteering_Guide]] or contact [[Team:Volunteers]]
* Are you a member of the press? Contact [[Team:Press]]
* Do you want to help with promotion/marketing? Contact [[Team:Info]] or [[User:Boekenwuurm]]
* Do you have a question about children at the event? Checkout the [[Family FAQ]] or contact [[Team:Family]]
* Do you have a question about villages? Contact [[Team:Villages]]
* Do you have a question about the network? Please check out [[Network]] or contact [[Team:NOC]]
* Do you have a question and don't know where to go? Contact [[Team:Info]] at info@why2025.org
* Are you looking for a phone number? [https://micropoc.de/phonebook Check the phonebook!]

= General =
=== Who is '''WHY''' for? ===
If you enjoy creative use of technology and are not afraid of the [https://arnout.engelen.eu/20000612.gif big blue room] then '''WHY''' might be a great event for you! Individual hackers age 16 and up are welcome, and hacker parents are welcome to [[Family_FAQ|bring their kids]] as well.

=== What does '''WHY''' stand for? ===

'''WHY''' stands for '''What Hackers Yearn''' for.

In the long standing tradition starting with the '''Galactic Hacker Party (GHP)''', every four (or during a pandemic five) years the Dutch hackerscene organizes a new camp with a new name.

Want know more, then explore the '''[[History of Dutch Hacker Camps]]''' about previous events like '''GHP, HEU, HIP, HAL, WTH, HAR, OHM, SHA or MCH'''.

=== What are the dates of WHY2025?===
The first '''WHY2025''' talk starts on '''Friday 8th of August''' at 17:00
and the event ends '''Tuesday 12th of August''' with the closing talk at 16:00.

=== Is there a schedule for the build-up ? ===
Yes, see [[Camping]]. Build-up planning follows soon.

=== When can I enter the terrain? ===
Visitors are welcome from '''Thursday 7th of August at noon (12:00)'''.

If you booked a village, you can start '''Wednesday 6th of August''' with the build up of your village.

-> At the time of writing (June 2025) this it is not final yet, therefore do keep checking the official schedule when closer to the event in August 2025.

If you want to help during build up, you are very welcome to do so.

We can really use some strong extra hands.

Please contact us before planning your extended stay.

Shifts will be added to the '''[https://angel.why2025.org/ Engelsystem]''' closer to the event, so make sure to check in the weeks before the event starts and make sure to register and to sign-up in the engelsystem.

===Where's my ticket?===
If you have ordered a ticket and received confirmation, the ticket will be in your email inbox.

See [[Tickets]] for more information.

=== What about accessibility? ===
First and foremost we will make sure toilet and shower facilities will be accessible.

Beyond that, if you have a specific disability please contact us so we can discuss what is needed to make your stay as comfortable as possible.

[[Team:Accessibility]] is working on making the most accessible event ever in Dutch Hacker History.

Do note that we are limited by the fact that we are an outdoor camping event, so for example we cannot give hard guarantees about the availability of reliable power on the field for medical devices. Nonetheless, we always try to do our best.

=== Children during build up ===

Please note that during build up kids <12 are not allowed on the terrain.

Older kids (12+) can help but have to be under adult supervision and wear a hi-vis vest '''AT ALL TIMES''' when outside their own tent. '''Even during non-working hours.'''

If kids (12+) don't help with build up, they have to be in the designated safe area.

=== Is there merchandise? A free volunteer shirt? ===
There is, goto https://tickets.why2025.org and order your merch right now.

If you do not order it in advance, it is probably sold out.

You can try your luck at the last day, to see what is left.

The Angel shirts are for those who've helped 3 days with build-up, or did 20 hours of shifts registered in the Engelsystem, or are part of the Orga.

=== Can I help? ===
We love to have some help. You can help in several ways, both before and during '''WHY2025'''.

Leading up to the event, you can help with the Orga.

This will give you unique possibilities to learn stuff and expand your skill set, while you have fun with other people and be involved with the event.

See team pages for available positions.

If you want to help out during the event, that will be great too.

You will be able to register as an angel in the weeks before the camp in the [https://angel.why2025.org/ Engelsystem].

It's still a bit empty now, but there will be many, many shifts and jobs to choose from.

'''More information will become available closer to the event.'''

=== Can my child help? ===
Yes. We encourage the next generation to be part of the camp as much as anyone else.

We are working on putting special children's tasks in the Engelystem, for kids to have an age-appropriate way to help out during the camp.

All kids age 6 and up can sign up.

=== I lost something! ===
We will have a Lost & Found at [[the Infodesk]].

If you lose something:
* Check the immediate area to see if you or someone else misplaced your item as it happens.
* Ask your friends if they know where your item is. They might have put it somewhere safe for you.
* You can go to [[the Infodesk]] tent to see if someone brought your item in. '''If the item is labeled properly, we might even contact you.'''
* If not: report the item as missing so we can keep an eye out for it. and contact you if it is found.
* If you think the item might be stolen, we can help you with the next steps.
* We will publish a list of items that are in lost and found after the event.

=== How can I pay? ===
Generally speaking, you can pay with your debit/credit card everywhere on site, as '''WHY2025''' is a "cashless festival". This includes the bars, foodcourt, merchandise and supermarket.

Should you not wish to pay by card, you can exchange cash into a prepaid payment voucher at the Infodesk.

For more details about the system see [[WHY2025 Payment System]]

= Camping, buildup & teardown and villages =

=== I want to help during build up ===
Great! Volunteers that want to help during buildup are welcome to show up on Saturday August 2 at the earliest. You tell us that you'll arrive on a date by carefully entering your arrival date in [https://angel.why2025.org/ Engelsystem]. No other registration required.

=== I want to help with tear-down ===
Great. Indicate in the volunteer system when you should be able to help.

If you don't want to help, that's fine too. But you will have to leave the campsite before 2025-08-13, 12:00.

=== Villages and their build up - what is the schedule? ===
Villages take some more time to build up. Therefore, organizers of pre-registered villages can enter the camp terrain from 6th of August at noon (12:00).

Please check the [[Villages-FAQ]] for details.

=== Is all the camping equipment provided and everything set up? ===
No, there is no camping equipment provided.

You need to bring your own tent and pitch it.

There are plenty of experienced hackers who can be helpful in setting it up.

=== I do not own a tent or cannot bring it in the plane, now what? ===
* Rent-A-Tent no longer available
<s>* Rent-A-Tent - It is a first time ever that we have a rent-a-tent option available for '''WHY2025''' in the ticketsystem.</s>

=== Can I bring my campervan or (folding) trailer onto the field? ===
'''You can only bring a camper or caravan if you have booked a special campervan/trailer ticket.'''

Check [[Campervan]] for more information on bringing your home-on-wheels.

Campers/caravans can only be located in one of the designated camper-van locations and will not be able to drive on/off field during the event.

'''Trailers (including folding/ tent-trailers)''' are considered the same as regular tents and can be on any field available to normal tents. They can '''not''' be moved during the event and should be positioned so that they do not block fire lanes or footpaths. Bonus points if your trailer doesn't look boring!
Cars are not allowed on the grass, so the trailer must pushed on the the fields by hand from the nearest hard road and you should bring wooden plate to put under the wheels.
Please check the [[Villages-FAQ]] for details.

=== Where can I set up my tent if I'm not part of a village? ===

Village areas are soft guidelines, not hard land claims, so feel free to find an empty spot and prepare to be a bit flexible. On larger villages, such as [[Village:milliways]], try to find someone who can coordinate placement. There are also some areas on the [https://map.why2025.org map] that are explicitly marked "free for all".

=== I need a shuttle to the station of Alkmaar Station? ===
The Shuttle_service is scheduled:
* [[Shuttle_Service]]

It departs from across the First Aid tent. <<verification needed>>

=== I need a ride to the station of <location of station> on another time? ===
* Take a regular bus. There is a bus stop not far from the site https://9292.nl/<details will follow>.
It leaves every hour from 6:39 up till 18:39.
The ride takes around 20 minutes.
Note: You cannot pay cash in the bus anymore.

* Call a taxi.

* Take a walk to the station.

=== Until when do I have power? ===
We will start shutdown power after the closing talk on Tuesday the 12th of August.
We start with the most empty fields and work our way up from there.
The last fields will lose power at some point Wednesday the 13th of August.

=== I need power for medical reasons, do you provide that? ===
If you require electricity for medical equipment such as a CPAP machine, please bring your own extension cord or cable spool to connect to the available power supply. In case of unforeseen power outages, it's recommended to bring a UPS.

=== What are the conditions on the terrain? What type of soil should I expect? ===
The terrain is grassy with soft soil. Due to the weather conditions in the days leading up to the event, the terrain might be wet and muddy when you arrive. [https://snaps.why2025.org Current pictures from build-up] will give you an idea of what to expect.

= Regulations =
=== What about noise, music and such? ===
Mind (y)our neighbors.
'''We like to keep it quiet from 23:00 till 9:00.'''
Around those times loud noise/music is not allowed.
If you want to make noise, start earlier.

Bottom left is noisiest, top right is quietest, see [https://wiki.why2025.org/Team:Villages#Noise_Gradient noise gradient]

To make sure our youngest guests get enough sleep, '''the camping around the FamilyZone has to be quiet from 21:00'''.

=== What is the photo/video policy for WHY2025? ===
When taking photos or recordings, always ask for clear consent, and do not touch anyone’s tech or setup without permission. Be mindful of others' privacy before taking recognisable pictures of strangers.

The decent thing to do is ask before you take a picture or video.
Not everyone wants to have their photo taken, and some might especially dislike finding themselves on the internet.
Large crowd shots are fine, as are other pictures where people are clearly unrecognizable.
Also no live streaming as you walk around the event.
Some areas and villages will be picture-free zones, make sure to follow the local guidelines.

'''Note:''' Be aware that the awesome projects the villages are hosting, may contain cameras or webcams.
from the code of conduct:

We all yearn for a bit of privacy. Taking a photo or video of a project or art installation is fine. Respect the privacy of others. Before you take pictures of strangers, ask for clear consent. The same applies if you wish to touch or alter someone else's setup.

=== How is waste-disposal arranged? ===
Regular event waste (trash bags) can be disposed of in one of the many bins around the fields. We prefer you use the ones near each set of showers/toilets for your village-trash. The ones at the track/workshop/etc tents are for small litter like a napkin you need to get rid of before going to see a talk.

For larger items (not household trash): Please take home everything you bring to '''WHY2025'''.

Bear in mind that everything you leave behind will cost us valuable volunteer time and possibly a lot of money that we would rather be spending on more fun stuff.

If you really want to get rid of bulk waste (grof vuil), like for instance a sofa, it might be possible to rent a bulk container for you. This will be very expensive, and needs to be paid up front. Check with the [mailto:info@why2025.org Infodesk] to see what we can arrange.

At the end of camp we will organize a free stuff area where you can bring your working cool things (like a nice working tent, airbed or sleeping bag). Note that the area will be monitored and the angel may refuse your contribution and defer you to the recycling bin or your car. More details to follow.

'''Don't leave bulk waste on the terrain.'''

===Are open fires allowed (bonfire, barbecue, ...)?===
No, unfortunately not because of safety reasons.
Open fire is anything that is not gas powered. Allowed are (butane, propane) powered stoves and barbecue grills.
Please make sure u have a fire-extinguisher in the area.

Check the Fire section for more information [[Team:Safety-Fire]]

=== Can I sell foods or drinks? ===
Food-safety regulations (HAACP) don't allow that.

If it's non-commercially (so donations only) this does not apply.

=== Are drugs allowed? ===

As with most improbable planets in this corner of the galaxy, our festival terrain operates under what the local authorities charmingly call a zero-tolerance policy. This is bureaucratese for: no soft drugs, no hard drugs, and no nitrous oxide (laughing gas) are allowed anywhere on the festival or camping fields.

Should you nonetheless be found clutching a suspicious little bag of something unwise, you risk confiscation of said something, possible entanglement with Earth’s rather humorless legal system, and, most tragically of all, the premature end of your stay. And nobody wants that.

That said, using drugs does not make you a criminal in our book. If you feel unwell or need assistance, our improbably friendly First Aid and crew are standing by, towels at the ready.

So: let’s party responsibly, watch out for each other, and above all… Let’s Celebrate Safe!

=== Can I put something on the dyke? ===
No.

=== Is it allowed to swim in the water on the terrain? ===
The water quality isn't monitored. 20 minutes walk away is the [https://www.openstreetmap.org/directions?engine=fossgis_valhalla_foot&route=52.693975%2C4.752531%3B52.691582%2C4.767366#map=17/52.691744/4.764558&layers=P Geestmerambacht lake], which has a nice beach.

=== Is it allowed to fly drones over the terrain? ===
<check rules for '''WHY2025'''>

See our [[DroneFlyingRules|drones page]] for the rules during the event.

=== Can I bring my dog, kitten or pet lizard? ===
As much as we love animals big and small, we can't have them on the field.

Certified service animals are, of course, allowed.

=Miscellaneous=
=== How can I contact Infodesk (online and on the camp)? ===
Before the camp you can mail us at [mailto:info@why2025.org info@why2025.org].
During the event we will have a physical desk in the Info tent and a phone number: INFO (4636).

===Where is the lost and found?===
During '''WHY2025''', Infodesk will be the place to leave all the valuables you have found.

If you have lost something, you check the infodesk to see if your belongings are found.
There will be a [[Lost_and_found]] page to register your lost and found items.

===Where is everything? Where's the map?===
There's an [https://map.why2025.org/ online map], and you can find the map in the booklet as well.

Remember the fields are arrange alphabetically, from North to South.

===Are there streams of the talks?===
Yes, streams will be provided by [https://streaming.media.ccc.de/ media.ccc.de]

===How can I get reminders for talks/workshops/entertainment in the programme?===
There's a [https://wiki.why2025.org/How_can_I_get_reminders_for_events_in_the_programme%3F page on the wiki] detailing how to track, favorite, and get reminders for events when they're about to begin.

===Where can I find information about Sponsors and Sponsoring?===
There's a [https://wiki.why2025.org/Team:Sponsors great Team:Sponsors page], including Wiki, brochure and more.

===Can I get a visa invitation letter?===
Unfortunately, we are not able to write any visa invitation letters. Here you can find more information regarding [https://www.netherlandsworldwide.nl/ travelling to the Netherlands], or [https://www.netherlandsworldwide.nl/visa-the-netherlands more specifically visas]

===What is the Secret Token Game / What are those weird "secret{...}" strings I see on the field?===
These are the Secret Tokens which are part of the Secret Token Game, check https://tokens.why2025.org/ for more info.

===Where can I find information on the Capture The Flag (CTF)?===
You can visit the CTF tent on the field, or check out the CTF website which can be found on https://ctf.why2025.org/

= Post '''WHY2025''' =
===When is the next Dutch Hackercamp?===
We hope that in four years time, there will be another event, with a new theme, a new abbreviation, a renewed orga and old people doing new things.

===Can I buy a badge or shirt after WHY?===
* If there are any leftover shirts and hoodies, we will sell them in the WHYticketshop. But don't get your hopes up.

* The badges are probably all gone by then. But since the badges are open source, you can always try to make them yourself, or have someone make them for you. You can find more info on the badge [https://wiki.why2025.org/Team:Badge here]

===Where can I drop my feedback?===
After the event there will be a feedback page, where you can leave your feedback. Tell us about things we can learn from and things that make us feel warm about the effort we put in.

User:Bas

2025-07-27T19:26:45Z

Bas:

{{UserInfo
|Bringing=Tent, trash compactors.
|Village=Village:̸̡̛̯̳͎͔̟̠̪̲͖̦̒̆̀̈̉̒͊̚̕͝
|Arrival=2025-08-01
|Departure=2025-08-15
|DECT=BASO
|Languages=EN, NL, mediocre DE
|HackerSpace=Revspace, Hackalot, RandomData
|NickName={{PAGENAME}}
}}
Teacher, Boardmember of RevSpace. I co-led team Volunteering at MCH2022, Waste at SHA2017. Also helped out with SHA2017 Badge. Currently not in a team (intentional), but if anyone needs advice or a braindump about things from previous events, hit me up!

User:SynQ

2025-07-27T19:18:45Z

Bas:

{{UserInfo
|Bringing=Myself, my family and most of ProcoliX/HackerHosting/OID.foundation
|Village=Village:̸̡̛̯̳͎͔̟̠̪̲͖̦̒̆̀̈̉̒͊̚̕͝
|Arrival=2025-08-01
|Departure=2025-08-15
|IRC=SynQ
|Mastodon=@koen@procolix.social
|Languages=EN, NL
|HackerSpace=RevSpace
}}
free, I am free text

User:SynQ

2025-07-27T19:18:20Z

Bas:

{{UserInfo
|Bringing=Myself, my family and most of ProcoliX/HackerHosting/OID.foundation
|Village::̸̡̛̯̳͎͔̟̠̪̲͖̦̒̆̀̈̉̒͊̚̕͝
|Arrival=2025-08-01
|Departure=2025-08-15
|IRC=SynQ
|Mastodon=@koen@procolix.social
|Languages=EN, NL
|HackerSpace=RevSpace
}}
free, I am free text

User:SynQ

2025-07-27T19:17:57Z

Bas:

{{UserInfo
|Bringing=Myself, my family and most of ProcoliX/HackerHosting/OID.foundation
|Village:̸̡̛̯̳͎͔̟̠̪̲͖̦̒̆̀̈̉̒͊̚̕͝
|Arrival=2025-08-01
|Departure=2025-08-15
|IRC=SynQ
|Mastodon=@koen@procolix.social
|Languages=EN, NL
|HackerSpace=RevSpace
}}
free, I am free text

User:Bas

2025-07-27T19:16:38Z

Bas:

{{UserInfo
|Village=Village:̸̡̛̯̳͎͔̟̠̪̲͖̦̒̆̀̈̉̒͊̚̕͝
|Languages=EN, NL, mediocre DE
|HackerSpace=Revspace, Hackalot, RandomData
|NickName={{PAGENAME}}
}}
Teacher, Boardmember of RevSpace. I co-led team Volunteering at MCH2022, Waste at SHA2017. Also helped out with SHA2017 Badge. Currently not in a team (intentional), but if anyone needs advice or a braindump about things from previous events, hit me up!

User:Bas

2025-07-27T19:15:44Z

Bas:

{{UserInfo
|Village=Village:CC%B8%CC%A1%CC%9B%CC%AF%CC%B3%CD%8E%CD%94%CC%9F%CC%A0%CC%AA%CC%B2%CD%96%CC%A6%CC%92%CC%86%CC%80%CC%88%CC%89%CC%92%CD%8A%CC%9A%CC%95%CD%9D
|Languages=EN, NL, mediocre DE
|HackerSpace=Revspace, Hackalot
|NickName={{PAGENAME}}
}}
Teacher, Boardmember of RevSpace. I co-led team Volunteering at MCH2022, Waste at SHA2017. Also helped out with SHA2017 Badge. Currently not in a team (intentional), but if anyone needs advice or a braindump about things from previous events, hit me up!

User:Bas

2025-07-27T19:15:14Z

Bas:

{{UserInfo
|Village=Village:Nbsp
|Languages=EN, NL, mediocre DE
|HackerSpace=Revspace, Hackalot
|NickName={{PAGENAME}}
}}
Teacher, Boardmember of RevSpace. I co-led team Volunteering at MCH2022, Waste at SHA2017. Also helped out with SHA2017 Badge. Currently not in a team (intentional), but if anyone needs advice or a braindump about things from previous events, hit me up!

Team:Waste

2025-04-05T19:11:38Z

Bas:

{{Team
|Lead=User:SynQ, User:Bas
|Description=Waste disposal during the event is key to not make a mess, so lets take care of it...
|Exclusive team=No
|Contact=waste@why2025.org
|team_is_essential_to_event=Show-stopper
|team_has_contact_info=Yes
|team_has_info_on_wiki=Yes
|team_has_planned_meetings=Yes
|team_has_enough_people=Yes
|team_has_drafted_budget=Yes
|team_has_informed_volunteer_team=Yes
|Projectleiding=User:Boekenwuurm
}}
==Team Members==
{| class="wikitable"
|+ Team Members
|-
! Username !! Previously involved !! Role
|-
| {{TeamMemberEntry|User:rixvet}} || Yes (On-site MCH2022)|| Helper
|-
| {{TeamMemberEntry|User:SynQ}} || || Team-Lead
|-
| {{TeamMemberEntry|User:Emma}} || No ||
|-
| {{TeamMemberEntry|User:Thijs}} || No ||
|-
| {{TeamMemberEntry|User:Bas}} || Yes (SHA2017) ||
|-
|}

==Introduction==

==Plan==

==ToDo==
* Talk with Terrain about locations and equipment size/routes
* Talk with sysadmin and terrain for c3 bottles integration in map.why2025.org (in progress already, Bas)
* Talk with GP Groot about bin-liners 240L and 60L, if they can get us those affordable or not.
* Talk with Warehouse about storing bin-liners (in progress, Bas)
* Talk with Horeca about foodcourt (in progress, Bas)
* Make weatherproof signs to put on bins with QR for reporting system
* Plot/plan bin locations on map
* Make team Waste merch ;)
* Setup phone stuff with POC team, callgroup, numbers, can we borrow phones?
* Info for booklet needs to be checked from previous events and updated with team Info
* Team toilets
** Please ask them to not put any papieren handdoekjes in the toilet blocks because it makes the trash cans very heavy. Air drying is good enough.
* Design and plan angel shifts
* Figure out our own schedule
* Integrate our planning into general event planning

==Done==
* Decide wether we also collect the Mate bottles and other pfand: we don't. Team Horeca is organizing it themselves.
* Talk with Dimitri if he needs bins to keep gas bottles warm: he doesn't.
* Talk with team Power to spec the power for the compactors: 2 locations 400v 32A
* Tool requisition sent to Warehouse
* Boels request (2x electric vehicle + trailer) sent to Onsite/Manduca)
* Talk with team:Villages that they will actively hand out trash bags to villages, keep an eye on 'big things' and that a village leaves the field cleaner than they found it.

==Dependencies==
* Fixed DECT call group (for example, GRBG, WAST, WSTE, TRSH) (contact [[Team:POC]] about this)
* Instructions about waste
** "Please take home '''everything''' you bring, especially couches and tents" or something like that
**Contact [[Team:Info]] and [[Team:Villages]] about this
* [[Team:Terrain]] for planning
** Where should we collect everything
** Where is most of the waste produced (bar, food court, ...)
* [[Team:Volunteers]] for arranging volunteer shifts (picking up garbage and stuff)
* [[Team:NUTS]] for the power to the garbage press containers that compress trash
* Contact [[Team:Foodcourt]] about managing trash
** We supply infra, they empty the bins around the court?
** Might be useful if they have a trash compactor as well
* [[Team:Bar]]
** For Mate crates to collect empty bottles
** Statiegeld - what do they want to offer? Plastic bottles and cans have statiegeld on them.

==Stuff we need==
=== Transport ===
* 2 big 40-foot waste containers for the end of the event
* 2,5 Gators and 2 trailers, reserved for Waste

=== Communication ===
* 1 portofoon per Gator
* DECT for each member of [[Team:Waste]]

=== Personal equipment ===
* Proper gloves in different sizes, for handling trash
* Workpants and/or some cheap shirts that can be dirty
** Free access to a washing machine
* Disinfecting soap

=== Trash collection ===
* Roll containers
** More than enough so that full ones can easily be swapped for empty ones during the event.
* Strong garbage bags
** One for every visitor
** A roll of garbage bags for every village
** Large ones for the bins
* Containers for special trash
** Paper
** Glass
** PMD
** Bulky waste
** Mate (no, team waste will not do 'statiegeld')
** Compost/green trash
** ???
* Sand for hot stuff like sigarettes
* Signs on the bins + tape

=== Trash handling ===
* Mobile press containers to compress trash
** Preferably should accept trash bags, instead of just containers
* Lighting for evening and night, so that trash handling can still be safely done in the dark

== Ideas ==
This section is for all volunteers. If you have any suggestions or idea's of stuff we could or should do (or not do), please post them here.
'''Your idea's won't go to waste!'''

* Collect radio active waste separately.
* Create a location to collect chemical waste or electronic waste.
* Statiegeld bags can be get trough wholesalers for bulk collection and return of deposit/ statiegeld bottle
* Lightning5: Hey, at MCH we've figured out during teardown that compacters can run while trash is being thrown in. That has turned out to be much better for the compactors (less trash per cycle) and nicer on the power supply (constant load). Check if this is possible with the compactors at WHY and if it is a good idea to operate this way :)
* Lightning5: Lol, I've got another idea: I've been at a festival where every participant got a mandatory trash bag that had a deposit. At the end of the event, you had to return (somewhat) full trash bag to get the deposit back.

Team:Waste

2025-04-05T19:02:59Z

Bas:

{{Team
|Lead=User:SynQ, User:Bas
|Description=Waste disposal during the event is key to not make a mess, so lets take care of it...
|Exclusive team=No
|Contact=waste@why2025.org
|team_is_essential_to_event=Show-stopper
|team_has_contact_info=Yes
|team_has_info_on_wiki=Yes
|team_has_planned_meetings=Yes
|team_has_enough_people=Yes
|team_has_drafted_budget=Yes
|team_has_informed_volunteer_team=Yes
|Projectleiding=User:Boekenwuurm
}}
==Team Members==
{| class="wikitable"
|+ Team Members
|-
! Username !! Previously involved !! Role
|-
| {{TeamMemberEntry|User:rixvet}} || Yes (On-site MCH2022)|| Helper
|-
| {{TeamMemberEntry|User:SynQ}} || || Team-Lead
|-
| {{TeamMemberEntry|User:Emma}} || No ||
|-
| {{TeamMemberEntry|User:Thijs}} || No ||
|-
| {{TeamMemberEntry|User:Bas}} || Yes (SHA2017) ||
|-
|}

==Introduction==

==Plan==

==ToDo==
* Talk with Terrain about locations and equipment size/routes
* Talk with sysadmin and terrain for c3 bottles integration in map.why2025.org (in progress already, Bas)
* Talk with GP Groot about bin-liners 240L and 60L, if they can get us those affordable or not.
* Talk with Warehouse about storing bin-liners (in progress, Bas)
* Talk with Horeca about foodcourt (in progress, Bas)
* Make weatherproof signs to put on bins with QR for reporting system
* Plot/plan bin locations on map
* Make team Waste merch ;)

==Done==
* Decide wether we also collect the Mate bottles and other pfand: we don't. Team Horeca is organizing it themselves.
* Talk with Dimitri if he needs bins to keep gas bottles warm: he doesn't.
* Talk with team Power to spec the power for the compactors: 2 locations 400v 32A

== Things to discuss ==
* Budget!
* Contact the local waste processor
** Source separation/post-separation?
** What types of waste do they accept and in what form?
* Find out where we can rent good equipment (ask your PL contact for this, we have all the info for you)
* Deposit system/Statiegeld (team:finance > please don't, its a headache for both the bar and the books)
** Refund deposit to visitors or set up donation bins for deposits?
** It might be useful to contact Statiegeld Nederland to ask how we can do this
* Glitter
* WHY: Waste Help Yourself system for waste notifications about full trash containers
* How do people know what to throw in which bin

==Dependencies==
* Fixed DECT call group (for example, GRBG, WAST, WSTE, TRSH) (contact [[Team:POC]] about this)
* Instructions about waste
** "Please take home '''everything''' you bring, especially couches and tents" or something like that
**Contact [[Team:Info]] and [[Team:Villages]] about this
* [[Team:Terrain]] for planning
** Where should we collect everything
** Where is most of the waste produced (bar, food court, ...)
* [[Team:Volunteers]] for arranging volunteer shifts (picking up garbage and stuff)
* [[Team:NUTS]] for the power to the garbage press containers that compress trash
* Contact [[Team:Foodcourt]] about managing trash
** We supply infra, they empty the bins around the court?
** Might be useful if they have a trash compactor as well
* [[Team:Bar]]
** For Mate crates to collect empty bottles
** Statiegeld - what do they want to offer? Plastic bottles and cans have statiegeld on them.
* Team toilets
** Please ask them to not put any papieren handdoekjes in the toilet blocks because it makes the trash cans very heavy. Air drying is good enough.
* [[Team:Sysadmin]] so they can host [https://github.com/c3bottles/c3bottles c3bottles] for us (Bottle drop and collection management system for chaos events)

==Stuff we need==
=== Transport ===
* 2 big 40-foot waste containers for the end of the event
* 2,5 Gators and 2 trailers, reserved for Waste

=== Communication ===
* 1 portofoon per Gator
* DECT for each member of [[Team:Waste]]

=== Personal equipment ===
* Proper gloves in different sizes, for handling trash
* Workpants and/or some cheap shirts that can be dirty
** Free access to a washing machine
* Disinfecting soap

=== Trash collection ===
* Roll containers
** More than enough so that full ones can easily be swapped for empty ones during the event.
* Strong garbage bags
** One for every visitor
** A roll of garbage bags for every village
** Large ones for the bins
* Containers for special trash
** Paper
** Glass
** PMD
** Bulky waste
** Mate (no, team waste will not do 'statiegeld')
** Compost/green trash
** ???
* Sand for hot stuff like sigarettes
* Signs on the bins + tape

=== Trash handling ===
* Mobile press containers to compress trash
** Preferably should accept trash bags, instead of just containers
* Lighting for evening and night, so that trash handling can still be safely done in the dark

== Ideas ==
This section is for all volunteers. If you have any suggestions or idea's of stuff we could or should do (or not do), please post them here.
'''Your idea's won't go to waste!'''

* Burn waste that can be burned in a large fire.
* Collect radio active waste separately.
* Create a location to collect chemical waste or electronic waste.
* Statiegeld bags can be get trough wholesalers for bulk collection and return of deposit/ statiegeld bottle
* Lightning5: Hey, at MCH we've figured out during teardown that compacters can run while trash is being thrown in. That has turned out to be much better for the compactors (less trash per cycle) and nicer on the power supply (constant load). Check if this is possible with the compactors at WHY and if it is a good idea to operate this way :)
* Lightning5: Lol, I've got another idea: I've been at a festival where every participant got a mandatory trash bag that had a deposit. At the end of the event, you had to return (somewhat) full trash bag to get the deposit back.

FieldDAY 2025 04 05

2025-04-01T19:30:45Z

Bas: /* WHO */

{{Meeting
|Name=WHY2025 FIELDDAY
|StartDate=2025-04-05 12:00:00
|EndDate=2025-04-05 18:00:00
|Where=Geestmermabacht (terrein) / Wagenweg 12, 1724 PT Oudkarspel (adres)
}}
Actual location:
[[File:Hierzitjegoed fieldboard.jpg|thumb|right|alt=Board at the entrance of the field|Board at the entrance of the field]]
What three words:
///graphics.flux.label
https://w3w.co/graphics.flux.label

https://maps.app.goo.gl/BzYVaaZANMAMnkFd8

https://www.openstreetmap.org/search?lat=52.69118&lon=4.74266#map=15/52.69119/4.74266

A last field day to check the terrain with your team. 

There's a WHY2025 spotify playlist, please add your favorite WHY-songs (Must Contain WHY in title)
https://open.spotify.com/playlist/6N6jHxRdLT7ilXMixsN9E8?si=a7568f302335499d&pt=077388a59a88ddbce8d802471e42de3e

== Where to park and meet ==

The canteen of Manege Beukers
Wagenweg 12, 1724PT Oudkarspel

https://www.openstreetmap.org/?mlat=52.6873&mlon=4.7521#map=16/52.69571/4.75852&layers=P

[[File:Fielday 5th of april.jpg|thumb]]

== Lunch options ==

We will have split pea soup made by Sandra in a vega or meat variaty.
We will also have some cheese or ham sandwiches avaialable

Please let us know if you want to have some lunch.

== Dinner options ==

This time we will have the choice of .... not 1 .... not 2 .... but 3 .... different food options !!

{| class="wikitable"
|-
| Carrot mash/Hutspot || Meat or vega
|-
| Lasagne || Meat only unfortunately
|-
| Chips || Frikandel or cheese soufflé sandwich
|}

Please let us know your choice.

== Program ==

12:00 - 13:00 Buildup

13:00 - 13:30 Arrival

13:30 - 14:30 Presentation

14:30 - 18:00 Opportunity for teams to walk around the field or have a team meeting

18:00 - 20:00 Dinner and time to relax and chat

20:00 End of the program

== WHO ==
{| class="wikitable"
|-
! Name !! Team !! Lunch !! Diner !! Dinner choice !! Allergies/Dietary requirements
|-
| {{UserLink|Netsmurf}} || [[Team:Projectleiding|PL]] || Yes Meat || Yes || Lasagne Meat ||
|-
| {{UserLink|FighterX64}} || [[Team:On-site_transportation|forklifters]] || || Yes || ribeye/entrecote ||
|-
| {{UserLink|Peetz0r}} || || || Yes || ||
|-
| {{UserLink|Techwolf12}} || || || Yes || ||
|-
| {{UserLink|Wheeze_NL}} || [[Team:ROC|ROC]],[[Team:On-site_transportation|forklifters]] || Yes Meat || Yes || Lasagne Meat ||
|-
| {{UserLink|cmpxchg}} || || || Yes || ||
|-
| {{UserLink|Elborro}} || [[Team:Info|Info]] || Yes || Yes || Lasagne || -
|-
| {{UserLink|Killergeek}} || [[Team:NOC|NOC]],[[Team:NUTS|NUTS]] || Yes ham sandwiches || Yes || Chips, Frikandel || -
|-
| {{UserLink|loppermann}} || [[Team:POC|POC]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|Twi}} || [[Team:POC|POC]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|Imtiaz101325}} || [[Team:Accessibility|Accessibility]],[[Team:Badge|Badge]] || Yes Meat || Yes || Lasagne || -
|-
| {{UserLink|Pmenke}} || [[Team:POC|POC]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|Psteffen}} || [[Team:POC|POC]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|justelex}} || [[Team:POC|POC]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|mirconnect}} || [[Team:POC|POC]] || || Yes || Chips ||
|-
| {{UserLink|Chris1911}} || [[Team:POC|POC]] || Yes Meat || Yes || Lasagne ||
|-
| {{UserLink|L3D}} || || Yes Meat || Yes || Lasagne ||
|-
| {{UserLink|Sja}} || [[Team:POC|POC]] || Yes Meat || Yes || Lasagne ||
|-
| {{UserLink|Thice}} || [[Team:CTF|CTF]] || || No || ||
|-
| {{UserLink|asby}} || [[Team:CTF|CTF]] || || No || ||
|-
| {{UserLink|inframan}} || || || yes || ||
|-
| {{UserLink|Damning}} || [[Team:Deco]] || Yes || Yes || Chips & Cheese souffle sandwich ||
|-
| {{UserLink|Halcyon}} || [[Team:Projectleiding|PL]] || Yes || Yes || Vega hutspot ||
|-
| {{UserLink|Polyfloyd}} || [[Team:Deco]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|Aranea}} || || Yes || Yes || || Lactose intolerant
|-
| {{UserLink|MrLinux}} || [[Team:ROC|ROC]] || Yes Meat || Yes || Chips, Frikandel ||
|-
| {{UserLink|Piiindakaas}} || [[Team:Projectleiding|PL]] || Yes || Yes || Hutspot or Lasagna ||
|-
| {{UserLink|Boekenwuurm}} || [[Team:Projectleiding|PL]] || || Yes || ||
|-
| {{UserLink|Gina}} || [[Team:Terrain|Terrain]] || Vega || Yes || Hutspot vega ||
|-
| {{UserLink|Wllm}} || [[Team:Sysadmin|Sysadmin]] || Yes || Yes || Chips, Cheese souffle sandwich ||
|-
| {{UserLink|Marjolein}} || [[Team:Sysadmin|Volunteers]] || Yes, meat || Yes || Lasagne||
|-
| {{UserLink|Jasper}} || [[Team:Sysadmin|Volunteers]] || Yes, meat || Yes || Lasagne ||
|-
| {{UserLink|AK}} || [[Team:NOC]] || Yes, meat || Yes || Lasagne ||
|-
| {{UserLink|Moem}} || [[Team:Deco]] || Vega || Yes || Hutspot vega ||
|-
| {{UserLink|Wido}} || [[Team:Off-site_transportation]] || - || Yes || Lasagne ||
|-
| {{UserLink|Thomascovenant}} || [[Team:Ticket_&_Entrance]] || Yes, meat || Yes || Lasagne ||
|-
| {{UserLink|Dany}} || [[Team:Cohesion|Cohesion]] [[Team:Content|Content]] || Yes, meat || Yes || Hutspot, Meat (but vega is good too) ||
|-
| {{UserLink|Knorrie}} || [[Team:On-site_transportation|Logistics]] || - || Yes || Lasagne || -
|-
| {{UserLink|Nancy}} || [[Team:projectleiding|PL]] || - || Yes || Lasagne || -
|-
| {{UserLink|K4T0}} || [[Team:Bar|Bar]] || Vega || Yes || Hutspot vega ||
|-
| {{UserLink|zeno4ever}} || [[Team:Permits|Permits]] || - || Yes || Lasagne or meat hutspot ||
|-
| {{UserLink|Rewby}} || [[Team:NOC|NOC]] || Yes || Yes || meat hutspot or chips || No cheese
|-
| {{UserLink|justSem}} || [[Team:Foodcourt|Foodcourt]] || Yes, meat || Yes || meat lasgne or chips ||
|-
| {{UserLink|Betsy}} || [[Team:Bar|Bar]] || Yes, Vega || Yes || Hutspot vega ||
|-
| {{UserLink|Splodin}} || [[Team:SysAdmin|SysAdmin]] || Yes || Yes || Lasagne || -
|-
| {{UserLink|Rox}} || [[Team:Terrain|Terrain]] || Yes, vega || Yes || Lasagne || -
|-
| {{UserLink|Juerd}} || [[Team:Warehouse|Warehouse]] || No || Yes || Chips, Cheese souffle (no sandwhich) || -
|-
| {{UserLink|IcyPalm}} || [[Team:Villages|Villages]] || Yes, Meat || Yes || Lasagne || -
|-
| {{UserLink|Nicolas}} || [[Team:Content|Content]] || Yes, meat || Yes || Hutspot,meat || -
|-
| {{UserLink|BIlIaN}} || [[Team:POC|POC]] || Yes, meat || Yes || Lasagne || -
|-
| {{UserLink|Mirwi}} || [[Team:POC|POC]] || Yes, meat || Yes || Lasagne || -
|-
| {{UserLink|Okarin}} || [[Team:Volunteers]] || Yes, meat || Yes || Lasagne || -
|-
| {{UserLink|Jel}} || [[Team:Info|Info]] || No || Yes || Chips || -
|-
| {{UserLink|Hp197}} || [[Team:Projectleiding|PL]] || Yes || Yes || Lasagna ||
|-
| The food has || Been counted and|| Ordered || up till || here || -
|-
| Still wanna Join ? || Put your name|| below here || we still have || the Chips and cheese soufle || or Frikandel option
|-
| {{UserLink|Winko}} || [[Team:Villages|Villages]] || I'll manage || and work it out || when needed || -
|-
| {{UserLink|Tidi}} || [[Team:Bar|Bar]] || Yes || Yes || Meat only (frikandel only = fine) || no carbs/sugar, sugar replacements.
|-
| {{UserLink|Bustux}} || [[Team:Villages|Villages]] || Yes || Yes || Chips || -
|-
| {{UserLink|Hans}} || [[Team:NUTS|NUTS]] || Yes || No || - || -
|-
| {{UserLink|redlizard}} || [[Team:Terrain|Terrain]] || Yes || Yes || Would very much appreciate the Lasagna if something can be arranged or traded || -
|-
| {{UserLink|Bas}} || Waste || Yes || Bij voorkeur lasagne, anders iets anders. || ||
|-
|}

== Travel & Carpool ==
===Public transport ===

===Seats offered===
{| class="wikitable"
|-
! Name !! Seats available !! Leaving from !! Time
|-
| {{UserLink|Wido}} || 3 || Wageningen || ~11.30
|-
| {{UserLink|Piiindakaas}} || 3 || IJsselstein || 11.00-ish
|-
| {{UserLink|AK}} || 3 || Amersfoort || 11.00-ish
|-
| {{UserLink|IcyPalm}} || 2/3 || Groningen(via Drachten/Leeuwarden) || 11.00-ish
|}

=== Seats needed ===
{| class="wikitable"
|-
! Name !! Seats needed !! Leaving from !! Time
|-
| {{UserLink|Tidi}} || 1 || Amsterdam/Holendrecht || whenever
|}

== Photos and Videos of the location ==

FieldDAY 2025 04 05

2025-04-01T19:24:43Z

Bas: /* WHO */

{{Meeting
|Name=WHY2025 FIELDDAY
|StartDate=2025-04-05 12:00:00
|EndDate=2025-04-05 18:00:00
|Where=Geestmermabacht (terrein) / Wagenweg 12, 1724 PT Oudkarspel (adres)
}}
Actual location:
[[File:Hierzitjegoed fieldboard.jpg|thumb|right|alt=Board at the entrance of the field|Board at the entrance of the field]]
What three words:
///graphics.flux.label
https://w3w.co/graphics.flux.label

https://maps.app.goo.gl/BzYVaaZANMAMnkFd8

https://www.openstreetmap.org/search?lat=52.69118&lon=4.74266#map=15/52.69119/4.74266

A last field day to check the terrain with your team. 

There's a WHY2025 spotify playlist, please add your favorite WHY-songs (Must Contain WHY in title)
https://open.spotify.com/playlist/6N6jHxRdLT7ilXMixsN9E8?si=a7568f302335499d&pt=077388a59a88ddbce8d802471e42de3e

== Where to park and meet ==

The canteen of Manege Beukers
Wagenweg 12, 1724PT Oudkarspel

https://www.openstreetmap.org/?mlat=52.6873&mlon=4.7521#map=16/52.69571/4.75852&layers=P

[[File:Fielday 5th of april.jpg|thumb]]

== Lunch options ==

We will have split pea soup made by Sandra in a vega or meat variaty.
We will also have some cheese or ham sandwiches avaialable

Please let us know if you want to have some lunch.

== Dinner options ==

This time we will have the choice of .... not 1 .... not 2 .... but 3 .... different food options !!

{| class="wikitable"
|-
| Carrot mash/Hutspot || Meat or vega
|-
| Lasagne || Meat only unfortunately
|-
| Chips || Frikandel or cheese soufflé sandwich
|}

Please let us know your choice.

== Program ==

12:00 - 13:00 Buildup

13:00 - 13:30 Arrival

13:30 - 14:30 Presentation

14:30 - 18:00 Opportunity for teams to walk around the field or have a team meeting

18:00 - 20:00 Dinner and time to relax and chat

20:00 End of the program

== WHO ==
{| class="wikitable"
|-
! Name !! Team !! Lunch !! Diner !! Dinner choice !! Allergies/Dietary requirements
|-
| {{UserLink|Netsmurf}} || [[Team:Projectleiding|PL]] || Yes Meat || Yes || Lasagne Meat ||
|-
| {{UserLink|FighterX64}} || [[Team:On-site_transportation|forklifters]] || || Yes || ribeye/entrecote ||
|-
| {{UserLink|Peetz0r}} || || || Yes || ||
|-
| {{UserLink|Techwolf12}} || || || Yes || ||
|-
| {{UserLink|Wheeze_NL}} || [[Team:ROC|ROC]],[[Team:On-site_transportation|forklifters]] || Yes Meat || Yes || Lasagne Meat ||
|-
| {{UserLink|cmpxchg}} || || || Yes || ||
|-
| {{UserLink|Elborro}} || [[Team:Info|Info]] || Yes || Yes || Lasagne || -
|-
| {{UserLink|Killergeek}} || [[Team:NOC|NOC]],[[Team:NUTS|NUTS]] || Yes ham sandwiches || Yes || Chips, Frikandel || -
|-
| {{UserLink|loppermann}} || [[Team:POC|POC]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|Twi}} || [[Team:POC|POC]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|Imtiaz101325}} || [[Team:Accessibility|Accessibility]],[[Team:Badge|Badge]] || Yes Meat || Yes || Lasagne || -
|-
| {{UserLink|Pmenke}} || [[Team:POC|POC]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|Psteffen}} || [[Team:POC|POC]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|justelex}} || [[Team:POC|POC]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|mirconnect}} || [[Team:POC|POC]] || || Yes || Chips ||
|-
| {{UserLink|Chris1911}} || [[Team:POC|POC]] || Yes Meat || Yes || Lasagne ||
|-
| {{UserLink|L3D}} || || Yes Meat || Yes || Lasagne ||
|-
| {{UserLink|Sja}} || [[Team:POC|POC]] || Yes Meat || Yes || Lasagne ||
|-
| {{UserLink|Thice}} || [[Team:CTF|CTF]] || || No || ||
|-
| {{UserLink|asby}} || [[Team:CTF|CTF]] || || No || ||
|-
| {{UserLink|inframan}} || || || yes || ||
|-
| {{UserLink|Damning}} || [[Team:Deco]] || Yes || Yes || Chips & Cheese souffle sandwich ||
|-
| {{UserLink|Halcyon}} || [[Team:Projectleiding|PL]] || Yes || Yes || Vega hutspot ||
|-
| {{UserLink|Polyfloyd}} || [[Team:Deco]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|Aranea}} || || Yes || Yes || || Lactose intolerant
|-
| {{UserLink|MrLinux}} || [[Team:ROC|ROC]] || Yes Meat || Yes || Chips, Frikandel ||
|-
| {{UserLink|Piiindakaas}} || [[Team:Projectleiding|PL]] || Yes || Yes || Hutspot or Lasagna ||
|-
| {{UserLink|Boekenwuurm}} || [[Team:Projectleiding|PL]] || || Yes || ||
|-
| {{UserLink|Gina}} || [[Team:Terrain|Terrain]] || Vega || Yes || Hutspot vega ||
|-
| {{UserLink|Wllm}} || [[Team:Sysadmin|Sysadmin]] || Yes || Yes || Chips, Cheese souffle sandwich ||
|-
| {{UserLink|Marjolein}} || [[Team:Sysadmin|Volunteers]] || Yes, meat || Yes || Lasagne||
|-
| {{UserLink|Jasper}} || [[Team:Sysadmin|Volunteers]] || Yes, meat || Yes || Lasagne ||
|-
| {{UserLink|AK}} || [[Team:NOC]] || Yes, meat || Yes || Lasagne ||
|-
| {{UserLink|Moem}} || [[Team:Deco]] || Vega || Yes || Hutspot vega ||
|-
| {{UserLink|Wido}} || [[Team:Off-site_transportation]] || - || Yes || Lasagne ||
|-
| {{UserLink|Thomascovenant}} || [[Team:Ticket_&_Entrance]] || Yes, meat || Yes || Lasagne ||
|-
| {{UserLink|Dany}} || [[Team:Cohesion|Cohesion]] [[Team:Content|Content]] || Yes, meat || Yes || Hutspot, Meat (but vega is good too) ||
|-
| {{UserLink|Knorrie}} || [[Team:On-site_transportation|Logistics]] || - || Yes || Lasagne || -
|-
| {{UserLink|Nancy}} || [[Team:projectleiding|PL]] || - || Yes || Lasagne || -
|-
| {{UserLink|K4T0}} || [[Team:Bar|Bar]] || Vega || Yes || Hutspot vega ||
|-
| {{UserLink|zeno4ever}} || [[Team:Permits|Permits]] || - || Yes || Lasagne or meat hutspot ||
|-
| {{UserLink|Rewby}} || [[Team:NOC|NOC]] || Yes || Yes || meat hutspot or chips || No cheese
|-
| {{UserLink|justSem}} || [[Team:Foodcourt|Foodcourt]] || Yes, meat || Yes || meat lasgne or chips ||
|-
| {{UserLink|Betsy}} || [[Team:Bar|Bar]] || Yes, Vega || Yes || Hutspot vega ||
|-
| {{UserLink|Splodin}} || [[Team:SysAdmin|SysAdmin]] || Yes || Yes || Lasagne || -
|-
| {{UserLink|Rox}} || [[Team:Terrain|Terrain]] || Yes, vega || Yes || Lasagne || -
|-
| {{UserLink|Juerd}} || [[Team:Warehouse|Warehouse]] || No || Yes || Chips, Cheese souffle (no sandwhich) || -
|-
| {{UserLink|IcyPalm}} || [[Team:Villages|Villages]] || Yes, Meat || Yes || Lasagne || -
|-
| {{UserLink|Nicolas}} || [[Team:Content|Content]] || Yes, meat || Yes || Hutspot,meat || -
|-
| {{UserLink|BIlIaN}} || [[Team:POC|POC]] || Yes, meat || Yes || Lasagne || -
|-
| {{UserLink|Mirwi}} || [[Team:POC|POC]] || Yes, meat || Yes || Lasagne || -
|-
| {{UserLink|Okarin}} || [[Team:Volunteers]] || Yes, meat || Yes || Lasagne || -
|-
| {{UserLink|Jel}} || [[Team:Info|Info]] || No || Yes || Chips || -
|-
| {{UserLink|Hp197}} || [[Team:Projectleiding|PL]] || Yes || Yes || Lasagna ||
|-
| The food has || Been counted and|| Ordered || up till || here || -
|-
| Still wanna Join ? || Put your name|| below here || we still have || the Chips and cheese soufle || or Frikandel option
|-
| {{UserLink|Winko}} || [[Team:Villages|Villages]] || I'll manage || and work it out || when needed || -
|-
| {{UserLink|Tidi}} || [[Team:Bar|Bar]] || Yes || Yes || Meat only (frikandel only = fine) || no carbs/sugar, sugar replacements.
|-
| {{UserLink|Bustux}} || [[Team:Villages|Villages]] || Yes || Yes || Chips || -
|-
| {{UserLink|Hans}} || [[Team:NUTS|NUTS]] || Yes || No || - || -
|-
| {{UserLink|redlizard}} || [[Team:Terrain|Terrain]] || Yes || Yes || Would very much appreciate the Lasagna if something can be arranged or traded || -
|-
| {{UserLink|Bas}} || Waste || Yes || Alles is lekker. Patatje frikandel, lasagna, boeie. Nogal onhandig dat ik niet wist dat er een deadline was. || ||
|-
|}

== Travel & Carpool ==
===Public transport ===

===Seats offered===
{| class="wikitable"
|-
! Name !! Seats available !! Leaving from !! Time
|-
| {{UserLink|Wido}} || 3 || Wageningen || ~11.30
|-
| {{UserLink|Piiindakaas}} || 3 || IJsselstein || 11.00-ish
|-
| {{UserLink|AK}} || 3 || Amersfoort || 11.00-ish
|-
| {{UserLink|IcyPalm}} || 2/3 || Groningen(via Drachten/Leeuwarden) || 11.00-ish
|}

=== Seats needed ===
{| class="wikitable"
|-
! Name !! Seats needed !! Leaving from !! Time
|-
| {{UserLink|Tidi}} || 1 || Amsterdam/Holendrecht || whenever
|}

== Photos and Videos of the location ==

FieldDAY 2025 04 05

2025-04-01T19:23:22Z

Bas: /* WHO */

{{Meeting
|Name=WHY2025 FIELDDAY
|StartDate=2025-04-05 12:00:00
|EndDate=2025-04-05 18:00:00
|Where=Geestmermabacht (terrein) / Wagenweg 12, 1724 PT Oudkarspel (adres)
}}
Actual location:
[[File:Hierzitjegoed fieldboard.jpg|thumb|right|alt=Board at the entrance of the field|Board at the entrance of the field]]
What three words:
///graphics.flux.label
https://w3w.co/graphics.flux.label

https://maps.app.goo.gl/BzYVaaZANMAMnkFd8

https://www.openstreetmap.org/search?lat=52.69118&lon=4.74266#map=15/52.69119/4.74266

A last field day to check the terrain with your team. 

There's a WHY2025 spotify playlist, please add your favorite WHY-songs (Must Contain WHY in title)
https://open.spotify.com/playlist/6N6jHxRdLT7ilXMixsN9E8?si=a7568f302335499d&pt=077388a59a88ddbce8d802471e42de3e

== Where to park and meet ==

The canteen of Manege Beukers
Wagenweg 12, 1724PT Oudkarspel

https://www.openstreetmap.org/?mlat=52.6873&mlon=4.7521#map=16/52.69571/4.75852&layers=P

[[File:Fielday 5th of april.jpg|thumb]]

== Lunch options ==

We will have split pea soup made by Sandra in a vega or meat variaty.
We will also have some cheese or ham sandwiches avaialable

Please let us know if you want to have some lunch.

== Dinner options ==

This time we will have the choice of .... not 1 .... not 2 .... but 3 .... different food options !!

{| class="wikitable"
|-
| Carrot mash/Hutspot || Meat or vega
|-
| Lasagne || Meat only unfortunately
|-
| Chips || Frikandel or cheese soufflé sandwich
|}

Please let us know your choice.

== Program ==

12:00 - 13:00 Buildup

13:00 - 13:30 Arrival

13:30 - 14:30 Presentation

14:30 - 18:00 Opportunity for teams to walk around the field or have a team meeting

18:00 - 20:00 Dinner and time to relax and chat

20:00 End of the program

== WHO ==
{| class="wikitable"
|-
! Name !! Team !! Lunch !! Diner !! Dinner choice !! Allergies/Dietary requirements
|-
| {{UserLink|Netsmurf}} || [[Team:Projectleiding|PL]] || Yes Meat || Yes || Lasagne Meat ||
|-
| {{UserLink|FighterX64}} || [[Team:On-site_transportation|forklifters]] || || Yes || ribeye/entrecote ||
|-
| {{UserLink|Peetz0r}} || || || Yes || ||
|-
| {{UserLink|Techwolf12}} || || || Yes || ||
|-
| {{UserLink|Wheeze_NL}} || [[Team:ROC|ROC]],[[Team:On-site_transportation|forklifters]] || Yes Meat || Yes || Lasagne Meat ||
|-
| {{UserLink|cmpxchg}} || || || Yes || ||
|-
| {{UserLink|Elborro}} || [[Team:Info|Info]] || Yes || Yes || Lasagne || -
|-
| {{UserLink|Killergeek}} || [[Team:NOC|NOC]],[[Team:NUTS|NUTS]] || Yes ham sandwiches || Yes || Chips, Frikandel || -
|-
| {{UserLink|loppermann}} || [[Team:POC|POC]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|Twi}} || [[Team:POC|POC]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|Imtiaz101325}} || [[Team:Accessibility|Accessibility]],[[Team:Badge|Badge]] || Yes Meat || Yes || Lasagne || -
|-
| {{UserLink|Pmenke}} || [[Team:POC|POC]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|Psteffen}} || [[Team:POC|POC]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|justelex}} || [[Team:POC|POC]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|mirconnect}} || [[Team:POC|POC]] || || Yes || Chips ||
|-
| {{UserLink|Chris1911}} || [[Team:POC|POC]] || Yes Meat || Yes || Lasagne ||
|-
| {{UserLink|L3D}} || || Yes Meat || Yes || Lasagne ||
|-
| {{UserLink|Sja}} || [[Team:POC|POC]] || Yes Meat || Yes || Lasagne ||
|-
| {{UserLink|Thice}} || [[Team:CTF|CTF]] || || No || ||
|-
| {{UserLink|asby}} || [[Team:CTF|CTF]] || || No || ||
|-
| {{UserLink|inframan}} || || || yes || ||
|-
| {{UserLink|Damning}} || [[Team:Deco]] || Yes || Yes || Chips & Cheese souffle sandwich ||
|-
| {{UserLink|Halcyon}} || [[Team:Projectleiding|PL]] || Yes || Yes || Vega hutspot ||
|-
| {{UserLink|Polyfloyd}} || [[Team:Deco]] || Yes || Yes || Lasagne ||
|-
| {{UserLink|Aranea}} || || Yes || Yes || || Lactose intolerant
|-
| {{UserLink|MrLinux}} || [[Team:ROC|ROC]] || Yes Meat || Yes || Chips, Frikandel ||
|-
| {{UserLink|Piiindakaas}} || [[Team:Projectleiding|PL]] || Yes || Yes || Hutspot or Lasagna ||
|-
| {{UserLink|Boekenwuurm}} || [[Team:Projectleiding|PL]] || || Yes || ||
|-
| {{UserLink|Gina}} || [[Team:Terrain|Terrain]] || Vega || Yes || Hutspot vega ||
|-
| {{UserLink|Wllm}} || [[Team:Sysadmin|Sysadmin]] || Yes || Yes || Chips, Cheese souffle sandwich ||
|-
| {{UserLink|Marjolein}} || [[Team:Sysadmin|Volunteers]] || Yes, meat || Yes || Lasagne||
|-
| {{UserLink|Jasper}} || [[Team:Sysadmin|Volunteers]] || Yes, meat || Yes || Lasagne ||
|-
| {{UserLink|AK}} || [[Team:NOC]] || Yes, meat || Yes || Lasagne ||
|-
| {{UserLink|Moem}} || [[Team:Deco]] || Vega || Yes || Hutspot vega ||
|-
| {{UserLink|Wido}} || [[Team:Off-site_transportation]] || - || Yes || Lasagne ||
|-
| {{UserLink|Thomascovenant}} || [[Team:Ticket_&_Entrance]] || Yes, meat || Yes || Lasagne ||
|-
| {{UserLink|Dany}} || [[Team:Cohesion|Cohesion]] [[Team:Content|Content]] || Yes, meat || Yes || Hutspot, Meat (but vega is good too) ||
|-
| {{UserLink|Knorrie}} || [[Team:On-site_transportation|Logistics]] || - || Yes || Lasagne || -
|-
| {{UserLink|Nancy}} || [[Team:projectleiding|PL]] || - || Yes || Lasagne || -
|-
| {{UserLink|K4T0}} || [[Team:Bar|Bar]] || Vega || Yes || Hutspot vega ||
|-
| {{UserLink|zeno4ever}} || [[Team:Permits|Permits]] || - || Yes || Lasagne or meat hutspot ||
|-
| {{UserLink|Rewby}} || [[Team:NOC|NOC]] || Yes || Yes || meat hutspot or chips || No cheese
|-
| {{UserLink|justSem}} || [[Team:Foodcourt|Foodcourt]] || Yes, meat || Yes || meat lasgne or chips ||
|-
| {{UserLink|Betsy}} || [[Team:Bar|Bar]] || Yes, Vega || Yes || Hutspot vega ||
|-
| {{UserLink|Splodin}} || [[Team:SysAdmin|SysAdmin]] || Yes || Yes || Lasagne || -
|-
| {{UserLink|Rox}} || [[Team:Terrain|Terrain]] || Yes, vega || Yes || Lasagne || -
|-
| {{UserLink|Juerd}} || [[Team:Warehouse|Warehouse]] || No || Yes || Chips, Cheese souffle (no sandwhich) || -
|-
| {{UserLink|IcyPalm}} || [[Team:Villages|Villages]] || Yes, Meat || Yes || Lasagne || -
|-
| {{UserLink|Nicolas}} || [[Team:Content|Content]] || Yes, meat || Yes || Hutspot,meat || -
|-
| {{UserLink|BIlIaN}} || [[Team:POC|POC]] || Yes, meat || Yes || Lasagne || -
|-
| {{UserLink|Mirwi}} || [[Team:POC|POC]] || Yes, meat || Yes || Lasagne || -
|-
| {{UserLink|Okarin}} || [[Team:Volunteers]] || Yes, meat || Yes || Lasagne || -
|-
| {{UserLink|Jel}} || [[Team:Info|Info]] || No || Yes || Chips || -
|-
| {{UserLink|Hp197}} || [[Team:Projectleiding|PL]] || Yes || Yes || Lasagna ||
|-
| The food has || Been counted and|| Ordered || up till || here || -
|-
| Still wanna Join ? || Put your name|| below here || we still have || the Chips and cheese soufle || or Frikandel option
|-
| {{UserLink|Winko}} || [[Team:Villages|Villages]] || I'll manage || and work it out || when needed || -
|-
| {{UserLink|Tidi}} || [[Team:Bar|Bar]] || Yes || Yes || Meat only (frikandel only = fine) || no carbs/sugar, sugar replacements.
|-
| {{UserLink|Bustux}} || [[Team:Villages|Villages]] || Yes || Yes || Chips || -
|-
| {{UserLink|Hans}} || [[Team:NUTS|NUTS]] || Yes || No || - || -
|-
| {{UserLink|redlizard}} || [[Team:Terrain|Terrain]] || Yes || Yes || Would very much appreciate the Lasagna if something can be arranged or traded || -
|-
| {{UserLink|Bas}} || Yes || || Alles is lekker. Patatje frikandel, lasagna, boeie. Nogal onhandig dat ik niet wist dat er een deadline was. || ||
|-
|}

== Travel & Carpool ==
===Public transport ===

===Seats offered===
{| class="wikitable"
|-
! Name !! Seats available !! Leaving from !! Time
|-
| {{UserLink|Wido}} || 3 || Wageningen || ~11.30
|-
| {{UserLink|Piiindakaas}} || 3 || IJsselstein || 11.00-ish
|-
| {{UserLink|AK}} || 3 || Amersfoort || 11.00-ish
|-
| {{UserLink|IcyPalm}} || 2/3 || Groningen(via Drachten/Leeuwarden) || 11.00-ish
|}

=== Seats needed ===
{| class="wikitable"
|-
! Name !! Seats needed !! Leaving from !! Time
|-
| {{UserLink|Tidi}} || 1 || Amsterdam/Holendrecht || whenever
|}

== Photos and Videos of the location ==

Orga Meet 21 June 2025

2025-03-23T12:04:56Z

Bas: /* WHO (max = 150) */

{{Meeting
|Name=Orga Jitsi 21 June 2025
|StartDate=2025/06/21 13:37
|EndDate=2025/06/21
|Where=Revspace Den Haag
}}
Monthly in-person meeting for all volunteers. 
Meet time: 13:37 UTC+01:00

== What ==
An in person meet for anyone interested in making '''WHY2025''' an awesome event!

== Placeholder Program ==
Page prepared by Wheeze_NL and gratefully copied by Elborro, this is an actual placeholder program!
* 13:37 Doors open
* 14:30 Start of program,
* 15:00 Teams presentations
* 16:00 Meeting of teams and meeting teams you want to chat with
* 17:00 End of official program
* approx. 19:00 food

* Party

== WHO (max = 75) ==

Please note that Revspace has limited inside- and outside capacity. Outside we can seat 50 people roughly. Be ready for a distributed main portion of the meeting.

{| class="wikitable"
|-
! Name !! team !! Diner !! Food (tbd) Meat/Vega(n) !! Allergies/Dietary requirements
|-
| {{UserLink|Wheeze_NL}} || [[Team:ROC|ROC]],[[Team:On-site_transportation|Logistics]] || Yes || Anything || -
|-
| {{UserLink|Elborro}} || [[Team:Info|Info]] || Yes || Anything || -
|-
| {{UserLink|Killergeek}} || [[Team:NOC|NOC]] [[Team:NUTS|NUTS]] || Yes || Foooood || -
|-
| {{UserLink|Peetz0r}} || [[Team:Warehouse|Warehouse]] || Yes || Vega || No cheese
|-
| {{UserLink|FighterX64}} || [[Team:On-site_transportation|Logistics]] || Yes || Foooood || -
|-
| {{UserLink|Bas}} || [[Team:Waste]] || Yes || Foooood || -
|-
|}

== Meeting notes ==
Will be made during the meeting, it's still early!

Team:Waste

2025-02-22T14:15:59Z

Bas:

{{Team
|Lead=User:SynQ, User:Bas
|Description=Waste disposal during the event is key to not make a mess, so lets take care of it...
|Exclusive team=No
|Contact=waste@why2025.org
|team_is_essential_to_event=Show-stopper
|team_has_contact_info=Yes
|team_has_info_on_wiki=Yes
|team_has_planned_meetings=Yes
|team_has_enough_people=Yes
|team_has_drafted_budget=Yes
|team_has_informed_volunteer_team=Yes
|Projectleiding=User:Boekenwuurm
}}
==Team Members==
{| class="wikitable"
|+ Team Members
|-
! Username !! Previously involved !! Role
|-
|

{{TeamMemberEntry|User:rixvet}}
{{TeamMemberEntry|User:SynQ}}
{{TeamMemberEntry|User:Emma}}
{{TeamMemberEntry|User:Thijs}}
{{TeamMemberEntry|User:Bas}}
|| Yes (On-site MCH2022)|| Helper
|-
| || || Team-Lead
|-
| || No ||
|-
| || No ||
|-
| || Yes (SHA2017) ||
|-
|}

==Introduction==

== Things to discuss ==
* Budget!
* Contact the local waste processor
** Source separation/post-separation?
** What types of waste do they accept and in what form?
* Find out where we can rent good equipment (ask your PL contact for this, we have all the info for you)
* Deposit system/Statiegeld (team:finance > please don't, its a headache for both the bar and the books)
** Refund deposit to visitors or set up donation bins for deposits?
** It might be useful to contact Statiegeld Nederland to ask how we can do this
* Glitter
* WHY: Waste Help Yourself system for waste notifications about full trash containers
* How do people know what to throw in which bin

==Dependencies==
* Fixed DECT call group (for example, GRBG, WAST, WSTE, TRSH) (contact [[Team:POC]] about this)
* Instructions about waste
** "Please take home '''everything''' you bring, especially couches and tents" or something like that
**Contact [[Team:Info]] and [[Team:Villages]] about this
* [[Team:Terrain]] for planning
** Where should we collect everything
** Where is most of the waste produced (bar, food court, ...)
* [[Team:Volunteers]] for arranging volunteer shifts (picking up garbage and stuff)
* [[Team:Power]] for the power to the garbage press containers that compress trash
* Contact [[Team:Foodcourt]] about managing trash
** We supply infra, they empty the bins around the court?
** Might be useful if they have a trash compactor as well
* [[Team:Bar]]
** For Mate crates to collect empty bottles
** Statiegeld - what do they want to offer? Plastic bottles and cans have statiegeld on them.
* Team toilets
** Please ask them to not put any papieren handdoekjes in the toilet blocks because it makes the trash cans very heavy. Air drying is good enough.
* [[Team:Sysadmin]] so they can host [https://github.com/c3bottles/c3bottles c3bottles] for us (Bottle drop and collection management system for chaos events)

==Stuff we need==
=== Transport ===
* 2 big 40-foot waste containers for the end of the event
* 2,5 Gators and 2 trailers, reserved for Waste

=== Communication ===
* 1 portofoon per Gator
* DECT for each member of [[Team:Waste]]

=== Personal equipment ===
* Proper gloves in different sizes, for handling trash
* Workpants and/or some cheap shirts that can be dirty
** Free access to a washing machine
* Disinfecting soap

=== Trash collection ===
* Roll containers
** More than enough so that full ones can easily be swapped for empty ones during the event.
* Strong garbage bags
** One for every visitor
** A roll of garbage bags for every village
** Large ones for the bins
* Containers for special trash
** Paper
** Glass
** PMD
** Bulky waste
** Mate (no, team waste will not do 'statiegeld')
** Compost/green trash
** ???
* Sand for hot stuff like sigarettes
* Signs on the bins + tape

=== Trash handling ===
* Mobile press containers to compress trash
** Preferably should accept trash bags, instead of just containers
* Lighting for evening and night, so that trash handling can still be safely done in the dark

== Ideas ==
This section is for all volunteers. If you have any suggestions or idea's of stuff we could or should do (or not do), please post them here.
'''Your idea's won't go to waste!'''

* Burn waste that can be burned in a large fire.
* Collect radio active waste separately.
* Create a location to collect chemical waste or electronic waste.
* Statiegeld bags can be get trough wholesalers for bulk collection and return of deposit/ statiegeld bottle

Team:Waste

2025-02-22T14:14:25Z

Bas:

{{Team
|Lead=User:SynQ, User:Bas
|Description=Waste disposal during the event is key to not make a mess, so lets take care of it...
|Exclusive team=No
|Contact=waste@why2025.org
|team_is_essential_to_event=Show-stopper
|team_has_contact_info=Yes
|team_has_info_on_wiki=Yes
|team_has_planned_meetings=Yes
|team_has_enough_people=Yes
|team_has_drafted_budget=No
|team_has_informed_volunteer_team=No
|Projectleiding=User:Boekenwuurm
}}
==Team Members==
{| class="wikitable"
|+ Team Members
|-
! Username !! Previously involved !! Role
|-
|

{{TeamMemberEntry|User:rixvet}}
{{TeamMemberEntry|User:SynQ}}
{{TeamMemberEntry|User:Emma}}
{{TeamMemberEntry|User:Thijs}}
{{TeamMemberEntry|User:Bas}}
|| Yes (On-site MCH2022)|| Helper
|-
| || || Team-Lead
|-
| || No ||
|-
| || No ||
|-
| || Yes (SHA2017) ||
|-
|}

==Introduction==

== Things to discuss ==
* Budget!
* Contact the local waste processor
** Source separation/post-separation?
** What types of waste do they accept and in what form?
* Find out where we can rent good equipment (ask your PL contact for this, we have all the info for you)
* Deposit system/Statiegeld (team:finance > please don't, its a headache for both the bar and the books)
** Refund deposit to visitors or set up donation bins for deposits?
** It might be useful to contact Statiegeld Nederland to ask how we can do this
* Glitter
* WHY: Waste Help Yourself system for waste notifications about full trash containers
* How do people know what to throw in which bin

==Dependencies==
* Fixed DECT call group (for example, GRBG, WAST, WSTE, TRSH) (contact [[Team:POC]] about this)
* Instructions about waste
** "Please take home '''everything''' you bring, especially couches and tents" or something like that
**Contact [[Team:Info]] and [[Team:Villages]] about this
* [[Team:Terrain]] for planning
** Where should we collect everything
** Where is most of the waste produced (bar, food court, ...)
* [[Team:Volunteers]] for arranging volunteer shifts (picking up garbage and stuff)
* [[Team:Power]] for the power to the garbage press containers that compress trash
* Contact [[Team:Foodcourt]] about managing trash
** We supply infra, they empty the bins around the court?
** Might be useful if they have a trash compactor as well
* [[Team:Bar]]
** For Mate crates to collect empty bottles
** Statiegeld - what do they want to offer? Plastic bottles and cans have statiegeld on them.
* Team toilets
** Please ask them to not put any papieren handdoekjes in the toilet blocks because it makes the trash cans very heavy. Air drying is good enough.
* [[Team:Sysadmin]] so they can host [https://github.com/c3bottles/c3bottles c3bottles] for us (Bottle drop and collection management system for chaos events)

==Stuff we need==
=== Transport ===
* 2 big 40-foot waste containers for the end of the event
* 2,5 Gators and 2 trailers, reserved for Waste

=== Communication ===
* 1 portofoon per Gator
* DECT for each member of [[Team:Waste]]

=== Personal equipment ===
* Proper gloves in different sizes, for handling trash
* Workpants and/or some cheap shirts that can be dirty
** Free access to a washing machine
* Disinfecting soap

=== Trash collection ===
* Roll containers
** More than enough so that full ones can easily be swapped for empty ones during the event.
* Strong garbage bags
** One for every visitor
** A roll of garbage bags for every village
** Large ones for the bins
* Containers for special trash
** Paper
** Glass
** PMD
** Bulky waste
** Mate (no, team waste will not do 'statiegeld')
** Compost/green trash
** ???
* Sand for hot stuff like sigarettes
* Signs on the bins + tape

=== Trash handling ===
* Mobile press containers to compress trash
** Preferably should accept trash bags, instead of just containers
* Lighting for evening and night, so that trash handling can still be safely done in the dark

== Ideas ==
This section is for all volunteers. If you have any suggestions or idea's of stuff we could or should do (or not do), please post them here.
'''Your idea's won't go to waste!'''

* Burn waste that can be burned in a large fire.
* Collect radio active waste separately.
* Create a location to collect chemical waste or electronic waste.
* Statiegeld bags can be get trough wholesalers for bulk collection and return of deposit/ statiegeld bottle

Orga Meet 22 February 2025

2025-02-21T20:56:11Z

Bas: /* WHO (max = 75) */

{{Meeting
|Name=Orga Meet 22 February 2025
|StartDate=2025-02-22 13:37:00
|EndDate=2025-02-22 00:00:00
|Where=Hack42, Arnhem
}}
Monthly in-person meeting for all volunteers. 
Meet time: 13:37 UTC+01:00

== What ==
An in person meet for anyone interested in making '''WHY2025''' an awesome event!

== Placeholder Program ==
Page prepared by Wheeze_NL, this is an actual placeholder program!
* 13:37 Doors open
* 14:30 Start of program,
* 15:00 Teams presentations
* 16:00 Meeting of teams and meeting teams you want to chat with

* 17:00 End of official program
* approx. 19:00 food

* Party

== WHO (max = 75) ==
The Wheeze_NL preparing this page has no clue if there will be food etc.! 
It's better to have the info, than to ask later.
{| class="wikitable"
|-
! Name !! team !! Diner !! Food (tbd) Meat/Vega(n) !! Allergies/Dietary requirements
|-
| {{UserLink|Wheeze_NL}} || [[Team:ROC]], [[Team:On-site_transportation]] || Yes || Meat || -
|-
| {{UserLink|Ad}} || [[Team:Info]] || Yes || Anything || -
|-
| {{UserLink|Mack}} || [[Team:Productiehuis]] || Yes || Foooood || -
|-
| {{UserLink|FighterX64}} || [[Team:On-site_transportation]] || Yes || Foooood || -
|-
| {{UserLink|Killergeek}} || [[Team:NOC]] [[Team:NUTS]] || Yes || Foooood || -
|-
| {{UserLink|hp197}} || [[Team:Projectleiding]] || Yes || ^.+?$ || -
|-
| {{UserLink|koffiepot}} || [[Team:Safety]] || Yes || Meat || -
|-
| {{UserLink|Boekenwuurm}} || [[Team:Projectleiding]] || Yes || vega || -
|-
| {{UserLink|NancyBeers}} || [[Team:Projectleiding]] || Yes || Anything || -
|-
| {{UserLink|SqyD}} || - || Yes || Low Carb || -
|-
| {{UserLink|Jvdbreemen}} || [[Team:Info]] || Yes || Meat || -
|-
| {{UserLink|Number3}} || IFCAT Board || Yes || Meat || -
|-
| {{UserLink|Peetz0r}} || [[Team:Warehouse]] || Yes || Vega || No cheese
|-
| {{UserLink|Obsidian}} || [[Village:Milliways]] || No food || nvt || -
|-
| {{UserLink|jos}} || [[Team:Content]] || Yes || Meat || -
|-
| {{UserLink|loppermann}} || [[Team:POC]] || Yes || Meat || -
|-
| {{UserLink|Twi}} || [[Team:POC]] || Yes || Meat || -
|-
| {{UserLink|Michaela}} || [[Team:POC]] || Yes || Meat || -
|-
| {{UserLink|Uglyhack}} || [[Team:Terrain]] || Yes || Vega || -
|-
| {{UserLink|K4T0}} || [[Team:Bar]] || Yes || Vega || -
|-
| {{UserLink|sirgoofy}} || [[Team:Info]] || Yes || Anything || -
|-
| {{UserLink|konmei}} || [[Team:Villages]] [[Team:Parking]] || Yes || Anything || -
|-
| {{UserLink|Winko}} || [[Team:Villages]] || No || Nope || -
|-
| {{UserLink|eightdot}} || [[Team:NOC]] [[Team:NUTS]] || Yes || Meat || -
|-
|| {{UserLink|AK}} || [[Team:NOC]] || Yes || Meat || -
|-
|| {{UserLink|Tomups}} || [[Team:Sponsors]] || Yes || Omnivore || Levo-amino acid
|-
| {{UserLink|Netsmurf}} || [[Team:Projectleiding]] || Yes || Meat || -
|-
| {{UserLink|denz}} || [[Team:Bar]] || Yes || Meat || -
|-
| {{UserLink|Lenneke}} || || Yes ||Anything || -
|-
| {{UserLink|raboof}} || [[Team:Info]] || Yes || Yes || -
|-
| {{UserLink|Bix}} || [[Team:Productiehuis]] || Yes || Yes || -
|-
| {{UserLink|Dany}} || [[Team:Cohesion]], [[Team:Content]] || Yes || Anything || -
|-
| {{UserLink|Polyfloyd}} || [[Team:Deco]] || Yes || Anything || -
|-
| {{UserLink|CH23}} || [[Team:Warehouse]] || Yes || Vega || -
|-
| {{UserLink|Rewby}} || [[Team:NOC]] || Yes || Meat || No cheese
|-
| {{UserLink|piiindakaas}} || [[Team:Projectleiding]] || Yes || Food ||
|-
| {{UserLink|Hoxolotl}} || [[Team:Deco]] || Yes || Food ||
|-
| {{UserLink|Splodin}} || [[Team:SysAdmin]] || Yes || Food ||
|-
| {{UserLink|rox}} || [[Team:Terrain]] || Yes || Vega ||
|-
| {{UserLink|Juerd}} || [[Team:Warehouse]] || Yes || Food || It's complicated; please provide ingredient lists.
|-
| {{UserLink|Gina}} || [[Team:Terrain]] || Yes || Vega ||
|-
| {{UserLink|Tidi}} || [[Team:Bar]] || Maybe || Meat only || Complicated, no sugars(no carbs, no sugar replacements, no natural sugars) Strict keto or meat only
|-
| {{UserLink|MissMaps}} || [[Team:Terrain]] || yes || anything ||
|-
| {{UserLink|Lmpsk}} || - || Yes || Meat || -
|-
| {{UserLink|Tatiana}} || [[Team:Safety-First-AID]] || Yes || Meat || -
|-
| {{UserLink|Jay9}} || [[Team:Badge]] || Yes || Vegan || -
|-
| {{UserLink|Dutchmartin}} || [[Team:NUTS]] || Yes || Meat || -
|-
| {{UserLink|INJMVO}} || [[Team:Terrain]] || Yes || Meat || -
|-
| {{UserLink|SynQ}} || [[Team:Waste]] || Yes || Meat || -
|-
| {{UserLink|Emma}} || [[Team:Waste]] || Yes || Meat || -
|-
| {{UserLink|Aranea}} || [[Team:Deco]] || Yes || Meat || No diary
|-
| {{UserLink|Quux}} || [[Team:Off-site_transportation]] || Yes || Meat || -
|-
| {{UserLink|Poef}} || [[Team:Deco]] || Yes || Food || -
|-
| {{UserLink|Moem}} || [[Team:Deco]] || Yes || Vega+Fish || -
|-
| {{UserLink|Josnoww}} || [[Team:Sponsors]] || TBD || Vega || -
|-
| {{UserLink|Huubje}} || [[Team:Bar]] || Yes || Vega || -
|-
| {{UserLink|Stitch}} || - || Yes || Meat || -
|-
| {{UserLink|Cr0w}} || [[Team:Sponsors]] || Yes || Vega/n || enough vega/n food pls :')
|-
| {{UserLink|Bas}} || [[Team:Waste]] || Yes || Any food really ||
|-
| You? || || ||
|-
|}

== Car pool ==

Aome people might coming from the same region. If you arrive by car and have space to spare or would like to travel with someone to the meeting: please add yourself here.

=== Seat offered ===

Add your nick here and which place you'll be departing from

{| class="wikitable"
|-
! Name !! Seats available !! Leaving from !! Time
|-
| {{UserLink|Piiindakaas}} || 4 || Utrecht || 12-ish
|-
|}

== Meeting notes ==
Will be made during the meeting, it's still early!

Team:Waste

2024-09-12T19:58:57Z

Bas: /* Team Members */

{{Team
|Lead=User:SynQ
|Description=Waste disposal during the event is key to not make a mess, so lets take care of it...
|Exclusive team=No
|team_is_essential_to_event=Important
|team_has_contact_info=No
|team_has_info_on_wiki=No
|team_has_planned_meetings=No
|team_has_enough_people=No
|team_has_drafted_budget=No
|team_has_informed_volunteer_team=No
|Projectleiding=User:Boekenwuurm
}}
==Team Members==

{| class="wikitable"
|+ Team Members
|-
! Username !! Previously involved !! Role
|-
| {{TeamMemberEntry|User:rixvet}} || Yes (On-site MCH2022)|| Helper
|-
| {{TeamMemberEntry|User:SynQ}} || ||
|-
| {{TeamMemberEntry|User:Emma}} || No ||
|-
| {{TeamMemberEntry|User:Thijs}} || No ||
|-
| {{TeamMemberEntry|User:Bas}} || Yes (SHA2017) ||
|-
|}

==Introduction==

== Things to discuss ==
* Budget!
* Contact the local waste processor
** Source separation/post-separation?
** What types of waste do they accept and in what form?
* Find out where we can rent good equipment (ask your PL contact for this, we have all the info for you)
* Deposit system/Statiegeld (team:finance > please don't, its a headache for both the bar and the books)
** Refund deposit to visitors or set up donation bins for deposits?
** It might be useful to contact Statiegeld Nederland to ask how we can do this
* Glitter
* WHY: Waste Help Yourself system for waste notifications about full trash containers
* How do people know what to throw in which bin

==Dependencies==
* Fixed DECT call group (for example, GRBG, WAST, WSTE, TRSH) (contact [[Team:POC]] about this)
* Instructions about waste
** "Please take home '''everything''' you bring, especially couches and tents" or something like that
**Contact [[Team:Info]] and [[Team:Villages]] about this
* [[Team:Terrain]] for planning
** Where should we collect everything
** Where is most of the waste produced (bar, food court, ...)
* [[Team:Volunteers]] for arranging volunteer shifts (picking up garbage and stuff)
* [[Team:Power]] for the power to the garbage press containers that compress trash
* Contact [[Team:Foodcourt]] about managing trash
** We supply infra, they empty the bins around the court?
** Might be useful if they have a trash compactor as well
* [[Team:Bar]]
** For Mate crates to collect empty bottles
** Statiegeld - what do they want to offer? Plastic bottles and cans have statiegeld on them.
* Team toilets
** Please ask them to not put any papieren handdoekjes in the toilet blocks because it makes the trash cans very heavy. Air drying is good enough.
* [[Team:Sysadmin]] so they can host [https://github.com/c3bottles/c3bottles c3bottles] for us (Bottle drop and collection management system for chaos events)

==Stuff we need==
=== Transport ===
* 2 big 40-foot waste containers for the end of the event
* 2,5 Gators and 2 trailers, reserved for Waste

=== Communication ===
* 1 portofoon per Gator
* DECT for each member of [[Team:Waste]]

=== Personal equipment ===
* Proper gloves in different sizes, for handling trash
* Workpants and/or some cheap shirts that can be dirty
** Free access to a washing machine
* Disinfecting soap

=== Trash collection ===
* Roll containers
** More than enough so that full ones can easily be swapped for empty ones during the event.
* Strong garbage bags
** One for every visitor
** A roll of garbage bags for every village
** Large ones for the bins
* Containers for special trash
** Paper
** Glass
** PMD
** Bulky waste
** Mate
** ???
* Sand for hot stuff like sigarettes
* Signs on the bins + tape

=== Trash handling ===
* Mobile press containers to compress trash
** Preferably should accept trash bags, instead of just containers
* Lighting for evening and night, so that trash handling can still be safely done in the dark

== Ideas ==
This section is for all volunteers. If you have any suggestions or idea's of stuff we could or should do (or not do), please post them here.
'''Your idea's won't go to waste!'''

* Burn waste that can be burned in a large fire.
* Collect radio active waste separately.
* Create a location to collect chemical waste or electronic waste.
* Statiegeld bags can be get trough wholesalers for bulk collection and return of deposit/ statiegeld bottle

User:Bas

2024-06-16T13:53:02Z

Bas:

{{UserInfo
|NickName={{PAGENAME}}
|Languages=EN, NL, mediocre DE
|HackerSpace=Revspace, Hackalot
}}
Teacher, Boardmember of RevSpace. I co-led team Volunteering at MCH2022, Waste at SHA2017. Also helped out with SHA2017 Badge. Currently not in a team (intentional), but if anyone needs advice or a braindump about things from previous events, hit me up!

User:Bas

2024-06-16T13:49:43Z

Bas: create user page

{{UserInfo
|NickName={{PAGENAME}}
|Languages=EN
|HackerSpace=
}}