We search an author for our "ReactOS Weekly Newsletter".
History:
Jason Filby had established the ReactOS Weekly Newsletter (called "ReactOS Weekly") in 1999 as a useful weekly news summary located on www.reactos.com. In 2000 the newsletter had been discontinued. With the website redesign in summer 2005, the newsletter came back with Stuart "TwoTailedFox" Robbins as author.
Requirements:
Here are requirements for an author:
1. Have enough time once a week to write the newsletter text (e.g. every sunday) 2. Be good in english language 3. Understand our technlogy (svn, reactos, windows nt, win32, kernel, drivers, apps, etc.) 4. Be in frequent contact with the ReactOS developer, and come in our IRC channels too (because mailing list traffic may be sometimes slow) 5. HTML knowledge is not required but an advantage
Goal:
The "ReactOS Weekly Newsletter" should be weekly (as the name implies) and sum up the ongoing mailing list discussions as well as irc conversations. Additionally it should contain ReactOS news, like new releases.
From time to time interviews, reviews (of apps compatibility and
reactos functions and releases) and maybe audio-podcasts, etc. would be great too. The layout of the newsletter issue page can be the same as the latest one (e.g. http://www.reactos.org/xhtml/en/newsletter_11.html), similar as WineHQ's one, or different.
Previous newsletters - links:
10/2005 - 02/2005: http://www.reactos.org/?page=newsletters
1999 - 2000: http://web.archive.org/web/20000522174140/reactos.com/public/weekly.html
WineHQ'S newsletters: http://www.winehq.com/?issue=back
Mailing List Information: http://www.reactos.org/?page=community_mailinglists
IRC Channel Information: http://www.reactos.org/?page=community_irc
So... if this sounds like something you would like to do, please reply to this mailing list email explaining why you you think you would be a good newsletter author.
Klemens Friedl
Maybe the devs could propose some topics and the newsletter author could search for more information on these topics. This way he wouldn't have to follow every devs moves, but could still create a newsletter, that contains important and interesting topics.
This would of course require the devs to start talking on the ros-dev mailinglist a bit more regularly and fill the wiki with more information, as it's very hard to separate the important things from all the off topic talk in #ReactOS.
If it was done this way, I would be able to create a newsletter. Maybe not weekly, but I would definitely be able to create two issues per month.
Just my thoughts on this topic...
Greets,
David Hinz
Ged Murphy schrieb:
Klemens Friedl wrote:
Requirements:
Here are requirements for an author:
I would like to see a more technical newsletter. Something similar to what Wine have.
Ged.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
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.
David Hinz schrieb:
...
If it was done this way, I would be able to create a newsletter. Maybe not weekly, but I would definitely be able to create two issues per month.
Just my thoughts on this topic...
Greets,
David Hinz
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
I see good use for a writer. For example, I cannot develop very well, but I speak very fluent English.
David Hinz wrote:
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:
- We have more up-to-date documentation
- Creating the newsletter is a not too time consuming job
Greets,
David Hinz _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
A ReactOS newsletter author should be good at writing technical articles. Wine Weekly Newsletter is popular source for news, we need something similar too.
Topics: SVN, Mailing List and IRC activity are the main topics of the newsletter. Interviews, reviews of new features/versions, podcasts, etc. are optional things.
After 0.3 release maybe will need an librarian coordinator again. Again? Yes, we had one (kjk, who is now ros dev) some years ago. The documentation is still in svn dir (docbook format). If someone want to write documenation for ReactOS for the meanwhile use our Wiki ( http://www.reactos.org/wiki/ ).
And after, I can translate this articles to portuguese for the brazilian community. Is it possible? Are you interested?
2006/6/14, Klemens Friedl frik85@gmail.com:
A ReactOS newsletter author should be good at writing technical articles. Wine Weekly Newsletter is popular source for news, we need something similar too.
Topics: SVN, Mailing List and IRC activity are the main topics of the newsletter. Interviews, reviews of new features/versions, podcasts, etc. are optional things.
After 0.3 release maybe will need an librarian coordinator again. Again? Yes, we had one (kjk, who is now ros dev) some years ago. The documentation is still in svn dir (docbook format). If someone want to write documenation for ReactOS for the meanwhile use our Wiki ( http://www.reactos.org/wiki/ ). _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-
:: Sandro :: -
Brandon/Bmwboy -
David Hinz -
Ged Murphy -
Klemens Friedl -
Saveliy Tretiakov -
Timo Kreuzer