On Tue, Aug 26, 2008 at 04:32:24PM +0100, martin f krafft said: > Maybe some of you want to look at the linux.conf.au registration, > which I find very easy and pleasing. Maybe we could use that system? I don't see any way to tell their conference registration system the dates for which I'll be attending and expecting free food and accomodation that the orga team will find for me? I also don't see a way to tell it that I am asking for $xxxx travel sponsorship? What size free T-shirt I expect? Maybe all of these things should go away, and we should go to a more LCA like model for Debconf, but that's a different argument - we have the conference we have now, so it would be nice if the management system worked with it. > It's my perception that penta brings mostly pain and dependence on our > admin team plus those few who actually are crazy enough to learn it (+ > Ruby). This may well be true, I'm not really in a postition to judge. I'm just curious how you expect the dozens of extra data mining things that come up every year are going to happen except by going through people who have access? It's not that we aren't happy to give out accounts and access when needed, but we do restrict who has access to conference user information since there are banking details and so on in there. That won't change if we change management systems, unless we lose the functionality of keeping information about bank details and so on. Of course, if we stop reimbursing people, we don't need that information any more (in fact, if we don't pay for anyone but speakers, we don't need anything any more. We could keep track of the few dozen speakers with a pen and paper). While I certainly don't love penta, I hate to see trying to migrate to Yet Another Conference Interface That Doesn't Do What We Need. I also (less importantly) can't find out what system they are using, so it's difficult to grab the source and see if it's easily extensible. I have this sneaking suspicion that by the time we modify whatever system they're using to do all the things we need every year + all the things the local team wants for a particular year, it won't be any simpler or easier. Of course, feel free to prove me wrong :) -- -------------------------------------------------------------------------- | Stephen Gran | BOFH excuse #310: asynchronous inode | | steve@lobefin.net | failure | | http://www.lobefin.net/~steve | | --------------------------------------------------------------------------
Attachment:
signature.asc
Description: Digital signature