MCH2022 wiki - User contributions [en]

Team:Content/LessonsLearned

2022-12-31T11:26:19Z

DWizzy: /* What could be done better */

= [[Team:Content|Team Content]] Lessons Learned =

== What went well ==

* Have a (bi) weekly meeting, consistency in that worked well
* Have meeting notes and action points
* Have a fridge in the speaker desk tent
* HDMI test at the speaker desk
* The box of AV adaptors and various cables
* Label printer (eventually!)
* Have a special sticker only for speakers
* Let visitors vote what they would likely attend
* Herald cue cards
* Stickynotes weekend

== What could be done better ==

* Allow for more redundancy in the team, because COVID is a bitch
* Ensure for more ticket types than just financial support tickets/more fluid UX
* Decision-making process on financial support of speakers. Make having that process an early deliverable, as early as the CfP. Use past requests as use cases for that process.
* Split the team in sub teams/tasks so that we don't need 10+ people in every meeting
* Treat SpeakerDesk more like HeraldDesk, so involvement pre-event is more limited
* Have Team:SpeakerDesk involved in the Team:Content meetings once a month / every 2 months, not necessarily every meeting. They are seperate teams.
* Have the same HDMI cable as used in the (workshop) tents for testing the speaker laptop
* Sync up better with Productiehuis beforehand
* Lightning talks coordination fell through almost completely
* Improve publlication process from PretalX to public schedule, the static export function proved to be a real pain in the behind.
* Notice that speakers did not arrive yet (have a better process for dealing with this)
* Be clearer about role and time expectations, and make sure everyone is willing to commit to those
** Fundraising, somehow this has been a responsibility of Team Content, this should at least have been communicated beforehand by Projectleiding and it would make sense for Projectleiding to "own" this, in collaboration with Team Content, and not the other way around.
* It looked like the expectations of what's part of content, what's part of speaker desk were not aligned always:
** Visa
** Assisting the speaker with financial support
** Stages/tents
** ...
* Understand requirements for Workshop tents better
* variety in team
* no veto's
* Do realise the event lives in CET/CEST, too often meetings were messy because of people expecting BST/EET.
* Tents and fresh (!) sleeping gear for a few speakers was difficult to acquire later during the event

== Suggestions for the next event ==

* Make it possible to only have the role reviewer
* Vet the speakers more thoroughly
** Strongly prefer watching a video of a speaker before? Both for content and fluency. [[User:DWizzy|DWizzy]] ([[User talk:DWizzy|talk]])
* Smaller sub teams
** Also make sure there is a subteam for subsidies (Do we have a document store with the subsidy request paperwork for MCH we can copy pasta?)
* Make it possible that Angels can use a part of the content management system so you need less people of Team Content/Speaker desk during the event
* Check if people are available hours/a day before they need to be on stage. Especially if the people presenting the first shift of the day are registered. Pretalx didn't really help here.
* Start 1.5 year before the event
* Have someone at Projectleiding responsible for *all* stages, including workshop stages.
* Figure out process for accepting sooner, especially in light of (financial) support of speakers for which there will be constraints in time (plane tickets get more expensive, visa processes take time)
* The above allows for more active scouting of interesting speakers
* Make it clear that if you drop out without communication that you cannot challenge decisions made during your absence.
* Figure out financial support for speakers criteria, and process to apply those criteria, way in advance.
* Ensure sticky notes meeting is booked very very far in advance
* Agree handover/touchpoints between Content <> SpeakerDesk <> PH (productiehuis?) <> HeraldDesk <> [[Team:Info]]
** Established communication lines: phone numbers, e-mail, radio...
** Established broadcasting: if changes in the schedule (or other events like blackout?) announce it through slides on the monitors (through Productiehuis?), heralds, Twitter..
** Make sure process for guests/speakers is clear at all three entrances (harbour, logistics gate/shuttle, parking/main entrance).
*** Maybe a cheat sheet at the locations so there’s no dependence on others (not all angels are trained well enough)
* Have the lightning talk coordinator in at least 2 of the team content meetings and a few of the team: Speakerdesk meetings
* Make sure there is a publication system well understood for the lightning desk coordinator
* Make sure either the lightning talk coordinator performs angeling or there is coordination with the herald desk

* Call for performances/art/entertainment so we get performances from the community (and perhaps cheaper) instead of booking them
* Lockbox for gator keys, so not dependent on the holder of the key to be around.
* Availability of booklets etc. for speakers
* locked stash of exclusive stickers etc., only have the daily amount on the desk
* speaker lounge a bit larger and more separated from the team desks; enough place to shelter from rain and sun
* more visible water boiler so people drink tea and coffee, and enough hot beverage cups. Perhaps a way to keep cups in the tent?
* Ice cubes
* have a few spare tents/sleeping arrangements in advance for speakers

= Intend to join team Content for the next event =

== Yes ==

* Viola
* Hugh
* Erik
* [[User:DWizzy]]

== No ==
* Walter (really people, had to gather energy to tinker with this lemma on the wiki)

== Maybe ==

* Martian
* Claudia
* Robin

Team:Content/LessonsLearned

2022-12-31T11:25:29Z

DWizzy: /* What could be done better */

= [[Team:Content|Team Content]] Lessons Learned =

== What went well ==

* Have a (bi) weekly meeting, consistency in that worked well
* Have meeting notes and action points
* Have a fridge in the speaker desk tent
* HDMI test at the speaker desk
* The box of AV adaptors and various cables
* Label printer (eventually!)
* Have a special sticker only for speakers
* Let visitors vote what they would likely attend
* Herald cue cards
* Stickynotes weekend

== What could be done better ==

* Allow for more redundancy in the team, because COVID is a bitch
* Ensure for more ticket types than just financial support tickets/more fluid UX
* Decision-making process on financial support of speakers. Make having that process an early deliverable, as early as the CfP. Use past requests as use cases for that process.
* Split the team in sub teams/tasks so that we don't need 10+ people in every meeting
* Treat SpeakerDesk more like HeraldDesk, so involvement pre-event is more limited
* Have Team:SpeakerDesk involved in the Team:Content meetings once a month / every 2 months, not necessarily every meeting. They are seperate teams.
* Have the same HDMI cable as used in the (workshop) tents for testing the speaker laptop
* Sync up better with Productiehuis beforehand
* Lightning talks coordination fell through almost completely
* Improve publlication process from PretalX to public schedule, the static export function proved to be a real pain in the behind.
* Notice that speakers did not arrive yet (have a better process for dealing with this)
* Be clearer about role and time expectations, and make sure everyone is willing to commit to those
** Fundraising, somehow this has been a responsibility of Team Content, this should at least have been communicated beforehand by Projectleiding and it would make sense for Projectleiding to "own" this, in collaboration with Team Content, and not the other way around.
* It looked like the expectations of what's part of content, what's part of speaker desk were not aligned always:
** Visa
** Assisting the speaker with financial support
** Stages/tents
** ...
* Understand requirements for Workshop tents better
* variety in team
* no veto's
* Do realise the event lives in CET/CEST, too often meetings were messy because of people expecting BST/EET.
* Tents and fresh (!) sleeping gear for a few speakers was difficult to

