Linked by Eugenia Loli on Fri 8th Dec 2006 00:15 UTC, submitted by Philipp Esselbach
Gnome GNOME 2.17.3 has been released: "This is our third development release on the road towards GNOME 2.18.0, which will be released in March 2007. You all know what you have to do now. Go download it. Go compile it. Go test it. And go hack on it, document it, translate it, fix it."
Thread beginning with comment 189485
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: bah
by Mitarai on Fri 8th Dec 2006 01:10 UTC in reply to "RE: bah"
Mitarai
Member since:
2005-07-28

I aggree thinks are weird in the OSS I did the same with KDE with the same results.

Reply Parent Score: 1

RE[3]: bah
by Daniel Borgmann on Fri 8th Dec 2006 02:55 in reply to "RE[2]: bah"
Daniel Borgmann Member since:
2005-07-08

It's weird that hobby developers sometimes have other things to do than bug triaging or reviewing patches? I guess writing the software for you just isn't enough. :/

Most maintainers do the best job they can, but in the end it's entirely their choice how much effort they put into it. Everyone who thinks they would do a better job should write their own successful software project and prove it.

Reply Parent Score: 5

RE[4]: bah
by tux68 on Fri 8th Dec 2006 03:36 in reply to "RE[3]: bah"
tux68 Member since:
2006-10-24

Daniel,

I'm an avid Gnome user.. haven't used anything else in a few years now, but I think your answer excusing the Gnome developers from responding to good bug reports is short sited. Sure, nobody can _demand_ that developers give a hoot about bug reports... but it's in the developers best interest if they really want to produce something better.

If you set up a bug reporting system, and everyone is conditioned to never use it by lack of a useful response.. there's no point in having ever set it up in the first place. Developers will become more and more isolated and the project will suffer.

It would be more useful, to look at the reasons why bugs aren't at least getting an acknowledgment response.. Some of the corporate sponsors, such as Red Hat might find it in their best interest to assign someone the job of monitoring bug reports and at least sending a "thank you" .. if not more. But first they have to see that there is a problem and people who are trying to help are being discouraged from doing so.

Reply Parent Score: 5

RE[4]: bah
by Manuma on Fri 8th Dec 2006 03:41 in reply to "RE[3]: bah"
Manuma Member since:
2005-07-28

This guys is doing them a favor reporting them a failure they should fix, every time I see someone complaining of a failure in [insert open source software name here] some one else comes asking "Did you fill a bug?", I don't see any excuse, if the bug report was duplicated should be tagged like it and not deleted w/o explanation.

I like GNOME and I thank them for the time they spend on it and a way to thank them is to fill bug reports.

Reply Parent Score: 2

RE[3]: bah
by GreatBunzinni on Fri 8th Dec 2006 20:16 in reply to "RE[2]: bah"
GreatBunzinni Member since:
2005-10-31

I did the same with KDE with the same results.

Hold on there. My experience with KDE has been very positive and the last bug report I filed (KOffice) was fixed on the spot and was featured right in the 1.6.1 release. Very nice.

On the other hand, not all bug reports I filed were fixed, nor wish reports. But thats the way it goes. I don't believe it is reasonable to expect that 100% of those reports are tackled.

Reply Parent Score: 2