Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp6545314rwl; Tue, 4 Apr 2023 14:42:02 -0700 (PDT) X-Google-Smtp-Source: AKy350bG/PZux8jgCKVtvZw8uoujXt2P78yEqF2WHQJbKP2V8pbgG5rEZNIc8D0RaauHRenY5G1B X-Received: by 2002:a05:6a20:1b10:b0:d9:f086:e756 with SMTP id ch16-20020a056a201b1000b000d9f086e756mr3036224pzb.39.1680644522524; Tue, 04 Apr 2023 14:42:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1680644522; cv=none; d=google.com; s=arc-20160816; b=SUYZd/v8g242UZBfZDy53hzgkCc8nq257JLawpLxM6qwSEhB8qa+MQiHBuG27tYHrQ bif2aqRN/NPdpE1zMEfGiTVkmGP4M0ohdbG5VSSY5zPaep3udsJo2lkp7cwHM+OAg6zI 72rlmk2/xkja4fxkEqu3sXuWT6YjGuDizH3zGOVka6Yx/nmirn5y0M8OKCjtJKxOY06y yQjG21uL8CQ93tO9kstvBr81PChMhbgjxu+VxxgXw0kb4DYECGrQtwbWC1v0VB0JSsPG C6KF/giqmJeZ3W8URhO4jVBb0M3Y2tbIFaoOVJSo+ZHL8nU4fevPGb46MctY+HnjYDbh swlg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:reply-to:message-id:subject:cc:to:from:date :dkim-signature:dkim-signature; bh=c6rnFBcBWfr2aiT8YSmtZUrPXOfzsUgPS2qkwzrhBQs=; b=uDV3Cj7XjghXrtnSiGgqPqwwq/OrK1JmzIoB5poLRq8beojkUQny0ZFnoFF6ok8GUe rX/uVU7u5oACBJZoC9WsKyTODEgcpzkmSJbtaw9Q2oIirasCqPYPToYdQYcE6o9Achpl NUjwWBDPasY2edOFgE1D69gxM9Gw7R58njH2LqVVj3cCBMVc/5d6VdlhLZ0sv0i75wo/ PIEafEXpEiM38v1kjXesxJq1dIF+/XFOnbnfy+0avoBeOC9G9Zy6D2Yv9d019hRDDwti AYZsercBKCelArlH8kFqXUu3MKKFO7XEVZJcWgr3rQwGQNGJnpxSXbFCzuK8v4rE/SpT FrSA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=Juq+gzub; dkim=neutral (no key) header.i=@suse.cz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w5-20020a623005000000b00628205a7f7esi11124357pfw.50.2023.04.04.14.41.51; Tue, 04 Apr 2023 14:42:02 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=Juq+gzub; dkim=neutral (no key) header.i=@suse.cz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236495AbjDDVjY (ORCPT + 99 others); Tue, 4 Apr 2023 17:39:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45872 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236421AbjDDVjW (ORCPT ); Tue, 4 Apr 2023 17:39:22 -0400 Received: from smtp-out2.suse.de (smtp-out2.suse.de [IPv6:2001:67c:2178:6::1d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BDA8D40FF; Tue, 4 Apr 2023 14:39:20 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 3BA411FDBE; Tue, 4 Apr 2023 21:39:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1680644359; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=c6rnFBcBWfr2aiT8YSmtZUrPXOfzsUgPS2qkwzrhBQs=; b=Juq+gzubV1kWRI+fBWdnbjM58H1OERRfulwEMts4fHSuASfQ6Bv5GcNBosDDlj6v44k+FH YSaIOuVjmrWSPAWP8psqWWbYgFn8mcPY78ij01RsT+NQ3BSiOX6tMOxeQdoqy9rlhLQWBm 1TVDUf0V/hGk4KQxFn4f9W/78Dx0wE0= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1680644359; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=c6rnFBcBWfr2aiT8YSmtZUrPXOfzsUgPS2qkwzrhBQs=; b=ujFyYHLB72/95xHjjUrl1gOKROPgRo1Zmn5OLJ7fk9tgPzotZGvKHOiVFGqPvThXoxtKY2 ke/9GUrfIP3HAvCw== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 0D42713920; Tue, 4 Apr 2023 21:39:19 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id tiFWAgeZLGS+LQAAMHmgww (envelope-from ); Tue, 04 Apr 2023 21:39:19 +0000 Date: Tue, 4 Apr 2023 23:39:17 +0200 From: David Sterba To: Konstantin Ryabitsev Cc: "Artem S. Tashkinov" , workflows@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Introducing bugbot Message-ID: <20230404213917.GG19619@twin.jikos.cz> Reply-To: dsterba@suse.cz References: <022e2ef8-2a94-3109-ab90-9ee980915887@gmx.com> <20230404-uncrown-detonate-8bc1ac@meerkat> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230404-uncrown-detonate-8bc1ac@meerkat> User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12) X-Spam-Status: No, score=-1.5 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_SOFTFAIL autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 04, 2023 at 01:35:34PM -0400, Konstantin Ryabitsev wrote: > On Tue, Apr 04, 2023 at 04:16:08PM +0000, Artem S. Tashkinov wrote: > > I love everything about what you've done except I've got a minor feature > > request for the kernel bugzilla and this new workflow specifically. > > Great to hear. > > > Let's have a bot which polls open bug reports every 3-6 months with this > > question: > > > > "Is this still an issue in the current kernel? Please leave a comment or > > this bug report will be closed due to inactivity". > > I plan to do it slightly differently -- there will be a "housekeeping" command > running daily that will auto-close bugs that haven't seen any activity for a > defined period (90 days, for example), with a message like: > > "This bug is now closed due to inactivity. Please reopen if this issue is > still relevant with the latest kernel version." Will there be a way to opt out of this? I'd rather see any bug closed after an inspection from a human, I find the auto-close messages a bit rude and I've read similar sentiment from others. The upstream bugzilla is a best-effort level of support so it's true that bugs are left open for months, sometimes years unfortunately, but I've seen many cases where the report is valid or the "fix" is to improve documentation. If we had enough people routinely going through the reports then some sort of reminders would make sense but we don't. I take the bug reports a task pool if there aren't more pressing things to do, which may not be the same way how others use bugzilla.k.org so I'd be fine with opting out of the auto-close or maybe out of any bugbot interactions.