Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Andrey Loskutov]

https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/959

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov


> Gesendet: Dienstag, 22. März 2022 um 08:56 Uhr
> Von: "Ed Merks" 
> An: platform-dev@eclipse.org
> Betreff: Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse 
> platform projects
>
> Do you have a link to the issue?  Auto-closing continues...

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Ed Merks]

Do you have a link to the issue?  Auto-closing continues...

On 04.03.2022 10:14, Andrey Loskutov wrote:

Hi all,

this is an update on current state.
I consider voting is done now, the results are (sorry if I've missed anyone) 
19:10 for stop current practice.
I think the result is clear and as proposed before, I will continue with 
creating a ticket for the foundation to disable auto-closing bugs for the 
platform.

+1 to stop closing
An Lo
Jö Ku
Th Si
Sa Si
Ch Lä
Al Fe
Si An
Ha We
JF Ma
St Wa
Ed Me
Al Bl
Li Io
Se Za
Ro Th
Ni Ne
Vi Ch
La Sh
Ka Th

-1 to stop closing
Mi Is
Al Ku
Wi Jo
Mi Wi
Th Wa
Ma Bo
Jo Gr
La Vo
Sr La
Ad Po

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov



Gesendet: Donnerstag, 17. Februar 2022 um 09:58 Uhr
Von: "Andrey Loskutov" 
An: "platform-dev" 
Betreff: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform 
projects

Hi all,

this is a follow up on PMC response 
https://www.eclipse.org/lists/platform-dev/msg03319.html

As of today, this bug auto-closing is not active only for JDT project.

The proposal is to switch "off" bug auto-closing for the all Eclipse platform 
projects, including Platform, JDT, PDE und Equinox.
I don't think if we need an additional vote for PDE & Equinox, because the only 
active committers there are same as on the Eclipse platform.

Therefore I would like to start voting to stop auto-closing bugs in bugzilla, 
github, gitlab (or whatever else bug trackers we might use in the future) for 
all Eclipse platform development.

I think it is enough to post your +1 / 0 / -1 as a reply on this mailing list.
Everyone is welcome to vote but binding votes are committers`votes.
I would propose to conclude the vote by the end of the next week (25 February).

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev


___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Wim Jongman]

Thanks for counting. It has been a good discussion.

Cheers, Wim

On Fri, 4 Mar 2022 at 10:14, Andrey Loskutov  wrote:

> Hi all,
>
> this is an update on current state.
> I consider voting is done now, the results are (sorry if I've missed
> anyone) 19:10 for stop current practice.
> I think the result is clear and as proposed before, I will continue with
> creating a ticket for the foundation to disable auto-closing bugs for the
> platform.
>
> +1 to stop closing
> An Lo
> Jö Ku
> Th Si
> Sa Si
> Ch Lä
> Al Fe
> Si An
> Ha We
> JF Ma
> St Wa
> Ed Me
> Al Bl
> Li Io
> Se Za
> Ro Th
> Ni Ne
> Vi Ch
> La Sh
> Ka Th
>
> -1 to stop closing
> Mi Is
> Al Ku
> Wi Jo
> Mi Wi
> Th Wa
> Ma Bo
> Jo Gr
> La Vo
> Sr La
> Ad Po
>
> Kind regards,
> Andrey Loskutov
>
> Спасение утопающих - дело рук самих утопающих
>
> https://www.eclipse.org/user/aloskutov
>
>
> > Gesendet: Donnerstag, 17. Februar 2022 um 09:58 Uhr
> > Von: "Andrey Loskutov" 
> > An: "platform-dev" 
> > Betreff: [platform-dev] Vote to stop bug auto-closing in all Eclipse
> platform projects
> >
> > Hi all,
> >
> > this is a follow up on PMC response
> https://www.eclipse.org/lists/platform-dev/msg03319.html
> >
> > As of today, this bug auto-closing is not active only for JDT project.
> >
> > The proposal is to switch "off" bug auto-closing for the all Eclipse
> platform projects, including Platform, JDT, PDE und Equinox.
> > I don't think if we need an additional vote for PDE & Equinox, because
> the only active committers there are same as on the Eclipse platform.
> >
> > Therefore I would like to start voting to stop auto-closing bugs in
> bugzilla, github, gitlab (or whatever else bug trackers we might use in the
> future) for all Eclipse platform development.
> >
> > I think it is enough to post your +1 / 0 / -1 as a reply on this mailing
> list.
> > Everyone is welcome to vote but binding votes are committers`votes.
> > I would propose to conclude the vote by the end of the next week (25
> February).
> >
> > Kind regards,
> > Andrey Loskutov
> >
> > Спасение утопающих - дело рук самих утопающих
> >
> > https://www.eclipse.org/user/aloskutov
> >
> > ___
> > platform-dev mailing list
> > platform-dev@eclipse.org
> > To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
> >
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
>
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Andrey Loskutov]

Hi all,

this is an update on current state.
I consider voting is done now, the results are (sorry if I've missed anyone) 
19:10 for stop current practice. 
I think the result is clear and as proposed before, I will continue with 
creating a ticket for the foundation to disable auto-closing bugs for the 
platform.

+1 to stop closing
An Lo
Jö Ku
Th Si
Sa Si
Ch Lä
Al Fe
Si An
Ha We
JF Ma
St Wa
Ed Me
Al Bl
Li Io 
Se Za
Ro Th
Ni Ne
Vi Ch
La Sh
Ka Th

-1 to stop closing
Mi Is
Al Ku
Wi Jo
Mi Wi
Th Wa
Ma Bo
Jo Gr
La Vo
Sr La
Ad Po

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov


> Gesendet: Donnerstag, 17. Februar 2022 um 09:58 Uhr
> Von: "Andrey Loskutov" 
> An: "platform-dev" 
> Betreff: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform 
> projects
>
> Hi all,
> 
> this is a follow up on PMC response 
> https://www.eclipse.org/lists/platform-dev/msg03319.html
> 
> As of today, this bug auto-closing is not active only for JDT project.
> 
> The proposal is to switch "off" bug auto-closing for the all Eclipse platform 
> projects, including Platform, JDT, PDE und Equinox.
> I don't think if we need an additional vote for PDE & Equinox, because the 
> only active committers there are same as on the Eclipse platform.
> 
> Therefore I would like to start voting to stop auto-closing bugs in bugzilla, 
> github, gitlab (or whatever else bug trackers we might use in the future) for 
> all Eclipse platform development.
> 
> I think it is enough to post your +1 / 0 / -1 as a reply on this mailing list.
> Everyone is welcome to vote but binding votes are committers`votes.
> I would propose to conclude the vote by the end of the next week (25 
> February).
> 
> Kind regards,
> Andrey Loskutov
> 
> Спасение утопающих - дело рук самих утопающих
> 
> https://www.eclipse.org/user/aloskutov
> 
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/platform-dev
>
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Ed Merks]

Yes, this is indeed an option for the working group to consider. Let's 
see how targeted development works out so that we can expand on such 
success stories...


On 22.02.2022 11:44, Thomas Singer wrote:
Eventually the free ride might come to an end... 


Maybe offering some kind of support contract for companies (for fixing 
their reported bugs) would be an option?



___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Wim Jongman]

> The difference is that that has nothing to do with auto-closing at all.

If the bug that was now worked on was correctly triaged we would have found
the auto-closed bug and reopened that. Point is that even if bugs are
automatically closed, they are not gone.

Anyway, the point is moot. I haven't counted but it looks like the vote
moves towards keeping issues open.

Cheers, Wim
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Thomas Singer]

Eventually the free ride might come to an end... 


Maybe offering some kind of support contract for companies (for fixing 
their reported bugs) would be an option?


--
Best regards,
Thomas Singer
=
syntevo GmbH
www.syntevo.com


On 2022-02-22 10:37, Ed Merks wrote:

Comment below.

On 22.02.2022 09:27, Liviu Ionescu wrote:


On 22 Feb 2022, at 10:42, Karsten Thoms  
wrote:


... but that’s just reality due to lack of resources.
According to the Annual Eclipse Foundation Community Report, in 2021 
the Foundation burnt 7.6 M$, so I would not blame the lack of resources.

Probably the word "burnt" is not really the best choice of words.


The question is how many of the 7.6 went to developers maintaining the 
Eclipse platform.
Funding development on one or more of the hundreds of projects hosted at 
Eclipse is not the role of the Foundation.  The Eclipse IDE Working 
Group is looking to do some targeted development work on some aspects of 
the Platform via its much more limited budget.  Its budget has also 
helped develop the improvements to mature PGP signing implementation in p2.


And generally how to find a solution to fix the bugs, not whether to 
auto-close them or not.


More people and organizations who consume things for free need to 
contribute more time and/or more money.  Eventually the free ride might 
come to an end...


I only raise this issue because I maintain lists and I manage what's in 
those lists, within my own personal resource capacity. I don't want a 
robot to remove things from my lists.  How others manage other parts is 
up to them.  But if more people spent a few hours a month looking at 
lists, that would sure help a lot.  If we don't plan to fix something 
ever, let's close it immediately not after 2 years...





Regards,

Liviu


___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Ed Merks]

Comment below.

On 22.02.2022 09:27, Liviu Ionescu wrote:



On 22 Feb 2022, at 10:42, Karsten Thoms  wrote:

... but that’s just reality due to lack of resources.

According to the Annual Eclipse Foundation Community Report, in 2021 the 
Foundation burnt 7.6 M$, so I would not blame the lack of resources.

Probably the word "burnt" is not really the best choice of words.


The question is how many of the 7.6 went to developers maintaining the Eclipse 
platform.
Funding development on one or more of the hundreds of projects hosted at 
Eclipse is not the role of the Foundation.  The Eclipse IDE Working 
Group is looking to do some targeted development work on some aspects of 
the Platform via its much more limited budget.  Its budget has also 
helped develop the improvements to mature PGP signing implementation in p2.


And generally how to find a solution to fix the bugs, not whether to auto-close 
them or not.


More people and organizations who consume things for free need to 
contribute more time and/or more money.  Eventually the free ride might 
come to an end...


I only raise this issue because I maintain lists and I manage what's in 
those lists, within my own personal resource capacity. I don't want a 
robot to remove things from my lists.  How others manage other parts is 
up to them.  But if more people spent a few hours a month looking at 
lists, that would sure help a lot.  If we don't plan to fix something 
ever, let's close it immediately not after 2 years...





Regards,

Liviu


___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Liviu Ionescu]

> On 22 Feb 2022, at 10:42, Karsten Thoms  wrote:
> 
> ... but that’s just reality due to lack of resources.

According to the Annual Eclipse Foundation Community Report, in 2021 the 
Foundation burnt 7.6 M$, so I would not blame the lack of resources.

The question is how many of the 7.6 went to developers maintaining the Eclipse 
platform.

And generally how to find a solution to fix the bugs, not whether to auto-close 
them or not.


Regards,

Liviu


___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Karsten Thoms]

+1 for stopping auto-close

I understand both sides and I don’t like to have so many bugs unattended, but 
that’s just reality due to lack of resources.
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Lakshmi P Shanmugam]

+1 to stop auto closing

During conference talks and presentations, we usually ask community to 
‘contribute’ bug reports. When they do, closing the bug as WONTFIX, many a 
times without any triage from the project side, gives the impression that we 
don’t value the effort of the ‘contributor’.
As a developer, I think auto closing is only helpful (to me) when there is no 
response for a long time on a bug marked as need-info, otherwise I have to add 
a comment and close it myself.

Thanks & Regards,
Lakshmi P Shanmugam

From: platform-dev  on behalf of Vikas 
Chandra 
Reply to: "Eclipse platform general developers list." 
Date: Tuesday, 22 February 2022 at 8:07 AM
To: "Eclipse platform general developers list." 
Subject: [EXTERNAL] Re: [platform-dev] Vote to stop bug auto-closing in all 
Eclipse platform projects

+1 stop auto closing

Reasons

1)  Marking it as stale helps as the inbox manager/reporter/assignee goes 
or check if the bug is still valid and many times bugs have been
fixed as a result. Only thing is no more than 2-3 bugs per day per component 
should be marked as stale. If 100s of bugs r marked as stale on a single day,
it is counter-productive.

2)  Auto-closing gives the impression “I don’t care”. Mark it stale instead

3)  What does auto-close achieve? I guess “nothing”  apart from 
artificially reducing the bug count. It helps no one.

From: platform-dev  On Behalf Of 
Jean-Francois Maury
Sent: 17 February 2022 16:43
To: Eclipse platform general developers list. 
Subject: [EXTERNAL] Re: [platform-dev] Vote to stop bug auto-closing in all 
Eclipse platform projects

+1 stop auto closing

On Thu, Feb 17, 2022 at 9:58 AM Andrey Loskutov 
mailto:losku...@gmx.de>> wrote:
Hi all,

this is a follow up on PMC response 
https://www.eclipse.org/lists/platform-dev/msg03319.html

As of today, this bug auto-closing is not active only for JDT project.

The proposal is to switch "off" bug auto-closing for the all Eclipse platform 
projects, including Platform, JDT, PDE und Equinox.
I don't think if we need an additional vote for PDE & Equinox, because the only 
active committers there are same as on the Eclipse platform.

Therefore I would like to start voting to stop auto-closing bugs in bugzilla, 
github, gitlab (or whatever else bug trackers we might use in the future) for 
all Eclipse platform development.

I think it is enough to post your +1 / 0 / -1 as a reply on this mailing list.
Everyone is welcome to vote but binding votes are committers`votes.
I would propose to conclude the vote by the end of the next week (25 February).

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

___
platform-dev mailing list
platform-dev@eclipse.org<mailto:platform-dev@eclipse.org>
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev


--

Jeff Maury

Manager, DevTools

Red Hat EMEA<https://www.redhat.com>

jma...@redhat.com<mailto:jma...@redhat.com>
@RedHat<https://twitter.com/redhat>  Red Hat 
<https://www.linkedin.com/company/red-hat>   Red Hat 
<https://www.facebook.com/RedHatInc>
[Image removed by sender.]<https://www.redhat.com>
[Image removed by sender.]<https://redhat.com/summit>

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Vikas Chandra]

