Hi,
just briefly, and maybe to provide a little historic context surrounding the newsletter, I would suggest to run a forum/devel list search.
Sooner or later, you will realize that we did have various forms and manifestations of the "FlightGear newsletter". In fact, the current "wiki-based community-driven newsletter" was inspired by a discussion we had on this very forum, roughly 9 years ago (IIRC).
Overall, the FlightGear project is facing certain challenges, and things like the newsletter are particularly prone to suffering due to certain constraints - which is why we've found the wiki-based contributions model to work particularly well compared to all the other attempts.
However, to be perfectly honest - the newsletter never was a working "on its own" - what people not involved in this community may not realize is that some of us (especially Gijs, Red Leader and myself) would normally reach out to people to get them involved in contributing to the newsletter.
I think Thorsten may recall that I reached out to him to encourage him to add news relating to this own developments to the newsletter - and that is actually something that I did somewhat regularly. In fact, I ended up using a simple template that basically invited people to contribute to the newsletter, pointing out how to get started doing this, which included links to basic introductory articles, including instructions on adding screenshots/images and youtube video. I also made it clear that the newsletter was community-driven and that everybody was invited to contribute to it, also people who stated that their grasp of the English language would not suffice, because we had others (like e.g. Red Leader) who were willing to help review/proof-read such contributions.
These days however, I am not as much involved in wiki/FG matters, and I guess that nobody is reaching out to our contributors anymore to get involved in the newsletter ?
Anyway, what I am trying to say is that the newsletter (or its schedule) is unlikely to benefit from being revamped - rather, I would suggest that people interested in the newsletter get started drafting a template to invite other contributors to get involved in the newsletter - there are tons of good ways to "harvest" contents from the forum/devel list and add those to the newsletter (or even the commit logs).
Actually, it didn't take much time to do that - like I said, I was using a template that I would personalize, and then I would configure the forum search such that it would show all topics created during the last 3-4 weeks, sending out roughly 10-15 PMs, with roughly ~3-5 people responding well to these invitations.
In other words, I guess what the newsletter primarily needs is someone involved in the forum/devel list, willing to monitor these channels and willing to reach out to contributors who may not be that familiar with the newsletter and the wiki in particular, while also offering to mentor people.
Apart from that, I don't think that the newsletter really needs any major improvements, it mainly needs contributors - and people willing to mentor new contributors.
Given the constraints of the project, my suggestion would be to start a new wiki article covering how to contribute to the newsletter, basically serving as/replacing the template that I would originally send out to people on the forum, and then sending out a link to the new article to people announcing new projects.
I guess that should work fairly well.
Then again, I am certainly not opposed to any efforts surrounding improvements to the newsletter, I just don't believe that it's necessary, or that it's going to work out too well - like I said, back when the newsletter was apparently working "well enough", there was quite a bit of behind-the-scenes networking going on, including 1:1 mentoring to get new contributors up to scratch with the wiki.
Finally, let me state that I would love to see the newsletter alive and kicking again, mainly because I am also not very involved in FG matters these days, and I find it annoying to have to browse the archives (forum/list) or the commit logs to come up to speed with FG matters.
Thus, I sincerely hope that people will find a way to make that happen !