Hi team, I was talking to puiterwijk about the registration/CFP app
and we noted a couple pieces of data we need basically right now:
* 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
welcome)
* 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):
Full Name
Location
Invitation letter needed? y/n
Flight funding requested? y/n
Hotel funding requested? y/n
Vegetarian/Vegan
Volunteer? y/n
Bringing family? y/n
T-shirt size
Looking for roomshare? y/n
Hotel booked? y/n
Blog URL
Twitter handle
Comments
Extra badge line
* Who wants to be on list of administrators (basically absolute power)
for the app? Patrick and I have volunteered. I'd like 1-2 more
people who can twiddle things to avoid blocking on either of us.
Also, please note that the current template styling for the app is
quite bare. I'm going to seek help from the Design and Websites team
to help make better Handlebars templates. The templating system is
quite simple to learn and you can see the affected files here in the
source:
<
https://github.com/puiterwijk/regcfp/tree/master/views>
(except for partials/ and desk/ which is being reworked)
The styling won't prevent early deployment or use, and we can make
things prettier as we go.
We already have a much more attractive website available, as some of
you've seen earlier, where we can publish the standard logistics info
once it's available.
--
Paul W. Frields
http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - -
http://pfrields.fedorapeople.org/
The open source story continues to grow:
http://opensource.com