Adrian

The interpreter change looks fine. What's the reason for the sys.path change?

While I can understand your usecase, this would be a major development effort. As it's not something needed by CERN, the chance that we implement such a feature is unfortunately...

> Would the proposal: > >optionally hide rooms which the user can not book from the room list (i.e. basically add an option which converts "not bookable" into "no access")....

I think this would be an excellent idea for a (third-party) plugin, but not necessarily something I could imagine in the core. > event organizers who want to improve their...

Just thinking.. an alternative solution could be adding this signal to block modifications on the field level (like we do for purged fields or payment-related fields in a paid registration)....

Not sure if the current solution is ideal. In a perfect world we would never use a From header using a user-supplied email address, but thanks to mailing lists etc....

This API allows requesting multiple events (e.g. `.../1-2-3.ics` would return those 3 events); and anything you cannot access is simply skipped. I agree that it's not pretty though :) As...

Yeah, I think with the current system it doesn't make that much sense - you'd lose the menu etc. Providing a sequential timetable view within the conference view in the...

> It'd also be useful to promote the "Zoom" link as first-class citizen for a session, rather than keeping it under "Presentation Materials". We support linking videoconference rooms/channels to session...

The problem is the (very) limited space there... especially since affiliations can be rather long (now imagine a long title, combined with a long speaker name and a long affiliation)....