From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-qk1-f173.google.com (mail-qk1-f173.google.com [209.85.222.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 82DBA4424 for ; Tue, 4 Oct 2022 20:25:43 +0000 (UTC) Received: by mail-qk1-f173.google.com with SMTP id u28so9094552qku.2 for ; Tue, 04 Oct 2022 13:25:43 -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=DGvJV2IIUZV7S3zU1Gd//TygTt/OG32AqXy+s65/XH0=; b=CQ6jzxz7pGsi/7Unxn/3myaDbDXR9ldixRssga58u32qNXAC6JjOpSI/qeMcu/HIUX EFZKLfcJkGHxiZasUc+40u8aAkxk+iPZVw4KCaeyTry2PMcmjVKojL9rrmRNk8Lg44fu YRxoeUmyTDJiq+KqrgkkWv23G0AOM3RM/FsI0= 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=DGvJV2IIUZV7S3zU1Gd//TygTt/OG32AqXy+s65/XH0=; b=QBSzCM3XfXlrvZm198sAuJ87r1BTtCxN+nsMnJ1g93VxcHqM6uWn2Q98U2mE31VS61 HXZ2iFO4UEdiaLGHIUfx24ctvJHbEGTbqAOvGE1MQkIMkiQvnGcNDklkpX/0Y0betmwB xn7cYFxN0It/NDW3jF5UWWYGDVOWlOsD/pxKqFFw5/Vmw52CZzAv12QgtZxSKbvlVgvl Ij/6dUws6SP/uymJeyUJDGBDOdSDsOiKltDxM09FgmmlNg8uHWso8GYWWamVHG7BBX3q e37+yudRyGvIjlle961FQTbf7GNn3HPpDAFX922sscMmDQ32vYl9IX3G63Bvc72YAAQI 3PHQ== X-Gm-Message-State: ACrzQf1c/key+RiZvZVXlePNahrkApSzbup9WUVljwWG7+iufRAoGaV8 8PUlZdsCJPT4DtY2IU450u1jOQ== X-Google-Smtp-Source: AMsMyM5g235+vx6KmW0J4fCOEYlimbuJcIi/EoLRom6zkxz2Hs63d2hk+LFSJ/eSNDEQQfP6UjUKNQ== X-Received: by 2002:a05:620a:12f5:b0:6ce:742c:b0d0 with SMTP id f21-20020a05620a12f500b006ce742cb0d0mr17910376qkl.19.1664915142362; Tue, 04 Oct 2022 13:25:42 -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 bp37-20020a05620a45a500b006ce7bb8518bsm15160606qkb.5.2022.10.04.13.25.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 04 Oct 2022 13:25:42 -0700 (PDT) Date: Tue, 4 Oct 2022 16:25:40 -0400 From: Konstantin Ryabitsev To: Thorsten Leemhuis Cc: "Artem S. Tashkinov" , ksummit , workflows@vger.kernel.org, LKML , Greg KH , Linus Torvalds , "regressions@lists.linux.dev" Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues" Message-ID: <20221004202540.etokkm3jk6sk7z7y@meerkat.local> References: <20221004175354.bfvg3vhfqch35ib5@meerkat.local> Precedence: bulk X-Mailing-List: ksummit@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: On Tue, Oct 04, 2022 at 10:06:28PM +0200, Thorsten Leemhuis wrote: > Your plan would afaics mean that we invest further into a software > abandoned by its upstream and already becoming more and more of a > maintenance burden. That investment would also further increase our > dependency on that software by establishing workflows that rely on it. > Is that really wise at this point? Wouldn't it be better to spend that > time and effort to build something better that is more future proof? Unfortunately, there's no such thing. ;) And maybe we'll even help tip the course of history into the other direction -- Red Hat uses bugzilla, and so does OpenSuse, so there's a pretty good core of well-funded companies that would be in a position to help keep bugzilla going if it's looking like the platform is still alive. Or that could all be wishful thinking and they'll all migrate to Jira or something equally horrible, who knows. I'm hoping that by keeping the bulk of this exchange relying on established decentralized end-to-end messaging, we won't be painting ourselves into the corner quite as much as with a tool that requires all interaction to happen strictly via the web interface. The alternative is to hire the folks behind patchwork to write "bugwork". -K