From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Vong Subject: Re: Feedback, ideas, discussion: tracking patches, discussions, bugs. Date: Fri, 02 Sep 2016 13:50:20 +0800 Message-ID: <8737liam03.fsf@gmail.com> References: <57B1AD4D.2080907@goebel-consult.de> <20160815153059.7c8201e6@scratchpost.org> <87h9am5aco.fsf@gmail.com> <57B2BEDA.2020202@goebel-consult.de> <874m6kbyg4.fsf@gmail.com> <57B5A049.6070206@goebel-consult.de> <87wpiwruyd.fsf@we.make.ritual.n0.is> <87inuf27h7.fsf@we.make.ritual.n0.is> <20160902002755.GA30382@jocasta.intra> <87vayfm821.fsf@we.make.ritual.n0.is> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51727) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bfhMz-0001bI-Mp for guix-devel@gnu.org; Fri, 02 Sep 2016 01:50:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bfhMu-00031t-Mt for guix-devel@gnu.org; Fri, 02 Sep 2016 01:50:29 -0400 Received: from mail-pa0-x22c.google.com ([2607:f8b0:400e:c03::22c]:36028) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bfhMu-00031p-F5 for guix-devel@gnu.org; Fri, 02 Sep 2016 01:50:24 -0400 Received: by mail-pa0-x22c.google.com with SMTP id fu3so29304367pad.3 for ; Thu, 01 Sep 2016 22:50:24 -0700 (PDT) In-Reply-To: <87vayfm821.fsf@we.make.ritual.n0.is> (ng0@n0.is's message of "Fri, 02 Sep 2016 00:58:30 +0000") 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.org@gnu.org Sender: "Guix-devel" To: ng0 Cc: guix-devel@gnu.org Hi, I think I share the same concern as you do, currently the mailing list is too crowded and it is difficult to find the relevant bit. Below are my opinions on it: While it may not be as user-friendly as web-based bug tracker these days, I think the Debian bug tracking system is still better than our current approach. In Debian, everything is a package. It is like a language primitive in the bug tracker system. There is an "intended to package" (ITP) package. When you want to package something, you simply file a bug against the ITP package. This has the advantage that, the relevant information stays within the bug report. So everyone can see the whole process, starting from someone intending to package, to a fully reviewed package, all in a single bug report. It is like having "lexical scoping". And the most important argument comes: We already have it now[0]! So, this could be a working intermediate solution. Currently, we are not using debbugs to its full potential. My suggestion will be to create a new package called "guix-package", and all people hoping to introduce a new package to guix should file a bug report to . If you are new to this type of bug tracking system, no problem! There is (some) documentation on it[1][2] and here is my own little example[3]. Hope this make sence! Cheers, Alex [0]: https://debbugs.gnu.org/cgi/pkgreport.cgi?package=guix [1]: https://debbugs.gnu.org/Reporting.html [2]: https://debbugs.gnu.org/server-control.html [3]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24352