[21:27:29] I understand why people want to do it, but it's really disruptive to bulk close tasks just because they haven't been touched in a certain amount of time :/ [21:29:11] legoktm: We should have a LRU phab bump bot [21:30:11] one way to fix the problem >.< [21:30:35] but the whole point of marking these tasks as low/lowest is so that people can ignore them when doing planning, etc. They're still legitimate bugs/feature requests [21:31:06] > Bugs are ideas. They're ideas about how software should work. People should take great caution when marking bugs as resolved to avoid killing good ideas. [21:31:50] (from https://www.mediawiki.org/wiki/User:MZMcBride/Bugs#Philosophy) [21:33:34] legoktm, https://phabricator.wikimedia.org/T248034 and https://phabricator.wikimedia.org/T252522 may be relevant [21:34:11] Stalled is differen to open and low/lowest [21:34:58] stalling is ok, lowest is ok. but just closing it with reason "hasn't been done yet" is baaad [21:35:25] unless it's truly declined forever [21:35:54] yeah, I like the framing legoktm quoted and I also like the "a bug report is a gift from your user" framing [21:36:57] (with the corollary that throwing it away is both rude and a self-disservice) [21:53:59] legoktm: might be best to raise it with them directly [21:55:40] imagine you are a volunteer..you report a bug.. first they wait 5 years and do nothing, then they lower priority and then they say "we close everything older than 6 months"...I can not think of an action that would make it more frustrating [21:58:13] on some of the tickets the last comment was even "certainly a good idea" or "works as intended" and then followed by the standard template [22:02:54] in some cases the bug report is "wrong" [22:02:54] also, what specifically are we discussing here? I linked relevant tasks I know of but did something actually get closed this way recently? [22:03:06] I missed the intro :) [22:03:09] it should be declined, but perhaps nobody is brave enough to do that [22:03:19] or doesn't feel they have the power to take that decision [22:03:41] Izno: a WMF staffer just closed a bunch of old tickets [22:03:49] otoh, other bug reports should clearly be fixed "at some point" [22:03:54] and they SHALL NOT be closed [22:03:56] RhinosF1, ok, where? [22:04:02] there was mass editing in phabricator [22:04:05] entire pages full [22:04:29] Izno: https://phabricator.wikimedia.org/p/MPhamWMF/ [22:04:33] jesus [22:04:35] it's really bad for community relations to mass reject [22:04:36] seriously [22:04:46] I already yelled at them once for this [22:04:58] I opened a couple of the more obvious ones [22:05:14] like where WMF employees said it's a good idea, for example [22:05:16] Izno: I've just told them in the search channel to consider explaining it [22:05:25] or where it's been called a good task for volunteers [22:05:29] not just consider explaining it, undo it entirely [22:05:44] let me see if I can find the last stupid time this happened [22:05:44] Izno: apparently a response is coming. Hopefully it will be that. [22:06:09] it will be linked from the one I already commented earlier [22:06:19] that's Really Bad™ [22:06:25] did he even read them all? [22:06:54] it's one thing if he actually read them and said closing because doing X is not appropriate for Y [22:07:15] but this is "I am closing this because I find the project cluttered" [22:07:24] https://phabricator.wikimedia.org/T267161 is the last time this happened [22:07:26] Hi, I know some of you have noticed that I recently bulk closed low/est priority 'inactive' search tickets. This was an attempt to tame our backlog a bit to make our workflows more usable, but I want to own that this may be counter to how these tickets and boards have been used to track our software development and ideas and communication with our volunteers, and apologize for making a big move without understanding its full consequences [22:07:30] well, you could use filters [22:08:13] hi mpham [22:08:20] we were just... discussing about that [22:08:29] mpham: if you're trying to clean up team specific boards, and it's not stuff you're going to work on soon (or even, ever), just untag your team, and fix your herald rule so it doesn't re-add your project(s) [22:09:10] thanks for the suggestion Reedy . i'll try that approach in the future [22:10:20] mpham: I think now would be better. As I'm reopening the tasks and removing your tag on the ones you just closed. [22:10:51] ok, thanks