[opensuse] How do bugs get resolved at opensuse?
Answer: They are ignored until the package goes out of support and are then closed with: "We no longer do non-critical <package XYZ> fixes, sorry." https://bugzilla.novell.com/show_bug.cgi?id=415270 Note: the bug was filed: August 7, 2008 p.s. This isn't a slam on Lubos, he does great work, I'm sure this was an auto generated response and I don't want it misunderstood. I just think it is kind of funny and ironic. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
Answer:
They are ignored until the package goes out of support and are then closed with:
"We no longer do non-critical <package XYZ> fixes, sorry."
David, as we are often being told this is a community project, so we have to ask - who is the "we" that is being referred to in the last response in that report? It appears to represent someone with some sort of authority. Where does that authority come from, in a community project? /Per -- Per Jessen, Zürich (-4.3°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, Feb 13, 2010 at 12:57 PM, Per Jessen
David C. Rankin wrote:
Answer:
They are ignored until the package goes out of support and are then closed with:
"We no longer do non-critical <package XYZ> fixes, sorry."
David, as we are often being told this is a community project, so we have to ask - who is the "we" that is being referred to in the last response in that report? It appears to represent someone with some sort of authority. Where does that authority come from, in a community project?
For a package to in the distro I'm sure it has to have a maintainer / packager or a similar team of people. I don't know opensuse's structure that well, but normally the identification of the maintainer / packager is fairly formal so you can figure out who it is if you know where opensuse tracks those things. Once you find that person you have normally found the person who can make support decisions. If you think they are too restricting you can consider taking over responsibility yourself. I know it happens in the kernel every now and then as people come and go. One major example is drivers/ide changed maintainers over the summer. The now current maintainer thought the old maintainer was making too many changes and that it should be treated as legacy stable code instead. The old maintainer said effectively that as long as he was the maintainer he was going to continue improving the code even if it did introduce a failure from time to time, but offered to let the complainer take over. The complainer did, so now we have a new maintainer. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 13 of February 2010, Per Jessen wrote:
David C. Rankin wrote:
Answer:
They are ignored until the package goes out of support and are then closed with:
"We no longer do non-critical <package XYZ> fixes, sorry."
David, as we are often being told this is a community project, so we have to ask - who is the "we" that is being referred to in the last response in that report? It appears to represent someone with some sort of authority. Where does that authority come from, in a community project?
From the maintainership, and, more importantly in this case, from the fact that nobody else is willing to accept the responsibility that comes together with the authority. "We" in that sentence stands for the openSUSE KDE team, which is only a handful people and only two (AFAIK) of those are actual developers capable of fixing bugs, and they have also other responsibilities. In other words, there's only so much we can do. Now, if the "we" you referred to yourself does not stand just for people who only use openSUSE, discuss and complain about it, but you'd like to also consider improving the situation, you can try helping with some of the work required and thus possibly leaving the developers more time to fix the bugs. For example, even just processing the large number of bugreports can take a considerable time, but it doesn't require any advanced skills besides common sense and experience which can be gained over time. See http://en.opensuse.org/KDE/BugSquashing for details. Or, of course, you can get SLED and a support contract for it if you are not satisfied enough with what you get for free. -- Lubos Lunak openSUSE Boosters team, KDE developer l.lunak@suse.cz , l.lunak@kde.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
David C. Rankin -
Greg Freemyer -
Lubos Lunak -
Per Jessen