From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Baines Subject: Re: Brainstorming features for issues.guix.gnu.org Date: Thu, 26 Mar 2020 20:56:43 +0000 Message-ID: <87v9mqkf78.fsf@cbaines.net> References: <87mu83xzzr.fsf@elephly.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:40471) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jHZYY-0008Lo-Ur for guix-devel@gnu.org; Thu, 26 Mar 2020 16:56:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jHZYX-0002Py-Di for guix-devel@gnu.org; Thu, 26 Mar 2020 16:56:50 -0400 Received: from mira.cbaines.net ([212.71.252.8]:50692) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jHZYX-0002P3-6d for guix-devel@gnu.org; Thu, 26 Mar 2020 16:56:49 -0400 Received: from localhost (unknown [46.237.161.230]) by mira.cbaines.net (Postfix) with ESMTPSA id 5F8E727BBE4 for ; Thu, 26 Mar 2020 20:56:48 +0000 (GMT) Received: from localhost (localhost [local]) by localhost (OpenSMTPD) with ESMTPA id 9570007a for ; Thu, 26 Mar 2020 20:56:46 +0000 (UTC) In-reply-to: <87mu83xzzr.fsf@elephly.net> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ricardo Wurmus writes: > I want issues.guix.gnu.org to become more useful for all of us. It=E2=80= =99s > easy to get lost in a deluge of bug reports and patch submissions, so > our tools should allow us to stay afloat. > > Do you use issues.guix.gnu.org? If you aren=E2=80=99t: what workflow do = you > have to review patch submissions? Normally when I look at reviewing patches, I end up finding something else to try and automate or make easier. My current workflow is, look for patches to review through email, or Patchwork [1], look the patches over, follow the link to the Guix Data Service instance, and maybe try building some of the derivations [2]. If I want to manipulate the patches locally, I checkout the branch or cherry-pick the relevant commits [3]. 1: https://patchwork.cbaines.net/project/guix-patches/list/ 2: I use the substitutes from the Guix Data Service instance for the derivation, so I can build it locally without having to apply the patches. 3: https://git.cbaines.net/guix/patches > If you do use it: what features do you think are missing? Being able to go to domain/patch-number would be useful ([4] for example). Debbugs does a redirect, so I usually end up typing that out instead. 4: http://issues.guix.info/39258 > Personally, I=E2=80=99d wish for a more streamlined workflow to download = and > apply patch sets. I don=E2=80=99t want to click on each =E2=80=9Cdownloa= d=E2=80=9D link in the > web interface. Instead I would like to run something like > > ./etc/review 12345 > > which would fetch the patches in issue 12345 and apply them to my > git worktree. I use the combination of Patchwork plus some scripts run through Laminar to populate a Git repository with commits for the patches for this. I've got the git repository as a remote, which makes applying the patches reasonably easy. > I would also like to see neglected issues in the web interface, i.e. a > list of open issues that haven=E2=80=99t seen any response in a while and= that > haven=E2=80=99t been tagged as awaiting more information from the submitt= er. > This should make it easier for us to prevent patches from slipping into > obscurity, which is a terrible thing to happen especially for new > contributors. Those are definitely features I'd like to see. They would be very useful to help people prioritise. While most of the discussion here has been about patches, I can think of a few useful things in terms of issues that don't directly relate to patches (or at least not yet). For bug reports, it could be useful to be able to associate them with packages that the bug is for. This could allow you to filter for bugs related to a package. It could also be useful to be able to mark which commit introduced an issue, and when it was resolved. Thanks for your work on issues.guix.info! Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEPonu50WOcg2XVOCyXiijOwuE9XcFAl59FwtfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcACgkQXiijOwuE 9Xf4ag/8CR4P3BanDyP1mgBV3ooRCGljTpxuFHXqW5bGVdwuGn5LkaercJkncH9e NJOCWlFXy5PAXODUnG1lxGhfYUJjHzaCIEizDY8lF1I7APjstYWGEReg5KLjmaEk S/G3j8a2OJoTWtJhq3/BwiybUzWZTey6ulZFTIxqRLZ1k2Ax8pXgW2wOIuVVw1Ws dt5dJTAvmGLobup9Tajxx6IpagjqGMJwQMLNsI7V8SJY3jKf7Vp+vFOg/NfztGox q+fq+OESR5pVbKJ83AXbaV1OO6QESwbsB0jY0Zbk7SfT+Jr4TiMgveOT8bI27JyV LYIFT158oUXm0O46ABd1RraRoW/wDV7e88x0f2apSkfj+hex89X5GMtNbrzJiXxR IAmS5rwRem9W7lSC8QMyCRyiJlPC750asmVXMBng4gxVQmqF3uYJ8KFXoonBz2uL lAYHPtfXos5vVOgD8CLfRBMUgv+SnBfSSYohF+4FqKFWByWV80TUS4Far91nijJ7 ejDzkjLw66EF9ggKChUB3tuR7oRvgjtGxX6iCX2WWahN/rohKra1FkPveZigZZFp AqEvtU+CFjQk8z4AvcAtHpzXduIxjb9466IDufbL9W3ZFsjUSXHyfNKzI4rUylrf M7S13k6EwBSzauVxptUT6hT0STUInvIJon4L3bwEUpbap30u8KA= =TPoM -----END PGP SIGNATURE----- --=-=-=--