After 36 issues and over 300 mailing list thread summaries, I have decided to take a semi-permanent break as editor of the Kernel Cousin KDE project. KC KDE was taking up quite a bit of my available time outside of work and family and, as enjoyable as it was to put KC KDE together, I have had to reprioritize things a bit. It would be a shame to see KC KDE simply go away forever, though. If anyone is interested in taking up the role of editor, I would be more than happy to get them started and co-edit the first few issues until they are confident and comfortable with the process.

Agreed - I spent a half hour trying to find out if there was a (tentative) release schedual for 3.1 (only the 3.0 release is on the various *.kde.org sites, miserably out of date). If KDE KC was up and running, I'd have at least an idea of what was going into it, and how soon it was looking to be released.

(No, I'm not expecting it tomorrow - we're thinking of switching the company over to KDE + Crossover Office this fall)

Tabbed browsing is what keeps me using Galeon more than Konqueror... I've been hoping to see it in Konq for some time now, excellent!
Opera introduced me to the tabbed browsing, I noticed Mozilla got it sometime, but Galeon 1.2's handling of these is probably the best... (option to have close buttons on them, etc). Opera opens a new window faster, though.

Big thanks for the service you provided to the KDE community. I read all issues of KC KDE from the beginning. And I really liked the view into the developers work on this great project. I hope it is possible to continue with KC KDE.

well, it isn't a single person job, it just happens that up until now a single person has been primarily responsible for most of the work. the individual summarries can be written by whomever (there were several contributors to kc kde over time who did a great job writting summaries) and there is even a mailing list for coordinating the whole affair, but someone still needs to ensure that it all gets proof read, put into a single issue, that the links are good, write an intro and send it off to Zack @KT for inclusion into the kernel cousins site...

this is a task that can be fairly easily split up amongst several people. i'd probably even keep writing summarries if there was someone (or someones) to take care of the editing and do some of the summaries. i just can't do the whole thing myself right now.

maybe it would be wise to spread teh work out among people who are members of the various lists, especially those who are on the lists mostly for informational purposes (and who dont spend loads fo time contributing actual content)

I can do the kde-artists summary whenever there is anything to summarize.

this would be great... please join the kc-kde@kde.org mailing list and announce yourself when you join. with enough people involved the load could indeed be distributed enough to ensure that kc kde continues.

I've done about 30 issues of KC Wine. So I have a pretty good understanding of the processes involved. This will probably just be a brain dump for anyone considering writing KC KDE (or any Kernel Cousin) issues:

Zack Brown has done a great job of putting together some tools to make writing these easy. Check out http://kt.zork.net/author.html for
more details. In particular, there's a stat tool for collecting list stats. (For multiple lists you can just cat different mbox's together.) I generally have a blank template that I fill in with the individual summaries. I write all the XML with vi (though lately I've used some nicer editors, but only for syntax highlighting, which vim can do.) When I'm done I throw the pages through xmllint to check everything.

As far as multiple people writing issues, I'd think it'd be easy. Especially because KDE has so many mailing lists. One person should be able to handle 2 or 3 lists pretty easily. Or, you can even share one list by claiming threads.