Introduction and Bug of the Month
Nate Graham
nate at kde.org
Thu Dec 8 20:14:22 GMT 2022
Sounds good, let's do it!
Nate
On 12/7/22 23:27, AnnoyingRains wrote:
> Draft 2, hopefully quite a bit shorter
>
> - - -
>
> Happy New Year KDE Developers!
>
> To celebrate the new year, the KDE Gardening team would like to
> reintroduce Bug of the Month, everyone’s favourite monthly bug-related
> KDE programme! (Although that might be due to a lack of competition…)
>
> This month (January 2023)‘s bug is ID 391905:
> https://bugs.kde.org/show_bug.cgi?id=391905
> <https://bugs.kde.org/show_bug.cgi?id=391905>
>
> ALL developers are invited (and encouraged) to participate in this
> programme, as, in my opinion, one of the most important things about
> growing an install base in an open source software project like this
> one, is proving that we listen to and work for our community.
>
> Far too many long-standing bugs exist in KDE software, and the last
> thing a user wants to see when trying to find a solution to an issue
> they are having, is a bug report that has seemingly been ignored by KDE
> developers for years on end. This is frustrating as an end user, and
> causes many to give up on the project entirely, losing us market share.
>
> If you’re wondering how this programme is different from the 15 minute
> bugs programme hosted by Nate Graham:
> * bug of the month is one bug per month, where 15 minute bugs may be many
> * the bugs may **not** be visible within 15 minutes of hitting the desktop
> * bug of the month has an emphasis on long-standing issues.
> * both affect a large amount of users
>
> Well then, thanks for reading right to the end, and again, happy new
> year! :)
>
> - Kye Potter, KDE Gardening
>
> On Thu, 8 Dec 2022 at 4:36 pm, Nate Graham <nate at kde.org
> <mailto:nate at kde.org>> wrote:
>
> I'd say condense it a bit if you can; people are more likely to get to
> the end if it's not so long. :)
>
> Nate
>
>
> On 12/6/22 22:20, AnnoyingRains wrote:
> > Great, let’s do that, and relaunch the programme on 1/1/2023 at
> 12:00 am
> > (ish) UTC.
> >
> > I say UTC as KDE is international, so using the international
> standard
> > for time makes sense.
> >
> > I have a rough draft of the announcement we could post to the
> > development mailing list below:
> >
> > –––
> >
> > Happy New Year KDE Developers!
> >
> > To celebrate the new year, the KDE Gardening team would like to
> > reintroduce Bug of the Month, everyone’s favourite monthly
> bug-related
> > KDE programme! (Although that might be due to a lack of competition…)
> >
> > For those of you who have been with us for a while, you might
> remember
> > that the last Bug of the Month was back in February 2016(!), but
> we are
> > planning to bring this programme back into action by kickstarting it
> > with this bug:
> > https://bugs.kde.org/show_bug.cgi?id=391905
> <https://bugs.kde.org/show_bug.cgi?id=391905>
> > <https://bugs.kde.org/show_bug.cgi?id=391905
> <https://bugs.kde.org/show_bug.cgi?id=391905>>
> >
> > ALL developers are invited (and encouraged) to participate in this
> > programme, as, in my opinion, one of the most important things about
> > growing an install base in an open source software project like this
> > one, is proving that we listen and work for our community.
> >
> > Also, fixing old bugs that affect many users, often gains us
> positive
> > press, like here:
> > https://youtu.be/Bxlf9v-SWW4 <https://youtu.be/Bxlf9v-SWW4>
> <https://youtu.be/Bxlf9v-SWW4 <https://youtu.be/Bxlf9v-SWW4>> . Note
> how
> > positive this is, even though the bug was actually a feature request!
> >
> > Far too many long-standing bugs exist in KDE software, and the last
> > thing a user wants to see when trying to find a workaround for a
> bug or
> > weird behaviour, is a bug report that has seemingly been ignored
> by KDE
> > developers for years. This experience is very frustrating as an end
> > user, and causes many to give up on the project entirely, losing us
> > market share.
> >
> > In case you’re wondering how this programme is different from the 15
> > minute bugs programme hosted by Nate Graham, this programme is
> only one
> > bug per month, where the bugs may not be visible within 15
> minutes of
> > hitting the desktop, but still affect a large amount of users,
> and with
> > an emphasis on long-standing issues.
> >
> > Well then, thanks for reading right to the end, and again, happy new
> > year! :)
> >
> > - Kye Potter, KDE Gardening
> >
> >
> > On Wed, 7 Dec 2022 at 2:20 pm, Nate Graham <nate at kde.org
> <mailto:nate at kde.org>
> > <mailto:nate at kde.org <mailto:nate at kde.org>>> wrote:
> >
> > 1 is clearly better; let's do that. I actually looked into it
> a few
> > months ago but got demoralized by the complexity of the code,
> but I'm
> > not really a real engineer. Maybe I'll give it a shot again.
> >
> > Nate
> >
> >
> >
> > On 12/6/22 19:38, AnnoyingRains wrote:
> > > Good points, we could use this (much more minor) bug:
> > > https://bugs.kde.org/show_bug.cgi?id=391905
> <https://bugs.kde.org/show_bug.cgi?id=391905>
> > <https://bugs.kde.org/show_bug.cgi?id=391905
> <https://bugs.kde.org/show_bug.cgi?id=391905>>
> > > <https://bugs.kde.org/show_bug.cgi?id=391905
> <https://bugs.kde.org/show_bug.cgi?id=391905>
> > <https://bugs.kde.org/show_bug.cgi?id=391905
> <https://bugs.kde.org/show_bug.cgi?id=391905>>> instead. It could easily
> > > be fixed in a month, as there are two ways to handle this bug:
> > >
> > > 1: add a trash can icon to the global themes menu (just
> like how
> > there
> > > is one in the other menus)
> > >
> > > 2: rename the "Get New Global Themes" button to "Install
> and Manage
> > > Global Themes"
> > >
> > > On Wed, Dec 7, 2022 at 11:57 AM Nate Graham <nate at kde.org
> <mailto:nate at kde.org>
> > <mailto:nate at kde.org <mailto:nate at kde.org>>
> > > <mailto:nate at kde.org <mailto:nate at kde.org>
> <mailto:nate at kde.org <mailto:nate at kde.org>>>> wrote:
> > >
> > > I think it depends on how we want to conceptualize
> this. The
> > harder the
> > > bug is, the more time we'll need to budget for it, and the
> > bigger the
> > > risk that it doesn't get done--which is just the
> status quo,
> > so I guess
> > > not that big of a risk, except for maybe demoralizing
> people
> > and making
> > > the initiative seem like a failure.
> > >
> > > FWIW I think the bugs for the 15-minute bug initiative
> > > (https://tinyurl.com/plasma-15-minute-bugs
> <https://tinyurl.com/plasma-15-minute-bugs>
> > <https://tinyurl.com/plasma-15-minute-bugs
> <https://tinyurl.com/plasma-15-minute-bugs>>
> > > <https://tinyurl.com/plasma-15-minute-bugs
> <https://tinyurl.com/plasma-15-minute-bugs>
> > <https://tinyurl.com/plasma-15-minute-bugs
> <https://tinyurl.com/plasma-15-minute-bugs>>>) are more suitable for the
> > > monthly approach, as each of these could definitely
> get done
> > in less
> > > than a month.
> > >
> > > Perhaps in addition to "bug of the month" we could do
> another
> > thing for
> > > bigger and harder bugs.
> > >
> > > Nate
> > >
> > >
> > > On 12/5/22 23:28, AnnoyingRains wrote:
> > > > Perhaps we could switch to “bug of the quarter”
> instead?
> > As most
> > > of the
> > > > bugs that are notable enough to be a serious hassle or
> > annoyance
> > > for a
> > > > large amount of users might not be suitable for one
> month,
> > as you
> > > > pointed out.
> > > >
> > > > Although I feel that “bug of the quarter” doesn’t
> sound as
> > > exciting, or
> > > > possibly even motivating enough to get devs on board.
> > Perhaps we
> > > could
> > > > create a section on the (would need to be created)
> Bug of the
> > > Quarter
> > > > wiki page, that lists all contributors who directly
> > contributed
> > > to the
> > > > patch, if there is more than one, of course.
> > > >
> > > > Other than that, perhaps just an email to the KDE dev
> > mailing list
> > > > congratulating them and announcing the next bug?
> That could
> > > encourage
> > > > people.
> > > >
> > > > On Tue, 6 Dec 2022 at 4:01 pm, Nate Graham
> <nate at kde.org <mailto:nate at kde.org>
> > <mailto:nate at kde.org <mailto:nate at kde.org>>
> > > <mailto:nate at kde.org <mailto:nate at kde.org>
> <mailto:nate at kde.org <mailto:nate at kde.org>>>
> > > > <mailto:nate at kde.org <mailto:nate at kde.org>
> <mailto:nate at kde.org <mailto:nate at kde.org>>
> > <mailto:nate at kde.org <mailto:nate at kde.org>
> <mailto:nate at kde.org <mailto:nate at kde.org>>>>> wrote:
> > > >
> > > > Hello Kyle,
> > > >
> > > > Yes, that sounds like a good idea.
> > > > https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>
> > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>>
> > > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>
> > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>>>
> > > > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>
> > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>>
> > > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>
> > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>>>> should also be quite a
> > > > challenge! I think for something like this we would
> > need to leave
> > > > plenty
> > > > of time for people technically capable of
> working on it to
> > > show up.
> > > >
> > > > Nate
> > > >
> > > >
> > > > On 12/4/22 04:40, AnnoyingRains wrote:
> > > > > Me again, we missed December, it would probably
> > have been too
> > > > busy for
> > > > > most devs to work on it anyway, but perhaps
> we could
> > > relaunch this
> > > > > program on 1/1/2023 as a new year’s thing?
> > > > >
> > > > > - Kye Potter (same person as
> AnnoyingRains,I’m slowly
> > > switching
> > > > all my
> > > > > KDE activities over to my real name)
> > > > >
> > > > > On Sun, 27 Nov 2022 at 10:13 am, AnnoyingRains
> > > > <annoyingrain5 at gmail.com
> <mailto:annoyingrain5 at gmail.com>
> > <mailto:annoyingrain5 at gmail.com
> <mailto:annoyingrain5 at gmail.com>> <mailto:annoyingrain5 at gmail.com
> <mailto:annoyingrain5 at gmail.com>
> > <mailto:annoyingrain5 at gmail.com
> <mailto:annoyingrain5 at gmail.com>>>
> > > <mailto:annoyingrain5 at gmail.com
> <mailto:annoyingrain5 at gmail.com>
> > <mailto:annoyingrain5 at gmail.com
> <mailto:annoyingrain5 at gmail.com>> <mailto:annoyingrain5 at gmail.com
> <mailto:annoyingrain5 at gmail.com>
> > <mailto:annoyingrain5 at gmail.com
> <mailto:annoyingrain5 at gmail.com>>>>
> > > > > <mailto:annoyingrain5 at gmail.com
> <mailto:annoyingrain5 at gmail.com>
> > <mailto:annoyingrain5 at gmail.com <mailto:annoyingrain5 at gmail.com>>
> > > <mailto:annoyingrain5 at gmail.com
> <mailto:annoyingrain5 at gmail.com> <mailto:annoyingrain5 at gmail.com
> <mailto:annoyingrain5 at gmail.com>>>
> > > > <mailto:annoyingrain5 at gmail.com
> <mailto:annoyingrain5 at gmail.com>
> > <mailto:annoyingrain5 at gmail.com <mailto:annoyingrain5 at gmail.com>>
> > > <mailto:annoyingrain5 at gmail.com
> <mailto:annoyingrain5 at gmail.com>
> > <mailto:annoyingrain5 at gmail.com
> <mailto:annoyingrain5 at gmail.com>>>>>> wrote:
> > > > >
> > > > > Hello again, just realised my last email
> only
> > had Nate
> > > in the
> > > > “to”
> > > > > field, hopefully this one works better.
> Sorry
> > if this
> > > creates a
> > > > > duplicate somewhere.
> > > > >
> > > > > Original email:
> > > > >
> > > > > To get the word out, I suggest we
> continue to
> > announce new
> > > > bugs of
> > > > > the month on the kde-devel mailing list
> and on
> > Planet
> > > KDE. Other
> > > > > than that, I don't really know of any other
> > communications
> > > > platforms
> > > > > we have with developers.
> > > > > Other than just asking nicely and
> encouraging devs
> > > from different
> > > > > projects to give the bug a shot, I don't
> think
> > there is
> > > > really much
> > > > > more we can do.
> > > > >
> > > > > For an easier bug to patch, perhaps
> > > > > https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>
> > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>>
> > > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>
> > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>>>
> > > > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>
> > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>>
> > > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>
> > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>>>>
> > > > >
> <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>
> > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>>
> > > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>
> > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>>>
> > > > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>
> > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>>
> > > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>
> > <https://bugs.kde.org/show_bug.cgi?id=408919
> <https://bugs.kde.org/show_bug.cgi?id=408919>>>>>would work, it's not
> > > > > quite as long standing as the other bug, but
> > still an
> > > annoying
> > > > > usability issue with core functionality.
> > > > >
> > > > > On Fri, 25 Nov 2022 at 3:51 pm, Nate Graham
> > > <nate at kde.org <mailto:nate at kde.org>
> <mailto:nate at kde.org <mailto:nate at kde.org>> <mailto:nate at kde.org
> <mailto:nate at kde.org>
> > <mailto:nate at kde.org <mailto:nate at kde.org>>>
> > > > <mailto:nate at kde.org <mailto:nate at kde.org>
> <mailto:nate at kde.org <mailto:nate at kde.org>>
> > <mailto:nate at kde.org <mailto:nate at kde.org>
> <mailto:nate at kde.org <mailto:nate at kde.org>>>>
> > > > > <mailto:nate at kde.org
> <mailto:nate at kde.org> <mailto:nate at kde.org <mailto:nate at kde.org>>
> > <mailto:nate at kde.org <mailto:nate at kde.org>
> <mailto:nate at kde.org <mailto:nate at kde.org>>>
> > > <mailto:nate at kde.org <mailto:nate at kde.org>
> <mailto:nate at kde.org <mailto:nate at kde.org>>
> > <mailto:nate at kde.org <mailto:nate at kde.org>
> <mailto:nate at kde.org <mailto:nate at kde.org>>>>>> wrote:
> > > > >
> > > > > Hello AnnoyingRains,
> > > > >
> > > > > Thanks for wanting to get involved
> with the
> > Gardening
> > > > team! It's
> > > > > a small
> > > > > team right now and can rally benefit
> from more
> > > members.
> > > > >
> > > > > https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>
> > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>>
> > > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>
> > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>>>
> > > > >
> <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>
> > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>>
> > > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>
> > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>>>> Would be quite a
> > > > > challenge.
> > > > > Implementing it properly can only
> really be
> > done
> > > in the
> > > > Wayland
> > > > > session,
> > > > > and even then, it's quite
> complicated. Of
> > the people I
> > > > can think
> > > > > of who
> > > > > would be definitely capable of
> implementing the
> > > feature,
> > > > all of
> > > > > them are
> > > > > super busy right now. So I doubt it
> could
> > get done
> > > in a
> > > > month,
> > > > > to be
> > > > > honest. But... maybe I'm wrong! One
> of the best
> > > ways to
> > > > get things
> > > > > moving is simply to care about them,
> > publicize the
> > > issue, and
> > > > > try to
> > > > > attract developers.
> > > > >
> > > > > Do you have ideas for how we can get the
> > word out
> > > here and
> > > > > generate buzz
> > > > > surrounding it?
> > > > >
> > > > > Nate
> > > > >
> > > > >
> > > > > On 11/23/22 22:18, AnnoyingRains
> Games wrote:
> > > > > > Hello, I am AnnoyingRains, a
> brand new
> > > contributor to KDE
> > > > > (and also new
> > > > > > to mailing lists).
> > > > > > I have been using KDE software
> (notably
> > Plasma,
> > > Konsole,
> > > > > Dolphin, KDE
> > > > > > Partition Manager and Kwrite) on my
> > laptop for
> > > over a year
> > > > > now (and
> > > > > > loving it), and I think now is
> finally
> > time for
> > > me to give
> > > > > back to the
> > > > > > community.
> > > > > >
> > > > > > I found the gardening team on the
> "Get
> > > Involved" page, and
> > > > > when looking
> > > > > > through the things that the team
> does, I
> > found
> > > Bug of the
> > > > > Month, a bug
> > > > > > fixing effort that hasn't been in
> place
> > since 2015.
> > > > > > I suggest we bring this programme
> back
> > into action.
> > > > > >
> > > > > > I believe that a good Bug of the
> Month
> > is a bug
> > > that
> > > > not only
> > > > > affects a
> > > > > > large amount of people, but one that
> > makes KDE look
> > > > bad, or the
> > > > > > developers look lazy for not
> fixing it,
> > and I
> > > believe
> > > > we have
> > > > > a good
> > > > > > contender for the first bug of
> the month in
> > > over 6 years.
> > > > > >
> > > > > > Bug 15329,
> > > (https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>
> > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>>
> > > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>
> > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>>>
> > > > >
> <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>
> > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>>
> > > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>
> > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>>>>
> > > > > >
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>
> > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>>
> > > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>
> > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>>>
> > > > >
> <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>
> > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>>
> > > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>
> > > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>
> > <https://bugs.kde.org/show_bug.cgi?id=15329
> <https://bugs.kde.org/show_bug.cgi?id=15329>>>>>>), is a great
> > > > > contender for
> > > > > > this. The bug is over 22 years
> old, and
> > can cause
> > > > > seemingly-broken
> > > > > > behaviour. If a new user sees
> this and
> > attempts
> > > to find a
> > > > > solution for
> > > > > > this annoying issue, then they
> will find
> > this
> > > ancient bug
> > > > > report. People
> > > > > > usually don't react to 22+ year
> old reports
> > > well, so
> > > > this may
> > > > > cause them
> > > > > > to choose to use a competing product
> > instead of
> > > KDEs, and
> > > > > make KDE look bad.
> > > > > >
> > > > > > I have no idea how to sign off an
> email to a
> > > mailing
> > > > list, so
> > > > > I'll just
> > > > > > cut it off here.
> > > > >
> > > >
> > >
> >
>
More information about the Kde-gardening
mailing list