Guide on the "social aspects" of compiler development

I think it would be useful to have a short guide on the social aspects of getting into compiler development. Some of this information already exists in the getting started section, but I think it might be good to include this information before mentioning anything technical. I know people with deep compiler experience (e.g., from the C++ world) who have found it hard to contribute not because of technical issues, but because of social issues (e.g., Zulip is very busy and it's hard to know where to even begin).

This would answer questions like the following:

• How can I get involved?
  • a short description of particular efforts that are pretty beginner friendly (e.g., issue triage, prioritization, compiler perf testing, etc.)
• Where do I get involved?
  • A short guide to zulip including relevant places to subscribe to (e.g., t-compiler/help, t-compiler/meetings, t-compiler/wg-prioritization, etc.)
• How do I find good issues to work on?
• Who can I ask for help?

Start with the existing getting started section and review the listed Zulip areas: t-compiler/help, t-compiler/meetings, and t-compiler/wg-prioritization. Done means adding a short guide that explains beginner-friendly ways to contribute, where to get involved, how to find issues, and who to ask for help.