On 03/12/2022 08.09, Michał Górny wrote:
Hi,I'd like to propose replacing the current UNCONFIRMED and CONFIRMED bug states with a simple NEW state. Why? 1. Only a handful of developers actually uses these two statuses in a meaningful way. 2. Some users are confused and demotivated by having their bugs stay UNCONFIRMED for a long time.
While I do not strictly oppose that change, I like the UNCONFIRMED / CONFIRMED states.
I don't know how 1. is an argument for removing it. Quite the contrary, the statement itself says that the feature is used. Furthermore, it is not my observation that only a handful of developers use it. Most open bugs are in the CONF state [1], so I would conclude that most use the feature. Of course, that depends on your definition of "used in a meaningful way". For me, CONFIRMED was always about someone, usually a -dev, acknowledging that the bug reports a valid issue that needs to be addressed (either by Gentoo or upstream). Is that using it in a meaningful way?
And 2. doesn't appear to be a solution but helps disguise the underlying issue. We should instead educate users that Gentoo, like most volunteer-driven FOSS projects, is short on the workforce. Therefore users can only expect that some bugs will be handled immediately, while others may lay dormant for an extended period (for different reasons).
Ultimately, the central angle to tackle this issue is e to empower users to fix the problems themselves or at least provide minimal reproducers and debugging information. We already put in much effort (and we are IMHO quite good at it already), but it requires continuous effort…
- Flow1: https://bugs.gentoo.org/buglist.cgi?component=Current%20packages&list_id=6623145&product=Gentoo%20Linux&resolution=---
OpenPGP_0x8CAC2A9678548E35.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
