@evan I think the language barrier is the first thing to tackle. Live video calls are the hardest format for non-native speakers, so shifting more of the work to written communication would help a lot, and every meeting really needs minutes, even rough ones, since at least those can be run through a translator afterward. I've tried the newer real-time transcription and translation tools a few times and honestly the quality still isn't there, especially with ActivityPub-specific jargon that general models just don't recognize; feed a bad transcript into a translator and it gets worse, not better. Written async channels, like the FEP process already is, seem like a better fit for now. On the community side, @fedidevkr (a Korean fediverse developer group I'm part of) has been kicking around the idea of a session where people draft FEP proposals together in Korean first, then translate and refine into English as a group. Still an early idea, but I think local hubs like that could lower the barrier more than any single W3C-side change.