Le jeudi 5 janvier 2023 à 11:02 AM, Halla Rempt <b...@valdyas.org> a écrit :
> Hi, > > I don't want to be a downer, but KDE Gardening is just making work for me, > instead of helping out. Randomly replying to bug reports or merge requests > without any knowledge of the project or how the team works only means more > work for me, since I have to take action every time, and that takes time I > would prefer to actually spend on my project. > > I guess it's fine for totally unmaintained projects where nobody is involved > anymore, like KDE bindings, but for actively maintained projects, it's not > helpful. At least, I do not find it helpful. Same here unfortunately with some kde-www tickets. I had to get out of my way to revert the status of some bugs report after it was changed to "need info" and was going to be automatically closed. This also happened to many tickets for Peruse and probably other projects too that I'm not following. If a ticket is in a "reported" state for a while, the solution is not to put it in the "needs info" automatically. This create more emails that I then need to read and correctly reclassify before the two weeks period as otherwise a perfectly valid ticket might be closed by mistake. Hector Martin had a nice thread on twitter about it a while ago (https://webcache.googleusercontent.com/search?q=cache:ZXl2pZ7teS4J:https://twitter.com/marcan42/status/1581245555753521152&cd=1&hl=en&ct=clnk&gl=de&lr=lang_fr|lang_en&client=firefox-b-d) that it was better to manually review the tickets or let stale tickets accumulate than just automatically closing the stale tickets. As it was otherwise quite disrespectful for the user who took some time to report a bug just to see their bug being automatically closed because nobody had the time to look into it. > Is there a way to actively exclude a project from this? > > Halla
