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. > > 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.
Am Donnerstag, den 22.01.2009, 12:02 -0800 schrieb ron minnich: > 3. 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. > 4. 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
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
-- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
