<div dir="ltr"><div>Good points, we could use this (much more minor) bug: <a href="https://bugs.kde.org/show_bug.cgi?id=391905">https://bugs.kde.org/show_bug.cgi?id=391905</a> instead. It could easily be fixed in a month, as there are two ways to handle this bug:</div><div><br></div><div>1: add a trash can icon to the global themes menu (just like how there is one in the other menus)<br></div><div><br></div><div>2: rename the "Get New Global Themes" button to "Install and Manage Global Themes"<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Dec 7, 2022 at 11:57 AM Nate Graham <<a href="mailto:nate@kde.org">nate@kde.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I think it depends on how we want to conceptualize this. The harder the <br>
bug is, the more time we'll need to budget for it, and the bigger the <br>
risk that it doesn't get done--which is just the status quo, so I guess <br>
not that big of a risk, except for maybe demoralizing people and making <br>
the initiative seem like a failure.<br>
<br>
FWIW I think the bugs for the 15-minute bug initiative <br>
(<a href="https://tinyurl.com/plasma-15-minute-bugs" rel="noreferrer" target="_blank">https://tinyurl.com/plasma-15-minute-bugs</a>) are more suitable for the <br>
monthly approach, as each of these could definitely get done in less <br>
than a month.<br>
<br>
Perhaps in addition to "bug of the month" we could do another thing for <br>
bigger and harder bugs.<br>
<br>
Nate<br>
<br>
<br>
On 12/5/22 23:28, AnnoyingRains wrote:<br>
> Perhaps we could switch to “bug of the quarter” instead? As most of the <br>
> bugs that are notable enough to be a serious hassle or annoyance for a <br>
> large amount of users might not be suitable for one month, as you <br>
> pointed out.<br>
> <br>
> Although I feel that “bug of the quarter” doesn’t sound as exciting, or <br>
> possibly even motivating enough to get devs on board. Perhaps we could <br>
> create a section on the (would need to be created) Bug of the Quarter <br>
> wiki page, that lists all contributors who directly contributed to the <br>
> patch, if there is more than one, of course.<br>
> <br>
> Other than that, perhaps just an email to the KDE dev mailing list <br>
> congratulating them and announcing the next bug? That could encourage <br>
> people.<br>
> <br>
> On Tue, 6 Dec 2022 at 4:01 pm, Nate Graham <<a href="mailto:nate@kde.org" target="_blank">nate@kde.org</a> <br>
> <mailto:<a href="mailto:nate@kde.org" target="_blank">nate@kde.org</a>>> wrote:<br>
> <br>
> Hello Kyle,<br>
> <br>
> Yes, that sounds like a good idea.<br>
> <a href="https://bugs.kde.org/show_bug.cgi?id=408919" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=408919</a><br>
> <<a href="https://bugs.kde.org/show_bug.cgi?id=408919" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=408919</a>> should also be quite a<br>
> challenge! I think for something like this we would need to leave<br>
> plenty<br>
> of time for people technically capable of working on it to show up.<br>
> <br>
> Nate<br>
> <br>
> <br>
> On 12/4/22 04:40, AnnoyingRains wrote:<br>
> > Me again, we missed December, it would probably have been too<br>
> busy for<br>
> > most devs to work on it anyway, but perhaps we could relaunch this<br>
> > program on 1/1/2023 as a new year’s thing?<br>
> ><br>
> > - Kye Potter (same person as AnnoyingRains,I’m slowly switching<br>
> all my<br>
> > KDE activities over to my real name)<br>
> ><br>
> > On Sun, 27 Nov 2022 at 10:13 am, AnnoyingRains<br>
> <<a href="mailto:annoyingrain5@gmail.com" target="_blank">annoyingrain5@gmail.com</a> <mailto:<a href="mailto:annoyingrain5@gmail.com" target="_blank">annoyingrain5@gmail.com</a>><br>
> > <mailto:<a href="mailto:annoyingrain5@gmail.com" target="_blank">annoyingrain5@gmail.com</a><br>
> <mailto:<a href="mailto:annoyingrain5@gmail.com" target="_blank">annoyingrain5@gmail.com</a>>>> wrote:<br>
> ><br>
> > Hello again, just realised my last email only had Nate in the<br>
> “to”<br>
> > field, hopefully this one works better. Sorry if this creates a<br>
> > duplicate somewhere.<br>
> ><br>
> > Original email:<br>
> ><br>
> > To get the word out, I suggest we continue to announce new<br>
> bugs of<br>
> > the month on the kde-devel mailing list and on Planet KDE. Other<br>
> > than that, I don't really know of any other communications<br>
> platforms<br>
> > we have with developers.<br>
> > Other than just asking nicely and encouraging devs from different<br>
> > projects to give the bug a shot, I don't think there is<br>
> really much<br>
> > more we can do.<br>
> ><br>
> > For an easier bug to patch, perhaps<br>
> > <a href="https://bugs.kde.org/show_bug.cgi?id=408919" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=408919</a><br>
> <<a href="https://bugs.kde.org/show_bug.cgi?id=408919" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=408919</a>><br>
> > <<a href="https://bugs.kde.org/show_bug.cgi?id=408919" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=408919</a><br>
> <<a href="https://bugs.kde.org/show_bug.cgi?id=408919" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=408919</a>>>would work, it's not<br>
> > quite as long standing as the other bug, but still an annoying<br>
> > usability issue with core functionality.<br>
> ><br>
> > On Fri, 25 Nov 2022 at 3:51 pm, Nate Graham <<a href="mailto:nate@kde.org" target="_blank">nate@kde.org</a><br>
> <mailto:<a href="mailto:nate@kde.org" target="_blank">nate@kde.org</a>><br>
> > <mailto:<a href="mailto:nate@kde.org" target="_blank">nate@kde.org</a> <mailto:<a href="mailto:nate@kde.org" target="_blank">nate@kde.org</a>>>> wrote:<br>
> ><br>
> > Hello AnnoyingRains,<br>
> ><br>
> > Thanks for wanting to get involved with the Gardening<br>
> team! It's<br>
> > a small<br>
> > team right now and can rally benefit from more members.<br>
> ><br>
> > <a href="https://bugs.kde.org/show_bug.cgi?id=15329" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=15329</a><br>
> <<a href="https://bugs.kde.org/show_bug.cgi?id=15329" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=15329</a>><br>
> > <<a href="https://bugs.kde.org/show_bug.cgi?id=15329" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=15329</a><br>
> <<a href="https://bugs.kde.org/show_bug.cgi?id=15329" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=15329</a>>> Would be quite a<br>
> > challenge.<br>
> > Implementing it properly can only really be done in the<br>
> Wayland<br>
> > session,<br>
> > and even then, it's quite complicated. Of the people I<br>
> can think<br>
> > of who<br>
> > would be definitely capable of implementing the feature,<br>
> all of<br>
> > them are<br>
> > super busy right now. So I doubt it could get done in a<br>
> month,<br>
> > to be<br>
> > honest. But... maybe I'm wrong! One of the best ways to<br>
> get things<br>
> > moving is simply to care about them, publicize the issue, and<br>
> > try to<br>
> > attract developers.<br>
> ><br>
> > Do you have ideas for how we can get the word out here and<br>
> > generate buzz<br>
> > surrounding it?<br>
> ><br>
> > Nate<br>
> ><br>
> ><br>
> > On 11/23/22 22:18, AnnoyingRains Games wrote:<br>
> > > Hello, I am AnnoyingRains, a brand new contributor to KDE<br>
> > (and also new<br>
> > > to mailing lists).<br>
> > > I have been using KDE software (notably Plasma, Konsole,<br>
> > Dolphin, KDE<br>
> > > Partition Manager and Kwrite) on my laptop for over a year<br>
> > now (and<br>
> > > loving it), and I think now is finally time for me to give<br>
> > back to the<br>
> > > community.<br>
> > ><br>
> > > I found the gardening team on the "Get Involved" page, and<br>
> > when looking<br>
> > > through the things that the team does, I found Bug of the<br>
> > Month, a bug<br>
> > > fixing effort that hasn't been in place since 2015.<br>
> > > I suggest we bring this programme back into action.<br>
> > ><br>
> > > I believe that a good Bug of the Month is a bug that<br>
> not only<br>
> > affects a<br>
> > > large amount of people, but one that makes KDE look<br>
> bad, or the<br>
> > > developers look lazy for not fixing it, and I believe<br>
> we have<br>
> > a good<br>
> > > contender for the first bug of the month in over 6 years.<br>
> > ><br>
> > > Bug 15329, (<a href="https://bugs.kde.org/show_bug.cgi?id=15329" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=15329</a><br>
> <<a href="https://bugs.kde.org/show_bug.cgi?id=15329" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=15329</a>><br>
> > <<a href="https://bugs.kde.org/show_bug.cgi?id=15329" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=15329</a><br>
> <<a href="https://bugs.kde.org/show_bug.cgi?id=15329" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=15329</a>>><br>
> > > <<a href="https://bugs.kde.org/show_bug.cgi?id=15329" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=15329</a><br>
> <<a href="https://bugs.kde.org/show_bug.cgi?id=15329" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=15329</a>><br>
> > <<a href="https://bugs.kde.org/show_bug.cgi?id=15329" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=15329</a><br>
> <<a href="https://bugs.kde.org/show_bug.cgi?id=15329" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=15329</a>>>>), is a great<br>
> > contender for<br>
> > > this. The bug is over 22 years old, and can cause<br>
> > seemingly-broken<br>
> > > behaviour. If a new user sees this and attempts to find a<br>
> > solution for<br>
> > > this annoying issue, then they will find this ancient bug<br>
> > report. People<br>
> > > usually don't react to 22+ year old reports well, so<br>
> this may<br>
> > cause them<br>
> > > to choose to use a competing product instead of KDEs, and<br>
> > make KDE look bad.<br>
> > ><br>
> > > I have no idea how to sign off an email to a mailing<br>
> list, so<br>
> > I'll just<br>
> > > cut it off here.<br>
> ><br>
> <br>
</blockquote></div>