Slashdot Mirror

KDE 4.10 gets definitely back into the fun zone. Hunting down bugs is more fun when there are few. The news test environments like Jenkins seem to be helpful, as well as reviewboard and EBN/krazy. Does KDE 4.10 compile with LLVM compiler?

I really like KDE and I believe that it needs to be supported better by distributions. Kubuntu is a mess.

The investments of KDE in code quality and design will pay off. Unfortunately runtime quality was lacking, esp. reg. Plasma crashes in earlier versions. KDE is now in a state where it maturates. Here the SC split in three components really makes a whole lot of sense.

Now all that is left is a web site full of slogans which tells you how to "download" KDE, stupid rebranding, anglo-imperialism, consensus culture.

I want to know how development progresses, how many bugs were fixed last week, how the EBN scores improved, which translations are complete.

I want a website which displays the reported recent plasma crashes. KDEoops

I want a website that explains me a single working methods how to set up a built environment on a free machine.

I want an idea torrent set up for KDE.

I want to see the users get involved to discuss KDE in a open and honest way.

I don't want slogans and empty marketing gibberish. I want better code.

I don't want a code of conduct bullshit, I want management by geeks and hacker ethics.

I want to praise the artists which make KDE great.

Having said that KDE 4.4 is really ok now. It is just two years late. The KDE community was much better in 2000.

I hear your frustration. You'd like Wine to work really well, and you are impatient with the current rate of progress. But implementing Win16/win32/win64 is a shitwad of work, so no matter how fast we go, you'll probably always be impatient. And so will I.

The best way to look at the current experimental DIB engine implementation is as a prototype. If apps work well enough with it, it'll be easier to commit the resources to do a production-quality one.

If patches are rejected, it means there's something wrong with them; good, persistant developers who listen to the feedback and submit small, incremental patches can get them accepted. It's true that it can be frustrating at times, but that's not unique to Wine; gcc and the linux kernel are also frustrating for new contributors. And don't even get me started about gibc :-)

http://www.englishbreakfastnetwork.org/krazy looks great, but a lot of its checks are for C++ specific issues, which Wine doesn't have because it's based on C. Wine is well aware of the benefits of automated testing and code analysis. We do have an automated build and test system, see http://test.winehq.org/ and we're slowly working on getting all the tests green. And we pay attention to Coverity's scans of our source tree. (We also have a patchwatcher, but it's out of action right now because I'm lame.)

If you want to go help raise funds from governmens stuck on win32, please do! I tried to make a little pitch for this at the end of my CeBIT talk last week, see http://kegel.com/cebit But it's hard to get their attention. First, they aren't impressed unless it can run all their apps, and second, the ones that are really serious about getting away from Windows tend to focus on native applications anyway.

So: the grapes really aren't that sour. Dive in and help - and be patient and persistent.

The English Breakfast Network

It helps to find potential problems and also checks for licenses, spelling errors and coding conventions.

Have a look at Krazy, the EBN's code quality checker if you want more info. It detects common spelling errors and suggests the appropriate spelling (US English); it's done via a Perl script IIRC with different modules for the various check types.

From my perspective English Breakfast Network looks like the greatest infrastructure improvement.

For KDE the question is how to attract more developers to the plattform. The answer is of course to remove entrance barriers, e.g. the small annoyances which regularly break stuff and need certain more or less trivial knowledge to fix them.

Cmake has to sides:
a) you have to learn it and it is different from the usual toolchain
b) it solves certain problems.