5th November 2004

by Derek Kite
 

This Week...

Kdevelop adds extension support. kommander improves signal and slot editor. Kwallet is now asynchronous. juk adds support for gstreamer 0.8. KPasswordDialog adds password strength meter.
The Kde development process is remarkably open. With a cvs account you can contribute to almost any part of Kde. Most developers work on specific areas, others touch almost all the code at one time or another.

What happens when someone oversteps the rules? (Yes, there are rules) I don't want to embarass anyone, but not everyday does someone have the privilege of being chewed out by our release coordinator. And it is a good reminder for everyone.
It all started with a rather large commit to kdelibs/kdeui changing all instances of (foo==false) with (!foo), etc. The response was swift. Lubos Lunak wondered:
Hmm, I don't remember seeing any mail on any of the lists about uglifying KDE code. What should be the point of this commit, besides making cvs annotate worse and offending a bunch of those people whose coding style you have changed without asking them? Doing such things is never a good idea.
Maks Orlovich asked:
Reviewed by? Approved by? IMHO it's very disrespectful to go touching people's coding style without asking for their OK. And wholesale commits in kdelibs are just utterly risky.
Stephan Kulow didn't hesitate:
You broke rule 8 of the little rules we have for KDE CVS: http://developer.kde.org/policies/commitpolicy.html#8 I disabled your CVS write access and I won't enable it for another two weeks. You're still welcome to contribute to KDE CVS, but you will have to do so using patches for the time being.
Quite a surprise to find in your inbox when sitting down to do some coding. All worked out for the best when apologies were offered, misunderstandings were cleared up, and cvs write privileges were restored.
David Faure explained why the strong response:
What hasn't really been said is why we all object to this.

Changes like "== QString::null" -> "isNull()" are accepted, because they make things a tiny bit faster without hurting readability.

But changes like

- while ( ( wdg = it.current() ) != 0 ) {
+ while ( ( wdg = it.current() ) ) {

don't make it faster, and do hurt readability (the changed line looks to me like it might be a typo for wdg == it.current(), whereas the original line didn't have that problem.

Same thing for myint == 0, this is more readable than !myint, when the int can take several values and we're only testing against 0 here, but maybe 1 and 2 later on. There is nothing to gain by writing !myint here, only loss of readability.

Some people might be able to read !myint and to notice the double parenthesis in the above while loop. Good for them. But that's no reason to make it harder for the others by changing the existing kdelibs code.
Renchi Raju announced the immediate availability of digiKam-0.7-rc1.
The highlights of this release are a number of bug fixes, updated documentation and various usability/cosmetic fixes since the beta1 release. The scheduled release for 0.7 stable is this weekend (Nov 7). The primary reason for this release is to give translators enough time to update the translations (the string freeze has been in effect since Oct 31).

------------------------------------------------------------------------

digiKam is a digital photo management application for KDE, which makes importing and organizing digital photos a "snap". The photos can be organized in albums which can be sorted chronologically, by directory layout or by custom collections. Additionally images can be tagged and these tagged images can be viewed in virtual albums. An easy to use interface is provided that enables you to connect to your camera and preview, download and/or delete your images.

More details available at: http://digikam.sourceforge.net
Petter Stokke announced KMLDonkey 0.10:
KMLDonkey 0.10 was released today, the 1st of November 2004. KMLDonkey is an advanced GUI frontend for the MLDonkey P2P core, offering a wealth of useful features and tight KDE integration for MLDonkey users.

Download and installation instructions can be found at the following address:
http://kmldonkey.org/node/view/21
An overview of KMLDonkey's major features can be found here:
http://kmldonkey.org/node/view/13

Aside from being an official release, version 0.10 contains only a few bug fixes since the 0.10pre4 release. The changes since the last official release, 0.9.1, are too numerous to list - please consult the aforementioned feature overview.

Statistics

Commits 2460 by 213 developers, 429017 lines modified, 1114 new files
Open Bugs 7829
Open Wishes 7223
Bugs Opened 324 in the last 7 days
Bugs Closed 381 in the last 7 days

Commit Summary

Module Commits
kde-i18n
 
541
kdenonbeta
 
275
kdepim
 
246
kdelibs
 
163
koffice
 
131
kdeextragear-2
 
120
khtmltests
 
110
www
 
97
kdeextragear-3
 
93
kdeextragear-1
 
88
Lines Developer Commits
104748
 
Stephan Kulow
 
118
2050
 
Stephan Binner
 
108
4007
 
David Faure
 
67
1958
 
Pedro Morais
 
66
725
 
Benjamin Meyer
 
61
21226
 
Hasso Tepper
 
59
772
 
Till Adam
 
58
1782
 
George Staikos
 
53
4127
 
Stefan Asserhäll
 
53
1645
 
Chris Howells
 
50

Internationalization (i18n) Status

Language Percentage Complete
British English (en_GB)
 
99.78%
Swedish (sv)
 
98.26%
Portuguese (pt)
 
95.74%
Danish (da)
 
94.14%
Estonian (et)
 
93.12%
Spanish (es)
 
90.88%
French (fr)
 
90.52%
Italian (it)
 
89.98%
Dutch (nl)
 
89.87%
Serbian (sr)
 
89.48%

Bug Killers

Person Bugs Closed
Stephan Kulow
 
63
George Staikos
 
42
Aaron J. Seigo
 
38
Tom Albers
 
22
Tobias Koenig
 
20
Scott Wheeler
 
15
Tommi Tervo
 
12
Luboš Luňák
 
9
Stephan Binner
 
8
Ingo Klöcker
 
8

No commits found

Thanks for reading the KDE Commit-Digest!