From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Brainstorming features for issues.guix.gnu.org Date: Thu, 26 Mar 2020 09:49:12 +0100 Message-ID: <87mu83xzzr.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:40514) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jHOCZ-0001oC-Ef for guix-devel@gnu.org; Thu, 26 Mar 2020 04:49:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jHOCY-0003DT-6I for guix-devel@gnu.org; Thu, 26 Mar 2020 04:49:23 -0400 Received: from sender4-of-o51.zoho.com ([136.143.188.51]:21128) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1jHOCX-0003CI-NR for guix-devel@gnu.org; Thu, 26 Mar 2020 04:49:22 -0400 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 Hello Guix! 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? If you do use it: what features do you think are missing? 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=9Cdownload= =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 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 t= hat haven=E2=80=99t been tagged as awaiting more information from the submitter. 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. What do you think? -- Ricardo