What? Unless you ignore what I've said in the last 2 pages I don't think the answer is as simple as you say.
I actually think it's very simple. Moving in FG circles, I meet people who say that FG should really do X or that Y would be a good idea on a daily basis. The implied meaning is really always that someone else should do it.
When asked why people don't do X themselves as they think it very important, the answers are always 'I can't code C++', 'I don't understand enough' or 'I'm not really qualified'.
Well, one can learn things... Nobody taught me how to use JSBSim or code GLSL - but I needed the tools to achive a goal, so I learned them. But in fact many things aren't hard to learn (Wiki, xml-configuration of effects,...),. Tagging aircraft is as simple as reading the Wikipedia article on the aircraft and match it with the tag list - in fact, I'm seriously over-qualified for the task, but surprisingly there's hardly anyone else who does it, and while I personally don't use the sorting feature at all, I think it adds a lot to the user experience - so I work on it.
Really all it takes to get the newsletter up to speed is someone who cares about it to take initiative, copy/paste the template and start filling it, and a few invitations in the forum to write something.
You're going to ask me next why I think someone else should do it and don't do it myself. The reason is that I already
* maintain AW
* maintain ALS
* develop the Space Shuttle
* provide the largest share of bug support in this forum
* do most of the PR for FG by writing reviews on the project page or articles for flightsim.com
* am busy writing documentation for the wiki
* am busy continuing tagging of aircraft for better user experience where the maintainers haven't done it yet
* am busy adding new-style splash screens to aircraft where the maintainers haven't done it yet
(...)
So unless you have a similarly full list of FG-related tasks, I suggest you take me off the list of candidates for yet another job - I'm doing my share of unpleasant work along with what actually interests me already.
Yes, I do think it's very simple: If you care for the newsletter because you found it useful in the past, take charge to revive it. If you do not care for it, don't lament it's passing away.
(Oh, and the typical reward for taking bug reports is being yelled at... I'm still waiting for the 'payment' to make this worth my time...)