Organizing the coreboot weekly news.

[Paul Menzel]

Dear everybody,

this thread is supposed to be for the discussion of the workflow to
write the newsletter. Please add your ideas and suggestions here.

1. Format/Layout
a) Markdown [1]

2. Organizing the content
a) A wiki page for each issue.
b) A directory in svn with a file per issue.
c) Open a thread on the list after each issue, where all important
things are added.

What else do we have to consider?

Thanks,

Paul

[1] http://daringfireball.net/projects/markdown/

[ron minnich]

I think the key will be picking the publishing interval. Too frequent
news with too little contribution won't go well. Expect lots of action
at first, but it will dwindle as the novelty wears off. I'd go for
monthly or biweekly. Tthe other most important thing is editing.
You'll avoid people who say there are two most important things if you
have good editing :-)

ron

[Paul Menzel]

Am Donnerstag, den 22.01.2009, 20:58 +0100 schrieb Paul Menzel:
> this thread is supposed to be for the discussion of the workflow to
> write the newsletter. Please add your ideas and suggestions here.
> Format/Layout
>
> a) Markdown [1]
> Organizing the content
>
> a) A wiki page for each issue.
> b) A directory in svn with a file per issue.
> c) Open a thread on the list after each issue, where all important
> things are added.

Am Donnerstag, den 22.01.2009, 12:02 -0800 schrieb ron minnich:
> I think the key will be picking the publishing interval. Too frequent
>
> news with too little contribution won't go well. Expect lots of action
> at first, but it will dwindle as the novelty wears off. I'd go for
> monthly or biweekly.

In my opinion we could do it this way.

i) Two or three categories/measures for importance.
30 points for a new port
20 points for ???
10 points for a new development started (for example for a new payload),
an event coreboot participates, documentation releases

ii) When 60 points (or another threshold) are reached or if a month
past, we should publish the newsletter.
> Tthe other most important thing is editing.
>
> You'll avoid people who say there are two most important things if you
> have good editing :-)

Sorry my English is not good enough. I did not get your point.
> [1] http://daringfireball.net/projects/markdown/

Thanks,

Paul

[ron minnich]

On Thu, Jan 22, 2009 at 12:49 PM, Paul Menzel
 wrote:
> > Tthe other most important thing is editing.
> >
> > You'll avoid people who say there are two most important things if you
> > have good editing :-)
>
> Sorry my English is not good enough. I did not get your point.

it's a silly joke. I said that two things were the most important
thing, but only one thing should be the most important thing. I was
poking fun at myself :-)

ron