+1 stop auto closing

Reasons

  1.  Marking it as stale helps as the inbox manager/reporter/assignee goes or 
check if the bug is still valid and many times bugs have been
fixed as a result. Only thing is no more than 2-3 bugs per day per component 
should be marked as stale. If 100s of bugs r marked as stale on a single day,
it is counter-productive.

  1.  Auto-closing gives the impression “I don’t care”. Mark it stale instead
  2.  What does auto-close achieve? I guess “nothing”  apart from artificially 
reducing the bug count. It helps no one.

From: platform-dev  On Behalf Of 
Jean-Francois Maury
Sent: 17 February 2022 16:43
To: Eclipse platform general developers list. 
Subject: [EXTERNAL] Re: [platform-dev] Vote to stop bug auto-closing in all 
Eclipse platform projects

+1 stop auto closing

On Thu, Feb 17, 2022 at 9:58 AM Andrey Loskutov 
mailto:losku...@gmx.de>> wrote:
Hi all,

this is a follow up on PMC response 
https://www.eclipse.org/lists/platform-dev/msg03319.html

As of today, this bug auto-closing is not active only for JDT project.

The proposal is to switch "off" bug auto-closing for the all Eclipse platform 
projects, including Platform, JDT, PDE und Equinox.
I don't think if we need an additional vote for PDE & Equinox, because the only 
active committers there are same as on the Eclipse platform.

Therefore I would like to start voting to stop auto-closing bugs in bugzilla, 
github, gitlab (or whatever else bug trackers we might use in the future) for 
all Eclipse platform development.

I think it is enough to post your +1 / 0 / -1 as a reply on this mailing list.
Everyone is welcome to vote but binding votes are committers`votes.
I would propose to conclude the vote by the end of the next week (25 February).

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

___
platform-dev mailing list
platform-dev@eclipse.org<mailto:platform-dev@eclipse.org>
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev


--

Jeff Maury

Manager, DevTools

Red Hat EMEA<https://www.redhat.com>

jma...@redhat.com<mailto:jma...@redhat.com>
@RedHat <https://twitter.com/redhat>   Red Hat 
<https://www.linkedin.com/company/red-hat>   Red Hat 
<https://www.facebook.com/RedHatInc>
[https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png]<https://www.redhat.com>
[https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/b53c57d310ace0d754773920434471b7/red-hat-summit-email-150.png]<https://redhat.com/summit>

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Sravan K Lakkimsetti]

-1 from me too.

I do echo McQ’s arguments.

Thanks
Sravan

From: platform-dev  On Behalf Of Lars Vogel
Sent: 17 February 2022 21:36
To: Eclipse platform general developers list. 
Subject: [EXTERNAL] Re: [platform-dev] Vote to stop bug auto-closing in all 
Eclipse platform projects

-1 from me too.

Great summary from Mike

Jonah Graham mailto:jo...@kichwacoders.com>> schrieb am 
Do., 17. Feb. 2022, 16:48:
-1 to stop auto-closing.

McQ's arguments ring true for me.

My personal preference  would prefer a much more aggressive auto-close strategy 
- however I do hear the active committers saying they don't like it.

Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com<http://www.kichwacoders.com>


On Thu, 17 Feb 2022 at 03:58, Andrey Loskutov 
mailto:losku...@gmx.de>> wrote:
Hi all,

this is a follow up on PMC response 
https://www.eclipse.org/lists/platform-dev/msg03319.html

As of today, this bug auto-closing is not active only for JDT project.

The proposal is to switch "off" bug auto-closing for the all Eclipse platform 
projects, including Platform, JDT, PDE und Equinox.
I don't think if we need an additional vote for PDE & Equinox, because the only 
active committers there are same as on the Eclipse platform.

Therefore I would like to start voting to stop auto-closing bugs in bugzilla, 
github, gitlab (or whatever else bug trackers we might use in the future) for 
all Eclipse platform development.

I think it is enough to post your +1 / 0 / -1 as a reply on this mailing list.
Everyone is welcome to vote but binding votes are committers`votes.
I would propose to conclude the vote by the end of the next week (25 February).

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

___
platform-dev mailing list
platform-dev@eclipse.org<mailto:platform-dev@eclipse.org>
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev
___
platform-dev mailing list
platform-dev@eclipse.org<mailto:platform-dev@eclipse.org>
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Nikita Nemkin]

+1 to stop automatic closing, for two reasons:

1. Auto-closing without any developer input creates the perception of
bugs being completely ignored. Reopening a bug might be seen as futile
by the original reporter.
2. Auto-closed bugs are hidden from the developers. It's possible to
dig them up, but inconvenient enough to never happen.

If the situation is so drastic that many bugs in truth will never be
looked at, the users should be warned before they report a bug.
Perhaps even before they download the software.

On Thu, Feb 17, 2022 at 1:58 PM Andrey Loskutov  wrote:
>
> Hi all,
>
> this is a follow up on PMC response 
> https://www.eclipse.org/lists/platform-dev/msg03319.html
>
> As of today, this bug auto-closing is not active only for JDT project.
>
> The proposal is to switch "off" bug auto-closing for the all Eclipse platform 
> projects, including Platform, JDT, PDE und Equinox.
> I don't think if we need an additional vote for PDE & Equinox, because the 
> only active committers there are same as on the Eclipse platform.
>
> Therefore I would like to start voting to stop auto-closing bugs in bugzilla, 
> github, gitlab (or whatever else bug trackers we might use in the future) for 
> all Eclipse platform development.
>
> I think it is enough to post your +1 / 0 / -1 as a reply on this mailing list.
> Everyone is welcome to vote but binding votes are committers`votes.
> I would propose to conclude the vote by the end of the next week (25 
> February).
>
> Kind regards,
> Andrey Loskutov
>
> Спасение утопающих - дело рук самих утопающих
>
> https://www.eclipse.org/user/aloskutov
>
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/platform-dev



--
Best regards,
Nikita Nemkin
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Thomas Singer]

OK, why not close ALL bugs and anyone who cares can reopen the bugs they 
want to get fixed.


Cheers,
Tom


On 2022-02-18 23:08, Adrián Pol wrote:

-1 close pls close

It is a common action used by all, in my opinion

Regards,
apolalca


El 17 feb 2022, a las 9:58, Andrey Loskutov  escribió:

Hi all,

this is a follow up on PMC response 
https://www.eclipse.org/lists/platform-dev/msg03319.html

As of today, this bug auto-closing is not active only for JDT project.

The proposal is to switch "off" bug auto-closing for the all Eclipse platform 
projects, including Platform, JDT, PDE und Equinox.
I don't think if we need an additional vote for PDE & Equinox, because the only 
active committers there are same as on the Eclipse platform.

Therefore I would like to start voting to stop auto-closing bugs in bugzilla, 
github, gitlab (or whatever else bug trackers we might use in the future) for 
all Eclipse platform development.

I think it is enough to post your +1 / 0 / -1 as a reply on this mailing list.
Everyone is welcome to vote but binding votes are committers`votes.
I would propose to conclude the vote by the end of the next week (25 February).

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev




___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Thomas Singer]

+1

On 2022-02-19 12:38, Rolf Theunissen wrote:

Op vr 18 feb. 2022 om 15:54 schreef Mickael Istria :




On Friday, February 18, 2022, Sebastian Zarnekow <
sebastian.zarne...@gmail.com> wrote:

The Bot that does the auto-closing at Eclipse though doesn't give a

heads-up, many tickets are never looked at.

I personally look at all notifications I receive from Bugzilla and react
to auto-close tickets either by taking the decision of not reopening, or by
reopening with extra info, just like it's recommended in the message.
And I'm happy with it bith as a reporter and a committer.



In this case you are a friendly user, so although you are happy with it as
a reporter, it might not be representative of the larger user community.
I get your point of having a reminder to look into a ticket again, It is
only a pity that it takes 2 years to get the reminder to look into an issue
again. As you get a reminder, you did have shown some interest in the bug
before. A more gentle reminder, such as a report that is emailed to you or
a query you run yourself would give a better impression of the project.
Also way too often bugs are closed without any reaction from the project to
it, there are currently at least 473 open bugs in platform without any
comment from a committer [1]. By the time the auto-close reminder comes in,
most users already gave up expecting any comment on the bug. The auto-close
is just a confirmation that the bug is ignored and the project doesn't seem
to care.

[1]
https://bugs.eclipse.org/bugs/buglist.cgi?cmdtype=runnamed_id=21212163=Platform%20-%20External%20no-comments




But if some people take the decision to not care about those notifications
,don't read them, don't react and fully ignore the bug just like if
notifications were not sent, then it's not really the process or the bot
notifications that's to blame if some bugs are ignored...



If after reporting a bug, the bug was totally ignored by the project, why
should I as a reporter care if it gets auto-closed? Personally, why should
I spend my limited time on re-opening issues when they get auto-closed? I
won't magically get time to work on a bug if it is auto-closed. I will
re-open when I find the time to work on the bug. I consider a bug labeled
with "stalebug" as an open bug anyhow.





If the only interaction with the reporter is an automated `Please reopen`


It's not what the message that comes with auto-close recommends as
possible reaction, and I've personally seen -and even fixed- several bugs
that I would have ignored if there were no notification. Maybe it's not
something you've encountered yet,but it does exist anyway.



