Digested

ade commented on the history available within the KDE repository. I thank coolo and ossi for their efforts to maintain an accurate record of development. You cannot know where you are going unless you know where you come from. KDE is as much a social phenomenon as a collection of software. Other projects have at their center a mailing list, but KDE seems to revolve around the source repository. Hence the importance of preserving the history, and my decision to document what goes in.

I am in the process of (actually have a blank open document in Kate) rewriting the statistics generating code for the Digest. A blank slate is daunting yet liberating. What information should I gather, and how should it be presented? I ask for comments and suggestions.

Currently a perl script goes through the cvs repository, file by file, selecting commits between the dates passed as arguments. From the cvs logs, it gathers everything and outputs an xml file (may62005.stat).

The commit summary data is as follows:

totalcommits

totallines

newfiles

modfiles

numdevs

For each module the following data is gathered:

modulename

moduleatomiccount

modulefilecount (which doesn't make sense)

and each author has this data:

authorname

authorfilecount

authoratomiccount

authorlines

Which with a bunch of lines and html is used to create the statistics page in the weekly Digest. svn log creates a line of data like this:

r410589 | dkite | 2005-05-07 16:56:21 -0700 (Sat, 07 May 2005) | 1 line

Throw in the list of files per commit, a rather long running loop through all the touched files, spit out an xml file, et voila.

So after all that blather, let's cut to the chase. What do you want? Some people mentioned graphs. Graphs of what?