Introduction and Bug of the Month

[AnnoyingRains]

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> wrote:

> Hello Kyle,
>
> Yes, that sounds like a good idea.
> 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>> 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>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>> 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> 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>>), 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.
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-gardening/attachments/20221206/13340233/attachment.htm>