== Suggestions for the next event ==

* Make it possible to only have the role reviewer
* Vet the speakers more thoroughly
** Strongly prefer watching a video of a speaker before? Both for content and fluency. [[User:DWizzy|DWizzy]] ([[User talk:DWizzy|talk]])
* Smaller sub teams
** Also make sure there is a subteam for subsidies (Do we have a document store with the subsidy request paperwork for MCH we can copy pasta?)
* Make it possible that Angels can use a part of the content management system so you need less people of Team Content/Speaker desk during the event
* Check if people are available hours/a day before they need to be on stage. Especially if the people presenting the first shift of the day are registered. Pretalx didn't really help here.
* Start 1.5 year before the event
* Have someone at Projectleiding responsible for *all* stages, including workshop stages.
* Figure out process for accepting sooner, especially in light of (financial) support of speakers for which there will be constraints in time (plane tickets get more expensive, visa processes take time)
* The above allows for more active scouting of interesting speakers
* Make it clear that if you drop out without communication that you cannot challenge decisions made during your absence.
* Figure out financial support for speakers criteria, and process to apply those criteria, way in advance.
* Ensure sticky notes meeting is booked very very far in advance
* Agree handover/touchpoints between Content <> SpeakerDesk <> PH (productiehuis?) <> HeraldDesk <> [[Team:Info]]
** Established communication lines: phone numbers, e-mail, radio...
** Established broadcasting: if changes in the schedule (or other events like blackout?) announce it through slides on the monitors (through Productiehuis?), heralds, Twitter..
** Make sure process for guests/speakers is clear at all three entrances (harbour, logistics gate/shuttle, parking/main entrance).
*** Maybe a cheat sheet at the locations so there’s no dependence on others (not all angels are trained well enough)
* Have the lightning talk coordinator in at least 2 of the team content meetings and a few of the team: Speakerdesk meetings
* Make sure there is a publication system well understood for the lightning desk coordinator
* Make sure either the lightning talk coordinator performs angeling or there is coordination with the herald desk

* Call for performances/art/entertainment so we get performances from the community (and perhaps cheaper) instead of booking them
* Lockbox for gator keys, so not dependent on the holder of the key to be around.
* Availability of booklets etc. for speakers
* locked stash of exclusive stickers etc., only have the daily amount on the desk
* speaker lounge a bit larger and more separated from the team desks; enough place to shelter from rain and sun
* more visible water boiler so people drink tea and coffee, and enough hot beverage cups. Perhaps a way to keep cups in the tent?
* Ice cubes
* have a few spare tents/sleeping arrangements in advance for speakers

= Intend to join team Content for the next event =

== Yes ==

* Viola
* Hugh
* Erik
* [[User:DWizzy]]

== No ==
* Walter (really people, had to gather energy to tinker with this lemma on the wiki)

== Maybe ==

* Martian
* Claudia
* Robin

Team:Content/LessonsLearned

2022-12-31T11:12:58Z

DWizzy: /* Suggestions for the next event */

= [[Team:Content|Team Content]] Lessons Learned =

== What went well ==

* Have a (bi) weekly meeting, consistency in that worked well
* Have meeting notes and action points
* Have a fridge in the speaker desk tent
* HDMI test at the speaker desk
* The box of AV adaptors and various cables
* Label printer (eventually!)
* Have a special sticker only for speakers
* Let visitors vote what they would likely attend
* Herald cue cards
* Stickynotes weekend

== What could be done better ==

* Allow for more redundancy in the team, because COVID is a bitch
* Ensure for more ticket types than just financial support tickets/more fluid UX
* Decision-making process on financial support of speakers. Make having that process an early deliverable, as early as the CfP. Use past requests as use cases for that process.
* Split the team in sub teams/tasks so that we don't need 10+ people in every meeting
* Treat SpeakerDesk more like HeraldDesk, so involvement pre-event is more limited
* Have Team:SpeakerDesk involved in the Team:Content meetings once a month / every 2 months, not necessarily every meeting. They are seperate teams.
* Have the same HDMI cable as used in the (workshop) tents for testing the speaker laptop
* Sync up better with Productiehuis beforehand
* Lightning talks coordination fell through almost completely
* Improve publlication process from PretalX to public schedule, the static export function proved to be a real pain in the behind.
* Notice that speakers did not arrive yet (have a better process for dealing with this)
* Be clearer about role and time expectations, and make sure everyone is willing to commit to those
** Fundraising, somehow this has been a responsibility of Team Content, this should at least have been communicated beforehand by Projectleiding and it would make sense for Projectleiding to "own" this, in collaboration with Team Content, and not the other way around.
* It looked like the expectations of what's part of content, what's part of speaker desk were not aligned always:
** Visa
** Assisting the speaker with financial support
** Stages/tents
** ...
* Understand requirements for Workshop tents better
* variety in team
* no veto's
* Do realise the event lives in CET/CEST, too often meetings were messy because of people expecting BST/EET.

== Suggestions for the next event ==

* Make it possible to only have the role reviewer
* Vet the speakers more thoroughly
** Strongly prefer watching a video of a speaker before? Both for content and fluency. [[User:DWizzy|DWizzy]] ([[User talk:DWizzy|talk]])
* Smaller sub teams
** Also make sure there is a subteam for subsidies (Do we have a document store with the subsidy request paperwork for MCH we can copy pasta?)
* Make it possible that Angels can use a part of the content management system so you need less people of Team Content/Speaker desk during the event
* Check if people are available hours/a day before they need to be on stage. Especially if the people presenting the first shift of the day are registered. Pretalx didn't really help here.
* Start 1.5 year before the event
* Have someone at Projectleiding responsible for *all* stages, including workshop stages.
* Figure out process for accepting sooner, especially in light of (financial) support of speakers for which there will be constraints in time (plane tickets get more expensive, visa processes take time)
* The above allows for more active scouting of interesting speakers
* Make it clear that if you drop out without communication that you cannot challenge decisions made during your absence.
* Figure out financial support for speakers criteria, and process to apply those criteria, way in advance.
* Ensure sticky notes meeting is booked very very far in advance
* Agree handover/touchpoints between Content <> SpeakerDesk <> PH (productiehuis?) <> HeraldDesk <> [[Team:Info]]
** Established communication lines: phone numbers, e-mail, radio...
** Established broadcasting: if changes in the schedule (or other events like blackout?) announce it through slides on the monitors (through Productiehuis?), heralds, Twitter..
** Make sure process for guests/speakers is clear at all three entrances (harbour, logistics gate/shuttle, parking/main entrance).
*** Maybe a cheat sheet at the locations so there’s no dependence on others (not all angels are trained well enough)
* Have the lightning talk coordinator in at least 2 of the team content meetings and a few of the team: Speakerdesk meetings
* Make sure there is a publication system well understood for the lightning desk coordinator
* Make sure either the lightning talk coordinator performs angeling or there is coordination with the herald desk

