From owner-freebsd-current@FreeBSD.ORG Wed Jan 14 09:26:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7EEC16A4CE; Wed, 14 Jan 2004 09:26:23 -0800 (PST) Received: from reverendtimms.isu.mmu.ac.uk (reverendtimms.isu.mmu.ac.uk [149.170.192.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6DCB43D41; Wed, 14 Jan 2004 09:26:18 -0800 (PST) (envelope-from p.robinson@mmu.ac.uk) Received: from agena.mmu.ac.uk ([149.170.168.195]) by reverendtimms.isu.mmu.ac.uk with esmtp (Exim 3.33 #2) id 1AgomT-0003y1-00; Wed, 14 Jan 2004 17:26:13 +0000 Received: from MMU-HSS-AGENA/SpoolDir by agena.mmu.ac.uk (Mercury 1.48); 14 Jan 04 17:26:13 +0100 Received: from SpoolDir by MMU-HSS-AGENA (Mercury 1.48); 14 Jan 04 17:25:49 +0100 Received: from PRGMMITER (149.170.101.200) by agena.mmu.ac.uk (Mercury 1.48) with ESMTP; 14 Jan 04 17:25:46 +0100 From: "Paul Robinson" To: "'Scott Long'" , "'Antal Rutz'" Date: Wed, 14 Jan 2004 17:25:46 -0000 Message-ID: <000a01c3dac3$71f38b10$1b01a8c0@MITERDOMAIN> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <400409F4.3090205@freebsd.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Mailman-Approved-At: Wed, 14 Jan 2004 11:28:23 -0800 cc: freebsd-advocacy@freebsd.org cc: freebsd-current@freebsd.org Subject: RE: Status reports - why not regularly? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2004 17:26:23 -0000 Scott Long wrote: > The bottleneck in this process is not that it takes too much > time/effort > to put them together. Taking all of the submissions and turning them > into a report takes about 1-2 evenings. There is of course a but of > overhead spent on sending the solicitation emails and reminders, but > it's not all that bad. It really comes down to me being too busy to > remember to start the process. Would it be of any use if we helped setup a closed mailing list and cron job, so that once every couple of months a mail just get sent out to a pre-defined list of developers (and therefore the maintenance is in keeping that list up to date), they send back their replies (those who don't within a week get a reminder mail) and these get processed into a big "draft" status report that just then gets edited by you (or somebody else?) before you then push it up onto a web server, or send it out to some other mailing lists? Seems like a bit of hacking would save you a lot of time. And I'm sure I'm not the only one who doesn't want to see the guy doing such a good job on release engineering burning out when we might be able to provide the tools for fixing it... If you want, I can throw some code out over the weekend to take a look at. It should just be a bit of perl or python - whatever postmaster is happy pipe'ing mail to in an alias on the freebsd.org mail server really. Let me know if that would help. -- Paul