Again, the problem here is that you need a notification to care about a bug
at all. Auto-closing should be a final resort, and the majority of
auto-closed bugs should be fixed or be inreallant by the time they get
auto-closed, this is currently not the case. Please consider another kind
of gentle reminder.



it's just sad and the poorest version of valuing contributors.


I find keeping the bug open and letting reporter face a heavy silence or
build hope that it will just get fixed while no code contributor will care
to fix it is in the end less nice to contributors that telling them "hey
that's old! Is it still relevant? If yes, please reopen"



If the reporter waits for the auto-close reminder, before sending a
reminder himself, he already gave up hope to get any reaction, let alone to
get a fix. So instead of a reminder, it is a confirmation that the issue is
indeed ignored, why would a reporter bother to keep interest in a project
that ignores its input?




IIRC whenever people ask how to contribute, part of the answer is also

"file bug reports".

Who told that the goal or even the real effect here is to reduce the
amount if incoming bug reports? There's probably something you
misunderstood.



In the end it is all about perception, I am not against an auto-close of
bugs as a final resort. However, given the current state of the project,
the auto-close can be for many the confirmation that the project is dying
and they are moving away. Also, given the amount of resources, the
auto-close period should be in line with that.

It would be better if bugs are triaged, and re-evaluated by committers
instead of an automatic process. There used to be a process in which at
bugs were triaged and labeled as "helpwanted" or "low-priorty" [2]. But of
course this takes up scarce resources. Note that being actively working
involved with bugs is one way to show that a project is alive, if you are
lucky you might attract some new committees in the process too.
Instead of just discussing the auto-closing of bugs, I would rather like to
see a discussion to revamp a bug-triage process and reminder process, in
which auto-closing might have its role. E.g. auto-closing bugs marked with
"needinfo" after only weeks would make sense to me.

[2] https://wiki.eclipse.org/Platform_UI/Bug_Triage

+1 for stop auto-closing in its 

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Andrey Loskutov]

The difference is that that has nothing to do with auto-closing at all.
 

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

 
 

Gesendet: Montag, 21. Februar 2022 um 09:05 Uhr
Von: "Wim Jongman" 
An: "Eclipse platform general developers list." 
Betreff: Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects



Good work, Sherlock ;). But what is the difference? It got resolved.

 

Cheers, Wim

 


On Sun, Feb 20, 2022 at 6:12 PM Christoph Läubrich <lae...@laeubi-soft.de> wrote:

Hi Wim,

good to hear the bug is fixed, but to be fair it seems Jörg simply
noticed the same problem, created a new bug with a different description
and you just linked it to a very old bug ;-)

Am 20.02.22 um 16:25 schrieb Wim Jongman:
> Here is some good news: Jörg Kubitz just resolved bug 89838 from march 2005.
>
> Bug 89838 was automatically closed after 15 years but emerged again by
> someone who cared and was resolved.
>





___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Christoph Läubrich]

The difference is, that auto-closing/notification has not helped here, 
in fact it produced more work as Jörg most probably was not aware that 
there was already an existing issue or ignored it as it was marked as 
closed.


I also have solved several bugs from Tycho 0.x releases, but for sure 
not because there was an auto-close notification for them ;-)


Am 21.02.22 um 09:05 schrieb Wim Jongman:

Good work, Sherlock ;). But what is the difference? It got resolved.

Cheers, Wim

On Sun, Feb 20, 2022 at 6:12 PM Christoph Läubrich 
mailto:lae...@laeubi-soft.de>> wrote:


Hi Wim,

good to hear the bug is fixed, but to be fair it seems Jörg simply
noticed the same problem, created a new bug with a different
description
and you just linked it to a very old bug ;-)

Am 20.02.22 um 16:25 schrieb Wim Jongman:
 > Here is some good news: Jörg Kubitz just resolved bug 89838 from
march 2005.
 >
 > Bug 89838 was automatically closed after 15 years but emerged
again by
 > someone who cared and was resolved.
 >
 > Cheers, Wim
 >
 > On Sat, Feb 19, 2022 at 12:47 PM Liviu Ionescu mailto:i...@livius.net>
 > >> wrote:
 >
 >
 >
 >      > On 19 Feb 2022, at 13:38, Rolf Theunissen
 >     mailto:rolf.theunis...@gmail.com>
>> wrote:
 >      >
 >      > However, given the current state of the project, the
auto-close
 >     can be for many the confirmation that the project is dying
and they
 >     are moving away.
 >
 >     Agree.
 >
 >     Liviu

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Wim Jongman]

Good work, Sherlock ;). But what is the difference? It got resolved.

Cheers, Wim

On Sun, Feb 20, 2022 at 6:12 PM Christoph Läubrich 
wrote:

> Hi Wim,
>
> good to hear the bug is fixed, but to be fair it seems Jörg simply
> noticed the same problem, created a new bug with a different description
> and you just linked it to a very old bug ;-)
>
> Am 20.02.22 um 16:25 schrieb Wim Jongman:
> > Here is some good news: Jörg Kubitz just resolved bug 89838 from march
> 2005.
> >
> > Bug 89838 was automatically closed after 15 years but emerged again by
> > someone who cared and was resolved.
> >
> > Cheers, Wim
> >
> > On Sat, Feb 19, 2022 at 12:47 PM Liviu Ionescu  > > wrote:
> >
> >
> >
> >  > On 19 Feb 2022, at 13:38, Rolf Theunissen
> > mailto:rolf.theunis...@gmail.com>>
> wrote:
> >  >
> >  > However, given the current state of the project, the auto-close
> > can be for many the confirmation that the project is dying and they
> > are moving away.
> >
> > Agree.
> >
> > Liviu
> >
> > ___
> > platform-dev mailing list
> > platform-dev@eclipse.org 
> > To unsubscribe from this list, visit
> > https://www.eclipse.org/mailman/listinfo/platform-dev
> > 
> >
> >
> > ___
> > platform-dev mailing list
> > platform-dev@eclipse.org
> > To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
>
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Christoph Läubrich]

Hi Wim,

good to hear the bug is fixed, but to be fair it seems Jörg simply 
noticed the same problem, created a new bug with a different description 
and you just linked it to a very old bug ;-)


Am 20.02.22 um 16:25 schrieb Wim Jongman:

Here is some good news: Jörg Kubitz just resolved bug 89838 from march 2005.

Bug 89838 was automatically closed after 15 years but emerged again by 
someone who cared and was resolved.


Cheers, Wim

On Sat, Feb 19, 2022 at 12:47 PM Liviu Ionescu > wrote:




 > On 19 Feb 2022, at 13:38, Rolf Theunissen
mailto:rolf.theunis...@gmail.com>> wrote:
 >
 > However, given the current state of the project, the auto-close
can be for many the confirmation that the project is dying and they
are moving away.

Agree.

Liviu

___
platform-dev mailing list
platform-dev@eclipse.org 
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev



___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Wim Jongman]

Here is some good news: Jörg Kubitz just resolved bug 89838 from march 2005.

Bug 89838 was automatically closed after 15 years but emerged again by
someone who cared and was resolved.

Cheers, Wim

On Sat, Feb 19, 2022 at 12:47 PM Liviu Ionescu  wrote:

>
>
> > On 19 Feb 2022, at 13:38, Rolf Theunissen 
> wrote:
> >
> > However, given the current state of the project, the auto-close can be
> for many the confirmation that the project is dying and they are moving
> away.
>
> Agree.
>
> Liviu
>
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
>
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Liviu Ionescu]

> On 19 Feb 2022, at 13:38, Rolf Theunissen  wrote:
> 
> However, given the current state of the project, the auto-close can be for 
> many the confirmation that the project is dying and they are moving away. 

Agree.

Liviu

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Rolf Theunissen]

Op vr 18 feb. 2022 om 15:54 schreef Mickael Istria :

>
>
> On Friday, February 18, 2022, Sebastian Zarnekow <
> sebastian.zarne...@gmail.com> wrote:
> > The Bot that does the auto-closing at Eclipse though doesn't give a
> heads-up, many tickets are never looked at.
>
> I personally look at all notifications I receive from Bugzilla and react
> to auto-close tickets either by taking the decision of not reopening, or by
> reopening with extra info, just like it's recommended in the message.
> And I'm happy with it bith as a reporter and a committer.
>

In this case you are a friendly user, so although you are happy with it as
a reporter, it might not be representative of the larger user community.
I get your point of having a reminder to look into a ticket again, It is
only a pity that it takes 2 years to get the reminder to look into an issue
again. As you get a reminder, you did have shown some interest in the bug
before. A more gentle reminder, such as a report that is emailed to you or
a query you run yourself would give a better impression of the project.
Also way too often bugs are closed without any reaction from the project to
it, there are currently at least 473 open bugs in platform without any
comment from a committer [1]. By the time the auto-close reminder comes in,
most users already gave up expecting any comment on the bug. The auto-close
is just a confirmation that the bug is ignored and the project doesn't seem
to care.

[1]
https://bugs.eclipse.org/bugs/buglist.cgi?cmdtype=runnamed_id=21212163=Platform%20-%20External%20no-comments


>
> But if some people take the decision to not care about those notifications
> ,don't read them, don't react and fully ignore the bug just like if
> notifications were not sent, then it's not really the process or the bot
> notifications that's to blame if some bugs are ignored...
>

If after reporting a bug, the bug was totally ignored by the project, why
should I as a reporter care if it gets auto-closed? Personally, why should
I spend my limited time on re-opening issues when they get auto-closed? I
won't magically get time to work on a bug if it is auto-closed. I will
re-open when I find the time to work on the bug. I consider a bug labeled
with "stalebug" as an open bug anyhow.


>
> > If the only interaction with the reporter is an automated `Please reopen`
>
> It's not what the message that comes with auto-close recommends as
> possible reaction, and I've personally seen -and even fixed- several bugs
> that I would have ignored if there were no notification. Maybe it's not
> something you've encountered yet,but it does exist anyway.
>

Again, the problem here is that you need a notification to care about a bug
at all. Auto-closing should be a final resort, and the majority of
auto-closed bugs should be fixed or be inreallant by the time they get
auto-closed, this is currently not the case. Please consider another kind
of gentle reminder.


> > it's just sad and the poorest version of valuing contributors.
>
> I find keeping the bug open and letting reporter face a heavy silence or
> build hope that it will just get fixed while no code contributor will care
> to fix it is in the end less nice to contributors that telling them "hey
> that's old! Is it still relevant? If yes, please reopen"
>

If the reporter waits for the auto-close reminder, before sending a
reminder himself, he already gave up hope to get any reaction, let alone to
get a fix. So instead of a reminder, it is a confirmation that the issue is
indeed ignored, why would a reporter bother to keep interest in a project
that ignores its input?

>
> > IIRC whenever people ask how to contribute, part of the answer is also
> "file bug reports".
>
> Who told that the goal or even the real effect here is to reduce the
> amount if incoming bug reports? There's probably something you
> misunderstood.
>
>
In the end it is all about perception, I am not against an auto-close of
bugs as a final resort. However, given the current state of the project,
the auto-close can be for many the confirmation that the project is dying
and they are moving away. Also, given the amount of resources, the
auto-close period should be in line with that.

It would be better if bugs are triaged, and re-evaluated by committers
instead of an automatic process. There used to be a process in which at
bugs were triaged and labeled as "helpwanted" or "low-priorty" [2]. But of
course this takes up scarce resources. Note that being actively working
involved with bugs is one way to show that a project is alive, if you are
lucky you might attract some new committees in the process too.
Instead of just discussing the auto-closing of bugs, I would rather like to
see a discussion to revamp a bug-triage process and reminder process, in
which auto-closing might have its role. E.g. auto-closing bugs marked with
"needinfo" after only weeks would make sense to me.

