gobby.debian.org debconf16/bof/dc17-website

Continuation from wafer-development

== Abstract ==

DebConf16 tried wafer, a different Conference management system.

Did it work out OK for us? Do we keep going down this road?

What big issues would we want to address in it?

== Notes ==

* Video Team / content team interaction. Moving talks into a videoed slot at the last minute means there are no volunteers.
	* idea: the software can warn the content team that last-minute room switches won't be videoed before they finalize the switch, and can notify the video team for earlier room switches

* Room mates / allocation. 
	* [ideas from madduck] Shared secret for sharing rooms, or let people select their own rooms
	* Keep data with the records, don't tell people to email us (includes food preferences)
	* [ideas from lavamind] Themed rooms (partygoers, families, late sleepers, "peace and quiet")
	* already planned, but don't forget: make a lot of arrangements with local hotels since 8-person classrooms handle fewer preferences than our accommodations from recent years
* re-confirmation is confusing, return to pre-registration and registration upon payment; sponsored people get registered upon accepting our offer. If people do not show up without a good excuse, then they don't get money back or lost their sponsorship privileges for the year(s) to come.
* Preview bill during registration.
* Rephrase registration fee questions with language that leads people to pay what they can afford. Example:
	"Are you attending DebConf on behalf of your employer? (Yes/No, leads to larger C$XXX)
	[only if No, then ask:] Can you afford to pay a registration fee? (Yes/No, leads to smaller C$XXX)
	[only if No, then say:] That's okay. We still want you to come!"
* Spread out registration over multiple pages. With final review at the end.
* Mail some teams if registration fields change. Django signals?
* Package FOSDEM volunteer app.
* Allow speakers to associate / upload their own talk slides?	

== END ==