"Gardening" old bugreports

[Alexander Potashev]

Hi,

Please exclude KTimeTracker.

Thanks!

On Sun, Jan 29, 2023 at 10:29 AM Nate Graham <nate at kde.org> wrote:

> We can turn it off for bugs reported by you, but I'm not sure "I'm
> getting too many emails" is a good reason to turn it off for whole
> products. These products aren't owned by you; they're community property
> and it's important for them to get triaged for the benefit of everyone.
> Nobody wins when Bugzilla fails to reflect an accurate state of reality.
>
> If those products are being actively triaged by you or someone else,
> that's a good reason. But if they're not, and stale bug reports and
> merge requests are piling up, that's a problem that needs to be fixed,
> and ignoring emails or preventing the Gardening team from doing part of
> their job isn't going to fix it.
>
> Nate
>
>
> On 1/29/23 02:23, Carl Schwan wrote:
> > Please exclude from the bug report reminder:
> >
> > koko
> > tokodon
> > kalendar
> > kde.org
> > planet.kde.org
> > www.kde.org
> > season.kde.org
> > KDE Mediawiki
> > and any bug reported by myself
> >
> > as well as the following projects for the MR reminder:
> >
> > koko
> > tokodon
> > kalendar
> > arianna
> > vail
> > arkade
> > basically everything in the websites namespace
> > and any MR created by myself
> >
> > I'm getting already way too many emails and I have an hard time keeping
> up
> > with them so if I can avoid getting more of them, that would be good.
> >
> > Cheers,
> > Carl
> >
> > ------- Original Message -------
> > Le vendredi 27 janvier 2023 à 10:56 PM, Justin Zobel <
> justin.zobel at gmail.com> a écrit :
> >
> >
> >> Thanks for the feedback, everyone.
> >>
> >> Given the distribution of positive vs negative feedback, we plan to
> >> resume automatic bug triage of old non-wishlist bugs that have not
> >> been updated in over 2 years. If you would like to opt your product
> >> out of this initiative because you're able to keep on top of the
> >> manual bug triage work, please let us know and we'll be happy to
> >> accommodate you.
> >>
> >> Exclusions so far:
> >> - okteta
> >> - krita
> >> - any bug reported by sitter at kde.org
> >>
> >> Thanks again for the feedback!
> >>
> >> On Sun, Jan 22, 2023 at 6:10 PM Thomas Baumgart thb at net-bembel.de
> wrote:
> >>
> >>> On Donnerstag, 19. Januar 2023 22:39:45 CET Johannes Zarl-Zierl wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> Am Donnerstag, 19. Jänner 2023, 12:26:08 CET schrieb Nicolas Fella:
> >>>>
> >>>>> Am 19.01.23 um 04:04 schrieb Justin:
> >>>>>
> >>>>>> The gardening team aims to find out if the bug reports are still
> >>>>>> relevant by involving the users who reported them in determining if
> >>>>>> they are still valid. This increases community involvement and helps
> >>>>>> KDE as there isn't anywhere near enough manpower to review the
> >>>>>> thousands upon thousands of bugs that haven't been touched in years.
> >>>>>
> >>>>> Anecdotally many people don't like such automated changes being done
> to
> >>>>> their bugreports that don't actually engage with the content of the
> report.
> >>>>
> >>>> Well, anecdotally you will mostly get feedback from people who don't
> like it.
> >>>> Unless something is exceptionally great, few people will take the
> time to
> >>>> speak out in favor of something that is already happening.
> >>>>
> >>>>>> The bugs that we are interacting with are ones that have not had any
> >>>>>> activity for over 2 years. We are simply trying to reinvigorate
> >>>>>> discussion on those bugs to see if they are still valid. If the user
> >>>>>> does not reply within the standard 30 day period after a bug is set
> to
> >>>>>> NEEDSINFO, it is automatically closed by the Bug Janitor.
> >>>>>>
> >>>>>> I am not simply closing bugs, so I do take offense that care is not
> >>>>>> applied.
> >>>>>
> >>>>> Properly "triaging" old reports requires at least some level of
> >>>>> understanding of the project, codebase etc. I'm afraid there is no
> >>>>> simple solution to that and rule-based approaches aren't good enough.
> >>>>> Even taking things like CONFIRMED status or wishlist priority into
> >>>>> account assumes that these have actually been consistently applied.
> >>>>
> >>>> As a maintainer on a small project, I'm quite happy to get an
> occasional nudge
> >>>> on old reports. Yes, I do occasionally go over old reports to see if
> they are
> >>>> still valid, but having somebody else doing this methodically makes
> sure I
> >>>> don't gloss over some bug that could be closed or fixed.
> >>>>
> >>>> Having this done by someone else without too much internal knowledge
> is an
> >>>> absolute plus in my opinion. After all, if you want to clean up your
> attic,
> >>>> you try to find a helper who does not have the same emotional
> attachment as
> >>>> yourself.
> >>>>
> >>>>>> I will halt it until it is approved by more developers. However if
> it
> >>>>>> is decided that it isn't wanted then the KDE as a whole will need to
> >>>>>> entice more people in sorting old bugs individually as it is clearly
> >>>>>> not a priority right now for the majority.
> >>>>
> >>>> Speaking for KPhotoAlbum, I really appreciate the bugzilla gardening.
> Thank
> >>>> you for doing it!
> >>>
> >>> I can second that for the KMyMoney project. An occasional poke and the
> >>> automated cleanup when no response arrives where it is needed helps a
> lot.
> >>>
> >>> --
> >>>
> >>> Regards
> >>>
> >>> Thomas Baumgart
> >>>
> >>> -------------------------------------------------------------
> >>> With every day I come closer to the grave and learn something new.
> >>> It all happens because I have wandered around too much and stumbled
> into
> >>> the Linux world - which is a fantastic place to be! (Algis Kabaila †)
> >>> -------------------------------------------------------------
>


-- 
Alexander Potashev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20230211/c83d4082/attachment.htm>