I'm unable to rsync with the cvs repository, so no digest is possible. It seems everything is in flux until the subversion changeover is done.

Hopefully all will be back to normal next week.

Perusing the apache logs I noticed some hits coming from

kdehispano.org.

Pedro Jurado aka melenas has translated some things from the digest.

Here is the digest from friday generated by the new! stuff.

http://cvs-digest.org/?issue=apr232004

It doesn't look much different than the regular one, except the links to source code.

The cvs-digest rewrite seems to have hit a wall, or I have. I suppose a couple of days away will help.

It looks like I'll be hosting the thing on my machine for the time being, until someone with a repository offers a bit of space and bandwidth. I'm short on hd space, got another one coming tomorrow. 120GB seagate. Should do for a week or two. Then do a chroot jail for apache and php, and get the thing running. How come this project, which I started to learn the kde api, ends up teaching me web server admin, php, perl and a host of other interesting but unrelated stuff? The security stuff makes me nervous. If anyone is willing to help with a security audit of the php code, and some suggestions on securing the server, please let me know.

A common complaint I get from developers is that their work isn't showing up in the digest.

I'll explain how the whole thing is done, and then get to the question. I go through the 2000 or so commit emails from kde-cvs list, and select commits that are either bugfixes, new features, optimizations or security fixes. With bugfixes, any that have a bug number are selected. I then run a script that builds the html, statistics and other stuff, edit, add a few things here and there, then publish. This works reasonably well, although there are imo too many trivial bugfixes highlighted.

Time to redo the digest. I'm getting bored with what is produced, and frustrated with the limitations of static pages. Most complaints I receive are from developers whose work isn't highlighted.

So, my goals are:

I am thinking of adding a feature each week describing the state of CVS HEAD. I will report which modules build, which don't, and any glaring bugs or neat stuff. My usage pattern is pretty typical, ie. email, browsing, addressbook, etc.

I am planning on doing a feature which will list all the Kde developers who are paid by someone.

Here is an incomplete list.

Waldo Bastian by Suse
Zack Rusin by Automatix ( there was someone else too)