As a suggestion the write up for the Commit Digest could give a 2-3 sentence overview of what the publictransport applet is about and who it's for with the rest of the writeup about how it's implemented and plans for future developments. You could also touch on how it may be extended and how it makes good use of the KDE libraries available (or if it extends them)<div>
<br></div><div>Your blog would be almost a flip of this with a lot more on how it's used and who would use it. The kind of situations it lends itself to and what use cases it would be very effective in. touch on how it's fed data so that people can figure out how to get it tuned for their area. So the commit digest is an explanation to developers and possible future collaborators while the blog is to end users and KDE enthusiasts who want to configure and advocate their most loved desktop :)<br>
<br><div class="gmail_quote">On Thu, Jan 20, 2011 at 3:36 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;">
On Tuesday 18 January 2011 20:35:17 you wrote:<br>
> Hello Alexander!<br>
><br>
> I just committed some bigger changes and yes, I would like to write a story<br>
> about it. I also thought about creating a blog (my first one) and introducing<br>
> all the publictransport stuff (data engines, applet, runner, new helper<br>
> library) to the people on planet kde.<br>
> What am I supposed to write for the commit digest, ie. where should I start? I<br>
> think the best is to write there about the latest changes and write about<br>
> older changes / history in a blog aggregated on planet kde.<br>
><br>
> Greetings,<br>
> Friedrich<br>
<br>
Sorry for replying a little bit late, you asked a good, but somewhat difficult question, I needed to think about it for a bit. That’s<br>
why I’m also CC’ing this reply to the Commit-Digest mailing list so that others with more experience might respond. I’m still<br>
relatively new to helping with the Commit-Digest.<br>
<br>
I also think that what you write for the Commit-Digest should not copy your blog. Your suggestion to write about the latest and<br>
greatest developments (after a sentence to introduce your public transport applet I assume, to inform the reader of it’s<br>
purpose) is a good one, because the Commit-Digest is in principle reporting on what the latest developments in SVN/Git are.<br>
I look forward to your story and appreciate your help.<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>
</blockquote></div><br></div>