* Call for performances/art/entertainment so we get performances from the community (and perhaps cheaper) instead of booking them
* Lockbox for gator keys, so not dependent on the holder of the key to be around.
* Availability of booklets etc. for speakers
* locked stash of exclusive stickers etc., only have the daily amount on the desk
* speaker lounge a bit larger and more separated from the team desks; enough place to shelter from rain and sun
* more visible water boiler so people drink tea and coffee, and enough hot beverage cups. Perhaps a way to keep cups in the tent?
* Ice cubes
* have a few spare tents/sleeping arrangements in advance for speakers

= Intend to join team Content for the next event =

== Yes ==

* Viola
* Hugh
* Erik
* [[User:DWizzy]]

== No ==
* Walter (really people, had to gather energy to tinker with this lemma on the wiki)

== Maybe ==

* Martian
* Claudia
* Robin

Team:Content/LessonsLearned

2022-12-25T08:19:19Z

DWizzy: I volunteer as tribute!

= [[Team:Content|Team Content]] Lessons Learned =

== What went well ==

* Have a (bi) weekly meeting, consistency in that worked well
* Have meeting notes and action points
* Have a fridge in the speaker desk tent
* HDMI test at the speaker desk
* The box of AV adaptors and various cables
* Label printer (eventually!)
* Have a special sticker only for speakers
* Let visitors vote what they would likely attend
* Herald cue cards
* Stickynotes weekend

== What could be done better ==

* Allow for more redundancy in the team, because COVID is a bitch
* Ensure for more ticket types than just financial support tickets/more fluid UX
* Decision-making process on financial support of speakers. Make having that process an early deliverable, as early as the CfP. Use past requests as use cases for that process.
* Split the team in sub teams/tasks so that we don't need 10+ people in every meeting
* Treat SpeakerDesk more like HeraldDesk, so involvement pre-event is more limited
* Have Team:SpeakerDesk involved in the Team:Content meetings once a month / every 2 months, not necessarily every meeting. They are seperate teams.
* Have the same HDMI cable as used in the (workshop) tents for testing the speaker laptop
* Sync up better with Productiehuis beforehand
* Lightning talks coordination fell through almost completely
* Improve publlication process from PretalX to public schedule, the static export function proved to be a real pain in the behind.
* Notice that speakers did not arrive yet (have a better process for dealing with this)
* Be clearer about role and time expectations, and make sure everyone is willing to commit to those
** Fundraising, somehow this has been a responsibility of Team Content, this should at least have been communicated beforehand by Projectleiding and it would make sense for Projectleiding to "own" this, in collaboration with Team Content, and not the other way around.
* It looked like the expectations of what's part of content, what's part of speaker desk were not aligned always:
** Visa
** Assisting the speaker with financial support
** Stages/tents
** ...
* Understand requirements for Workshop tents better
* variety in team
* no veto's
* Do realise the event lives in CET/CEST, too often meetings were messy because of people expecting BST/EET.

== Suggestions for the next event ==

* Make it possible to only have the role reviewer
* Vet the speakers more thoroughly
* Smaller sub teams
** Also make sure there is a subteam for subsidies (Do we have a document store with the subsidy request paperwork for MCH we can copy pasta?)
* Make it possible that Angels can use a part of the content management system so you need less people of Team Content/Speaker desk during the event
* Check if people are available hours/a day before they need to be on stage. Especially if the people presenting the first shift of the day are registered. Pretalx didn't really help here.
* Start 1.5 year before the event
* Have someone at Projectleiding responsible for *all* stages, including workshop stages.
* Figure out process for accepting sooner, especially in light of (financial) support of speakers for which there will be constraints in time (plane tickets get more expensive, visa processes take time)
* The above allows for more active scouting of interesting speakers
* Make it clear that if you drop out without communication that you cannot challenge decisions made during your absence.
* Figure out financial support for speakers criteria, and process to apply those criteria, way in advance.
* Ensure sticky notes meeting is booked very very far in advance
* Agree handover/touchpoints between Content <> SpeakerDesk <> PH <> HeraldDesk
* Have the lightning talk coordinator in at least 2 of the team content meetings and a few of the team: Speakerdesk meetings
* Make sure there is a publication system well understood for the lightning desk coordinator
* Make sure either the lightning talk coordinator performs angeling or there is coordination with the herald desk

= Intend to join team Content for the next event =

== Yes ==

* Viola
* Hugh
* Erik
* [[User:DWizzy]]

== No ==
* Walter (really people, had to gather energy to tinker with this lemma on the wiki)

== Maybe ==

* Martian
* Claudia
* Robin

User:DWizzy

2022-11-07T20:31:01Z

DWizzy: har, har

{{UserInfo
|NickName=DWizzy
|Arrival=2022-07-20
|BuildupVehicle=No
|EMail=mch@dwizzy.nl
|Twitter=djoris
|DECT=5550
|Languages=nl, en
|HackerSpace=Capellespace
}}
Have some experience from previous camps:
* SHA: team lead info & press
* HAR: shift supervisor bar
* WTH: core orga, infodesk
* HAL: runner A/V-team

Will just enjoy camping in a quiet spot this time and help out where I can

Afterparty

2022-10-23T18:54:08Z

DWizzy: checked train schedule, night train to Utrecht stops at Elst!

{{Meeting
|Name=Afterparty
|StartDate=2022/11/19
|EndDate=2022/11/20
|Where=Industrieweg Oost 7b, 6662 NE Elst , The Netherlands
}}

[[image:mchafterparty.png|thumb|right|450px|The poster for the MCH2022 afterparty, as usually high quality design has prevailed]]

'''The MCH2022 afterparty is for everyone who made MCH2022 possible: all orga, angels, friends, secret angels, everyone who helped or want to help in the future and so on.
'''

== Location ==
The afterparty will take place in Elst, because it is close to the German border. It is in the GKS ICT Solutions building, at Industrieweg Oost 7b in Elst. Parking avaidable around the building. A train station is at 15 minutes walking distance.

== Travel ==

=== Car ===
Parking spots are available around the venue. There's basically infinite parking space, so if you can walk an infinite distance it will be fine.

