Re: [Debconf-team] registration metadata
On 10.04.2014 21:58, Steve Langasek wrote:
>> Nickname
>> *(seems like this should be explicitly "irc nick" or split?)
>
> Historically, we print the nick on the badges, to help with mapping
> real-world to virtual identities. It's often an IRC nick, but could be
> whatever nick someone wants printed on their badges.
It is mostly the debian username / mail username.
>> Full name (for e.g. badges)
>
> Should default to the oauth2 data, but should be overridable to
account for
> non-obvious name order preferences etc.
>
>> Title
IMHO this should be removed
>> Sex
>> unspecified
>> male
>> female
>
> Since this information will be gathered by the PSU website for any
roommate
> assignment questions, this would be for statistical purposes only
this year
> - but it's worth having for that purpose alone.
We need for statistics (diversity). Maybe we could add a comment on the
question.
>
>> Image
>> file upload
>
> FWIW I'm happy to take care of this piece, I've done image upload
handling
> in django before so it should be no trouble
>
>> Make Image public
>> checkbox
>
> I am unsure why we would ever allow people to upload pictures to our
server
> if they're not going to be public. Should we drop this option, and just
> tell people not to upload pictures they don't want public?
Could be usefull for orga team / registration team, looking for a
person, but AFAIK we never used it. So we can remove.
>> Reconfirm Attendance
>> checkbox
>
> This is a field that becomes active only later; needs to be part of the
> model but hidden initially.
yes, this should be hidden.
>> Contact me regarding disability accommodation
>> checkbox
This option doesn't really work. We have mostly false positives, and we
need to try several time to contact people. So I would remove it: better
a comment: "please contact us if you have special needs".
> The only options we should need this time are:
>
> I will arrange my own accomodation
> I request sponsored accommodation (basic registration only)
>
> "Arrange my own accomodation" may include "I click the link to PSU's
website
> and will pay for a room on campus myself". And since all rooms are
doubles,
> I don't think it's useful to offer upgrades to singles for sponsored
> attendees.
I'm not sure. I would have two option for non sponsored accommodation
(extern and at PSU): the people at PSU should be handled differently (or
all room allocation is done by PSU)
>> Food preferences
>> No dietary restrictions
>> Vegetarian
>> Vegan (strict vegetarian)
>> Other (contact organizers)
>> Not eating with the group
>> Food preferences
>> *(seems like this should be "Food payment")
>> I wish to pay for food at the conference (25 CHF/day)
>> I request sponsored food
>> I will care for my own food and understand that there are
no shops or restaurants nearby.
>> *(last option is untrue)
>
> Yes, the last option should be dropped.
>
> We may not need the "I wish to pay for food at the conference" option
> either; it may be that this should just go via the PSU form. In
which case,
> maybe food + accomodation only need a single "I request sponsorship" box
> this year, thanks to the limited set of options we need to handle?
I think we should have the two (food and accommodation) split:
- local people could have sponsored food, but no accommodation
- few people prefer to eat outside (special dietary, own preferences),
so having the option would reduce our food cost.
>
>> Daytrip
>> *(this needs updating...)
>> A: International Clock Museum
>> B: Asphalt mine
>> C: Absinthe distillery
>> D1: Hiking from Les Rochats, 2.5h (7.4km, 300m elevation)
>> D2: Hiking from Le Camp, 5-6h (17km, 950m elevation)
>> O: Conference dinner only, I won't take part in the day trip
>> X: I won't take part in the day trip or conference dinner
This could be added later (at reconfirmation period.
>> "Spoken languages"
>
> I believe this should be dropped.
it was used for room allocation. No real need for the rest (but annoying
warning if language missmatch of speakers and talk)
>> "Contact"
>
>> Contact e-mail address
>> text field
>> Public e-mail address
>> text field
>> Include in mass mailings
>> checkbox
>
> Contact email should default from oauth2 data (and possibly be
non-editable
> for @debian.org users).
No, I think it should be editable for all people. Sometime people prefer
work email or other mobile email, for quick contacts (or on travel).
>
>> "Phone number"
>
>> Phone type
>> (multi-drop down)
>> mobile
>> secretary
>> work
>> private
>> dect
>> skype
>> fax
>> sip
>> Phone number
>> text field
>
> I'm not aware if we've ever used this. I suspect that we probably
only need
> one contact phone number per person.
registration: did you ever used them?
> The country list is out of date, South Sudan is not listed. ;P Hopefully
> there's some way for us to import the country list into django so we
don't
> have to maintain it.
>
>> "Emergency Contact"
>
>> Name
>> text field
>> Way of contact
>> text field
>
> Should be retained
>
>> "Travel"
>>
>> Arrival
>> Date of arrival
>> date selection
>> Arrival time
>> text field
>> Special transport requirements?
>> checkbox
>
>> Departure
>> Date of departure
>> date selection
>> Departure time
>> text field
>> Special transport requirements?
>> checkbox
>
> Looks right to me.
Note: arrival time are usually not consistent. SO possibly we could add
"arrival time at the venue", which make easier the calculation of meals
for sponsored people.
>> Can the travel data be made public (other attendees)?
>> checkbox
>
> Punt on this. AIUI we haven't used it lately.
Now we use the wiki for travel coordination, so we can remove.
>> Need help paying travel fare?
>> checkbox
>> Travel costs
>> text field
>> currency drop-down
>> Travel sponsorship needed in order for me to attend DebConf
>> text field
>> currency drop-down
>
> Looks sane, but if we're planning to have a single checkbox for
food+accom
> sponsorship we probably want to group the sponsorship questions together
food+accommodation and travel sponsorship are done differently (and I
think sometime it was done by two different team). In any case we should
track them separatelly. We have much more budget for food+accommodation.
I we can formulate some more strongly (making clear that travel
sponsorship is limited, so only for people really need it) would be better.
I would also drop the currency drop-down, and let people to do currency
conversion.
ciao
cate
Reply to: