Travel planning for future events (discussion)

IMO cierge worked well for presentations, but less well for travel plans.

I propose that we dont use this repo for travel planning next time. We would lose "assignee" to subtask, but I found that tracking information across matrix (multiple threads over months), zoom, and a handful of concierge issues to be a bit spooky, accidentally missed info could be costly!

Also I'd prefer that information about my travel plans not be posted publicly. (Even the dates.) Whether privacy is the reason or not, individuals specific plans did not end up in the issues, even though that stuff is necessary to coordinate. Instead, I had to do "matrix archaeology".

For future travel plans my preference is a single email thread, one place for whats needed, and the personal details. We'd still use cierge, but limited to stuff that needs to be public (inviting non-team members to our retreat, presentations, collaboration). For USRSE, since the specific details didnt go to the issues, we ended up with fragmented bits of information over too many sources.

The issue names no files, tests, or entry points to inspect. Read the discussion and related Matrix, email, Zoom, and concierge workflows first; done would require a maintainer decision and documented guidance for handling future travel planning.

Written by the indexing model from the issue text.