General note: I notice that lots of the feedback here is quite specific to EAGxBerkeley and doesn’t seem to generalise across other EAG and EAGx events. There were a few things that were unusual about EAGxBerkeley:
We were trialling out a new application form, so previous responses didn’t load onto the new form. This also meant applications launched later than we wanted to.
As you know, we had to quite drastically cut down the catering budget from the initial proposal. This created an unusually hard cap on numbers since we didn’t build in much extra room.
I’ll post lots of separate comments so that it’s easier to respond to them individually.
We were trialling out a new application form, so previous responses didn’t load onto the new form. This also meant applications launched later than we wanted to.
I (personally + 1-2 people I know) did find bugs on previous application forms as well fwiw.
Okay, adding some more detail.
General note: I notice that lots of the feedback here is quite specific to EAGxBerkeley and doesn’t seem to generalise across other EAG and EAGx events. There were a few things that were unusual about EAGxBerkeley:
We were trialling out a new application form, so previous responses didn’t load onto the new form. This also meant applications launched later than we wanted to.
As you know, we had to quite drastically cut down the catering budget from the initial proposal. This created an unusually hard cap on numbers since we didn’t build in much extra room.
I’ll post lots of separate comments so that it’s easier to respond to them individually.
I (personally + 1-2 people I know) did find bugs on previous application forms as well fwiw.
Noted, and I’m not surprised. We’re hoping the new system (hosted by Salesforce) will be less buggy *crosses fingers*