Scale-up blog post update writing

For 6 to 7 months now we're writing these monthly blog updates. They've been quite some work, but they've been fun to write. However, the more I work on them, the more it becomes obvious we need a different process than me going through the whole of the project getting a list of things that have been done. Remarkably, in the last month, I've had @longnoserob, @ollieparanoid, and @craftyguy prepare or share some thoughts of things that should go into the update. This was great, but shows that both I am responsible, but don't scale. At the same time, I feel more and more uncomfortable manually triaging the project and deciding what is and what isn't newsworthy. It introduces a massive bias that I don't want to be responsible for.

Therefore, I propose we move to something similar to "This week in GNOME/KDE/Matrix", with the exception that we probably want to have "this month" instead, we want to edit things manually more, e.g: add number of kernels, new devices, etc. and we want to publish it into our blog-post, instead of a specific website. For that, we need:

• A matrix room
• To setup the bot (possibly do not need to be done at the same time, and we could possibly live some months without it)
• To give it publicity and encourage people to write short updates whenever they do something "big", "cool", "nice", "noteworthy", etc.
• Approval that this makes sense

Any thoughts? I'm happy to continue working on this, do research on the bot, and even take care of infra maintenance afterwards if needed, but would possibly need some help from the infra team (@z3ntu, @olliparanoid) to set it up. I know I can find the bot, but I'm right now on a ferry with a terrible internet connection, so will put the link here if nobody does it first.