Thanks for the feedback. I've tried to capture the current state of the requirements in the wiki: https://wiki.debconf.org/action/edit/DebConf14/Registration I'll keep it up to date as the discussion here progresses. Please discuss on the list before making any changes; and if no one objects to the proposals, silence will be taken for assent. ;) The only piece that I think still needs to be fleshed out is which fields are required or not. On Fri, Apr 11, 2014 at 12:07:25PM +0200, Giacomo Catenazzi wrote: > 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. But it could be any nickname that they want printed on their badge. We should keep the field and not try to overspecify. > >> Title > IMHO this should be removed Done. > >> 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. Noted. > >> 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. Right, if the registration team isn't using this then let's not make it part of the process. We'll just note that any images may be displayed publically. > >> 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". Ok. Which email address should be listed as the contact for this? > > 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) All room allocation is done by PSU. We are supposed to be able to designate which attendees we are paying for, but everything else is done with PSU directly. So I expect our reports from PSU to include a list of everyone registered through their site, and information about whether they've paid; we can then reconcile this report against our own list of people we are sponsoring. But other than providing attendees with the pointer to the registration form, if someone is not in sponsored accomodation it's entirely out of our hands (which is as it should be). > > 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. Ok. I'm not sure how common these cases will be, but if you think there will be some and it may matter, let's ask both questions separately. FWIW, I assume that even among those who accept sponsored food, there will be some number of people each day eating outside instead. > >> "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) Anyone who has a specific roommate preference will be able to enter it; beyond that I'm not sure how much we want to be involved in room allocation, as opposed to letting the PSU staff handle it. I think we can open registration without this, and if we decide later that it's so important, we can add it? > >> "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). Historically, the penta site has always said "please use your Debian email address if applicable". Why do we say this? Is it just to be able to identify DDs? If that's the case, then yes, oauth2 will give us this information and we can let the user pick another email address as their preferred contact address. We just have to make sure we're careful about using the right field for the right thing. > >> 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. Thanks, clarified. > >> 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 didn't say they shouldn't be tracked separately, only that the questions should be grouped together in a section on "sponsorship". (I don't think it makes any sense to have travel and food/accom sponsorship handled by different teams, though.) > I we can formulate some more strongly (making clear that travel > sponsorship is limited, so only for people really need it) would be > better. Ok. We can wordsmith this once the initial form is available for testing. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slangasek@ubuntu.com vorlon@debian.org
Attachment:
signature.asc
Description: Digital signature