The Planet and Digest have slightly different audiences I would think. I pretty much split "readers" up into those who just want to use something and don't care at all what's happening as long s they know when something new is out. They would probably read the Dot or just KDE's front page news. You have "most people" who use FOSS that care about the applications but also somewhat as to the process. They will read the planet which normally goes over a problem and what the solution is but rarely touches on technical details much. A more technical person who may not want to get mired down in the humdrum of most code will likely want more detailed regular information about how the code changes affect things and what they are. They will likely read the Commit Digest. (As a side note. For these people things like the structure of the various modules in KDE and how they relate to each other may be useful information ) Then you have people deeply invested in the code and progression of KDE and they will likely be on the mailing lists or looking at raw commits. <div>
<br></div><div>If you can see that a writeup on the Planet has gathered interest it may be worth it to do a followup a few weeks later with more detailed information about how the application fits overall into the KDE ecosystem with more technical wirting on the challenges it's just overcome or is facing. The extra detail will probably be welcome. If there isn't much more technical aspects to write about then that's fine the planet has already done it's job. There are plenty of things in KDE to write about. <br>
<br><div class="gmail_quote">On Tue, Dec 28, 2010 at 3:28 PM, Alexander van Loon <span dir="ltr"><<a href="mailto:a.vanloon@alexandervanloon.nl">a.vanloon@alexandervanloon.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I feel I still need more time to get acquainted with the commits<br>
activity to get a feeling of what’s being worked on and what’s worthy<br>
material for a write up before I’d apply to be chief editor. And even<br>
then I’m thinking to far ahead because all I have done so far is<br>
reviewing and classifying, I should get down to writing something.<br>
<br>
Maybe I’m a bit perfectionist, but I think it’s difficult not to overlap<br>
with Planet KDE in this regard. After seeing all the commits for Muon<br>
for example I considered contacting Jonathan Thomas, but he already beat<br>
me to it by writing about the changes on his blog –<br>
<a href="http://jontheechidna.wordpress.com/" target="_blank">http://jontheechidna.wordpress.com/</a> – so that it’s no longer suitable<br>
for the Commit Digest.<br>
<br>
Back on topic, only if no one more experienced is available for the role<br>
of editor in chief, I’d be willing to do the job.<br>
<div><div></div><div class="h5"><br>
On do, 2010-12-23 at 09:45 +0000, Danny Allen wrote:<br>
> Well, I really want (and need!) to transition out of the chief editor role... i'm fine with maintaining adding features to Enzyme, but I didn't restart this in order for it to take up all my free time like it used to! :)<br>
><br>
> So I need to find a good candidate (or group of people) to take this over, preferably before the end of January.<br>
> That person is likely to come from this list, so let me know if you're interested.<br>
><br>
> Danny<br>
><br>
><br>
> ----- Original Message -----<br>
> From: "Roger Pixley" <<a href="mailto:skreech2@gmail.com">skreech2@gmail.com</a>><br>
> To: "Danny Allen" <<a href="mailto:danny@commit-digest.org">danny@commit-digest.org</a>><br>
> Sent: Thursday, 23 December, 2010 3:44:11 AM<br>
> Subject: Re: Oxygen Commit-digest write up<br>
><br>
> Thanks :) would be great if we could have some group of people appointed to be able to put up a digest even if you are on vacation or a slow boat to china<br>
><br>
><br>
> On Wed, Dec 22, 2010 at 4:08 AM, Danny Allen < <a href="mailto:danny@commit-digest.org">danny@commit-digest.org</a> > wrote:<br>
><br>
><br>
> Hi Roger,<br>
> That's great!<br>
> Any content you can get right now would be useful (haven't heard from anyone else yet!)<br>
><br>
> I'll be working on the editor interface of Enzyme next to hopefully solve this issue.<br>
><br>
> Danny<br>
><br>
><br>
><br>
><br>
><br>
> ----- Original Message -----<br>
> From: "Roger Pixley" < <a href="mailto:skreech2@gmail.com">skreech2@gmail.com</a> ><br>
> To: "digest" < <a href="mailto:digest@kde.org">digest@kde.org</a> ><br>
> Sent: Wednesday, 22 December, 2010 5:11:25 AM<br>
> Subject: Oxygen Commit-digest write up<br>
><br>
><br>
> Sorry about this I started getting it last week Tuesday for last week Sunday but it just came in. Going to try and get a writeup from the Solid team for this week<br>
><br>
><br>
><br>
><br>
> Should we add in something about the new Wallpaper and look for KDE 4.6?<br>
><br>
><br>
> Roger Pixley.<br>
><br>
> ---------- Forwarded message ----------<br>
> From: Hugo Pereira Da Costa < <a href="mailto:hugo.pereira@free.fr">hugo.pereira@free.fr</a> ><br>
><br>
> As promised, some lines about oxygen for KDE's commit digest. Since I'm not<br>
> 100% sure of what's usually written, feel free to edit, comment, and do<br>
> whatever you want with it.<br>
><br>
> Take care,<br>
><br>
> Hugo<br>
><br>
> PS: sorry for the delay (got sidetracked).<br>
><br>
> -------------------------------------<br>
> Oxygen is at the heart of KDE's look and feel since day one of the 4.0<br>
> version, for icons, sounds, application's appearance (widget style) and window<br>
> decoration. The widget style and window decoration notably have evolved a lot<br>
> since the beginning, their design becoming more polished, professional and<br>
> attractive, and more features being added, such as support for window<br>
> grouping, smooth animations for practically every interaction between the user<br>
> and an application or the possibility to move windows from any of its empty<br>
> area. They also have become more configurable, while keeping a simple interface<br>
> to the user and a satisfying set of default settings.<br>
><br>
> Since KDE 4.5, the style and decoration have become rather stable both design-<br>
> wise and feature-wise, judging notably from the small number of bug reports<br>
> related to either of these two components. So we decided to move one step<br>
> further and develop an official KDE port of the oxygen style to the other widely<br>
> used widget toolkit: gtk. It is named oxygen-gtk, is hosted in the brand new<br>
> KDE git repository, and originates from one of active developer of the QT<br>
> version of the style (me!).<br>
><br>
> This project aims to provide users with seamless integration of a large number<br>
> of non-KDE applications into KDE, such as Gimp, Inkscape, and even Firefox.<br>
><br>
> The very first version of this new theme has been released few weeks ago and<br>
> reactions so far have been very positive. We expect distributions to start<br>
> packaging the code after the first bug-fixing cycle is finished.<br>
><br>
> There is a lot of activity going on to fix bugs present in this first release<br>
> and reported by users, and to add more features so that both versions of the<br>
> style (QT/KDE and GTK) ultimately match perfectly. This results in tenth of<br>
> changes pushed to the repository daily. Already today, this project is likely<br>
> the best matching GTK port of the KDE's Oxygen widget style. Being developed<br>
> (and hosted) by the KDE community guaranties high quality of the code, long<br>
> term support as well as fast response to user's demands. Oh, and its a lot of<br>
> fun to code into !<br>
><br>
><br>
> _______________________________________________<br>
> Digest mailing list<br>
> <a href="mailto:Digest@kde.org">Digest@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/digest" target="_blank">https://mail.kde.org/mailman/listinfo/digest</a><br>
><br>
</div></div>> _______________________________________________<br>
<div class="im">> Digest mailing list<br>
> <a href="mailto:Digest@kde.org">Digest@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/digest" target="_blank">https://mail.kde.org/mailman/listinfo/digest</a><br>
<br>
<br>
</div>_______________________________________________<br>
<div><div></div><div class="h5">Digest mailing list<br>
<a href="mailto:Digest@kde.org">Digest@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/digest" target="_blank">https://mail.kde.org/mailman/listinfo/digest</a><br>
</div></div></blockquote></div><br></div>