[2] https://wiki.eclipse.org/Platform_UI/Bug_Triage

+1 for stop 

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Adrián Pol]

-1 close pls close

It is a common action used by all, in my opinion

Regards,
apolalca

> El 17 feb 2022, a las 9:58, Andrey Loskutov  escribió:
> 
> Hi all,
> 
> this is a follow up on PMC response 
> https://www.eclipse.org/lists/platform-dev/msg03319.html
> 
> As of today, this bug auto-closing is not active only for JDT project.
> 
> The proposal is to switch "off" bug auto-closing for the all Eclipse platform 
> projects, including Platform, JDT, PDE und Equinox.
> I don't think if we need an additional vote for PDE & Equinox, because the 
> only active committers there are same as on the Eclipse platform.
> 
> Therefore I would like to start voting to stop auto-closing bugs in bugzilla, 
> github, gitlab (or whatever else bug trackers we might use in the future) for 
> all Eclipse platform development.
> 
> I think it is enough to post your +1 / 0 / -1 as a reply on this mailing list.
> Everyone is welcome to vote but binding votes are committers`votes.
> I would propose to conclude the vote by the end of the next week (25 
> February).
> 
> Kind regards,
> Andrey Loskutov
> 
> Спасение утопающих - дело рук самих утопающих
> 
> https://www.eclipse.org/user/aloskutov
> 
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/platform-dev

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Mickael Istria]

On Friday, February 18, 2022, Sebastian Zarnekow <
sebastian.zarne...@gmail.com> wrote:
> The Bot that does the auto-closing at Eclipse though doesn't give a
heads-up, many tickets are never looked at.

I personally look at all notifications I receive from Bugzilla and react to
auto-close tickets either by taking the decision of not reopening, or by
reopening with extra info, just like it's recommended in the message.
And I'm happy with it bith as a reporter and a committer.

But if some people take the decision to not care about those notifications
,don't read them, don't react and fully ignore the bug just like if
notifications were not sent, then it's not really the process or the bot
notifications that's to blame if some bugs are ignored...

> If the only interaction with the reporter is an automated `Please reopen`

It's not what the message that comes with auto-close recommends as possible
reaction, and I've personally seen -and even fixed- several bugs that I
would have ignored if there were no notification. Maybe it's not something
you've encountered yet,but it does exist anyway.

> it's just sad and the poorest version of valuing contributors.

I find keeping the bug open and letting reporter face a heavy silence or
build hope that it will just get fixed while no code contributor will care
to fix it is in the end less nice to contributors that telling them "hey
that's old! Is it still relevant? If yes, please reopen"

> IIRC whenever people ask how to contribute, part of the answer is also
"file bug reports".

Who told that the goal or even the real effect here is to reduce the amount
if incoming bug reports? There's probably something you misunderstood.


-- 
Mickael Istria
Eclipse IDE  developer, for Red Hat
Developers 
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Thomas Singer]

Mickael,

Do you mean reopened, auto-closed issues won't get auto-closed in the 
future again? Or does the auto-closing will occur automatically for all 
issues without any change within a certain period regardless of the 
re-opened state?


--
Best regards,
Thomas Singer
=
syntevo GmbH
www.syntevo.com


On 2022-02-18 14:44, Mickael Istria wrote:

On Fri, Feb 18, 2022 at 11:09 AM Liviu Ionescu  wrote:


Personally, when I see my tickets automatically closed, I regret the time
spent to file the reports, and I start to think about looking for alternate
solutions to replace the buggy project.



Reporters can also read the message that's send with the close message to
know why it is closed and other possible reactions.

If the final decision will be to auto-close the tickets, and we really care

for the users, sorry to say it, but how about providing a link to VS Code?



That won't change much. VSCode also auto-close inactive tickets:
https://github.com/microsoft/vscode/issues/52247#issuecomment-400660468



This might also reduce the risk of having the tickets reopened... :-(



You totally misunderstood the rationale in favor auto-closing. Having
tickets reopened is exactly what auto-closing is meant for, it's the
desired effect that someone will read the notification and think the ticket
is still worth a comment to revive it, providing extra info even just a
"still happens with latest release". Good triaging/prioritizing means we
have people doing this kind of work, as the committers are not doing it
because they're busy with other things and have their own goals and
motivations that can often be different from just making some random users
happy, it's fair to give some more responsibility to the community in
triaging/verifying their bugs themselves; so at least someone care.
Auto-closing implies some triaging: it's reopened => still worth being
considered, no-one reopens => no need to care, no need to keep tracking it.


___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Thomas Singer]

Auto-closing also make the project seem dead as it clearly indicates that there 
is no resources or people just don't care to handle valid reports.

I'd better have a growing number of issues showing that we need more resources 
than a constant number of issues that gives the false impression there is no 
problem.

In the end, its just a matter of what we want to deliver 'more' or 'better' software. As mentioned before, it might be good to have one of the releases per year that is dedicated to bug fixing (and maybe bug triage) where we simply do not accept new features. For example the 20xx-12 release as its is a bit shorter and we can have a fresh start for the new year. 


I completely agree with you. We only make use of SWT in our projects and 
pay a developer to fix bugs in SWT. Without looking at my reported 
issues, I would say nearly all of them were bugs.


This does not mean that SWT is very buggy, but even a good project can 
(and should) get better.


--
Best regards,
Thomas Singer
=
syntevo GmbH
www.syntevo.com


On 2022-02-18 07:13, Christoph Läubrich wrote:

 > Auto-closing is more likely to stimulate people in
 > trying to contribute [...] Sometimes they reopen
 > with frustration and this can trigger a new conversation with some
 > committers to help them in contributing more.

I'm not sure if you suggest here to

a) frustrate users more 'stimulate' them
   -or-
b) user should rant more to get more attention and 'stimulate' contributors

;-)

 > It just make the
 > project seem dead.

Auto-closing also make the project seem dead as it clearly indicates 
that there is no resources or people just don't care to handle valid 
reports.


I'd better have a growing number of issues showing that we need more 
resources than a constant number of issues that gives the false 
impression there is no problem.


In the end, its just a matter of what we want to deliver 'more' or 
'better' software. As mentioned before, it might be good to have one of 
the releases per year that is dedicated to bug fixing (and maybe bug 
triage) where we simply do not accept new features. For example the 
20xx-12 release as its is a bit shorter and we can have a fresh start 
for the new year.



Am 17.02.22 um 21:12 schrieb Mickael Istria:

 > We all know that the root cause of this discussion is the 10+ years of
under-resourcing for Eclipse platform.

Eclipse Platform is not under-resourced. It's OK-resourced, and just 
like any project would benefit from more resources, but let's move the 
resources discussion away and focus on the community aspects of 
auto-closing bugs.


 > Do we expect big players to come back and sponsor teams of 
developers again as it was in 00ths? I doubt so. Perhaps, small 
companies and individuals from the community are the only hope.


I don't get how it's related to the discussion about auto-closing bugs 
or not. And I also don't get how Alex's answer triggered that question.


    And if yes, how auto-close could help to recruit new resources for
    triaging (not even dreaming about bug fixing) from the community?


Auto-closing is more likely to stimulate people in trying to 
contribute than just keeping the bug silent. At least, people can 
decide to reopen with more details, or to add other information (not 
useful anymore, was fixed), and that's a form of contribution already. 
Sometimes they reopen with frustration and this can trigger a new 
conversation with some committers to help them in contributing more.
On the other hand, keeping the bugs open but silent brings no 
interaction and thus no new opportunity to recruit. It just make the 
project seem dead.


___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Sebastian Zarnekow]

> That won't change much. VSCode also auto-close inactive tickets:
https://github.com/microsoft/vscode/issues/52247#issuecomment-400660468

Interesting example since it's the exact opposite of what happens in the
Eclipse Bugzilla with the auto-closer:
Here, we had immediate engagement of two real people with the issue
reporter and I'd bet it was closed because it had the 'needs more info' tag
attached and nothing happened to it afterwards.

In other words: It was triaged, scheduled for "closing" if no more
information was arriving and then it was acted accordingly.

The Bot that does the auto-closing at Eclipse though doesn't give a
heads-up, many tickets are never looked at. If the only interaction with
the reporter is an automated `Please reopen`, it's just sad and the poorest
version of valuing contributors.
IIRC whenever people ask how to contribute, part of the answer is also
"file bug reports".

+1 for stopping auto closing in its current worst-of-all-worlds
implementation.

Best
Sebastian


On Fri, Feb 18, 2022 at 2:45 PM Mickael Istria  wrote:

>
>
> On Fri, Feb 18, 2022 at 11:09 AM Liviu Ionescu  wrote:
>
>> Personally, when I see my tickets automatically closed, I regret the time
>> spent to file the reports, and I start to think about looking for alternate
>> solutions to replace the buggy project.
>>
>
> Reporters can also read the message that's send with the close message to
> know why it is closed and other possible reactions.
>
> If the final decision will be to auto-close the tickets, and we really
>> care for the users, sorry to say it, but how about providing a link to VS
>> Code?
>
>
> That won't change much. VSCode also auto-close inactive tickets:
> https://github.com/microsoft/vscode/issues/52247#issuecomment-400660468
>
>
>> This might also reduce the risk of having the tickets reopened... :-(
>
>
> You totally misunderstood the rationale in favor auto-closing. Having
> tickets reopened is exactly what auto-closing is meant for, it's the
> desired effect that someone will read the notification and think the ticket
> is still worth a comment to revive it, providing extra info even just a
> "still happens with latest release". Good triaging/prioritizing means we
> have people doing this kind of work, as the committers are not doing it
> because they're busy with other things and have their own goals and
> motivations that can often be different from just making some random users
> happy, it's fair to give some more responsibility to the community in
> triaging/verifying their bugs themselves; so at least someone care.
> Auto-closing implies some triaging: it's reopened => still worth being
> considered, no-one reopens => no need to care, no need to keep tracking it.
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
>
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Liviu Ionescu]

> On 18 Feb 2022, at 15:44, Mickael Istria  wrote:
> 
> You totally misunderstood the rationale in favor auto-closing.

Probably. But I did understand that Eclipse is an old project that lived its 
life. At least for Embedded CDT I see less and less downloads and less and less 
hits in the project web. It is in the nature of things that a project no longer 
growing is already on the downslope.

Thus I'm currently migrating my projects to VS Code, in an attempt to provide 
an alternate solution to Embedded CDT users, so in the long run they'll 
probably not be very affected regardless how this vote ends up.


Regards,

Liviu


___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Mickael Istria]

On Fri, Feb 18, 2022 at 11:09 AM Liviu Ionescu  wrote:

> Personally, when I see my tickets automatically closed, I regret the time
> spent to file the reports, and I start to think about looking for alternate
> solutions to replace the buggy project.
>

Reporters can also read the message that's send with the close message to
know why it is closed and other possible reactions.

If the final decision will be to auto-close the tickets, and we really care
> for the users, sorry to say it, but how about providing a link to VS Code?


That won't change much. VSCode also auto-close inactive tickets:
https://github.com/microsoft/vscode/issues/52247#issuecomment-400660468


> This might also reduce the risk of having the tickets reopened... :-(


You totally misunderstood the rationale in favor auto-closing. Having
tickets reopened is exactly what auto-closing is meant for, it's the
desired effect that someone will read the notification and think the ticket
is still worth a comment to revive it, providing extra info even just a
"still happens with latest release". Good triaging/prioritizing means we
have people doing this kind of work, as the committers are not doing it
because they're busy with other things and have their own goals and
motivations that can often be different from just making some random users
happy, it's fair to give some more responsibility to the community in
triaging/verifying their bugs themselves; so at least someone care.
Auto-closing implies some triaging: it's reopened => still worth being
considered, no-one reopens => no need to care, no need to keep tracking it.
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Liviu Ionescu]

Personally, when I see my tickets automatically closed, I regret the time spent 
to file the reports, and I start to think about looking for alternate solutions 
to replace the buggy project.

If the final decision will be to auto-close the tickets, and we really care for 
the users, sorry to say it, but how about providing a link to VS Code? This 
might also reduce the risk of having the tickets reopened... :-(


Liviu

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Mickael Istria]

On Friday, February 18, 2022, Andrey Loskutov  wrote:
>> And it's important that we understand that in the way we interact with
consumers, and also in the way we plan to future of the project.
>
> You don't see that you contradict youself?
> According to this, we  seem to plan to "auto close" the future of the
project.

I don't contradict myself, you just fail at reading me correctly (or I fail
at explaining my thoughts correctly).
Closing bugs is actually more likely to help project focusing on its
preseny and future than keeping tons of probably outdated or irrelevant
bugs open with a dead silence around them. It does force some triaging or
contributiin actions from stakeholders that are otherwise just forgetting
about this issue. It does boost community activity. Reopened bugs usually
start discussions that wouldn't have happened without an auto-close... it's
probably more helpful to boost bugzilla discussions that all committer
efforts united.

Only arguments against it are just emotions (I don't want this email, I'm
annoyed people don't care enough abou my issue...) but there is no solid
data points to consolidate not closing is helpfulto the project and
community IMO, while I see tons of auto-closed bugs that turned into a
happy end.

-- 
Mickael Istria
Eclipse IDE  developer, for Red Hat
Developers 
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Andrey Loskutov]

> And it's important that we understand that in the way we interact with consumers, and also in the way we plan to future of the project.

 

You don't see that you contradict youself?

According to this, we  seem to plan to "auto close" the future of the project.

 

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

 
 

Gesendet: Freitag, 18. Februar 2022 um 09:01 Uhr
Von: "Mickael Istria" 
An: "Eclipse platform general developers list." 
Betreff: Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects



 
 


On Fri, Feb 18, 2022 at 8:23 AM Andrey Loskutov <losku...@gmx.de> wrote:




May be I'm living in some parallel universe, but in my world Eclipse Platform is utterly under-resourced




 

Every OSS project is as much resourced as people need it. If it's really under-resourced to its consumers, then their consumers can contribute resources. If they don't it implies that it's OK-resourced. And it's important that we understand that in the way we interact with consumers, and also in the way we plan to future of the project.

 




that's the main reson bugs aren't processed as it should be and therefore closed without any activity.




 

I'm surprised that people still hope that a 20+ years old project that has been used constantly by 3 to 12 million users can have an empty backlog and expect its developers to resolve all its bugs/requirements. Maybe I've been only part of "dirty" teams and projects, but from my various experiences in a diverse set of organizations and goals, I've never seen a team nor a project expecting to fix or implement every issue or idea someone ever faced. And the amount of open issues has always kept growing. There are priorities, there are things that no-one care about, there are ideas that were good years ago and are now bad... not everything must be done; filtering and prioritizing is a key factor of success. It's totally fine to tell people that as a committer you don't care enough about X to work on it but would welcome further resources to take care of X, and it's exactly what the auto-close bugs are about.


___ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev



___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Wim Jongman]

 I can still hear Erich Gamma say in Ludwigsburg: "Every bug report is a
love letter" . It is true, and we get a lot of love!


> I'm surprised that people still hope that a 20+ years old project that
has been used constantly by 3 to 12 million users can have an empty backlog
and expect its developers
> to resolve all its bugs/requirements. Maybe I've been only part of
"dirty" teams and projects, but from my various experiences in a diverse
set of organizations and goals, ...

I totally agree. Our high bug rate is a sign of success. if you have more
devs than reports, you are in trouble.

Also, every rant about auto-closing a bug is someone who cares and maybe
will now step up to help fix the issue.

Peace, Wim




On Fri, Feb 18, 2022 at 9:02 AM Mickael Istria  wrote:

>
>
> On Fri, Feb 18, 2022 at 8:23 AM Andrey Loskutov  wrote:
>
>> May be I'm living in some parallel universe, but in my world Eclipse
>> Platform is utterly under-resourced
>>
>
> Every OSS project is as much resourced as people need it. If it's really
> under-resourced to its consumers, then their consumers can contribute
> resources. If they don't it implies that it's OK-resourced. And it's
> important that we understand that in the way we interact with consumers,
> and also in the way we plan to future of the project.
>
>
>> that's the main reson bugs aren't processed as it should be and therefore
>> closed without any activity.
>>
>
> I'm surprised that people still hope that a 20+ years old project that has
> been used constantly by 3 to 12 million users can have an empty backlog and
> expect its developers to resolve all its bugs/requirements. Maybe I've been
> only part of "dirty" teams and projects, but from my various experiences in
> a diverse set of organizations and goals, I've never seen a team nor a
> project expecting to fix or implement every issue or idea someone ever
> faced. And the amount of open issues has always kept growing. There are
> priorities, there are things that no-one care about, there are ideas that
> were good years ago and are now bad... not everything must be done;
> filtering and prioritizing is a key factor of success. It's totally fine to
> tell people that as a committer you don't care enough about X to work on it
> but would welcome further resources to take care of X, and it's exactly
> what the auto-close bugs are about.
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
>
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Mickael Istria]

On Fri, Feb 18, 2022 at 8:23 AM Andrey Loskutov  wrote:

> May be I'm living in some parallel universe, but in my world Eclipse
> Platform is utterly under-resourced
>

Every OSS project is as much resourced as people need it. If it's really
under-resourced to its consumers, then their consumers can contribute
resources. If they don't it implies that it's OK-resourced. And it's
important that we understand that in the way we interact with consumers,
and also in the way we plan to future of the project.


> that's the main reson bugs aren't processed as it should be and therefore
> closed without any activity.
>

I'm surprised that people still hope that a 20+ years old project that has
been used constantly by 3 to 12 million users can have an empty backlog and
expect its developers to resolve all its bugs/requirements. Maybe I've been
only part of "dirty" teams and projects, but from my various experiences in
a diverse set of organizations and goals, I've never seen a team nor a
project expecting to fix or implement every issue or idea someone ever
faced. And the amount of open issues has always kept growing. There are
priorities, there are things that no-one care about, there are ideas that
were good years ago and are now bad... not everything must be done;
filtering and prioritizing is a key factor of success. It's totally fine to
tell people that as a committer you don't care enough about X to work on it
but would welcome further resources to take care of X, and it's exactly
what the auto-close bugs are about.
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Aleksandar Kurtakov]

On Fri, Feb 18, 2022 at 9:23 AM Andrey Loskutov  wrote:

> May be I'm living in some parallel universe, but in my world Eclipse
> Platform is utterly under-resourced, and this is since years, and that's
> the main reson bugs aren't processed as it should be and therefore closed
> without any activity.
>

Everyone's experience varies depending on what they see in other projects
they work on.


>
> Kind regards,
> Andrey Loskutov
>
> Спасение утопающих - дело рук самих утопающих
>
> https://www.eclipse.org/user/aloskutov
>
>
> *Gesendet:* Donnerstag, 17. Februar 2022 um 21:12 Uhr
> *Von:* "Mickael Istria" 
> *An:* "Eclipse platform general developers list." <
> platform-dev@eclipse.org>
> *Betreff:* Re: [platform-dev] Vote to stop bug auto-closing in all
> Eclipse platform projects
> > We all know that the root cause of this discussion is the 10+ years of
> under-resourcing for Eclipse platform.
>
> Eclipse Platform is not under-resourced. It's OK-resourced, and just like
> any project would benefit from more resources, but let's move the resources
> discussion away and focus on the community aspects of auto-closing bugs.
>
> > Do we expect big players to come back and sponsor teams of developers
> again as it was in 00ths? I doubt so. Perhaps, small companies and
> individuals from the community are the only hope.
>
> I don't get how it's related to the discussion about auto-closing bugs or
> not. And I also don't get how Alex's answer triggered that question.
>
>
>> And if yes, how auto-close could help to recruit new resources for
>> triaging (not even dreaming about bug fixing) from the community?
>
>
> Auto-closing is more likely to stimulate people in trying to contribute
> than just keeping the bug silent. At least, people can decide to reopen
> with more details, or to add other information (not useful anymore, was
> fixed), and that's a form of contribution already. Sometimes they reopen
> with frustration and this can trigger a new conversation with some
> committers to help them in contributing more.
> On the other hand, keeping the bugs open but silent brings no interaction
> and thus no new opportunity to recruit. It just make the project seem dead.
> ___ platform-dev mailing list
> platform-dev@eclipse.org To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
>


-- 
Aleksandar Kurtakov
Red Hat Eclipse Team
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Andrey Loskutov]

May be I'm living in some parallel universe, but in my world Eclipse Platform is utterly under-resourced, and this is since years, and that's the main reson bugs aren't processed as it should be and therefore closed without any activity.
 

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

 
 

Gesendet: Donnerstag, 17. Februar 2022 um 21:12 Uhr
Von: "Mickael Istria" 
An: "Eclipse platform general developers list." 
Betreff: Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects



> We all know that the root cause of this discussion is the 10+ years of
under-resourcing for Eclipse platform.

 

Eclipse Platform is not under-resourced. It's OK-resourced, and just like any project would benefit from more resources, but let's move the resources discussion away and focus on the community aspects of auto-closing bugs.

 

> Do we expect big players to come back and sponsor teams of developers again as it was in 00ths? I doubt so. Perhaps, small companies and individuals from the community are the only hope.

 

I don't get how it's related to the discussion about auto-closing bugs or not. And I also don't get how Alex's answer triggered that question.
 


And if yes, how auto-close could help to recruit new resources for
triaging (not even dreaming about bug fixing) from the community?


 

Auto-closing is more likely to stimulate people in trying to contribute than just keeping the bug silent. At least, people can decide to reopen with more details, or to add other information (not useful anymore, was fixed), and that's a form of contribution already. Sometimes they reopen with frustration and this can trigger a new conversation with some committers to help them in contributing more.

On the other hand, keeping the bugs open but silent brings no interaction and thus no new opportunity to recruit. It just make the project seem dead.

___ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev



___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Aleksandar Kurtakov]

On Fri, Feb 18, 2022 at 9:02 AM Alexander Fedorov <
alexander.fedo...@arsysop.ru> wrote:

> Thank you, Christoph!
>
> It was surprising to learn that Platform is not under-resourced. For
> example, looking into the E4 story, that is abandoned for years.
>

The E4 story is "another" story. All people that worked on it moved on and
current committers don't have much (if any) interest in continuing it. But
the same could be said for other things e.g. for pde-build.


> Or, more closely to our topic, during our discussion regarding "should
> we close bugs automatically or just leave them open forever, because
> there is no ability to reasonably process them".
> Does this look like a project that is OK-resourced?
>
> In the past we had one major and two service releases per year, that was
> a kind of guarantee that the most wanted bugs will be fixed each year.
> Now we have four releases per year, but in practice none of them are
> dedicated to fix bugs.
>
> I fully agree with Christoph that 20XX-12 release should be fully
> dedicated to bugfix activities.
> And this will align well with the practice of last decades where we had
> service releases after the big release in summer.
>

Some of us do only releng, bug fixes, CVE fixes and dependency updates for
years already so that would make no difference to this group.

I welcome and support every effort in that direction. We can not tell any
committer what to work on  so it's a matter of convincing more people to
think that bug fixes and triaging are more important.
Even more important in my opinion is to streamline our codebase and
actively remove duplicate/triplicate/quadruplicate functionality and API -
that would make it easier to get new people in and even enhance support and
user satisfaction. If I have to start with do you use action and command
for XYZ and following up with several similar questions the usual result is
either I lose track due to more pressing issues or the submitter just gives
up. This is the biggest burden for me - it really prevents me from
effective working, maybe I'm just badly organized and can't concentrate,
who knows.


>
> Regards,
> AF
>
> 2/18/2022 9:13 AM, Christoph Läubrich пишет:
> > > Auto-closing is more likely to stimulate people in
> > > trying to contribute [...] Sometimes they reopen
> > > with frustration and this can trigger a new conversation with some
> > > committers to help them in contributing more.
> >
> > I'm not sure if you suggest here to
> >
> > a) frustrate users more 'stimulate' them
> >   -or-
> > b) user should rant more to get more attention and 'stimulate'
> > contributors
> >
> > ;-)
> >
> > > It just make the
> > > project seem dead.
> >
> > Auto-closing also make the project seem dead as it clearly indicates
> > that there is no resources or people just don't care to handle valid
> > reports.
> >
> > I'd better have a growing number of issues showing that we need more
> > resources than a constant number of issues that gives the false
> > impression there is no problem.
> >
> > In the end, its just a matter of what we want to deliver 'more' or
> > 'better' software. As mentioned before, it might be good to have one
> > of the releases per year that is dedicated to bug fixing (and maybe
> > bug triage) where we simply do not accept new features. For example
> > the 20xx-12 release as its is a bit shorter and we can have a fresh
> > start for the new year.
> >
> >
> > Am 17.02.22 um 21:12 schrieb Mickael Istria:
> >>  > We all know that the root cause of this discussion is the 10+
> >> years of
> >> under-resourcing for Eclipse platform.
> >>
> >> Eclipse Platform is not under-resourced. It's OK-resourced, and just
> >> like any project would benefit from more resources, but let's move
> >> the resources discussion away and focus on the community aspects of
> >> auto-closing bugs.
> >>
> >>  > Do we expect big players to come back and sponsor teams of
> >> developers again as it was in 00ths? I doubt so. Perhaps, small
> >> companies and individuals from the community are the only hope.
> >>
> >> I don't get how it's related to the discussion about auto-closing
> >> bugs or not. And I also don't get how Alex's answer triggered that
> >> question.
> >>
> >> And if yes, how auto-close could help to recruit new resources for
> >> triaging (not even dreaming about bug fixing) from the community?
> >>
> >>
> >> Auto-closing is more likely to stimulate people in trying to
> >> contribute than just keeping the bug silent. At least, people can
> >> decide to reopen with more details, or to add other information (not
> >> useful anymore, was fixed), and that's a form of contribution
> >> already. Sometimes they reopen with frustration and this can trigger
> >> a new conversation with some committers to help them in contributing
> >> more.
> >> On the other hand, keeping the bugs open but silent brings no
> >> interaction and thus no new opportunity to recruit. It just make the
> >> project seem dead.

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Alexander Fedorov]

Thank you, Christoph!

It was surprising to learn that Platform is not under-resourced. For 
example, looking into the E4 story, that is abandoned for years.
Or, more closely to our topic, during our discussion regarding "should 
we close bugs automatically or just leave them open forever, because 
there is no ability to reasonably process them".

Does this look like a project that is OK-resourced?

In the past we had one major and two service releases per year, that was 
a kind of guarantee that the most wanted bugs will be fixed each year.
Now we have four releases per year, but in practice none of them are 
dedicated to fix bugs.


I fully agree with Christoph that 20XX-12 release should be fully 
dedicated to bugfix activities.
And this will align well with the practice of last decades where we had 
service releases after the big release in summer.


Regards,
AF

2/18/2022 9:13 AM, Christoph Läubrich пишет:

> Auto-closing is more likely to stimulate people in
> trying to contribute [...] Sometimes they reopen
> with frustration and this can trigger a new conversation with some
> committers to help them in contributing more.

I'm not sure if you suggest here to

a) frustrate users more 'stimulate' them
  -or-
b) user should rant more to get more attention and 'stimulate' 
contributors


;-)

> It just make the
> project seem dead.

Auto-closing also make the project seem dead as it clearly indicates 
that there is no resources or people just don't care to handle valid 
reports.


I'd better have a growing number of issues showing that we need more 
resources than a constant number of issues that gives the false 
impression there is no problem.


In the end, its just a matter of what we want to deliver 'more' or 
'better' software. As mentioned before, it might be good to have one 
of the releases per year that is dedicated to bug fixing (and maybe 
bug triage) where we simply do not accept new features. For example 
the 20xx-12 release as its is a bit shorter and we can have a fresh 
start for the new year.



Am 17.02.22 um 21:12 schrieb Mickael Istria:
 > We all know that the root cause of this discussion is the 10+ 
years of

under-resourcing for Eclipse platform.

Eclipse Platform is not under-resourced. It's OK-resourced, and just 
like any project would benefit from more resources, but let's move 
the resources discussion away and focus on the community aspects of 
auto-closing bugs.


 > Do we expect big players to come back and sponsor teams of 
developers again as it was in 00ths? I doubt so. Perhaps, small 
companies and individuals from the community are the only hope.


I don't get how it's related to the discussion about auto-closing 
bugs or not. And I also don't get how Alex's answer triggered that 
question.


    And if yes, how auto-close could help to recruit new resources for
    triaging (not even dreaming about bug fixing) from the community?


Auto-closing is more likely to stimulate people in trying to 
contribute than just keeping the bug silent. At least, people can 
decide to reopen with more details, or to add other information (not 
useful anymore, was fixed), and that's a form of contribution 
already. Sometimes they reopen with frustration and this can trigger 
a new conversation with some committers to help them in contributing 
more.
On the other hand, keeping the bugs open but silent brings no 
interaction and thus no new opportunity to recruit. It just make the 
project seem dead.


___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev




___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Christoph Läubrich]

> Auto-closing is more likely to stimulate people in
> trying to contribute [...] Sometimes they reopen
> with frustration and this can trigger a new conversation with some
> committers to help them in contributing more.

I'm not sure if you suggest here to

a) frustrate users more 'stimulate' them
  -or-
b) user should rant more to get more attention and 'stimulate' contributors

;-)

> It just make the
> project seem dead.

Auto-closing also make the project seem dead as it clearly indicates 
that there is no resources or people just don't care to handle valid 
reports.


I'd better have a growing number of issues showing that we need more 
resources than a constant number of issues that gives the false 
impression there is no problem.


In the end, its just a matter of what we want to deliver 'more' or 
'better' software. As mentioned before, it might be good to have one of 
the releases per year that is dedicated to bug fixing (and maybe bug 
triage) where we simply do not accept new features. For example the 
20xx-12 release as its is a bit shorter and we can have a fresh start 
for the new year.



Am 17.02.22 um 21:12 schrieb Mickael Istria:

 > We all know that the root cause of this discussion is the 10+ years of
under-resourcing for Eclipse platform.

Eclipse Platform is not under-resourced. It's OK-resourced, and just 
like any project would benefit from more resources, but let's move the 
resources discussion away and focus on the community aspects of 
auto-closing bugs.


 > Do we expect big players to come back and sponsor teams of developers 
again as it was in 00ths? I doubt so. Perhaps, small companies and 
individuals from the community are the only hope.


I don't get how it's related to the discussion about auto-closing bugs 
or not. And I also don't get how Alex's answer triggered that question.


And if yes, how auto-close could help to recruit new resources for
triaging (not even dreaming about bug fixing) from the community?


Auto-closing is more likely to stimulate people in trying to contribute 
than just keeping the bug silent. At least, people can decide to reopen 
with more details, or to add other information (not useful anymore, was 
fixed), and that's a form of contribution already. Sometimes they reopen 
with frustration and this can trigger a new conversation with some 
committers to help them in contributing more.
On the other hand, keeping the bugs open but silent brings no 
interaction and thus no new opportunity to recruit. It just make the 
project seem dead.


___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Alex Blewitt]

+1

Sent from my iPhone 

> On 17 Feb 2022, at 08:58, Andrey Loskutov  wrote:
> 
> Hi all,
> 
> this is a follow up on PMC response 
> https://www.eclipse.org/lists/platform-dev/msg03319.html
> 
> As of today, this bug auto-closing is not active only for JDT project.
> 
> The proposal is to switch "off" bug auto-closing for the all Eclipse platform 
> projects, including Platform, JDT, PDE und Equinox.
> I don't think if we need an additional vote for PDE & Equinox, because the 
> only active committers there are same as on the Eclipse platform.
> 
> Therefore I would like to start voting to stop auto-closing bugs in bugzilla, 
> github, gitlab (or whatever else bug trackers we might use in the future) for 
> all Eclipse platform development.
> 
> I think it is enough to post your +1 / 0 / -1 as a reply on this mailing list.
> Everyone is welcome to vote but binding votes are committers`votes.
> I would propose to conclude the vote by the end of the next week (25 
> February).
> 
> Kind regards,
> Andrey Loskutov
> 
> Спасение утопающих - дело рук самих утопающих
> 
> https://www.eclipse.org/user/aloskutov
> 
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/platform-dev
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Mickael Istria]