=== Train / Public transport ===
The venue is located almost next to a [https://www.ns.nl/stationsinformatie/est/elst railway station in Elst]. Trains run up until [https://www.ns.nl/en/journeyplanner/#/?vertrek=Elst&vertrektype=treinstation&aankomst=Utrecht%20Centraal&aankomsttype=treinstation&type=vertrek&tijd=2022-11-19T23:30&firstMileModality=PUBLIC_TRANSPORT&lastMileModality=PUBLIC_TRANSPORT&entireTripModality=OWN_CAR&disabledTransportModalities=&context=arnu%7CfromStation%3D8400207%7CtoStation%3D8400621%7CplannedFromTime%3D2022-11-20T01:56:00%2B01:00%7CplannedArrivalTime%3D2022-11-20T02:42:00%2B01:00%7CexcludeHighSpeedTrains%3Dfalse%7CsearchForAccessibleTrip%3Dfalse%7CaddChangeTime%3D0&ritnummers=23406 01:56]. Since Elst is very close to Arhnem, there is always an option for a carpool to the city. They start running _really_ early in the morning as well... so [https://www.youtube.com/watch?v=hHkKJfcBXcw trains are your friends]. <br />
Note that due to scheduled maintenance the train schedule might be adjusted that weekend for those to/from Utrecht.

== Program ==
Not final at all

=== Saturday ===
* 11:00 Buildup and idling
* 12:00 Lunch
* 13:37 Doors open, preparty
* 16:00 Party
* 18:00 Food
* 00:00 Continuous party

=== Sunday ===
* 12:00 Brunch + Start Cleanup
* ??:?? Food stuffs is picked up

== Attending the afterparty ==

If you've been an angel, orga or feel connected to organizing the event, please come! By listing yourself here you'll let us know how many people to expect for food :). If you're wondering about the costs, there will be none.

Please choose '''the one option that suits you best''' in the table below:

{| class="wikitable sortable"
|-
! Name !! Vega !! Meat !! Fish !! MeatGlutenfree !! MeatHalal !! Comment
|-
{{AttendeeBBQ|Attendee=Stitch|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Rizoom|Meat=0|Vega=1|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Martian|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Coco|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Pwuts|Meat=0|Vega=0|Fish=1|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=cmpxchg|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Quux|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=sirgoofy|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=konmei|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Robin|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Knorrie|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Twi|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=phjl|Meat=0|Vega=1|Fish=1|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Firewall|Meat=0|Vega=0|Fish=1|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Hoxolotl|Meat=0|Vega=0|Fish=1|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Hp197|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Winko|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Hobbybob|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Xesxen|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Eightdot|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=f0x|Meat=0|Vega=1|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Xenomatrix|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Netsmurf|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=SynQ|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=I have there now already sin in. First comment!}}
{{AttendeeBBQ|Attendee=hvwees|Meat=0|Vega=0|Fish=0|MeatGlutenfree=1|MeatHalal=0|Comment=No dairy products}}
{{AttendeeBBQ|Attendee=denz|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=}}
{{AttendeeBBQ|Attendee=wilcoe|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=}}
{{AttendeeBBQ|Attendee=Pikachu|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=}}
{{AttendeeBBQ|Attendee=Chrisha|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=}}
{{AttendeeBBQ|Attendee=Procyon|Meat=0|Vega=0|Fish=0|MeatGlutenfree=1|MeatHalal=0|Comment=wondering if for brunch/breakfast dietary options will also be taken into account}}
{{AttendeeBBQ|Attendee=Crablab|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Halcyon|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=}}
{{AttendeeBBQ|Attendee=redlizard|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=Yes}}
{{AttendeeBBQ|Attendee=Renze|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=¯\_(ツ)_/¯}}
{{AttendeeBBQ|Attendee=upstar|Meat=0|Vega=1|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Boekenwuurm|Meat=0|Vega=1|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=Paars}}
{{AttendeeBBQ|Attendee=DWizzy|Meat=0|Vega=1|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=drop table}}
{{AttendeeBBQ|Attendee=IcyPalm|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Peterp|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}

|-
! Subtotal
! {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountVega|limit=999|format=sum}}
! {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountMeat|limit=999|format=sum}}
! {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountFish|limit=999|format=sum}}
! {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountMeatGlutenfree|limit=999|format=sum}}
! {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountMeatHalal|limit=999|format=sum}}
!
|-
! Total
! colspan=5 | {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountVega|?AttendeeCountMeat|?AttendeeCountFish|?AttendeeCountMeatGlutenfree|?AttendeeCountMeatHalal|?AttendeeCountMeatKosher|limit=999|format=sum}}
!
|}

== COVID ==
Please do a rapid antigen test (dutch: Self test) before attending. Winter is coming, and we have seen how that worked the last few years. We will monitor the situation to see if more is needed closer to November 19th.

