Gardening/BugOfTheMonth: Difference between revisions
(Add February BOTM) |
(Update status of bugs) |
||
| Line 3: | Line 3: | ||
Those bugs often raise endless discussions from frustrated users about how KDE developers do not care. The truth is, most developers are not even aware of them, because the issues do not happen on their system. KDE Developers also usually do not read bug tickets for projects they do not maintain. Getting attention of all developers is one part of the effort, by announcing one selected bug on Planet KDE and the KDE developer mailing list monthly. | Those bugs often raise endless discussions from frustrated users about how KDE developers do not care. The truth is, most developers are not even aware of them, because the issues do not happen on their system. KDE Developers also usually do not read bug tickets for projects they do not maintain. Getting attention of all developers is one part of the effort, by announcing one selected bug on Planet KDE and the KDE developer mailing list monthly. | ||
Sometimes the code in question does no longer have a maintainer, or the current maintainer does not have the time or | Sometimes the code in question does no longer have a maintainer, or the current maintainer does not have the time or expertise to address the bug. Sometimes the bug is actually caused by underlying software components, but the KDE code is the only test case developers have, making the bug hard to investigate. Finding someone able to propose changes to underlying components is an additional goal. | ||
BOTM is similar to the "Junior-Jobs" initiative from the KDE Bug Team. But in contrast to Junior-Jobs, which are easy to solve even for newcomers, BOTM bugs are complex to investigate or solve, are buried in hard-to-understand code or in code which has long been unmaintained. They sometimes require deep understanding of underlying components, or require discussion with upstream developers or with distribution packagers. Call them "Senior-Jobs" if you like. | BOTM is similar to the "Junior-Jobs" initiative from the KDE Bug Team. But in contrast to Junior-Jobs, which are easy to solve even for newcomers, BOTM bugs are complex to investigate or solve, are buried in hard-to-understand code or in code which has long been unmaintained. They sometimes require deep understanding of underlying components, or require discussion with upstream developers or with distribution packagers. Call them "Senior-Jobs" if you like. | ||
| Line 20: | Line 20: | ||
|- | |- | ||
|[https://kdepepo.wordpress.com/2015/02/03/february-bug-of-the-month/ 02/2015] | |[https://kdepepo.wordpress.com/2015/02/03/february-bug-of-the-month/ 02/2015] | ||
|style="background-color: # | |style="background-color: #80FF80;"|fixed | ||
|{{Bug|309193}}: Keyboard shortcuts doesn't work if non-english keyboard layout is set before english one | |{{Bug|309193}}: Keyboard shortcuts doesn't work if non-english keyboard layout is set before english one | ||
| | | | ||
| Line 30: | Line 30: | ||
|- | |- | ||
|[https://kdepepo.wordpress.com/2014/11/28/december-bug-of-the-month/ 12/2014] | |[https://kdepepo.wordpress.com/2014/11/28/december-bug-of-the-month/ 12/2014] | ||
|style="background-color: # | |style="background-color: #80FF80;"|Fixed | ||
|{{Bug|288410}}: kde deamon crash on wakeup | |{{Bug|288410}}: kde deamon crash on wakeup | ||
| | | | ||
Revision as of 13:33, 26 July 2020
Bug Of The Month (BOTM) is an effort to get developers from all KDE projects to investigate annoying, but (long) unresolved issues in KDE software.
Those bugs often raise endless discussions from frustrated users about how KDE developers do not care. The truth is, most developers are not even aware of them, because the issues do not happen on their system. KDE Developers also usually do not read bug tickets for projects they do not maintain. Getting attention of all developers is one part of the effort, by announcing one selected bug on Planet KDE and the KDE developer mailing list monthly.
Sometimes the code in question does no longer have a maintainer, or the current maintainer does not have the time or expertise to address the bug. Sometimes the bug is actually caused by underlying software components, but the KDE code is the only test case developers have, making the bug hard to investigate. Finding someone able to propose changes to underlying components is an additional goal.
BOTM is similar to the "Junior-Jobs" initiative from the KDE Bug Team. But in contrast to Junior-Jobs, which are easy to solve even for newcomers, BOTM bugs are complex to investigate or solve, are buried in hard-to-understand code or in code which has long been unmaintained. They sometimes require deep understanding of underlying components, or require discussion with upstream developers or with distribution packagers. Call them "Senior-Jobs" if you like.
How to participate
Every KDE developer is invited to add valuable feedback to the bug ticket or to proposed code changes in ReviewBoard. If you have ideas to solve the issue, create new review requests on ReviewBoard (make sure you add the gardening-team group) and add the link below.
List of BOTM Bugs
| Month | Status | Bug Number and Title | Links |
|---|---|---|---|
| 02/2015 | fixed | Bug #309193: Keyboard shortcuts doesn't work if non-english keyboard layout is set before english one | |
| 01/2015 | Fixed | Bug #271934: kded4 process grows on memory usage (possible leak) | |
| 12/2014 | Fixed | Bug #288410: kde deamon crash on wakeup | |
| 11/2014 | Fixed | Bug #324975: Volume gets restored to 100% after each knotify event | Review Requests: [1] [2] |