> We all know that the root cause of this discussion is the 10+ years of
under-resourcing for Eclipse platform.

Eclipse Platform is not under-resourced. It's OK-resourced, and just like
any project would benefit from more resources, but let's move the resources
discussion away and focus on the community aspects of auto-closing bugs.

> Do we expect big players to come back and sponsor teams of developers
again as it was in 00ths? I doubt so. Perhaps, small companies and
individuals from the community are the only hope.

I don't get how it's related to the discussion about auto-closing bugs or
not. And I also don't get how Alex's answer triggered that question.

And if yes, how auto-close could help to recruit new resources for
> triaging (not even dreaming about bug fixing) from the community?


Auto-closing is more likely to stimulate people in trying to contribute
than just keeping the bug silent. At least, people can decide to reopen
with more details, or to add other information (not useful anymore, was
fixed), and that's a form of contribution already. Sometimes they reopen
with frustration and this can trigger a new conversation with some
committers to help them in contributing more.
On the other hand, keeping the bugs open but silent brings no interaction
and thus no new opportunity to recruit. It just make the project seem dead.
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Alexander Fedorov]

Aleksandar,

We all know that the root cause of this discussion is the 10+ years of 
under-resourcing for Eclipse platform.
Do we expect big players to come back and sponsor teams of developers 
again as it was in 00ths? I doubt so.
Perhaps, small companies and individuals from the community are the only 
hope.


