From owner-freebsd-current@FreeBSD.ORG Fri Jun 4 11:17:22 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 0C0A116A4CE; Fri, 4 Jun 2004 11:17:22 -0700 (PDT) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id E817D43D2F; Fri, 4 Jun 2004 11:17:21 -0700 (PDT) (envelope-from linimon@lonesome.com) Received: from [192.160.235.2] (cs242743-143.austin.rr.com [24.27.43.143]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.soaustin.net (Postfix) with ESMTP id 524D9141DF; Fri, 4 Jun 2004 13:17:18 -0500 (CDT) From: Mark Linimon Organization: Lonesome Dove Computing Services To: freebsd-current@freebsd.org Date: Fri, 4 Jun 2004 13:13:54 -0500 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406041313.54674.linimon@lonesome.com> X-Mailman-Approved-At: Sat, 05 Jun 2004 04:40:05 -0700 cc: freebsd-doc@FreeBSD.org Subject: current Works In Progress (was: What happened to src/sys/dev/sound/midi?) 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: Fri, 04 Jun 2004 18:17:22 -0000 > Have you thought about using the FreeBSD perforce server? It's invaluable > for things like checkpointing. One of the main reasons Peter set it up > was that people were walking around with months of work on notebooks at > conferences, and he was concerned they'd drop/lose/have stolen/destroy > the notebooks and the project would lose a lot of work. This brings to mind a related question. It's never clear to me who is exactly working on what. ISTM that some kind of listing of Work-In-Progress (either in Perforce or local patches) would be valuable to the project to prevent duplication. (The projects.html seems to be a) at a much higher level, and b) terribly out of date). Yes, I will volunteer to wrangle this information. Should we create a 'projects@' mailing-list (or at least a place that quick summaries can be posted to)? Should we rework projects.html to separate it into Continuing Projects/Work-In-Progress/Research Topics? Should it be a separate page entirely, built from recent status reports? Note: freebsd-doc Cc:ed. mcl