From nobody Sun Feb 7 09:28:17 2021 Authentication-Results: mail-b.sr.ht; dkim=none Received: from cressida.uberspace.de (cressida.uberspace.de [185.26.156.202]) by mail-b.sr.ht (Postfix) with ESMTPS id 55EAE11EFF6 for <~andir/nixpkgs-dev@lists.sr.ht>; Sun, 7 Feb 2021 09:28:17 +0000 (UTC) Received: (qmail 21197 invoked from network); 7 Feb 2021 09:28:15 -0000 Received: from localhost (HELO localhost) (127.0.0.1) by cressida.uberspace.de with SMTP; 7 Feb 2021 09:28:15 -0000 Date: Sun, 7 Feb 2021 10:28:14 +0100 From: Matthias Beyer To: ~andir/nixpkgs-dev@lists.sr.ht Subject: Re: Mailing list and tooling for nixpkgs-dev Message-ID: <20210207092814.othyo2q6ruxpcmsy@hoshi> Reply-To: Matthias Beyer X-message-flag: Mails containing HTML will not be read! Please send only plain text. References: <87eehtrqa6.fsf@jb55.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="rr54bpgewny7ro3u" Content-Disposition: inline In-Reply-To: <87eehtrqa6.fsf@jb55.com> --rr54bpgewny7ro3u Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi again. Sorry for the noise, but I have some more ideas for tooling to drive this M= L. First of all, I think we really need a repo to put all the tools and script= s we use. The b4-notmuch integration for example, but also the script that is used to submit patches as github PRs. On submitting patches to github PRs: =46rom what I see, the PR message right now includes the following data (us= ing the b4 patchset [0] for reference): * git trailers * Message-Id * Link to the patchset I think this can be improved with the following changes (I would submit a p= atch, but I don't know whether the tool/script is even open source at this point): * In the PR: A "mailto" link to reply on the thread the patch was submitted with, possibly with CC to the patch Author. This way, people on github are one click from replying to a patchset. * On this ML: An automatically generated message with * A link to the PR * A summary of the "b4 am | git-am" output (which trailers were added, = for example) * A git remote URL to `git fetch` the patchset from github (This would be nice so I can see my patchset in my git-log output as = it appears on github) * A link to reply to the issue on github via mail. I bet this is possib= le as github generates message IDs rather transparently (see below). Another thought that I currently have is that comments on the PR are not forwarded to me and comments I make on the patchset are not forwarded to gi= thub. I think that is possible, but am not sure how. I also think that a proper mirroring of comments is _hard_ because one easi= ly can build an endless loop. =46rom what I see, github sends a mail for each comment, and the message ID= of the mail refers to the comment URL!!! For example: I have a mail that has the message ID Message-ID: that refers to: https://github.com/NixOS/nixpkgs/pull/97666/#issuecomment-702657111 One can clearly see the scheme: Message-ID: //pull//c@github.com URL: github.com///pull//#issuecomment- That is really nice. Maybe we can make something out of that? [0] https://github.com/NixOS/nixpkgs/pull/112244 --rr54bpgewny7ro3u Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEUJGUus1GMTrRclzcEKWX9Kitz80FAmAfsqsACgkQEKWX9Kit z80Cgg/8CLbJma4l3S5AFODD2rYTBfPnhtt1/OCrBiuWzRz4DX2t6jDCYGhj/lDx B8+vIVe5Xyv3+JANCQmlaz4Tdi1YYdLap1V69JJgFE2xhZdBMdYh0wrhsXHh4F3E FeeK+GF6yySnvMgNrOQioxChhEanL4TWemsnBb89Vj55fYlh3fW0PLKc6Q0rSWGM rO2eDZH3M7Gei88ZvQtWfQuYt/cLEAu4FJ1TvVjMhfrcg96AHU0K+KRtPE2wSNL0 D1emcjKtmmsFcQzvDeKHV6m0qH0o8jf6M0ZZnW/xF9qSxI2fCMxLUKHI/ix8gRpn iTrqgre/mICFmJDT0bPjd22hjpw7AaI4t7ECO+bNWtDnBBWBJCNfhUToikeOtj7B Jgl8l5Y3u3C84VANIPSpPuK92/2ThZA6IN4nQ9VQ3Rnaowc+uR/l3G9hWDiWhokb u/RnhyEB6Pwwzh455oVUMhbQRCx0rlEpaXGCLoewgYTDOYayhKUe9x3lYFccPuLg 86Yp9HKQQlAJHaQeQO61ItzaM3SMVMQ2heCBznmwKmzbzeqSF7kAKzIFi3rBJaro Nie9p0EPTyiAGVUBJ184vok/1xXitUkZ+n6wQTLBzaWW6MiqNzTL1sp5/dAjPiFb /CQr7bx4uxRzbiNxeHB6t8dxB8ziZCl2A/sCopf4vB9kG6gJLeQ= =ZDP6 -----END PGP SIGNATURE----- --rr54bpgewny7ro3u--