From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) by sourceware.org (Postfix) with ESMTPS id 513753857351 for ; Thu, 29 Sep 2022 18:54:25 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 513753857351 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-pj1-x102c.google.com with SMTP id x1-20020a17090ab00100b001fda21bbc90so6813287pjq.3 for ; Thu, 29 Sep 2022 11:54:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=Xl9t7aTQVDDHFCL28KICiWtIl/z7VmaWq0vvAYDLXVE=; b=QV0H2vTLE1bNJGIpQJbmTSO3GmciC+EfHFuvjeScX0MOyDiqnlCoty3nbp1iqzyWFz uxjRtSt2YFqCrdXAvFTQLLPH2hCEMgxbOermFpdUWTVPef1qp/4BjkuOcDgf5TIcv+Hp kP6HhNIMcoDHLyYyHdxDr2lh0wUvqtZuwO3SLpmCa7XI2p8nF/e/8QxDlUB4rG2j1xVm jAZzTTazXYNt3/DW2vPbS0JUt91tBUE7WOirWZLj3i3M8M22dTNNF7tLv7w+TeTchODV Y6mdzMZVEvH2Oa9goGvezIDLvrAQbz3f+K+tXNSmYBh7LscQMvokXjNAwFHxuv+pmoAl RTXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=Xl9t7aTQVDDHFCL28KICiWtIl/z7VmaWq0vvAYDLXVE=; b=chbhYTMzXRUCLvUNYlcZarzJgrwThI+OE7zm49R2MGz7/GEvFenJWea9XzgLPVlLLw A/WYZJPZ2RL01mqmq0LUqE0D4epa7ndOBon92mN3YLOLrSwx1oFKbch6MkAl6MT4U/jI V6GyhCkLGd/sKoij0e59vGhssZip6Ok8HMnCMSDQm3c32Fkhhk4R/g86kLoF/iLbsB8e IHPxkMTBAbnsGNlJRRq/MEEcfKmVnUdBux3Yo5i8/J5h7ztzrd2ljc90cefOfa4t+B0F bm3ptQqFONVwWojfZayKMg7n+HetpGsckAsoVIe5FlpD18tg0b9g8LiStpQZkTDcqE0W JAng== X-Gm-Message-State: ACrzQf2Y3f2YQpi3oaWnaXLmWSN4nMz4vW7LBxOaosHM//f9BJSuTTYv 6DJdJXzqdYlPh4otKBCiKQMLSAgF9USOYRy+Ly1MCFuA X-Google-Smtp-Source: AMsMyM5o2/ES1De7WGXU8UWko0xRSepKCtGWxvZiFeSW3nVwrmffuHWptdn4Z5CendtbYT89x2abWOLSwlW6exapb0A= X-Received: by 2002:a17:902:d2c7:b0:176:c8a4:2f2 with SMTP id n7-20020a170902d2c700b00176c8a402f2mr4832852plc.119.1664477664073; Thu, 29 Sep 2022 11:54:24 -0700 (PDT) MIME-Version: 1.0 References: <87v8p6i6ht.fsf@meer.lwn.net> In-Reply-To: From: Andrew Pinski Date: Thu, 29 Sep 2022 11:54:11 -0700 Message-ID: Subject: Re: The GNU Toolchain Infrastructure Project To: Overseers mailing list Cc: Joseph Myers , Jonathan Corbet Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Thu, Sep 29, 2022 at 10:13 AM Joseph Myers via Overseers wrote: > > On Thu, 29 Sep 2022, Jonathan Corbet via Overseers wrote: > > > Just for the record, it is still my feeling that the LF's infrastructure > > management has been a good thing for the kernel community. Whether it > > would be suitable for the toolchain community is not something I'm in a > > position to have an opinion on. If anybody is curious about how > > interactions with that group work, there is a current discussion on > > bugzilla that might be interesting: > > > > https://lwn.net/ml/ksummit-discuss/05d149a0-e3de-8b09-ecc0-3ea73e080be3@leemhuis.info/ > > Regarding Bugzilla, also see the GTI TAC meeting (24 Aug 2022) recording > at 23:37 to 25:44. It's not clear what good solutions are right now for > free software issue tracking, taking into account considerations such as: > > * easy for anyone to submit and comment on bugs; > > * protection against spam bug and comment submission (which is in tension > with easy bug submission; we have restricted account creation, with people > needing to email overseers to create an account on sourceware Bugzilla at > all, or to email gcc-bugzilla-account-request to create an account on GCC > Bugzilla from a large number of common email domains in which spammers can > easily create accounts); > > * configurability of the fields and values of those fields and other logic > used in the bug tracker; I don't think there is even a non-free bug tracking system which conforms to these requirements which is not bugzilla. github does not even support fields at all. It supports keywords but they are not as powerful as the fields. JIRA supports fields but searching requires you to know basically SQL. gitlab issue tracking is similar to github but has some fields. I looked into others and most don't have the (custom) fields support and easy searchability. I know the LLVM folks moved from bugzilla to github but that would be backwards movement for GCC bug tracking. The LLVM folks are not as active in their bug tracking system before as far as I could tell unlike the way majority of the projects on sourceware have been. Thanks, Andrew Pinski > > * ability to get a local copy of the tracker data (this is an area where > Bugzilla is weak; you can probably do something with the REST API, but > it's not designed to make it easy for someone to keep a local copy of all > the data up to date the way git is); > > * being an actively maintained project (that also being a concern for > Bugzilla). > > -- > Joseph S. Myers > joseph@codesourcery.com