Submitted by “This is the listing of the open bugs that are relatively new, around 2.6.22 and up. They are vaguely classified by specific area,” Natalie Protasevich said, posting a current list of bugs each linking to an appropriate bugzilla.kernel.org entry. Andrew Morton reviewed the list, noting ‘no response from developers’ in response to many of the bugs. David Miller pointed out that in some cases this wasn’t true, referring to 46 bug fixes queued in his networking tree and another 10 already pushed upstream, “when someone like me is bug fixing full time, I take massive offense to the impression you’re trying to give especially when it’s directed at the networking. So turn it down a notch Andrew.” Andrew wasn’t convinced, “first we need to work out whether we have a problem. If we do this, then we can then have a think about what to do about it. I tried to convince the 2006 KS attendees that we have a problem and I resoundingly failed. People seemed to think that we’re doing OK.”
No response from developers
…
No response from developers
…
No response from developers
…
I think we might have fixed this.
…
Zero responses from developers
…
One response from a developer
I definitely feel progress here….
*ggg*
Developers, developers, developers.
Developers.
You would feel progress, if you read the whole thread.
Most of the bugs got responses (just not on bugzilla, because many of them migrate from mailing lists to bugzilla). Many have been fixed. Most of the ones that had aren’t fixed or have no responses are new bugs (ie. 24 hours old); or one-off reports that can’t be reproduced (thus are very hard to fix), which filter down to lower on developers’ priority.
Theo “Go f–k yourself your the problem ”
…
Oliver “We have the Best OS , you ae the problem if it don’t work on 99.999% of computers.”
…
No developers to respond …
…
Developer got fired due to incompetence or got a real job at GNU/Linux company and no one filled the post or care about it.
…
No community developer to respond …
…
No developer to work on it because BSD is in Debt …
…
antik is a GNU/Linux problem all by himself :
http://osnews.com/usercomments.php?uid=7529
I seriously prefer the GNU/Linux approach of not responding when they don’t know , to the lies , bulshit , multiple hourly rants cutting in development time , excuse and blaming of other’s the BSD do.
No response from developers should be changed to no one as the budget to affect a full time developer on your problem please send 10k so that we can hire someone to look at it and fix it.
Moulinneuf,
Why are you always *so* venomous about BSD? What did the BSD community ever do to you to deserve the utter hatred of them (there really is no other word) that I see in you. Like you, I prefer Linux, in general. But I respect those who prefer BSD, and/or develop it, and believe that having rivals like *BSD and OpenSolaris gives everyone inventive to do their best. I see it all as a matter of friendly competition. But you do not seem to see it that way at all.
This is a serious query. I know you are not just trolling to get responses. You are consistent in your dislike of all things BSD, and have been for a long time. So, if you care to, would you let us in on *why* you feel the way you do?
Sincerely,
Steve Bergman
sbergman27 :
http://osnews.com/usercomments.php?uid=266
I cant help you more then that , I guess your too uneducated on how the site work to do it on your own. I don’t suscribe to the feeling of the month or undertsand the insanity of you wanting to portray me as anti BSD and having an hatred of BSD.
Telling someone to fix a problem is not a dilsike of someone else , telling it in unpolite ways is also warranted when the 50 polite way did not provide any tangible result and that on top of that the one who as the problem is pointing at your flaws and ridiculizing them and as a delusion that they don’t have any of there own.
Lies, damn lies, and statistics… Seriously, though, I think it’s great that Linux has a maintainer whose hobby is to convince everybody that there’s a looming quality disaster happening in slow motion. Of course there’s a quality problem. That’s just smart people management for a free software project.
Most commercial software companies employ people to do the opposite. A friend of mine once spent a whole summer internship with an unnamed major software vendor finding creative ways to make the PowerPoint slides on quality look less embarrassing.
Leadership is about controlling the stuff that people worry about. The difference between good and bad leaders is what they decide to let their people worry about, a decision which has far-reaching affects on social behavior and economic output.
One can judge the health of a collective by what they’re worrying about. A software development project that’s worrying about the possibility of a gradual deterioration of quality is healthy. Here in America, on the other hand, we’re worried about everything, from the minutia of Dateline NBC to the paranoia of FOX News to the myopia of Washington, and it’s decidedly unhealthy.
http://www.youtube.com/watch?v=AI4QRiyr3Gc
Writing new code (or rewriting existing code) is more fun than fixing bugs.
D’oh.
One of the biggest issues with bugs in the linux kernel is that many kernel developers don’t use and don’t want to use bugzilla, because they say it sucks. And I don’t blame them…..but this means that many bug reports go unnoticed just because developers don’t watch them. Fortunately these days there’re people making list of bugs that try to make developers aware of the problems…this has improved the situation, but it’s just a bandaid…the FOSS community should be able to do better things than bugzilla…
And is not that this is a Linux problem. I’ve reported bugs in GNOME that have gone unnoticed for more than a year (fe., evolution should not ask you to set up an email account when you’re trying to add a calendar event using the gnome clock…a such simple issue has still not been fixed). The Linux developers just are one of the few projects that are apparently trying to improve the situation.
Edited 2007-11-14 19:41
“And is not that this is a Linux problem. I’ve reported bugs in GNOME that have gone unnoticed for more than a year”
And I have an unnoticed patch (my only one). All they need to do is apply it.
“I’ve reported bugs in GNOME that have gone unnoticed for more than a year…”
Some of Gnome’s little quirks and bugs have persisted for years – plural! It’s the same with many large open source projects. Sometimes, in their haste and excitement to shoehorn in new features, the less thrilling bug fixing gets put on the back burner. I point to Beryl and Compiz-Fusion as shining examples of this mentality. Ubuntu gets a whack in this area too as they have been known to let what I’d consider to be show-stopping bugs survive in Gold releases, rather than miss a release deadline. I would much prefer the slow and steady progression of good, clean, strong code than rapidly “improving” code that’s infested with bugs that go long periods before being fixed.
Some of Gnome’s little quirks and bugs have persisted for years – plural! It’s the same with many large open source projects. Sometimes, in their haste and excitement to shoehorn in new features, the less thrilling bug fixing gets put on the back burner. I point to Beryl and Compiz-Fusion as shining examples of this mentality.
What does Beryl and Compiz have to do with this? They are not a part of the GNOME project. Compiz is its own project and has progressed quite nicely since its inception. In fact Compiz was always more focused on code quality over adding new features. This was part of the reason Beryl split from Compiz in the first place. Beryl was more interested in adding features while Compiz was more focused on doing it right.
Compiz is its own project and has progressed quite nicely since its inception. In fact Compiz was always more focused on code quality over adding new features.
There are many many bugs with both Compiz and Beryl, just look on their bug tracker. The backward compatibility should be much better, when last I checked neither Java nor Wine worked properly for example.
Compiz is exactly the chaff Morton described in my opinion. You can’t blame the developers if they tend to fix the network crashes first rather than the eye-candy or bugs related to exotic hardware phenomena.
A matter of priority. Although the picture people outside the inner circle get is possibly bad publicity.
Perhaps time to recruit new blood to debug the lower hanging fruits.
There are many many bugs with both Compiz and Beryl, just look on their bug tracker. The backward compatibility should be much better, when last I checked neither Java nor Wine worked properly for example.
Beryl is no more so looking at their bug tracker is pointless. Compiz itself is still a fairly young project. I use it and the latest version has been virtually bug free for me. The only issue I have come across is with Blender. I haven’t had a problem with Java. As for WINE I couldn’t tell you because I don’t use it on this machine.
Justt goes to show that Linux is no better than Windows. In fact, in the old proven adage of too-many-cooks.. it’s often worse off.
heh as expected, the score on my anti-Linux comment goes down. Is that all the penguin zombies are good at? Burying the sour truth?
“””
“””
No. The scores on your intentionally provocative posts, lacking in constructive value, are getting modded down. You could have made… whatever point you were trying to make… constructively. But you chose not to, since the real point was to attract negative mod points and then pretend to complain about it.
I probably should not have responded at all, but I believe in calling a spade a spade.
No , it just goes to show that no one is willing to work for free on certain problems and that there is a need for getting funding to hire full time people to solve the problem.
Where as with windows there is no public accountability , you are unaware of the list of problem windows as.
Of course the kernel developers don’t want to fix bugs – they all want to work for these big corporations that now own the Linux kernel, lock, stock & barrel. Better to appease these corporations and introduce new code that THEY want in the kernel, than fix outstanding bugs. I mean, hell, fixing bugs means time, and that means less time spent on keeping the big corporations happening.
I’ve said it before, and I’ll keep saying it, I firmly believe the 2.6 kernel tree has been backwards – we no longer have a kernel for the people, but a kernel for big corporations, with the people a non thought of distand 2nd.
Dave
Let me see… the 2.6 Kernel series got more drivers included in a shorter time than any other kernel before, along with the big-iron features.
Therefore I would say, the 2.6 Kernel got better for the desktop, and got better for the server. Both faster than ever. I do not think, that hindering the big corporation’s contributions to go into the kernel would speed up development for desktop user features and drivers, quite the opposite would occur.
Let me see more stuff in the kernel, less developers who care about it, more problems in the end. Quality instead quantity!
“””
“””
And you are wrong. The single largest group of developers of the Linux kernel are unaffiliated. In fact, 29.6% of the lines changed between 2.6.22 and 2.6.23 (actually, rc6) were changed by unaffiliated developers.
http://tinyurl.com/35xtkw