Investigate ways to announce compiler team updates.

Quoting @nikomatsakis from Zulip:

So I was talking to the person who runs readrust.net on discord. I feel like we need better visibility for the summaries and activities of the various compiler working groups. I was envisioning that it would be nice to have a central blog that just contains these sorts of updates and announcements -- basically, the activity of each of the working groups. In fact, I suspect that the blog should be project wide, with the ability to filter by team, by working group, or by other things.

The readrust.net author encouraged me to write-up an issue with more details. Before doing that, I thought I would open up some discussion here.

I've also been wondering about the structure of the weekly meetings -- I was thinking that maybe, instead of pulling from the groups, each group should push updates, content, and questions, and we can review them in the triage meeting.

Originally, I had in mind that we would go round robin because I thought it'd be useful to be able to see if working groups haven't been active with updates in a while. But we can do that separately just by having the updates organized by working group and checking for working groups that haven't posted any comments in a while (or, honestly, just monitoring Zulip). This could be a signal to go check-in and see how things are going and if we can do anything to help.

Start by reviewing the linked Zulip discussion and the readrust.net context, then compare the proposed central blog, team or working-group filtering, and update flow with compiler-team triage meetings. The issue does not define an implementation entry point or acceptance criteria, so a concrete proposal and agreed definition of done would be needed first.