And if yes, how auto-close could help to recruit new resources for 
triaging (not even dreaming about bug fixing) from the community?


Regards,
AF

2/17/2022 12:43 PM, Aleksandar Kurtakov пишет:

-1
In my opinion having bugs open without anyone looking into them for 
years is bad and even worse as it gives false sense of support which 
in reality is not there. I would change my mind if/when I see active 
triaging going on.


___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Ed Merks]

+1

On 17.02.2022 09:58, Andrey Loskutov wrote:

Hi all,

this is a follow up on PMC response 
https://www.eclipse.org/lists/platform-dev/msg03319.html

As of today, this bug auto-closing is not active only for JDT project.

The proposal is to switch "off" bug auto-closing for the all Eclipse platform 
projects, including Platform, JDT, PDE und Equinox.
I don't think if we need an additional vote for PDE & Equinox, because the only 
active committers there are same as on the Eclipse platform.

Therefore I would like to start voting to stop auto-closing bugs in bugzilla, 
github, gitlab (or whatever else bug trackers we might use in the future) for 
all Eclipse platform development.

I think it is enough to post your +1 / 0 / -1 as a reply on this mailing list.
Everyone is welcome to vote but binding votes are committers`votes.
I would propose to conclude the vote by the end of the next week (25 February).

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Lars Vogel]

-1 from me too.

Great summary from Mike

Jonah Graham  schrieb am Do., 17. Feb. 2022, 16:48:

> -1 to stop auto-closing.
>
> McQ's arguments ring true for me.
>
> My personal preference  would prefer a much more aggressive auto-close
> strategy - however I do hear the active committers saying they don't like
> it.
>
> Jonah
>
> ~~~
> Jonah Graham
> Kichwa Coders
> www.kichwacoders.com
>
>
> On Thu, 17 Feb 2022 at 03:58, Andrey Loskutov  wrote:
>
>> Hi all,
>>
>> this is a follow up on PMC response
>> https://www.eclipse.org/lists/platform-dev/msg03319.html
>>
>> As of today, this bug auto-closing is not active only for JDT project.
>>
>> The proposal is to switch "off" bug auto-closing for the all Eclipse
>> platform projects, including Platform, JDT, PDE und Equinox.
>> I don't think if we need an additional vote for PDE & Equinox, because
>> the only active committers there are same as on the Eclipse platform.
>>
>> Therefore I would like to start voting to stop auto-closing bugs in
>> bugzilla, github, gitlab (or whatever else bug trackers we might use in the
>> future) for all Eclipse platform development.
>>
>> I think it is enough to post your +1 / 0 / -1 as a reply on this mailing
>> list.
>> Everyone is welcome to vote but binding votes are committers`votes.
>> I would propose to conclude the vote by the end of the next week (25
>> February).
>>
>> Kind regards,
>> Andrey Loskutov
>>
>> Спасение утопающих - дело рук самих утопающих
>>
>> https://www.eclipse.org/user/aloskutov
>>
>> ___
>> platform-dev mailing list
>> platform-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/platform-dev
>>
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
>
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Jonah Graham]

