Keeping track of all the same changes for next time for changes to registration
Have a mandatory short field where people indicate what projects they are working on, what teams they are working with, what their core subject area is. This will help quite a bit with both understanding who is where and matching up questions and answers.
Collect information about what topics mentors are willing to mentor. Not just that they are willing to mentor.
Does "event" here more or less mean "hackathon", or is this somehow broader?
If "Hackathon": Anything collected in this task should probably be added to https://www.mediawiki.org/wiki/Hackathons/Handbook/Manage_participants#Registration_form_templates , in addition to other proposed registration form changes covered in T165200 and T169850#3826631.
In 2018 we forgot to add the question where we state we are going to post people's username on the participants list unless they don't agree to it. its important!
Updated questions from this year which are in a google doc should be incorporated into the 2019 registration
Lessons for Prague Hackathon
- We need to ask for age (or at least over / under 18) in the registration form
- We need to have basic requirements for level of activity within out projects for scholarship application
- People who are activity community members who are rejected should get a different declined email than random non-active non-community members.