From owner-freebsd-doc@FreeBSD.ORG Wed Sep 13 09:58:57 2006 Return-Path: X-Original-To: Freebsd-doc@freebsd.org Delivered-To: Freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5417A16A40F for ; Wed, 13 Sep 2006 09:58:57 +0000 (UTC) (envelope-from paulalexwilson@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAC0843D46 for ; Wed, 13 Sep 2006 09:58:56 +0000 (GMT) (envelope-from paulalexwilson@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so2341259wxd for ; Wed, 13 Sep 2006 02:58:56 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=bbfHnJgU/1G9DQDNdZou+RR5cekRFWHcc2oGXI/nA2tbBBhHncUc9rulJtyOVpN1BQYh9NkM4rG8WBnMUZmhbXcd/zfuAbDHantej+00Qc76g1W4/GsOgvj+m51yfzmgqBFah5IvmP/x//LEKJeF/doFrKbbaXJFld0H+yY/mrQ= Received: by 10.70.113.15 with SMTP id l15mr10139357wxc; Wed, 13 Sep 2006 02:58:55 -0700 (PDT) Received: by 10.70.89.11 with HTTP; Wed, 13 Sep 2006 02:58:55 -0700 (PDT) Message-ID: <3c3d11cf0609130258s5ebf8274q18acf31a83b403a7@mail.gmail.com> Date: Wed, 13 Sep 2006 10:58:55 +0100 From: "Paul Wilson" To: Freebsd-doc@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: man pages and handbooks X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Sep 2006 09:58:57 -0000 On 12/09/06, Duane Whitty wrote: > > Paul Wilson wrote: > > Duane, > > > > I was interested to read of your proposal to update the FreeBSD > > Architecture Handbook on the documentation mailing list. It seems that > > we've been experiencing similar problems of late; I too have been trying > > my best to acquaint myself with SMPng, the different locks, atomic > > operations etc, but have found the lack of native FreeBSD locking > > documentation and advice to be a hinderence. Of your suggestions I > > particularly liked the idea creating diagrams for illustration and > > believe that they would be well applied for communicating lock > > interactions. > > > > If you are open to assistance with your project then I would be more > > than happy to help. > > > > Paul Wilson > > Hi, > > Of course help is always welcome. What we should do, IMHO, > is use the doc mailing list for our communications. That > way if others also want to join in they can. As for the > mechanics of collaboration I'm not sure what the best > approach is just yet. I guess one thing we could do is post > patches to a website or either of us could setup a > repository for the project. The problem then becomes > keeping it synched with the FreeBSD doc repository. > > I suggest we bring this to the list. Perhaps there would be > an interested doc committer who could fast-tract commits > into HEAD if they were technically accurate or perhaps a > Perforce project could be started; I don't know. I guess > setting-up our own repository would take care of > communication. As most of the new development is going into > the kernel infrastructure and manpages we probably don't > need to worry too much in staying synched with the official > version of the FreeBSD Architecture Handbook. > > And just as a note I want to reaffirm that, for me, this is > a longterm project requiring a significant amount of > research. I personally don't anticipate generating huge > volumes of material in any one week. > > I think as well we will need a great deal of help from > various kernel systems developers if we are to be sure our > information is accurate. > > If you wouldn't mind, perhaps you could forward this to the > freebsd-doc@freebsd.org mailing list with your original > message intact so that we can receive some feedback from the > community on how to best go about collaborating on this project. > > One of the most important issues for me is that everyone and > anyone who desires to participate be able to do so. The > real strength of the FreeBSD project is the FreeBSD > community. Without that community no amount of individual > technical achievement will be able to keep the FreeBSD > project the vibrant entity it is today. > > Most Respectfully, > > Duane Whitty