From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3717CC433FE for ; Thu, 29 Sep 2022 13:04:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235475AbiI2NEP (ORCPT ); Thu, 29 Sep 2022 09:04:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35618 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235623AbiI2NEO (ORCPT ); Thu, 29 Sep 2022 09:04:14 -0400 Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D8AA917AC91 for ; Thu, 29 Sep 2022 06:04:13 -0700 (PDT) Received: by mail-qt1-x830.google.com with SMTP id s18so688719qtx.6 for ; Thu, 29 Sep 2022 06:04:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date; bh=qpdOjHoVeeBXawuhfGss23fD+10+rI0bqQ2kczWUCBE=; b=G5+5vtHrOwCkZ1NKDM/wqQUQ1URVwqeIG62iNVHh68BtD5jU9DHjLQGOglsRV7k9QL odkEPI5MJ6oy9/j9AW8BD1gdwGcGBS3MYWXx6f/OvhJR/XcdrdImKVshig0EcIBZIpHb EOYhIZesKEbUMT7ki+TlhNL/ZXma/Wub52ozU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date; bh=qpdOjHoVeeBXawuhfGss23fD+10+rI0bqQ2kczWUCBE=; b=bYxk5Udvq7AUF5AkvZLAMjeF5sUTutAUl1I5eNjopw+STmVG0oBdiZHU/5Znj4JNX6 IKDi1IA0oNEpAkZDInZNuzxQBN1QYqYEdjIx10WbcFyG9WsmodSbwCbqbbE+0dcAtapb f6Bp8BsiaQp8bI6osLM+APblZBunNJXdiCoX4Pgxnf6BQqeNGgvsNiMkV7DjBJrH+EzY WO2B481K9YhSEdBYxWwdw/nRVkTzi8zlcBCuot7VQ+IXyHXJM1w+0s9XTyoC0wD52HGc 1/19DVd4uRmxjBZ/woRd9DaygvnawAUNZiT7u1B+8Tzkw/L8y/05sIUJoyOziIptYOoB ukxg== X-Gm-Message-State: ACrzQf3CFs/CA3bTWpYn1wt2siEwVJ6ndnprfkZTqll7C0U3qMYbF6w2 uUJ9jPnsMDmpf9vQLX/f18pzzQ== X-Google-Smtp-Source: AMsMyM5MXuYjd1O59zouVYEcPOQV28TNv4ifR4ELIB2VcXSipLzGkZAbTBUDRw/04XgZ+YCRklN/dA== X-Received: by 2002:a05:622a:1492:b0:35c:b7e6:12ef with SMTP id t18-20020a05622a149200b0035cb7e612efmr2215287qtx.94.1664456652720; Thu, 29 Sep 2022 06:04:12 -0700 (PDT) Received: from meerkat.local (bras-base-mtrlpq5031w-grc-33-142-113-79-147.dsl.bell.ca. [142.113.79.147]) by smtp.gmail.com with ESMTPSA id bj7-20020a05620a190700b006bad7a2964fsm5936297qkb.78.2022.09.29.06.04.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 29 Sep 2022 06:04:12 -0700 (PDT) Date: Thu, 29 Sep 2022 09:04:10 -0400 From: Konstantin Ryabitsev To: "Artem S. Tashkinov" Cc: Thorsten Leemhuis , workflows@vger.kernel.org, LKML , Greg KH , Linus Torvalds , "regressions@lists.linux.dev" , ksummit@lists.linux.dev Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues" Message-ID: <20220929130410.hxtmwmoogzkwcey7@meerkat.local> References: <05d149a0-e3de-8b09-ecc0-3ea73e080be3@leemhuis.info> <93a37d72-9a88-2eec-5125-9db3d67f5b65@gmx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <93a37d72-9a88-2eec-5125-9db3d67f5b65@gmx.com> Precedence: bulk List-ID: X-Mailing-List: workflows@vger.kernel.org On Thu, Sep 29, 2022 at 12:22:35PM +0000, Artem S. Tashkinov wrote: > AFAIK, the kernel bugzilla is a Linux Foundation project and the > organization receives funding from its very rich members including > Google, Meta, Intel, and even Microsoft. The fact that no one is > seriously working on it looks shameful and sad. We are not talking about > a minor odd library with a dozen users we are talking about the kernel. The bugzilla as a software platform is a Mozilla product, not Linux Foundation. Unfortunately, it's pretty much dead: 1. all development has stopped years ago 2. it doesn't even work with recent MySQL servers 3. it is written in perl5 and can only pretty much run with mod_perl We're committed to running it as far as we can, but we all must also admit that the platform is near-death and probably will become an ever-increasing burden to keep it operating. Heck, one of our IT staff is currently trying to convert bugzilla.kernel.org to use Postgres just so we can keep operating it past the end of 2022. The Linux Foundation IT is in charge of running infrastructure -- we're not a development shop. All of our software projects are pretty much "skunkworks" efforts (and yes, this includes b4). We do have ability to fund development efforts -- LF has been the primary sponsor behind public-inbox.org over the past 3 years. However, there must be a clear, strong, and well-articulated mandate from the community. From what I heard, the vast majority of maintainers simply want a web form that would allow someone to: 1. clearly state what kernel version they are using 2. clearly describe what they were trying to do 3. explain what they expected vs. what they got 4. attach any files 5. give this bug report a unique identifier Then a designated person would look through the bug report and either: a. quick-close it (with the usual "talk to your distro" or "don't use a tainted kernel" etc) b. identify the responsible maintainers and notify them The hard part is not technical -- the hard part is that "designated person." Being a bugmaster is a thankless job that leads to burnout, regardless of how well you are paid. Everyone is constantly irate at you from both ends -- the users are annoyed because their stuff doesn't work, and the maintainers are annoyed because you keep yanking them to work on dull problems that require a ton of back-and-forth with people who aren't capable of applying patches and booting custom kernels. Before we try to fix/replace bugzilla, we really need to figure out the entire process and pinpoint who is going to be the one in charge of bug reports. If you think that LF should establish a fund for a position like that, then you should probably approach LF fellows (Greg KH, Shuah Khan), who can then talk to LF management. The IT team will be happy to support you with the tooling, but tooling should come second to that -- otherwise we'll just be replacing an old and rusty dumpster on fire with a new and shiny dumpster on fire. -K