The current compiler team meetings are entirely reactive: we review P-high bugs, address nominated questions, etc. This is vital. But we rarely take the time to proactively do design work. I think there are lots of interesting questions to discuss in depth about how to structure the compiler. Moreover, as @arielb1 pointed out to me, there is a certain amount of overlap between the compiler team meetings and the #rust-triage meetings that take place every two weeks.
Therefore, I am thinking that perhaps we should say that, on those weeks when #rust-triage takes place (i.e., every 2 weeks), we will schedule a proactive design discussion. We should schedule these topics in advance so that people have some time to prepare. The idea would be to go over some planned changes, discuss the overall design, and make sure we're all satisfied.
Typically, I would say that such discussions work best over some kind of video chat. But I'm not entirely sure, maybe IRC is suitable. If did opt for video chat, I'm not sure what would be the best system -- Vidyo is sort of "mozilla only". WebRTC-based things are linux friendly, but don't scale well to more than a few participants in my experience. Google Hangouts might work but doesn't work in Firefox right now (sigh).