From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: To-do lists Date: Fri, 18 Jan 2013 14:09:04 +0100 Message-ID: <87obgm7i4v.fsf_-_@gnu.org> References: <874nifuuad.fsf@karetnikov.org> <201301181118.29250.andreas@enge.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:54296) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TwBhE-00056L-FT for bug-guix@gnu.org; Fri, 18 Jan 2013 08:09:25 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TwBh3-0004xX-Gr for bug-guix@gnu.org; Fri, 18 Jan 2013 08:09:23 -0500 Received: from mail1-relais-roc.national.inria.fr ([192.134.164.82]:21707) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TwBh3-0004sz-AD for bug-guix@gnu.org; Fri, 18 Jan 2013 08:09:13 -0500 In-Reply-To: <201301181118.29250.andreas@enge.fr> (Andreas Enge's message of "Fri, 18 Jan 2013 11:18:29 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Andreas Enge Cc: bug-guix@gnu.org Hi! Andreas Enge skribis: > So maybe to avoid working on the same things, I currently have gnunet,=20 > libextractor, flac (with a patch), curl, groff, netpbm, openldap and=20 > ghostscript in my pipeline. These are all dependencies in one way or=20 > another of gnunet. But I think it could take quite a while until I arrive= =20 > at the top of the (only partially discovered) dependency tree... Good, thanks for sharing your to-do list. Another thing we can do to avoid duplicated work, is to commit and push individual packages as soon as we have them. For instance, as soon as you have a working libextractor, go ahead and push it. Some packages require more effort, and in that case it=E2=80=99s a good ide= a to announce your plans as you start working on it. Or maybe we should use an Org file somewhere, or a wiki, or some sort of locally-hosted Web 2.0 task management thing. Ideas? Ludo=E2=80=99.