Hi,
Please exclude KTimeTracker.
Thanks!
On Sun, Jan 29, 2023 at 10:29 AM Nate Graham 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 communi
On zondag 29 januari 2023 10:29:10 CET Nate Graham wrote:
> get triaged
The problem is that the bug gardening process does no triaging, it asks
reporters to triage.
Halla Rempt
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
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
Hello,
> Just to clarify, should we just exclude Falkon from bug report
> gardening or also from merge request gardening too?
>
> Merge request gardening is pinging MRs with no activity for 30 days,
> then closing if there is no response even two months after the ping
> message.
Good idea, I wo
Just to clarify, should we just exclude Falkon from bug report
gardening or also from merge request gardening too?
Merge request gardening is pinging MRs with no activity for 30 days,
then closing if there is no response even two months after the ping
message.
On Sun, Jan 29, 2023 at 1:18 PM Just
Hi Juraj,
Of course we are happy to exclude Falkon from the list.
Regards,
Justin
On 28/1/23 23:45, Juraj Oravec wrote:
Hello,
Exclusions so far:
- okteta
- krita
- any bug reported by sit...@kde.org
Thanks again for the feedback!
Can you also add Falkon to the exclusion list?
There are n
Hello,
> Exclusions so far:
> - okteta
> - krita
> - any bug reported by sit...@kde.org
>
> Thanks again for the feedback!
Can you also add Falkon to the exclusion list?
There are not that many bugs nor people working on it and at the moment
it is easy to browse the bugs.
Also I do not know if
He mentioned that the activity he was getting on the reports was just
noise to him and was ignoring them. So instead of causing more noise for
him, I have excluded reports made by him. If he'd like to continue
receiving them I'm happy to work on them.
On 28/1/23 08:51, Neal Gompa wrote:
On Fr
On Fri, Jan 27, 2023 at 4:57 PM Justin Zobel wrote:
>
> 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 prod
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
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 user
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 commu
On 1/19/23 02:35, Nicolas Fella wrote:> Properly cleaning up old
bugreports is important. However, it requires
some level of care and expertise to judge whether a bugreport is still
useful. Judging by the volume of bugreports that is pinged with the same
copy&paste message this care is not appli
Hello folks,
I did approve this initiative and I do think there's value to it, but of
course we can definitely have this discussion in the open and tweak its
parameters, or end it if we think it's destroying more value than it's
creating.
I totally agree with Nicolas that in an ideal world,
velopers. 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.
>> >
>> > Regards,
>> >
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.
> >
> > Regards,
> >
> > Justin
> >
> Don't get me wr
f cleaning up bugs.
But we do need to handle this with a lot of care to avoid it backfiring.
Cheers
Nico
On 19/1/23 11:05, Nicolas Fella wrote:
Hi,
can we please put the effort of "gardening" old bugreports on hold until
we figured out whether this is actually something we want to
We can do that but not all developers use a KDE email address.
On Thu, 19 Jan 2023, 9:15 pm AnnoyingRains, wrote:
> Actually, what if we just ignore reports that come from a *@kde.org email
> address?
>
> On Thu, 19 Jan 2023 at 9:42 pm, Justin Zobel
> wrote:
>
>> I'll have a look when I'm back
Actually, what if we just ignore reports that come from a *@kde.org email
address?
On Thu, 19 Jan 2023 at 9:42 pm, Justin Zobel wrote:
> I'll have a look when I'm back at my PC and see if I can exclude bugs
> reported by you.
>
> On Thu, 19 Jan 2023, 8:57 pm Harald Sitter, wrote:
>
>> On Thu, J
I'll have a look when I'm back at my PC and see if I can exclude bugs
reported by you.
On Thu, 19 Jan 2023, 8:57 pm Harald Sitter, wrote:
> On Thu, Jan 19, 2023 at 4:05 AM Justin wrote:
> > The gardening team aims to find out if the bug reports are still
> > relevant by involving the users who
On Thu, Jan 19, 2023 at 4:05 AM Justin wrote:
> 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.
FWIW that probably doesn't work nearly as well as one would hope when
the user is a develo
;>> > I am not simply closing bugs, so I do take offense that care is not
>>> applied.
>>> >
>>> > 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
t;
> > > I am not simply closing bugs, so I do take offense that care is not
> > applied.
> > >
> > > 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
>
t; > more people in sorting old bugs individually as it is clearly not a
> > priority right now for the majority.
> >
> > Regards,
> >
> > Justin
> >
> > On 19/1/23 11:05, Nicolas Fella wrote:
> > > Hi,
> > >
> > > can we please
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.
>
> Regards,
>
> Justin
>
> On 19/1/
ed 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.
Regards,
Justin
On 19/1/23 11:05, Nicolas Fella wrote:
Hi,
can we please put the effort of "gardening" old
Am 19.01.23 um 01:35 schrieb Nicolas Fella:
Hi,
can we please put the effort of "gardening" old bugreports on hold until
we figured out whether this is actually something we want to do? Several
people already expressed concerns about this.
Improperly applied such mass changes can do
Hi,
can we please put the effort of "gardening" old bugreports on hold until
we figured out whether this is actually something we want to do? Several
people already expressed concerns about this.
Improperly applied such mass changes can do more harm than good. We may
close bugreport
29 matches
Mail list logo
