Cristian Tibirna has written up a summary of the KDE Three Meeting, held in Nürnberg, Germany from Febuary 25 - March 4, 2002. Through the commitment of a group of active KDE developers (group picture, thumbnails 1, thumbnails 2), a large number of bugs were fixed, promising to make 3.0 KDE's best-tested and most stable .0 release yet. Thanks to all the developers for their great work, and to Cristian for the summary.
Wasn't the meeting in Trysil, Norway, before the release of KDE 2.0 called KDE Three?
Shouldn't this be called KDE Four then?
That was called KDE Three Beta :)
I'm sure I remember reading on one of the *-devel lists that there was a system in place at KDE Three which considerably sped up the time it took to recompile the KDE code.
Was this system Doozer?
If not, what was used?
What kind of hardware was it running on?
And about how long did it take to compile a base system from scratch (e.g. qt-copy + arts + kdelibs + kdebase)?
Go ahead: make me jealous!
No, it was a tool developed by TrollTech, teambuilder, which is probably going to be a closed-source commercial tool (they've got to make a living)...
I'm still hoping KDE developers could use a free version of that tool, e.g. with machine-related license numbers to prevent redistribution (like Insure did). It's only useful with a bunch of machines connected together, obviously.
How many of the programmers there were using KDevelop?
And how many used non-KDE programs for hacking?
I'm just curious... ;-)
Mostly vi and xemacs, IIRC :} Oh and I remember some kate and nedit users.
do I suck
It's funny how two people can take the same statistic - the large large number of commits during the meeting - and see it as evidence of something different.
Not really. Some people are optimists, some people are pessimists, some people are realists and others just like to stir shit up. Given that variety among people, it is not suprising at all that different individuals will interpret the results of the meeting in different ways. Fortunately we don't need to rely on forcasts and interpretations, since we will know for certain how useful everything really was when KDE 3.0 is released.
The danger of prognostication is that the future may prove you wrong.
Danger? My *goal* was that by writing what I wrote, that things would change (oh, like the release slipping a great deal as it has), and that the changes would make me wrong.
AFAIR there where just developer on the meeting. Maybe usability (which is imhbo the reason of making a gui) would from a bunch of "normal" users. . .
Who are those guys kneeling on the floor? The users?
There's only one that I can recognize on the floor : David Faure, laughing in the middle...
group.jpg is not broken/has all names.
No, it seems to be missing a few names of those in the upper row.
(I have a sneaking suspicion I've posted this before... I hope not) Does the latest KHTML CVS code render vBulletins correctly? KDE2.0 used to but it's been broken ever since KDE2.1.
And, sorry for being lazy but my computer sucks and I dont want to tie up half a Gb of disk space and eight hours waiting for the CVS to compile. I spend a lot of time on vBulletins... a fix would be much appreciated. (try reading a thread on the vbulletin.com forum if you want an example; compare with what it looks like in Mozilla)
You don't have to checkout CVS or program. What you do have to do is post a proper bug report via the standard bugs.kde.org interface. And, even better, you should filter out the vBulletins site down to the tags/script that isn't working. Then and only then can these people put a finger on something.
Well, if I have to compile Qt3 then KDE3 base and libs from source then this is how much it takes up; I'd use the debian Qt3 package but word has it that's broken. I can't really submit a bug report if I can't even check the error is still there, best I can do is to perhaps trim out the offending HTML code to an example and then offer a comparison with say the Mozilla rendering (unless it's already been fixed...)