-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Aaron Nabil wrote:
> #1 Ability to schedule one event across multiple rooms > > and "everything else" (in no particular order) > > We would like to have finer control of a speakers free/busy schedule then > simply when they arrive and depart. Ideally something like a grid of > every hour in the convention which they could click a checkbox for > for "busy" (or "free"). I know this probably doesn't map well into any > existing database object. Many of our speakers have quirks about when they > want to eat lunch, sleep, etc. A simple grid of busy/available for each day > would solve this nicely. This is both planned. > We'd like to use Pentabarf for our entire registration system. Since we > had to copy everyone from our main reg system into Penatabarf so they > could use the self-scheduling system (which was a REALLY BIG DEAL at > the convention, everyone LOVED it) we decided next year to instead just > enter everyone into pentabarf instead. One problem is that the current > system needs email addresses to be unique, there is just no way this can > be done in a live conference, attendees often share the same email address. > It > would be nice if there were some other niceties for dealing with conference > attendees. I plan to separate the visitor system accounts from pentabarf accounts. This would also remove the necessity for unique email addresses and you don't clutter your person table with participant entries. > Some kind of mechanism for "user defined" fields. As an example, we rated > all of our talks by skill/expertise, ie, beginner/intermediate/expert. > There > was no way to encode this into the event (we ended up putting it in the > description). It would be nice if there was a flexible, easy to use way to > tag events with properties or fields specific to one convention. Also, > applying the same > logic to rooms, it would have been nice to be able to flag some rooms with > properties important to us, say, like if the room had a PA system, or > electric > outlets, number of chairs, etc. What we did is prefix all the room numbers > with codes for > properties in the scheduling phase, then stripped all those off later. The > design > should make it easier for a convention to customize what is stored about a > person/event/room. Can you give some more examples. What other fields did you miss. For stuff like PA, chairs, ... it is planned to have a subsystem for resource management. But it's unclear whether this will make it into 0.3. > The Day 1 2 3 references weren't very user-friendly, I hack in a little bit > of ruby to translate them into proper day names (in a very non-portable > way), it > would be nice if this were actually in the code. > > Our schedule is still browsable here... > http://www.gamestorm.org/schedule/day_1.en.html > we made a bunch of minor localization changes of no general interest, but > some of them > I'm sure other people would be interested in. For example, we wanted to be > able to look > up a person and see what there public schedule was in an "info box" sorted > by time > http://www.gamestorm.org/schedule/speakers/43.en.html > and a few other small changes along the same lines. I've been meaning to > diff our tree > against the original and make a commented list of changes, maybe I'll do > that soon. I really like the changes you made to the html export escpecially the events by track stuff and the info box at the speaker page. I would love to get a diff of your modifications. > > Finer-grained permission controls. It would have been VERY nice to be able > to delegate > control of rooms to certain departments so they could only schedule events > into those > rooms. Also, the ability to tag submissions with which department could > then be > in charge of scheduling it. The permission system will be changed a lot for 0.3. I plan to implement conference-based permissions but it's not yet clear how exactly the permission handling for 0.3 will be. I think per room permissions really make sense too. If you have further ideas/suggestions for the permission controls please tell me about it. > I'll think of more and let you know. That would be great. Thank you very much, Sven -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEkdRIevlgTHEIT4YRAkQMAJ9L15PBAObIvmYvqXB09spV3Fq1sACdH2Bn /vU6hjTjPfPfnq+24vAIriw= =IAiL -----END PGP SIGNATURE----- _______________________________________________ pentabarf mailing list pentabarf@mail.skyhub.de https://mail.skyhub.de/cgi-bin/mailman/listinfo/pentabarf