-1 to stop auto-closing.

McQ's arguments ring true for me.

My personal preference  would prefer a much more aggressive auto-close
strategy - however I do hear the active committers saying they don't like
it.

Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Thu, 17 Feb 2022 at 03:58, Andrey Loskutov  wrote:

> Hi all,
>
> this is a follow up on PMC response
> https://www.eclipse.org/lists/platform-dev/msg03319.html
>
> As of today, this bug auto-closing is not active only for JDT project.
>
> The proposal is to switch "off" bug auto-closing for the all Eclipse
> platform projects, including Platform, JDT, PDE und Equinox.
> I don't think if we need an additional vote for PDE & Equinox, because the
> only active committers there are same as on the Eclipse platform.
>
> Therefore I would like to start voting to stop auto-closing bugs in
> bugzilla, github, gitlab (or whatever else bug trackers we might use in the
> future) for all Eclipse platform development.
>
> I think it is enough to post your +1 / 0 / -1 as a reply on this mailing
> list.
> Everyone is welcome to vote but binding votes are committers`votes.
> I would propose to conclude the vote by the end of the next week (25
> February).
>
> Kind regards,
> Andrey Loskutov
>
> Спасение утопающих - дело рук самих утопающих
>
> https://www.eclipse.org/user/aloskutov
>
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
>
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Stephan Wahlbrink]

+1 stop auto closing

Am 2022-02-17 12:12, schrieb Jean-Francois Maury:

+1 stop auto closing

On Thu, Feb 17, 2022 at 9:58 AM Andrey Loskutov 
wrote:


Hi all,

this is a follow up on PMC response
https://www.eclipse.org/lists/platform-dev/msg03319.html

As of today, this bug auto-closing is not active only for JDT
project.

The proposal is to switch "off" bug auto-closing for the all Eclipse
platform projects, including Platform, JDT, PDE und Equinox.
I don't think if we need an additional vote for PDE & Equinox,
because the only active committers there are same as on the Eclipse
platform.

Therefore I would like to start voting to stop auto-closing bugs in
bugzilla, github, gitlab (or whatever else bug trackers we might use
in the future) for all Eclipse platform development.

I think it is enough to post your +1 / 0 / -1 as a reply on this
mailing list.
Everyone is welcome to vote but binding votes are committers`votes.
I would propose to conclude the vote by the end of the next week (25
February).

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих
утопающих

https://www.eclipse.org/user/aloskutov

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev


--

 Jeff Maury

 Manager, DevTools

 Red Hat EMEA [1]

 jma...@redhat.com

 @RedHat [2]   Red Hat [3]  Red Hat [4]

 [1]

 [5]



Links:
--
[1] https://www.redhat.com
[2] https://twitter.com/redhat
[3] https://www.linkedin.com/company/red-hat
[4] https://www.facebook.com/RedHatInc
[5] https://redhat.com/summit
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Mat Booth]

-1 from me


On Thu, 17 Feb 2022 at 13:59, Thomas Watson  wrote:
>
> -1 from me.
>
> I agree with Mcq and Alex points on this.
>
> Tom
> 
> From: platform-dev  on behalf of Andrey 
> Loskutov 
> Sent: Thursday, February 17, 2022 2:58 AM
> To: platform-dev 
> Subject: [EXTERNAL] [platform-dev] Vote to stop bug auto-closing in all 
> Eclipse platform projects
>
> Hi all,
>
> this is a follow up on PMC response 
> https://www.eclipse.org/lists/platform-dev/msg03319.html
>
> As of today, this bug auto-closing is not active only for JDT project.
>
> The proposal is to switch "off" bug auto-closing for the all Eclipse platform 
> projects, including Platform, JDT, PDE und Equinox.
> I don't think if we need an additional vote for PDE & Equinox, because the 
> only active committers there are same as on the Eclipse platform.
>
> Therefore I would like to start voting to stop auto-closing bugs in bugzilla, 
> github, gitlab (or whatever else bug trackers we might use in the future) for 
> all Eclipse platform development.
>
> I think it is enough to post your +1 / 0 / -1 as a reply on this mailing list.
> Everyone is welcome to vote but binding votes are committers`votes.
> I would propose to conclude the vote by the end of the next week (25 
> February).
>
> Kind regards,
> Andrey Loskutov
>
> Спасение утопающих - дело рук самих утопающих
>
> https://www.eclipse.org/user/aloskutov
>
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/platform-dev
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/platform-dev



-- 
Mat Booth
http://fedoraproject.org/get-fedora
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Thomas Watson]

-1 from me.

I agree with Mcq and Alex points on this.

Tom

From: platform-dev  on behalf of Andrey 
Loskutov 
Sent: Thursday, February 17, 2022 2:58 AM
To: platform-dev 
Subject: [EXTERNAL] [platform-dev] Vote to stop bug auto-closing in all Eclipse 
platform projects

Hi all,

this is a follow up on PMC response 
https://www.eclipse.org/lists/platform-dev/msg03319.html

As of today, this bug auto-closing is not active only for JDT project.

The proposal is to switch "off" bug auto-closing for the all Eclipse platform 
projects, including Platform, JDT, PDE und Equinox.
I don't think if we need an additional vote for PDE & Equinox, because the only 
active committers there are same as on the Eclipse platform.

Therefore I would like to start voting to stop auto-closing bugs in bugzilla, 
github, gitlab (or whatever else bug trackers we might use in the future) for 
all Eclipse platform development.

I think it is enough to post your +1 / 0 / -1 as a reply on this mailing list.
Everyone is welcome to vote but binding votes are committers`votes.
I would propose to conclude the vote by the end of the next week (25 February).

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Mike Wilson]

I definitely understand the negative comments about auto-closing bugs. For 
context, I can say that we've been discussing the pros and cons of auto-closing 
since the day the Eclipse Project had >1000 open bugs -- yes, that was many 
years ago.



In those days, we could at least make the claim that we reviewed all the open 
bugs occasionally, so we knew that they actually represented real issues in 
current versions of Eclipse, or they were ideas about new things we could 
conceive of doing at some point even if not in the short term.



The hard truth today, is as Alex said:



> In my opinion having bugs open without anyone looking into them for years

> is bad and even worse as it gives false sense of support which in reality is 
> not there.

> I would change my mind if/when I see active triaging going on.



We talk about the harsh reaction people have about seeing their bugs 
auto-closed, but we don't talk about the fact that our current way of working 
leaves people with the feeling that reporting Eclipse bugs is a black hole. 
Today, reporting a bug (or a design improvement) that isn’t a critical failure 
on one of the main Eclipse developer flows is useless. I don’t know that 
auto-closing bugs helps with that, but at least if the reporter still cares 
about it, they have an opportunity to put it back in the committers view by 
re-opening it. • that’s the piece of the auto-closing story that’s important: 
If someone re-opens a bug after 2 years (or however long we chose), we sure as 
heck better review it again. It is an issue that someone cares about.



So, you can see where this is going: My vote, FWIW, is -1 for “switch "off" bug 
auto-closing”. I would be happy to see updated wording on the auto-close 
message that made it clearer that re-opening the issue would cause it to be 
re-reviewed by current contributors, but I believe we should continue to 
auto-close.



McQ.



On 2022-02-17, 03:59, "platform-dev on behalf of Andrey Loskutov" 
 wrote:



Hi all,



this is a follow up on PMC response 
https://www.eclipse.org/lists/platform-dev/msg03319.html



As of today, this bug auto-closing is not active only for JDT project.



The proposal is to switch "off" bug auto-closing for the all Eclipse 
platform projects, including Platform, JDT, PDE und Equinox.

I don't think if we need an additional vote for PDE & Equinox, because the 
only active committers there are same as on the Eclipse platform.



Therefore I would like to start voting to stop auto-closing bugs in 
bugzilla, github, gitlab (or whatever else bug trackers we might use in the 
future) for all Eclipse platform development.



I think it is enough to post your +1 / 0 / -1 as a reply on this mailing 
list.

Everyone is welcome to vote but binding votes are committers`votes.

I would propose to conclude the vote by the end of the next week (25 
February).



Kind regards,

Andrey Loskutov



Спасение утопающих - дело рук самих утопающих



https://www.eclipse.org/user/aloskutov



   ___

platform-dev mailing list

platform-dev@eclipse.org

To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Wim Jongman]

-1 close close close

Please note that it is *LESS *work to keep open because *no one will ever
look at it again.*

If it still matters to people then they can reopen. It is a tool to restart
the discussion. Without closing, it would be sitting there forever.

This bug hasn't had any activity in quite some time.



If you have further information on the current state of the bug, please add it

and *reopen this bug*. The information can be, for example, that the problem

still occurs, that you still want the feature, that more information is needed,

or that the bug is (for whatever reason) no longer relevant.


On Thu, Feb 17, 2022 at 12:12 PM Jean-Francois Maury 
wrote:

> +1 stop auto closing
>
> On Thu, Feb 17, 2022 at 9:58 AM Andrey Loskutov  wrote:
>
>> Hi all,
>>
>> this is a follow up on PMC response
>> https://www.eclipse.org/lists/platform-dev/msg03319.html
>>
>> As of today, this bug auto-closing is not active only for JDT project.
>>
>> The proposal is to switch "off" bug auto-closing for the all Eclipse
>> platform projects, including Platform, JDT, PDE und Equinox.
>> I don't think if we need an additional vote for PDE & Equinox, because
>> the only active committers there are same as on the Eclipse platform.
>>
>> Therefore I would like to start voting to stop auto-closing bugs in
>> bugzilla, github, gitlab (or whatever else bug trackers we might use in the
>> future) for all Eclipse platform development.
>>
>> I think it is enough to post your +1 / 0 / -1 as a reply on this mailing
>> list.
>> Everyone is welcome to vote but binding votes are committers`votes.
>> I would propose to conclude the vote by the end of the next week (25
>> February).
>>
>> Kind regards,
>> Andrey Loskutov
>>
>> Спасение утопающих - дело рук самих утопающих
>>
>> https://www.eclipse.org/user/aloskutov
>>
>> ___
>> platform-dev mailing list
>> platform-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/platform-dev
>>
>
>
> --
>
> Jeff Maury
>
> Manager, DevTools
>
> Red Hat EMEA 
>
> jma...@redhat.com
> @RedHat    Red Hat
>   Red Hat
> 
> 
> 
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
>
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Jean-Francois Maury]