== Drinks? ==
I still have some beer ([https://www.bocq.be/en/#biere-blanche-de-namur Blanche de Namur]) and 0.0 Beer ([https://www.budels.nl/non-alcoholic-beers Budels Hopped 0.0 (bottom of page)]). I could be convinced to bring some. [[User:Denz|denz]] ([[User talk:Denz|talk]]) 17:00, 27 September 2022 (CEST)

== Carpool? ==
=== Looking for a ride ===

{| class="wikitable"
|-
! Who !! From where (to party) !! To where (from party) !! Leaving when?
|-
| [[User:Pwuts]] || Delft || Delft or Leiderdorp || Not before the party ends :)
|-
| [[User:Hoxolotl]] || Enschede || Enschede or Trainstations Enschede-Arnhem || Depending on transport
|-
| [[User:Renze]] || Enschede || Enschede ||
|-
| [[User:Procyon]] || Ermelo or trainstation Utrecht Central || Ermelo or trainstation Utrecht Central || Depending on transport
|-
|}

=== Offering a ride ===
{| class="wikitable"
|-
! Who !! From where (to party) !! Arriving when?!! To where (from party) !! Leaving when?
|-
| [[User:Hp197|Hp197]] || (provincie) Utrecht || ||(provincie) Utrecht || last
|-
| [[User:Netsmurf|Netsmurf]] || Alkmaar/Amsterdam || first ||Alkmaar/Amsterdam || last
|-
| [[User:IcyPalm|IcyPalm]] || Groningen || Planning around 11:00 || Groningen || TBD
|-
|}

Afterparty

2022-10-23T18:49:22Z

DWizzy: train maintenance...

{{Meeting
|Name=Afterparty
|StartDate=2022/11/19
|EndDate=2022/11/20
|Where=Industrieweg Oost 7b, 6662 NE Elst , The Netherlands
}}

[[image:mchafterparty.png|thumb|right|450px|The poster for the MCH2022 afterparty, as usually high quality design has prevailed]]

'''The MCH2022 afterparty is for everyone who made MCH2022 possible: all orga, angels, friends, secret angels, everyone who helped or want to help in the future and so on.
'''

== Location ==
The afterparty will take place in Elst, because it is close to the German border. It is in the GKS ICT Solutions building, at Industrieweg Oost 7b in Elst. Parking avaidable around the building. A train station is at 15 minutes walking distance.

== Travel ==

=== Car ===
Parking spots are available around the venue. There's basically infinite parking space, so if you can walk an infinite distance it will be fine.

=== Train / Public transport ===
The venue is located almost next to a railway station in Elst. Trains run up until midnight. Since Elst is very close to Arhnem, there is always an option for a carpool to the city. They start running _really_ early in the morning as well... so [https://www.youtube.com/watch?v=hHkKJfcBXcw trains are your friends]. <br />
Note that due to scheduled maintenance the train schedule might be adjusted that weekend for those to/from Utrecht.

== Program ==
Not final at all

=== Saturday ===
* 11:00 Buildup and idling
* 12:00 Lunch
* 13:37 Doors open, preparty
* 16:00 Party
* 18:00 Food
* 00:00 Continuous party

=== Sunday ===
* 12:00 Brunch + Start Cleanup
* ??:?? Food stuffs is picked up

== Attending the afterparty ==

If you've been an angel, orga or feel connected to organizing the event, please come! By listing yourself here you'll let us know how many people to expect for food :). If you're wondering about the costs, there will be none.

Please choose '''the one option that suits you best''' in the table below:

{| class="wikitable sortable"
|-
! Name !! Vega !! Meat !! Fish !! MeatGlutenfree !! MeatHalal !! Comment
|-
{{AttendeeBBQ|Attendee=Stitch|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Rizoom|Meat=0|Vega=1|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Martian|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Coco|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Pwuts|Meat=0|Vega=0|Fish=1|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=cmpxchg|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Quux|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=sirgoofy|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=konmei|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Robin|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Knorrie|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Twi|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=phjl|Meat=0|Vega=1|Fish=1|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Firewall|Meat=0|Vega=0|Fish=1|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Hoxolotl|Meat=0|Vega=0|Fish=1|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Hp197|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Winko|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Hobbybob|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Xesxen|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Eightdot|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=f0x|Meat=0|Vega=1|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Xenomatrix|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Netsmurf|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=SynQ|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=I have there now already sin in. First comment!}}
{{AttendeeBBQ|Attendee=hvwees|Meat=0|Vega=0|Fish=0|MeatGlutenfree=1|MeatHalal=0|Comment=No dairy products}}
{{AttendeeBBQ|Attendee=denz|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=}}
{{AttendeeBBQ|Attendee=wilcoe|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=}}
{{AttendeeBBQ|Attendee=Pikachu|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=}}
{{AttendeeBBQ|Attendee=Chrisha|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=}}
{{AttendeeBBQ|Attendee=Procyon|Meat=0|Vega=0|Fish=0|MeatGlutenfree=1|MeatHalal=0|Comment=wondering if for brunch/breakfast dietary options will also be taken into account}}
{{AttendeeBBQ|Attendee=Crablab|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Halcyon|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=}}
{{AttendeeBBQ|Attendee=redlizard|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=Yes}}
{{AttendeeBBQ|Attendee=Renze|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=¯\_(ツ)_/¯}}
{{AttendeeBBQ|Attendee=upstar|Meat=0|Vega=1|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Boekenwuurm|Meat=0|Vega=1|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=Paars}}
{{AttendeeBBQ|Attendee=DWizzy|Meat=0|Vega=1|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=drop table}}
{{AttendeeBBQ|Attendee=IcyPalm|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Peterp|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}

|-
! Subtotal
! {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountVega|limit=999|format=sum}}
! {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountMeat|limit=999|format=sum}}
! {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountFish|limit=999|format=sum}}
! {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountMeatGlutenfree|limit=999|format=sum}}
! {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountMeatHalal|limit=999|format=sum}}
!
|-
! Total
! colspan=5 | {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountVega|?AttendeeCountMeat|?AttendeeCountFish|?AttendeeCountMeatGlutenfree|?AttendeeCountMeatHalal|?AttendeeCountMeatKosher|limit=999|format=sum}}
!
|}

== COVID ==
Please do a rapid antigen test (dutch: Self test) before attending. Winter is coming, and we have seen how that worked the last few years. We will monitor the situation to see if more is needed closer to November 19th.

