On Thu, Jan 14, 2016 at 4:10 PM, Paul W. Frields <stickster(a)gmail.com>
* Initial names for tracks/categories for paper submission. We may
not want to make final decisions about tracks until after there is a
complete set of submissions. Do we want to have a set of defaults,
like Technical, Team Status/Planning, and Outreach? (suggestions
That is probably the simplest option. Last year we had:
* What data do we need to capture for each registrant? Here's what we
captured for each person (identified by email address, which you can
consider a unique ID):
Email address is critical! We have not always had this asking for FAS
names, even when FAS name was required, as it turned out that many, many of
the email addresses associated with the FAS accounts bounced.
For anyone whose plane ticket is being booked for them, there is a chunk of
other information we need that is very personal, including passport number.
We can make this a separate process, but it's worth noting.
Flight funding requested? y/n
Hotel funding requested? y/n
You may also want to find a way to track whether funding has been granted.
It has been the case that people assumed that simply because they checked
the box here that they would be paid for.
I don't know if there's a better way to ask for dietary requirements, but
one year I sent out prospective menus, and nearly all the people who had
picked vegan chose the dish full of cheese.
If there is likely to be a bus from Brno, you might ask if people were
interested in that possibility so they don't have to guess later.
* Who wants to be on list of administrators (basically absolute power)
for the app? Patrick and I have volunteered. I'd like 1-2
people who can twiddle things to avoid blocking on either of us.
I am fine with being on that list.