+1 stop auto closing

On Thu, Feb 17, 2022 at 9:58 AM Andrey Loskutov  wrote:

> Hi all,
>
> this is a follow up on PMC response
> https://www.eclipse.org/lists/platform-dev/msg03319.html
>
> As of today, this bug auto-closing is not active only for JDT project.
>
> The proposal is to switch "off" bug auto-closing for the all Eclipse
> platform projects, including Platform, JDT, PDE und Equinox.
> I don't think if we need an additional vote for PDE & Equinox, because the
> only active committers there are same as on the Eclipse platform.
>
> Therefore I would like to start voting to stop auto-closing bugs in
> bugzilla, github, gitlab (or whatever else bug trackers we might use in the
> future) for all Eclipse platform development.
>
> I think it is enough to post your +1 / 0 / -1 as a reply on this mailing
> list.
> Everyone is welcome to vote but binding votes are committers`votes.
> I would propose to conclude the vote by the end of the next week (25
> February).
>
> Kind regards,
> Andrey Loskutov
>
> Спасение утопающих - дело рук самих утопающих
>
> https://www.eclipse.org/user/aloskutov
>
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
>


-- 

Jeff Maury

Manager, DevTools

Red Hat EMEA 

jma...@redhat.com
@RedHat    Red Hat
  Red Hat



___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Aleksandar Kurtakov]

On Thu, Feb 17, 2022 at 11:42 AM Hannes Wellmann 
wrote:

> +1 to stop auto-closing.
>
> Nevertheless maybe it is useful to add an automatic reminder message, with
> a similar text as today but without automatically closing the bug.
> Then appropriated actions can still be taken.
>

Eclipse bugzilla bot can do that.


>
> *Gesendet:* Donnerstag, 17. Februar 2022 um 09:58 Uhr
> *Von:* "Andrey Loskutov" 
> *An:* "platform-dev" 
> *Betreff:* [platform-dev] Vote to stop bug auto-closing in all Eclipse
> platform projects
> Hi all,
>
> this is a follow up on PMC response
> https://www.eclipse.org/lists/platform-dev/msg03319.html
>
> As of today, this bug auto-closing is not active only for JDT project.
>
> The proposal is to switch "off" bug auto-closing for the all Eclipse
> platform projects, including Platform, JDT, PDE und Equinox.
> I don't think if we need an additional vote for PDE & Equinox, because the
> only active committers there are same as on the Eclipse platform.
>
> Therefore I would like to start voting to stop auto-closing bugs in
> bugzilla, github, gitlab (or whatever else bug trackers we might use in the
> future) for all Eclipse platform development.
>
> I think it is enough to post your +1 / 0 / -1 as a reply on this mailing
> list.
> Everyone is welcome to vote but binding votes are committers`votes.
> I would propose to conclude the vote by the end of the next week (25
> February).
>
> Kind regards,
> Andrey Loskutov
>
> Спасение утопающих - дело рук самих утопающих
>
> https://www.eclipse.org/user/aloskutov
>
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
>
>
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
>


-- 
Aleksandar Kurtakov
Red Hat Eclipse Team
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Aleksandar Kurtakov]

On Thu, Feb 17, 2022 at 10:58 AM Andrey Loskutov  wrote:

> Hi all,
>
> this is a follow up on PMC response
> https://www.eclipse.org/lists/platform-dev/msg03319.html
>
> As of today, this bug auto-closing is not active only for JDT project.
>
> The proposal is to switch "off" bug auto-closing for the all Eclipse
> platform projects, including Platform, JDT, PDE und Equinox.
>
I don't think if we need an additional vote for PDE & Equinox, because the
> only active committers there are same as on the Eclipse platform.
>

This should happen per project as even if active committers are  Eclipse
platform committers too not every platform committer is PDE or Equinox
committer and this doesn't guarantee that the voting will have the same
conclusion.


>
> Therefore I would like to start voting to stop auto-closing bugs in
> bugzilla, github, gitlab (or whatever else bug trackers we might use in the
> future) for all Eclipse platform development.
>
> I think it is enough to post your +1 / 0 / -1 as a reply on this mailing
> list.
> Everyone is welcome to vote but binding votes are committers`votes.
> I would propose to conclude the vote by the end of the next week (25
> February).
>

-1
In my opinion having bugs open without anyone looking into them for years
is bad and even worse as it gives false sense of support which in reality
is not there. I would change my mind if/when I see active triaging going on.


>
> Kind regards,
> Andrey Loskutov
>
> Спасение утопающих - дело рук самих утопающих
>
> https://www.eclipse.org/user/aloskutov
>
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
>


-- 
Aleksandar Kurtakov
Red Hat Eclipse Team
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Hannes Wellmann]

+1 to stop auto-closing.

 

Nevertheless maybe it is useful to add an automatic reminder message, with a similar text as today but without automatically closing the bug.
Then appropriated actions can still be taken.


 

Gesendet: Donnerstag, 17. Februar 2022 um 09:58 Uhr
Von: "Andrey Loskutov" 
An: "platform-dev" 
Betreff: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

Hi all,

this is a follow up on PMC response https://www.eclipse.org/lists/platform-dev/msg03319.html

As of today, this bug auto-closing is not active only for JDT project.

The proposal is to switch "off" bug auto-closing for the all Eclipse platform projects, including Platform, JDT, PDE und Equinox.
I don't think if we need an additional vote for PDE & Equinox, because the only active committers there are same as on the Eclipse platform.

Therefore I would like to start voting to stop auto-closing bugs in bugzilla, github, gitlab (or whatever else bug trackers we might use in the future) for all Eclipse platform development.

I think it is enough to post your +1 / 0 / -1 as a reply on this mailing list.
Everyone is welcome to vote but binding votes are committers`votes.
I would propose to conclude the vote by the end of the next week (25 February).

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev




 

 
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[S A]

+1

On Thu, 17 Feb 2022 at 10:58, Andrey Loskutov  wrote:

> Hi all,
>
> this is a follow up on PMC response
> https://www.eclipse.org/lists/platform-dev/msg03319.html
>
> As of today, this bug auto-closing is not active only for JDT project.
>
> The proposal is to switch "off" bug auto-closing for the all Eclipse
> platform projects, including Platform, JDT, PDE und Equinox.
> I don't think if we need an additional vote for PDE & Equinox, because the
> only active committers there are same as on the Eclipse platform.
>
> Therefore I would like to start voting to stop auto-closing bugs in
> bugzilla, github, gitlab (or whatever else bug trackers we might use in the
> future) for all Eclipse platform development.
>
> I think it is enough to post your +1 / 0 / -1 as a reply on this mailing
> list.
> Everyone is welcome to vote but binding votes are committers`votes.
> I would propose to conclude the vote by the end of the next week (25
> February).
>
> Kind regards,
> Andrey Loskutov
>
> Спасение утопающих - дело рук самих утопающих
>
> https://www.eclipse.org/user/aloskutov
>
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
>
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Alexander Fedorov]

+1

Regards,
AF

2/17/2022 11:58 AM, Andrey Loskutov пишет:

Hi all,

this is a follow up on PMC response 
https://www.eclipse.org/lists/platform-dev/msg03319.html

As of today, this bug auto-closing is not active only for JDT project.

The proposal is to switch "off" bug auto-closing for the all Eclipse platform 
projects, including Platform, JDT, PDE und Equinox.
I don't think if we need an additional vote for PDE & Equinox, because the only 
active committers there are same as on the Eclipse platform.

Therefore I would like to start voting to stop auto-closing bugs in bugzilla, 
github, gitlab (or whatever else bug trackers we might use in the future) for 
all Eclipse platform development.

I think it is enough to post your +1 / 0 / -1 as a reply on this mailing list.
Everyone is welcome to vote but binding votes are committers`votes.
I would propose to conclude the vote by the end of the next week (25 February).

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev


___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Christoph Läubrich]

+1

Am 17.02.22 um 09:58 schrieb Andrey Loskutov:

Hi all,

this is a follow up on PMC response 
https://www.eclipse.org/lists/platform-dev/msg03319.html

As of today, this bug auto-closing is not active only for JDT project.

The proposal is to switch "off" bug auto-closing for the all Eclipse platform 
projects, including Platform, JDT, PDE und Equinox.
I don't think if we need an additional vote for PDE & Equinox, because the only 
active committers there are same as on the Eclipse platform.

Therefore I would like to start voting to stop auto-closing bugs in bugzilla, 
github, gitlab (or whatever else bug trackers we might use in the future) for 
all Eclipse platform development.

I think it is enough to post your +1 / 0 / -1 as a reply on this mailing list.
Everyone is welcome to vote but binding votes are committers`votes.
I would propose to conclude the vote by the end of the next week (25 February).

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Mickael Istria]

-1
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Sarika Sinha]

+1 to stop auto closing of bugs.
Thanks & Regards,
Sarika

On 17/02/22, 2:44 PM, "platform-dev on behalf of Thomas Singer" 
 wrote:

+1 for not auto-closing bugs

On 2022-02-17 09:58, Andrey Loskutov wrote:
> Hi all,
> 
> this is a follow up on PMC response 
https://www.eclipse.org/lists/platform-dev/msg03319.html
> 
> As of today, this bug auto-closing is not active only for JDT project.
> 
> The proposal is to switch "off" bug auto-closing for the all Eclipse 
platform projects, including Platform, JDT, PDE und Equinox.
> I don't think if we need an additional vote for PDE & Equinox, because 
the only active committers there are same as on the Eclipse platform.
> 
> Therefore I would like to start voting to stop auto-closing bugs in 
bugzilla, github, gitlab (or whatever else bug trackers we might use in the 
future) for all Eclipse platform development.
> 
> I think it is enough to post your +1 / 0 / -1 as a reply on this mailing 
list.
> Everyone is welcome to vote but binding votes are committers`votes.
> I would propose to conclude the vote by the end of the next week (25 
February).
> 
> Kind regards,
> Andrey Loskutov
> 
> Спасение утопающих - дело рук самих утопающих
> 
> https://www.eclipse.org/user/aloskutov
> 
> ___
> platform-dev mailing list
> platform-dev@eclipse.org
> To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

[Thomas Singer]

+1 for not auto-closing bugs

On 2022-02-17 09:58, Andrey Loskutov wrote:

Hi all,

this is a follow up on PMC response 
https://www.eclipse.org/lists/platform-dev/msg03319.html

As of today, this bug auto-closing is not active only for JDT project.

The proposal is to switch "off" bug auto-closing for the all Eclipse platform 
projects, including Platform, JDT, PDE und Equinox.
I don't think if we need an additional vote for PDE & Equinox, because the only 
active committers there are same as on the Eclipse platform.

Therefore I would like to start voting to stop auto-closing bugs in bugzilla, 
github, gitlab (or whatever else bug trackers we might use in the future) for 
all Eclipse platform development.

I think it is enough to post your +1 / 0 / -1 as a reply on this mailing list.
Everyone is welcome to vote but binding votes are committers`votes.
I would propose to conclude the vote by the end of the next week (25 February).

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev