Timo Kreuzer schrieb:
Maybe it's a good idea to have one responsible person, but more than one writer. Several people could make proposals about topics and write small articles. The responsible person than already has some stuff he can use and put together. Then noone has to write the complete stuff alone. There could be a wiki page with topic proposals and chosen topics for the next newsletter(s) and people can then apply for an article and write it. 1 Newsletter Coordinator, few "permanent" writers and several "casual" writers. Maybe one native English person to check for misspelling and wrong grammar/expression. This would also make "more technical" articles possible, because some people might have enough knowledge, but not the time to write a full newsletter.
This is a good idea. Maybe we could even extend this a bit and create something like a knowledge base. There could be a newsletter/knowledge base coordinator and several authors, writing knowledge base articles in the wiki. These KB articles could be used for writing the "more technical" part of the newsletter, so the newsletter creator would only have to have an eye on svn and get informed by the devs about larger patches, planned releases and so on.
This has two advantages:
1. We have more up-to-date documentation 2. Creating the newsletter is a not too time consuming job
Greets,
David Hinz