Team:Projectleiding
| Projectleiding | |
|---|---|
| Team:Projectleiding, the team who does the project management things. | |
| 1st line contacts: | Boekenwuurm, NancyBeers |
| Is an exclusive team: | Yes |
| Contact e-mail: | |
| Responsible for: | |
| IRC: | #WHY2025 |
Team members
Boekenwuurm (Christel) wanted to make a booklet for SHA2017 and ended up with a large role within team:Info, and graduated to projectleiding MCH2025. She is active with Hackalot in Eindhoven and will always make time to geek out about the physics behind printers, camera's, wearables or colors.
Halcyon (Tom) has organised events for over a decade, and started the HackZone hacker field at the yearly 11-day CampZone event in 2015. Sha2017 was his first Dutch hacker camp, and he fell in love with them immediately. He is one of the people behind Badge.Team: a group that makes electronic badges for a bunch of hacker events. Founder of a geeky electronics company that makes hardware security tools and embedded development kits 👾⚡️, and a biotech startup that grows tropical wood without cutting down a single tree 🌳🌎. Firm believer in social equality and freedom of information.
Hp197 (Henry) has the drive to empower a successful event by just doing and making happen. You wont see him leading many projects, as treasurer his job is to keep the check and balances and make current and future events possible. Henry strongly believes in equality and inclusivity for everybody, as a minority subculture he very well knows how it feels like to be not included and out of this believe he contributes to more equality for future beings.
Netsmurf (Jeroen) has organized events since HAL and started out there as a general volunteer. Volunteered for the NOC teams of WtH, OHM, EMF, CCC Camp and Congres for the last few times. Joined PL for SHA2017/MCH2021 and now again for MCH2022. His hobbies are diving & paragliding, working with wood and he enjoy organizing awesome events with all the nice volunteers. His day jobs are managing his companies, building/maintaining/troubleshooting large ISP networks and trading in IP addresses. Netsmurf believes in equal rights and opportunities for everyone and paying it forward.
NancyBeers (Nancy) plays serious games for a living. Which is not that far off from social engineering. This will be her 5th Dutch camp, and after being an Angel and Speaker, she now will help organise. Together with Boekwuurm she's the Chair of Ifcat.
Piiindakaas (Marieke) If you see someone bounce through a group of people, it's probably Piiindakaas. MCH22 was her first hackercamp, she joined team press and by the end of the camp she joined so much teams and made a lot of friends. On a daily base she works in communication for a cybersecurity company and is responsible for the communication of DIVD. Guess what's her favorite food?
Vacancies
Currently no vacancies.
Who is contact for which teams?
| Team | PL Contactperson | Team is essential to event | Team has contact info | Team has info on wiki | Team has planned meetings | Team has enough people | Team needs x people | Team has drafted budget | Team contact info |
|---|---|---|---|---|---|---|---|---|---|
| Accessibility | NancyBeers | Important | ✅ | ✅ | ❌ | ❌ | No | {{{10}}} | |
| Badge | Halcyon | Flavour | ✅ | ✅ | ✅ | ✅ | Yes | {{{10}}} | |
| Bar | Netsmurf | Important | ❌ | ❌ | ✅ | ❌ | No | {{{10}}} | |
| CTF | Halcyon | Substance | ✅ | ✅ | ✅ | ✅ | Yes | {{{10}}} | |
| Cohesion | Piiindakaas | Show-stopper | ✅ | ✅ | ❌ | ❌ | Yes | {{{10}}} | |
| Content | NancyBeers | Substance | ✅ | ✅ | ✅ | ✅ | Yes | {{{10}}} | |
| Deco | Boekenwuurm | Flavour | ✅ | ✅ | ✅ | ❌ | Yes | {{{10}}} | |
| Entertainment | NancyBeers | Flavour | ✅ | ❌ | ❌ | ❌ | No | {{{10}}} | |
| Family | Boekenwuurm | Substance | ✅ | ✅ | ✅ | ❌ | Yes | {{{10}}} | |
| Finance | Hp197 | Show-stopper | ✅ | ❌ | ❌ | ✅ | Yes | {{{10}}} | |
| Flags | Boekenwuurm | Flavour | ✅ | ❌ | ❌ | ❌ | Yes | {{{10}}} | |
| Foodcourt | Piiindakaas | Substance | ✅ | ✅ | ✅ | ✅ | Yes | {{{10}}} | |
| Heralds | NancyBeers | Substance | ✅ | ✅ | ✅ | ❌ | Yes | {{{10}}} | |
| Huisstijl | Piiindakaas | Flavour | ✅ | ✅ | ❌ | ✅ | No | {{{10}}} | |
| Info | Boekenwuurm | Important | ✅ | ✅ | ✅ | ❌ | Yes | {{{10}}} | |
| Merch | Netsmurf | Flavour | ✅ | ✅ | ✅ | ❌ | Yes | {{{10}}} | |
| Moebelhaus | Netsmurf | Substance | ❌ | ✅ | ❌ | ❌ | Yes | {{{10}}} | |
| NOC | Netsmurf | Substance | ❌ | ❌ | ❌ | ❌ | Yes | {{{10}}} | |
| NUTS | Halcyon | Show-stopper | ✅ | ✅ | ✅ | ✅ | Yes | {{{10}}} | |
| Off-site Logistics | Boekenwuurm | Important | ✅ | ✅ | ❌ | ❌ | No | {{{10}}} | |
| On-site Logistics | Halcyon | Show-stopper | ✅ | ✅ | ✅ | ✅ | No | {{{10}}} | |
| POC | Piiindakaas | Important | ✅ | ✅ | ✅ | ✅ | Yes | {{{10}}} | |
| Parking | Netsmurf | Important | ✅ | ✅ | ❌ | ❌ | No | {{{10}}} | |
| PartyArea | Netsmurf | Flavour | ❌ | ✅ | ❌ | ❌ | No | {{{10}}} | |
| Permits | NancyBeers | Show-stopper | ✅ | ✅ | ✅ | ✅ | Yes | {{{10}}} | |
| Press | Piiindakaas | Substance | ✅ | ✅ | ❌ | ❌ | No | {{{10}}} | |
| Productiehuis | Piiindakaas | Substance | ✅ | ✅ | ✅ | ❌ | Yes | {{{10}}} | |
| Projectleiding | [[ |]] | New and improved | ✅ | ✅ | ✅ | ✅ | Yes | {{{10}}} | |
| ROC | Halcyon | Important | ❌ | ❌ | ❌ | ❌ | No | {{{10}}} | |
| Safety-Fire | Netsmurf | Show-stopper | ❌ | ✅ | ✅ | ❌ | Yes | {{{10}}} | |
| Safety-First-AID | Netsmurf | Show-stopper | ❌ | ✅ | {{{10}}} | ||||
| Safety-Security | Netsmurf | Important | {{{10}}} | ||||||
| Shuttle | NancyBeers | Flavour | ✅ | ✅ | ❌ | ❌ | No | {{{10}}} | |
| Speaker Desk | NancyBeers | Flavour | ❌ | ❌ | ❌ | ❌ | Yes | {{{10}}} | |
| Sponsors | Halcyon | Important | ✅ | ✅ | ✅ | ❌ | No | {{{10}}} | |
| Sysadmin | Boekenwuurm | Show-stopper | ✅ | ✅ | ✅ | ✅ | Yes | {{{10}}} | |
| Terrain | Boekenwuurm | Show-stopper | ✅ | ✅ | ✅ | ✅ | No | {{{10}}} | |
| Ticket & Entrance | Boekenwuurm | Important | ✅ | ❌ | ❌ | ❌ | Yes | {{{10}}} | |
| Villages | Piiindakaas | Substance | ✅ | ✅ | ✅ | ❌ | Yes | {{{10}}} | |
| Volunteers | NancyBeers | Important | ✅ | ✅ | ✅ | ❌ | No | {{{10}}} | |
| Warehouse | Boekenwuurm | Important | ✅ | ✅ | ❌ | ✅ | No | {{{10}}} | |
| Waste | NancyBeers | Show-stopper | ✅ | ✅ | ✅ | ✅ | Yes | {{{10}}} |
Meetings
We meet every on uneven week Wednesday on the WHY Jitsi.
Upcoming meetings
| Name | Start | Location |
|---|---|---|
| Meeting Projectleiding 2025 06 25 | 25 June 2025 20:00:00 | https://meet.hack42.nl/why-meet |
| Meeting Projectleiding 2025 07 09 | 9 July 2025 20:00:00 | https://meet.hack42.nl/why-meet |
| Meeting Projectleiding 2025 07 23 | 23 July 2025 20:00:00 | https://meet.hack42.nl/why-meet |
Past meetings
Team status list
Todo: update this list. This is outdated and taken from MCH2022.
This overview gives an insight on the health of teams. Also see Vacancies.
Meaning of the fields:
This team is required for the event:
Meaning: without the deliverables of this team the event can not continue. For example: team:power is a requirement for lectures, recording, sanitation and so on. Counter example: a badge is a great add on to the event, but even if it fails, the event can continue safely. Crucial teams contribute to safety, essential services, hygiene, health.
Status: Team has contact information:
Meaning: a new volunteer or the existing network of volunteers can easily contact this team and ask questions or status information.
Status: Team has informative wiki page:
Meaning: the wiki page of the team details a bit of their plans, how they do it and what they provide to others. It contains who the team members are. This is a treasure trove for next events, as well as a way to streamline information to other teams.
Status: Team has meetings are planned until the event:
Meaning: the team is in control and regular meetings / gatherings to check progress, todo's, questions and whatever is relevant to the team. Meetings do not always need to be formal or documented in order to set this checkmark of course.
Status: Team has enough orga-volunteers to function:
Meaning: there are enough dedicated people on the team that everyone on the team can enjoy at least two days at the camp without doing anything for this team. The stress level is relatively low because work is shared among team members. Angels are excluded in this metric: note that angels often need training, which also takes time which must be allocated. Examples of what this being unchecked can mean: people are not exclusive to this team and thus cannot guarantee time before and during the event, there are tons of plans but no actual work is planned, performed or managed, people are out of reach, there is no backup for crucial team roles, there is no time allocated to instruct and guide angels. There is no tracking of progress.
Status: Team has drafted a budget:
Meaning: there is a table of expected expenses and projected income. This consists of listing of items, with their price. This does not need to be public, but team:finance must know. If there is no budget, the finance team / board will try to determine one: better to be in control yourself, so allocate, estimate and write it down.
Status: Team has informed team:volunteers:
Meaning: if there are any angel requirements, or orga-volunteers needed, team:volunteers is aware of their numbers and needed capabilities. Yes you can search yourself, and you can also get more searching capacity if these numbers and skills are shared.