== Drinks? ==
I still have some beer ([https://www.bocq.be/en/#biere-blanche-de-namur Blanche de Namur]) and 0.0 Beer ([https://www.budels.nl/non-alcoholic-beers Budels Hopped 0.0 (bottom of page)]). I could be convinced to bring some. [[User:Denz|denz]] ([[User talk:Denz|talk]]) 17:00, 27 September 2022 (CEST)

== Carpool? ==
=== Looking for a ride ===

{| class="wikitable"
|-
! Who !! From where (to party) !! To where (from party) !! Leaving when?
|-
| [[User:Pwuts]] || Delft || Delft or Leiderdorp || Not before the party ends :)
|-
| [[User:Hoxolotl]] || Enschede || Enschede or Trainstations Enschede-Arnhem || Depending on transport
|-
| [[User:Renze]] || Enschede || Enschede ||
|-
| [[User:Procyon]] || Ermelo or trainstation Utrecht Central || Ermelo or trainstation Utrecht Central || Depending on transport
|-
|}

=== Offering a ride ===
{| class="wikitable"
|-
! Who !! From where (to party) !! Arriving when?!! To where (from party) !! Leaving when?
|-
| [[User:Hp197|Hp197]] || (provincie) Utrecht || ||(provincie) Utrecht || last
|-
| [[User:Netsmurf|Netsmurf]] || Alkmaar/Amsterdam || first ||Alkmaar/Amsterdam || last
|-
| [[User:IcyPalm|IcyPalm]] || Groningen || Planning around 11:00 || Groningen || TBD
|-
|}

Afterparty

2022-10-23T18:38:01Z

DWizzy: /* Attending the afterparty */

{{Meeting
|Name=Afterparty
|StartDate=2022/11/19
|EndDate=2022/11/20
|Where=Industrieweg Oost 7b, 6662 NE Elst , The Netherlands
}}

[[image:mchafterparty.png|thumb|right|450px|The poster for the MCH2022 afterparty, as usually high quality design has prevailed]]

'''The MCH2022 afterparty is for everyone who made MCH2022 possible: all orga, angels, friends, secret angels, suppliers, everyone who helped or want to help in the future and so on.
'''

== Location ==
The afterparty will take place in Elst, because it is close to the German border. It is in the GKS ICT Solutions building, at Industrieweg Oost 7b in Elst. Parking avaidable around the building. A train station is at 15 minutes walking distance.

== Travel ==

=== Car ===
Parking spots are available around the venue. There's basically infinite parking space, so if you can walk an infinite distance it will be fine.

=== Train / Public transport ===
The venue is located almost next to a railway station in Elst. Trains run up until midnight. Since Elst is very close to Arhnem, there is always an option for a carpool to the city. They start running _really_ early in the morning as well... so [https://www.youtube.com/watch?v=hHkKJfcBXcw trains are your friends].

== Program ==
Not final at all

=== Saturday ===
* 11:00 Buildup and idling
* 12:00 Lunch
* 13:37 Doors open, preparty
* 16:00 Party
* 18:00 Food
* 00:00 Continuous party

=== Sunday ===
* 12:00 Brunch + Start Cleanup
* ??:?? Food stuffs is picked up

== Attending the afterparty ==

If you've been an angel, orga or feel connected to organizing the event, please come! By listing yourself here you'll let us know how many people to expect for food :). If you're wondering about the costs, there will be none.

Please choose '''the one option that suits you best''' in the table below:

{| class="wikitable sortable"
|-
! Name !! Vega !! Meat !! Fish !! MeatGlutenfree !! MeatHalal !! Comment
|-
{{AttendeeBBQ|Attendee=Stitch|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Rizoom|Meat=0|Vega=1|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Martian|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Coco|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Pwuts|Meat=0|Vega=0|Fish=1|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=cmpxchg|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Quux|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=sirgoofy|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=konmei|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Robin|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Knorrie|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Twi|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=phjl|Meat=0|Vega=1|Fish=1|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Firewall|Meat=0|Vega=0|Fish=1|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Hoxolotl|Meat=0|Vega=0|Fish=1|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Hp197|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Winko|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Hobbybob|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Xesxen|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Eightdot|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=f0x|Meat=0|Vega=1|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Xenomatrix|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Netsmurf|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=SynQ|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=I have there now already sin in. First comment!}}
{{AttendeeBBQ|Attendee=hvwees|Meat=0|Vega=0|Fish=0|MeatGlutenfree=1|MeatHalal=0|Comment=No dairy products}}
{{AttendeeBBQ|Attendee=denz|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=}}
{{AttendeeBBQ|Attendee=wilcoe|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=}}
{{AttendeeBBQ|Attendee=Pikachu|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=}}
{{AttendeeBBQ|Attendee=Chrisha|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=}}
{{AttendeeBBQ|Attendee=Procyon|Meat=0|Vega=0|Fish=0|MeatGlutenfree=1|MeatHalal=0|Comment=wondering if for brunch/breakfast dietary options will also be taken into account}}
{{AttendeeBBQ|Attendee=Crablab|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Halcyon|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=}}
{{AttendeeBBQ|Attendee=redlizard|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=Yes}}
{{AttendeeBBQ|Attendee=Renze|Meat=1|Vega=0|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=¯\_(ツ)_/¯}}
{{AttendeeBBQ|Attendee=upstar|Meat=0|Vega=1|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=No}}
{{AttendeeBBQ|Attendee=Boekenwuurm|Meat=0|Vega=1|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=Paars}}
{{AttendeeBBQ|Attendee=DWizzy|Meat=0|Vega=1|Fish=0|MeatGlutenfree=0|MeatHalal=0|Comment=drop table}}
|-
! Subtotal
! {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountVega|limit=999|format=sum}}
! {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountMeat|limit=999|format=sum}}
! {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountFish|limit=999|format=sum}}
! {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountMeatGlutenfree|limit=999|format=sum}}
! {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountMeatHalal|limit=999|format=sum}}
!
|-
! Total
! colspan=5 | {{#ask:[[-Has subobject::{{FULLPAGENAME}}]]|?AttendeeCountVega|?AttendeeCountMeat|?AttendeeCountFish|?AttendeeCountMeatGlutenfree|?AttendeeCountMeatHalal|?AttendeeCountMeatKosher|limit=999|format=sum}}
!
|}

== COVID ==
Please do a rapid antigen test (dutch: Self test) before attending. Winter is coming, and we have seen how that worked the last few years. We will monitor the situation to see if more is needed closer to November 19th.

== Drinks? ==
I still have some beer ([https://www.bocq.be/en/#biere-blanche-de-namur Blanche de Namur]) and 0.0 Beer ([https://www.budels.nl/non-alcoholic-beers Budels Hopped 0.0 (bottom of page)]). I could be convinced to bring some. [[User:Denz|denz]] ([[User talk:Denz|talk]]) 17:00, 27 September 2022 (CEST)

== Carpool? ==
=== Looking for a ride ===

{| class="wikitable"
|-
! Who !! From where (to party) !! To where (from party) !! Leaving when?
|-
| [[User:Pwuts]] || Delft || Delft or Leiderdorp || Not before the party ends :)
|-
| [[User:Hoxolotl]] || Enschede || Enschede or Trainstations Enschede-Arnhem || Depending on transport
|-
| [[User:Renze]] || Enschede || Enschede ||
|-
| [[User:Procyon]] || Ermelo or trainstation Utrecht Central || Ermelo or trainstation Utrecht Central || Depending on transport
|-
|}

=== Offering a ride ===
{| class="wikitable"
|-
! Who !! From where (to party) !! Arriving when?!! To where (from party) !! Leaving when?
|-
| [[User:Hp197|Hp197]] || (provincie) Utrecht || ||(provincie) Utrecht || last
|-
| [[User:Netsmurf|Netsmurf]] || Alkmaar/Amsterdam || first ||Alkmaar/Amsterdam || last
|-
|}

Team:Content

2022-07-24T18:10:04Z

DWizzy: added myself because User:Crablab invited me

{{Team
|Lead=User:Martian, User:Robin, User:Claudia, User:Walter
|Description=Curates the programme, from managing the CfP to setting up the schedule.

This team will have separate subteams for the speaker desk and the heralds. During the event it should ideally be based at the speaker lounge.

It will not do anything infodesk, media lounge, media desk related.
|Exclusive team=No
|Contact=content@mch2022.org
|team_is_essential_to_event=Substance
|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:Stitch
|Backup_Projectleiding=User:Rizoom
}}
==Team Members==
*

{{TeamMemberEntry|User:Claudia}}
{{TeamMemberEntry|User:ErikTews}}
{{TeamMemberEntry|User:Crablab}}
{{TeamMemberEntry|User:Jos}}
{{TeamMemberEntry|User:Kirils}}
{{TeamMemberEntry|User:Martian}}
{{TeamMemberEntry|User:Nicolas}}
{{TeamMemberEntry|User:Robin}}
{{TeamMemberEntry|User:Teirdes}}
{{TeamMemberEntry|User:Viola}}
{{TeamMemberEntry|User:Wvholst}}
{{TeamMemberEntry|User:DWizzy}}
*
*
*
*
*
*
*
*
*
*

== Vacancies ==

None.

== Current deliverables: ==

* [[Team:Content/VillageContentInProgramme|Village content in the MCH2022 programme]]
* [[Speaker FAQ]]
* https://cfp.mch2022.org
* [[Team:Content/HowToInvite|How to invite a speaker]]
* [[Review_Guidelines|Review Guidelines]]
* A plan how to [[Team:Content-Travel-Budget-Management|manage the travel budget]]
* Settle on motto
* Consider integration Pretalx/ticketing system (which ticketing system?)
* Document [[Team:Content#Outline|outlines]] of processes
** What to do in event of emergency (e.g. sudden society lock-down, etc)
** How to organize with ancillary teams (Music, Academic)

== Previous deliverables: ==

* [[Team:Content-Tool-Evaluation|Evaluate PretalX]]

== Meetings ==

[[2022-07-15-Content-meeting|2022-07-15]] | [[2022-07-15-Content-meeting-minutes|minutes]]

[[2022-07-03-Content-meeting|2022-07-03]] | [[2022-07-03-Content-meeting-minutes|minutes]]

[[2022-06-16-Content-meeting|2022-06-16]] | [[2022-06-16-Content-meeting-minutes|minutes]]

[[2022-06-10-Content-meeting|2022-06-10]] | [[2022-06-10-Content-meeting-minutes|minutes]]

[[2022-06-04-Content-meeting|2022-06-04]] | [[2022-06-04-Content-meeting-minutes|minutes]]

[[2022-05-29-Content-meeting|2022-05-29]] | [[2022-05-29-Content-meeting-minutes|minutes]]

[[2022-05-21-Content-meeting|2022-05-21]] | [[2022-05-21-Content-meeting-minutes|minutes]]

[[2022-05-07-Content-meeting|2022-05-07]] | [[2022-05-07-Content-meeting-minutes|minutes]]

[[2022-05-01-Content-meeting|2022-05-01]] | [[2022-05-01-Content-meeting-minutes|minutes]]

[[2022-04-24-Content-meeting|2022-04-24]] | [[2022-04-24-Content-meeting-minutes|minutes]]

[[2022-04-23-Content-meeting|2022-04-23]] | [[2022-04-23-Content-meeting-minutes|minutes]]

[[2022-04-10-Content-meeting|2022-04-10]] | [[2022-04-10-Content-meeting-minutes|minutes]]

[[2022-04-02-Content-meeting|2022-04-02]] | [[2022-04-02-Content-meeting-minutes|minutes]]

[[2022-03-19-Content-meeting|2022-03-19]] | [[2022-03-19-Content-meeting-minutes|minutes]]

[[2022-03-05-Content-meeting|2022-03-05]] | [[2022-03-05-Content-meeting-minutes|minutes]]

[[2022-02-19-Content-meeting|2022-02-19]] | [[2022-02-19-Content-meeting-minutes|minutes]]

[[2022-02-05-Content-meeting|2022-02-05]] | [[2022-02-05-Content-meeting-minutes|minutes]]

[[2022-01-22-Content-meeting|2022-01-22]] | [[2022-01-22-Content-meeting-minutes|minutes]]

[[2022-01-09-Content-meeting|2022-01-09]] | [[2022-01-09-Content-meeting-minutes|minutes]]

[[2021-12-18-Content-meeting|2021-12-18]] | [[2021-12-18-Content-meeting-minutes|minutes]]

[[2021-12-04-Content-meeting|2021-12-04]] | [[2021-12-04-Content-meeting-minutes|minutes]]

[[2021-11-20-Content-meeting|2021-11-20]] | [[2021-11-20-Content-meeting-minutes|minutes]]

[[2021-11-06-Content-meeting|2021-11-06]] | [[2021-11-06-Content-meeting-minutes|minutes]]

[[2021-10-23-Content-meeting|2021-10-23]] | [[2021-10-23-Content-meeting-minutes|minutes]]

[[2021-10-09-Content-meeting|2021-10-09]] | [[2021-10-09-Content-meeting-minutes|minutes]]

[[2021-09-04-Content-meeting|2021-09-04]] | [[2021-09-04-Content-meeting-minutes|minutes]]

[[2021-02-27-Content-meeting|2021-02-27]] | [[2021-02-27-Content-meeting-minutes|minutes]]

[[2021-02-13-Content-meeting|2021-02-13]] | [[2021-02-13-Content-meeting-minutes|minutes]]

[[2021-01-23-Content-meeting|2021-01-23]] | [[2021-01-23-Content-meeting-minutes|minutes]]

[[2021-01-09-Content-meeting|2021-01-09]] | [[2021-01-09-Content-meeting-minutes|minutes]]

[[2020-12-12-Content-meeting|2020-12-12]] | [[2020-12-12-Content-meeting-minutes|minutes]]

[[2020-11-28-Content-meeting|2020-11-28]] | [[2020-11-28-Content-meeting-minutes|minutes]]

[[2020-11-14-Content-meeting|2020-11-14]] | [[2020-11-14-Content-meeting-minutes|minutes]]

[[2020-10-31-Content-meeting|2020-10-31]] | [[2020-10-31-Content-meeting-minutes|minutes]]

[[2020-10-10-Content-meeting|2020-10-10]] | [[2020-10-10-Content-meeting-minutes|minutes]]

[[2020-09-26-Content-meeting|2020-09-26]] | [[2020-09-26-Content-meeting-minutes|minutes]]

[[2020-09-12-Content-meeting|2020-09-12]] | [[2020-09-12-Content-meeting-minutes|minutes]]

[[2020-08-29-Content-meeting|2020-08-29]] | [[2020-08-29-Content-meeting-minutes|minutes]]

[[2020-07-25-Content-meeting|2020-07-25]] | [[2020-07-25-Content-meeting-minutes|minutes]]

[[2020-07-04-Content-meeting|2020-07-04]] | [[2020-07-04-Content-meeting-minutes|minutes]]

[[2020-06-20-Content-meeting|2020-06-20]] | [[2020-06-20-Content-meeting-minutes|minutes]]

[[2020-06-06-Content-meeting|2020-06-06]] | [[2020-06-06-Content-meeting-minutes|minutes]]

[[2020-05-16-Content-meeting|2020-05-16]] | [[2020-05-16-Content-meeting-minutes|minutes]]

[[2020-05-02-Content-meeting|2020-05-02]] | [[2020-05-02-Content-meeting-minutes|minutes]]

[[2020-04-11-Content-meeting|2020-04-11]] | [[2020-04-11-Content-meeting-minutes|minutes]]

[[2020-03-28-Content-meeting|2020-03-28]] | [[2020-03-28-Content-meeting-minutes|minutes]]

==Tasks==

From [[Roles]]:

'''Content'''

* Write and publish a call for papers
* Evaluate submissions for presentations and workshops, inform speakers about whether their submission is accepted or not
* Schedule presentations and workshops
* Publish the program online
* Invite specific known interesting speakers
* Determine, with PL, the policy for reimbursement of expenses
* Integrate content organized by villages

With special assistance to

'''Heralds'''
* Train the Herald volunteers
* Moderate Q&A sessions at the end of talks (if requested by speaker)
* Monitor speakers and take care of needs that arise during presentations
* Watch the room and making sure the event/talk runs smoothly
* Minimize delays in the schedule (ensure speakers start and end on time)
'''Speaker desk'''
* Have a physical presence at the event where speakers can go to
* Confirm that the speakers are present, contact them and initiate rescheduling if not
* Inform speakers about the license for the stream
* Try to deal with last-minute requests/needs from speakers

The team curates the programme, and also somewhat coordinate* things outside of the lecture-halls; like workshops, village activities, etcetera. With the help of villages and other groups, we will attempt to provide a more cohesive visitor experience, content-wise; with some overlap between the stuff going on at the campgrounds and the stuff in the lecture halls*.
*<small>Coordination in this context doesn't mean deciding what is good content and what is not. Nor does it involve a high committee telling other people what to do. It rather means to entice villagers and other volunteers to join the bigger picture, and try to (partially) merge their content with the program, or prepare their own content in an accessible way. This may, of course, involve us pushing, harassing and stalking you from time to time. It also is likely to involve your stage place to give stage space to the main programme.</small>

We are also responsible for helping out with the Speaker Desk and Heralds, although these will have separate (partially overlapping) teams.

== Outline ==

''Every potential speaker, including big names, have to have a proposal in FRAB or any other Programming Management System software. That doesn't mean that every speaker has to put it in themselves, only that there must be one (and with the consent of the speaker(s) involved, obviously)'' For instance, at OHM, the rather famous Dutch writer Arnon Grunberg had his literary agent put in a proposal for a storytelling workshop. Which we gratefully accepted after finally convincing ourselves that we weren't being trolled. Which we weren't.

Team:Content members "adopt" several high-profile speakers and had proposals put in Frab on their behalf in former camps.

If you feel a speaker *should* be there and none in Team:Content wants to "adopt" that speaker, then you must do it yourself or convince someone else to perform that task. If neither you nor anyone else cares enough to make a simple proposal in Frab happen, then it probably is not such a terrific idea, to begin with.

===== What does the approval process look like? =====

Since writing this, Team:Content has agreed on [[Review Guidelines]] which you can read if you want a much more formal description on how we rate submissions. Enjoy!

# Every proposal gets voted on in Frab by every member of Team:Content. Proposals that get high votes, clearly have the nearly unanimous "wow-factor" and are the ones that get confirmed first and are probably a good fit for the biggest stage. Since this voting process is more or less anonymous (well, not really, but for most intents and purposes it is), it also prevents the programme from becoming someone's line-up of favourite speakers.
# At this point we will try to work with Team:Communications to start communicating publicly about these cherries on the cake. This will be on our Blog, set up for this propose. Because those are likely to attract ticket sales.
# The rest of the proposals get discussed in several meetings. We aim for quality over quantity and rather have a sparse programme with lots of long breaks but high-quality talks than a crammed programme. It is an open-air hacker festival after all and there should be plenty of other things happening in villages to have a good time. Either way, the discussions about edge cases will be settled in person and will not necessarily be by consensus but just by majority voting.
# At OHM and SHA we asked villages to be able to use their stages (not very successfully). Unless a village specifically wants to hand over stage slots to the official SHA programming, we want to encourage villages to develop their own village programmes and want to give their curators access to Frab for that purpose.
# For every proposal that gets accepted, a member of Team:Content now *must* adopt that proposal, chase the speaker for confirmation and be the PoC for that speaker. This may include activities for visa-processing, travel and lodging arrangements etc. for those speakers that simply cannot be expected to arrange that themselves.
# Covering traveling and lodging expenses is ultimately a bit of an arbitrary decision. It is more a less a function of how much we want that speaker and what can be expected from a speaker her- or himself. If someone is a starving ethical hacker from, say, Moldova or Peru, we're much more likely to consider that person worth supporting than in the case of an employee of a Silicon Valley behemoth. In some cases there will have been preliminary discussions about that already along the lines of "if your proposal gets accepted and it is as good as you have shown elsewhere so you get to be the opening/closing speaker of one of the days, we may be able to contribute to your traveling and lodging arrangements". Thanks to several people in Team:Finance and Team:Projektleiding we have secured a modest budget through a government subsidy that is earmarked for this purpose. If anyone else wants to chip in for this purpose, please have them talk to Team:Finance first, but in principle that is welcome.
# Once we have done all the confirmations/rejections/passing on to villages, there will be a few weekends of planning sessions. With lots of post-its on the wall of an undisclosed location. Which should result in a programme. And therefore a pretext for all of us to have an awesome time.

== Speaker Desk: ==

See [[Team:Speaker_Desk]]

* [[User:Kirils]]
* [[User:Crablab]]

== Heralds ==
* Katzazi

== Question log ==
Question log to look up questions answered (so you don't have to search all meeting minutes. only public information here).

- Accessibilty for speakers (e.g. wheelchair ramps): see [[Team:Accessibility]]

== Lessons learned from SHA2017 ==

https://orga.sha2017.org/index.php?title=Team:Content

https://orga.sha2017.org/index.php?title=Team:Content/Heralds

https://orga.sha2017.org/index.php?title=Team:Content/Speakerdesk

== Quick guide to creating village tracks in PretalX ==

* Create a new track for the relevant village:
- This can be done under the CfP menu, tracks option

* Create a new room
- This can be done under the Schedule menu

User:DWizzy

2022-07-20T08:44:55Z

DWizzy:

{{UserInfo
|NickName=DWizzy
|Arrival=2022-07-20
|BuildupVehicle=No
|EMail=mch@dwizzy.nl
|Twitter=djoris
|DECT=5550
|Languages=nl, en
}}
Have some experience from previous camps:
* SHA: team lead info & press
* HAR: shift supervisor bar
* WTH: core orga, infodesk
* HAL: runner A/V-team

Will just enjoy camping in a quiet spot this time and help out where I can

File:User-DWizzy.jpg

2022-07-20T08:38:46Z

DWizzy: Photo of DWizzy by [https://www.flickr.com/photos/dvanzuijlekom/ Dennis van Zuijlekom]. License: [https://creativecommons.org/licenses/by-sa/2.0/ CC BY-SA 2.0].

== Summary ==
Photo of DWizzy by [https://www.flickr.com/photos/dvanzuijlekom/ Dennis van Zuijlekom]. License: [https://creativecommons.org/licenses/by-sa/2.0/ CC BY-SA 2.0].