From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 03:01:03 2014 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B2D19B77; Tue, 4 Feb 2014 03:01:03 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 62207157C; Tue, 4 Feb 2014 03:01:03 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id s14311Tl031648; Mon, 3 Feb 2014 20:01:01 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id s14311Ar031645; Mon, 3 Feb 2014 20:01:01 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Mon, 3 Feb 2014 20:01:01 -0700 (MST) From: Warren Block To: Dru Lavigne Subject: Re: updating documentation set In-Reply-To: <1391476740.64494.YahooMailNeo@web184904.mail.gq1.yahoo.com> Message-ID: References: <1391476740.64494.YahooMailNeo@web184904.mail.gq1.yahoo.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Mon, 03 Feb 2014 20:01:01 -0700 (MST) Cc: "freebsd-doc@freebsd.org" X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Feb 2014 03:01:03 -0000 On Mon, 3 Feb 2014, Dru Lavigne wrote: > This section: > > 23.4. Updating the Documentation Set > > really belongs (and is already mostly duplicated in): > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/overview.html#overview-doc > > Any objections to me doing the following? > > 1. remove "23.4. Updating the Documentation Set" from the Handbook, replacing it with a NOTE in the updating section that docs can either be updated during an OS upgrade or, at any other time, by following the instructions in the FDP overview (with link) > > > 2. make sure that any points covered by 23.4 and currently missing from the FDP overview are added to the FDP overview Don't we have doc ports specifically for users to keep a current version of the documentation on their system? Upgrading a port is simpler for an end user than an svn checkout, there's less overhead, and we would not have to expose them to developer instructions.