Differences between revisions 10 and 11
Revision 10 as of 2005-07-27 20:13:39
Size: 3480
Editor: anonymous
Comment:
Revision 11 as of 2005-07-27 20:15:25
Size: 3494
Editor: anonymous
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
     * Is today the arrival date he said he would arrive? If not this needs to be indicated      * Mark him as checked-in and record his arrival date if its different then what he indicated earlier

<<< DebConf6

As there seem to be some requirements that had not been fulfilled by the software that has been used to support the organisation of DebConf5, and I (HenningSprang) saw people talking about what other tools could be used, I have proposed to go for a structured approach; First analyze requirements for the software, then see what products meet them, or which ones come as close as possible and can easily enhanced with the missing features.

Requirements for DebConf6

features needed / use cases that need to be solved

  • Registration (The following proccesses need to be supported)
    • Online registration, (all their relevant info is recorded e.g. name, contact info, food-preference, etc.)
    • Confirmation round a few weeks before the conference starts (during this round people will need to enter when they are arriving and leaving and confirm their registration)
    • Check-in when arriving at the conference. (The steps below describe the process used during ["DC5"])
      • Check identification
      • Mark him as checked-in and record his arrival date if its different then what he indicated earlier
      • Which room is he assigned to?
      • Hand out a key (if a deposit is needed, it should be indicated if the person left the deposit and how much)
      • Did he request a laptop?
      • Handout laptop if requested and take a deposit in return (it needs to be recorded what the deposit was, and a small contract on use of the laptop is signed)
      • Handout the conference bag
    • Check-out when leaving the conference
      • Receive the key
      • Give back the key-deposit if that person left it previously (record this happened)
      • Receive the laptop when it was borrowed and give back the deposit (record this happened)
      • Mark the person has signed out and indicate day of departure if it differs from the one given previously
  • Issue tracking
  • Voting for talks
  • managing an the external website (that includes what?)
  • conference Calendar (which talk by whom is at which time in which room?)
  • Video Volunteer management
    • which roles do we need
    • which volunteer with which skills has to be in service at which talk as described above in the conference calendar
    • when and how does the volunteer do the training to be able to fit in a role
  • we should look at ?DebConf5WhatToImprove what we can get from there as requirements for the next debconf software ( especially the sections website and conference management)

  • those links also provide information about the requirements of the conference management:

soft requirements (like how specific things should behave)

  • Any web-based software should be available through the debconf.org domain.
  • everything should be easily usable
  • any data should be easily exportable, because we could need it suddenly in a specific format that's not provided by the system, so we need some generic output that we can adjust to our needs (XML/CSV)
  • anything must work in at least english language, having other additional languages is a plus.

Software that has been used for organising DebConf5

Registration

  • Comas

Internal communication

  • List-server - hosted by Lars Wirzenius - lists are available under the DebConf domain