Date: Fri, 4 Jun 2004 13:13:54 -0500 From: Mark Linimon <linimon@lonesome.com> To: freebsd-current@freebsd.org Cc: freebsd-doc@FreeBSD.org Subject: current Works In Progress (was: What happened to src/sys/dev/sound/midi?) Message-ID: <200406041313.54674.linimon@lonesome.com> In-Reply-To: <Pine.NEB.3.96L.1040604135000.34555M-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1040604135000.34555M-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406041313.54674.linimon>