From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=benboeckel.net header.i=@benboeckel.net header.b="e0hsgplA"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="e25QCN4i" Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 447FA18D for ; Wed, 22 Nov 2023 16:53:48 -0800 (PST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 399315C007D; Wed, 22 Nov 2023 19:53:44 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 22 Nov 2023 19:53:44 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=benboeckel.net; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to; s=fm3; t=1700700824; x=1700787224; bh=HOq93W3M+1IvNOCOMEdNVb7Ln RfO6RnR7DLtnUG4LnA=; b=e0hsgplAcWHGU8kAcCD9imwJ/Lp+ziDGeG1i+ECIl VEHaScAM8J8bIYD2CnKJr/6n6/cDK1rmptr1DdRs+WWJMw6K4KB2fIQZ/PG4nj79 ZLw/dmi+KMDHJJXkmP8ZTVzZCjqNYEZqlyaCmdLuwU0fe9hIGCC6RX4yBlL0AVli A3mQJ2kXXIsoKg8v1yVdb7BdrtUIae0VsdO+pfulal6D7gZ5QYbT3MSYlQ+UNz2f lPXdOl1q+wSxeu2Vm0bRIxfZlrXKj1GR4RjOCEcO5vhSujU1gTQ+4+9LryiaHhED 1/1UdgFJw4f93YjOCFNNYMBF+0ortwKoRNHp1SNmj3RhA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1700700824; x=1700787224; bh=HOq93W3M+1IvNOCOMEdNVb7LnRfO6RnR7DL tnUG4LnA=; b=e25QCN4iz/pd8jZh4T+tstK4L8b5cObG5t0DRtZEFqjlT4GNcE1 PIyBepX7Y92tKLvcSJxqvseMWeWCcXs0wB71UNKT/A1z7wwdl4PCmjkPfLbs2XfY Tvhk2RGtj1klWv91OcW7lX6CytaUc068QiW+FV1WjICrzZz7H5lwHENsCEaYUsdB PmqOc66CsbboTFOFsS/QgE8umklsEbkayRVzoZFozdGby+K2rNlo7CrIoj+eYofi Lx2bmoHm/MLH2R5v1d7IzZzepXGQknjH/Jk0TOhlTc3euhqSXaUHkvKVQ2ASLzfo 8rlLFbMXzxacF4FnpgNcz8IDqDzWrjOwL1g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudehvddgvdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkfhggtggugfgjfgesthekredttderjeenucfhrhhomhepuegv nhcuuehovggtkhgvlhcuoehmvgessggvnhgsohgvtghkvghlrdhnvghtqeenucggtffrrg htthgvrhhnpeeiheehvdeufeeuteeihedtheeliefhueekhfduveelhfdtheegheefvdfg tddvjeenucffohhmrghinhepghhithhlrggsrdgtohhmpdhkvghrnhgvlhdrohhrghdpkh hithifrghrvgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgr ihhlfhhrohhmpehmvgessggvnhgsohgvtghkvghlrdhnvght X-ME-Proxy: Feedback-ID: iffc1478b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 22 Nov 2023 19:53:43 -0500 (EST) Date: Wed, 22 Nov 2023 19:53:42 -0500 From: Ben Boeckel To: David Howells Cc: keyrings@vger.kernel.org, Jarkko Sakkinen Subject: Re: GitLab repo for keyrings Message-ID: References: <268530.1700676155@warthog.procyon.org.uk> <271142.1700684889@warthog.procyon.org.uk> Precedence: bulk X-Mailing-List: keyrings@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <271142.1700684889@warthog.procyon.org.uk> User-Agent: Mutt/2.2.12 (2023-09-09) On Wed, Nov 22, 2023 at 20:28:09 +0000, David Howells wrote: > Ben Boeckel wrote: > > > > I'm intending to move keyrings to GitLab for its upstream repo: > > > > > > https://gitlab.com/linux-afs/keyutils > > > > Thanks for the notice. Is the patch submission workflow going to add > > merge requests via the GitLab instance? If so, will the list be notified > > of activity on them? > > Hmmm... I wonder if I can make gitlab do that automatically. I don't see anything on my (unpaid) account at least under project integrations. Closest that seems useful is a webhook delivery service…needs something to reflect that to email though. Maybe something kernel.org would be willing to host (once developed)? For listening to and categorizing webhooks, we use this project: https://gitlab.kitware.com/utils/webhook-listen which turns them into JSON files on disk that can then be used as a work queue at least. (We split it up because it lets us lifecycle the daemon handling events independently from the webhook receiver; I recommend that for email reflection as well.) Another alternative is setting up a gitlab.com account that receives notifications and forwards/subscribes using the ML address. --Ben