From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 0B9523858421 for ; Thu, 3 Aug 2023 10:10:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0B9523858421 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1691057408; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=zgJOF/oUf1aQE75D50LoxFweZZIqUrd7P5dNsh6chfo=; b=VuoCwTnOobwog+6C239R0DpJByIbgDnFOKC2ZLTOc8LYA4sVukoaGhBe9zytYZHZmGR9DM 9vGe7j3sIidZN/oP78FJxI050qSpwgmzoBJvNV86zEvd0UX5OOctd4gK+ZoCFcI/4u1sTq x/j3WvSq9CemSwln1s62gG9SwU24GnQ= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-495-0HVgHkq1O_yYyuzed_lcXg-1; Thu, 03 Aug 2023 06:10:03 -0400 X-MC-Unique: 0HVgHkq1O_yYyuzed_lcXg-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 0642C185A791; Thu, 3 Aug 2023 10:10:03 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.2.16.14]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 8B8042166B25; Thu, 3 Aug 2023 10:10:01 +0000 (UTC) From: Florian Weimer To: Konstantin Ryabitsev Cc: Carlos O'Donell via Libc-alpha , Carlos O'Donell , Joseph Myers , "Ryan S. Arnold" , Paul Eggert , Jakub Jelinek , Maxim Kuvyrkov , Andreas Schwab Subject: Re: Core Toolchain Infrastructure - Services for glibc References: <45e98807-908f-0968-b6fe-5dbb0af265b1@redhat.com> <87ttu6oh9j.fsf@oldenburg.str.redhat.com> <20230714-card-radium-prow-27d2f1@meerkat> Date: Thu, 03 Aug 2023 12:10:00 +0200 In-Reply-To: <20230714-card-radium-prow-27d2f1@meerkat> (Konstantin Ryabitsev's message of "Fri, 14 Jul 2023 11:34:26 -0400") Message-ID: <87zg38zbbb.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-4.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE 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: * Konstantin Ryabitsev: > On Fri, Jul 14, 2023 at 01:38:00PM +0200, Florian Weimer wrote: >> > * Support public-inbox for mailing list archives. >> > * Use of public-inbox means archives can be cloned and copied. >> > * Use of LF IT Subspace mailing list services (mlmmj, postfix). >>=20 >> I assume LF IT is able to run mailing lists without =E2=80=9Cvia=E2=80= =9D From: >> rewriting? > > Yes, that practice is horrible and we do not support it in any way shape = or > form for mailing lists. That's good to know. >> > * bug database >> > * Consider starting fresh in new Bugzilla 5.0.4+ instance and freeze = old product. >> > * glibc component in sourceware instance marked "Not open for new bug= s." >> > * No easy way to clone this but we can discuss options. >> > * Isolate bugzilla from other services. >>=20 >> Does LF IT offer some Bugzilla anti-spam services? To what extent do we >> need to constrain new sign-ups? > > We have various approaches here, depending on the project. > > We do not constrain sign-ups for bugzilla.kernel.org. We have a script > that reports new comments containing links or potentially spammy > attachments. These comments are junked and accounts posting them are > banned. > > We do constrain sign-ups for bugzilla.yoctoproject.org -- users must > request a new account to be created before they can file any bugs. Okay, so there are options, good. >> Can we keep using the AdaCore hooks? Or would they have to run on the >> side somehow? Who is going to implement changes to the AdaCore scripts? > > This is the main point of contemplation -- we do not currently support cu= stom > hooks on the server side: > > - they tend to significantly slow down pushes > - they run extensive codebases with the same permissions as the owner of = the > repositories, significantly increasing security risks > > Our recommendation was to move all CI tasks to a system that is better > suited for it. For example, CI can run on a patchwork system and the > pre-commit hook can then check that each commit matches a patchwork > entry that passed CI. One way to deal with this on our end would be a policy that allows branch rebases to pull faulty commits for a time. Lately we have pushed some misformatted commit messages in the current setup, with its commit hooks. Thanks, Florian