[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: [Fwd: [Bug 84101] In the KCM,
From:       "George Goldberg" <grundleborg () googlemail ! com>
Date:       2008-11-20 18:08:50
Message-ID: 1aa4e8880811201008j32a18d91wc189020bda46bf7e () mail ! gmail ! com
[Download RAW message or body]

On Thu, Nov 20, 2008 at 5:57 PM, Aaron J. Seigo <aseigo@kde.org> wrote:
> On Thursday 20 November 2008, Daniel Winter wrote:
>> Am Thursday 20 November 2008 07:20:07 schrieb James Richard Tyrer:
>> > Guess that you didn't read the bug either.  I assigned it to myself and
>> > then fixed it.  Strange thing is that even after I assigned it to myself
>> > that someone still insisted on closing it.
>>
>> Well, I think you are right.
>
> it is, of course, absolutely fine for people to fix any bug they wish.
>
>> Although aRts has no maintainer and is not active developed at all, it is
>> still widely used. As long as there are a lot of users there is possible
>> interest to report and also fix such bugs. Some of those users (or distros
>> or it departements who are responsible for KDE 3 setups somehwere) may want
>> to fix such bugs at some point.
>
> and yet nobody has ... it's a nice theory, but a couple years on and it's
> clear that aRts is not only EOL'd in the theory but very much so in practice.
> and that is OK.
>
> there's a difference between using a product and us maintaining it upstream. if
> someone out there is using KDE1, for instance, that doesn't mean we work on it
> upstream.
>
> usage != development, and it's important to be clear to people what our
> development situations are. we are not very good at clearly communicating the
> reality of our development situation and we pay for that in terms of
> downstream screw ups (*cough*Kubuntu LTS*cough*). we're getting a lot better
> at it thanks to the release team (so kudos to that effort!), but should be a
> lot more honest when it comes to things such as what components we actually do
> spend time on. aRts is not one of them.
>
> one thing I discussed with Matt prior to him closing these aRts bugs is to
> ensure that they are closed with a dinstinct resolution status so we can
> easilly retrieve the reports closed as such. so that if by some stroke of
> chance someone appears who wants to work on aRts in a meaningful way, we can
> easily reinstate all the bugs that were closed en masse due to aRts being
> shelved.

This reminds me of a proposal that has been put forward a few times in
the last year or so - to have an UINMAINTAINED state for bugs in
bugs.kde.org. Its pretty simple - bugs that are closed on mass for
this reason are closed as UNMAINTAINED, and so they can easily be
reopened en-masse if someone takes over the maintainership of the
program, yet they don't fill bugzilla queries up with cruft for
everyone else. Imho, it's the best of both worlds.

---
George Goldberg
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]