From owner-freebsd-doc@FreeBSD.ORG Tue Jun 15 00:17:05 2004 Return-Path: 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 23E4C16A4D1; Tue, 15 Jun 2004 00:17:05 +0000 (GMT) Received: from pittgoth.com (14.zlnp1.xdsl.nauticom.net [209.195.149.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9630243D49; Tue, 15 Jun 2004 00:17:04 +0000 (GMT) (envelope-from trhodes@FreeBSD.org) Received: from localhost.pittgoth.com ([192.168.0.5]) (authenticated bits=0) by pittgoth.com (8.12.11/8.12.11) with ESMTP id i5F0GwBi048117 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 14 Jun 2004 20:16:58 -0400 (EDT) (envelope-from trhodes@FreeBSD.org) Date: Mon, 14 Jun 2004 20:17:28 -0400 From: Tom Rhodes To: fbsd_user@a1poweruser.com Message-Id: <20040614201728.4c6e1e3c@localhost.pittgoth.com> In-Reply-To: References: <20040614222336.GB15924@eborcom.com> X-Mailer: Sylpheed version 0.9.11claws (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: Tom Hukins cc: freebsd-doc@FreeBSD.org Subject: Re: firewall section of handbook X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jun 2004 00:17:05 -0000 On Mon, 14 Jun 2004 20:05:38 -0400 "fbsd_user" wrote: > As the originator of the work, I don't care any longer about the > wording in the firewall section. My stuff contains all the technical > details which has been missing from the handbook for an very long > time. All I am interested in is finding someone who will take my > source and prepare it for publication / replacing the current > firewall section. Hassling over wording is not as important as > getting the details and examples published in the handbook. I am > ready to pass on the source to who ever will see this through to the > end. Looking for powerful ramrod type of person who once they bite > into the project will not let go until it's completed. Perhaps a slow ramrod, but I am a ramrod. I think. Ummm, Ceri, what am I again? Hmmmm. find projects/newdocuments -type f -name '*' | xargs wc -l ... Ack. I'm not a ramrod, I'm a loser ... > > Is that you???? Is there any one on the doc list who has the time > and commitment to take on this publishing project?? At this point I'm not sure if I stepped forward or everyone else stepped backward. But I guess I'll look over it. I want a few more things to keep me busy this week and next. > > > By time this is ready for inclusion in the handbook I may have the > rough draft of the pf firewall stuff written so it can be included > also. We need pf documentation. That alone is enough reason to go through with the effort. > > > Let me know if you have the right stuff to take control of the > project and see it all the way through. As I stated before, I have > work related deadlines and projects which do not leave me time to > work my way through the process of peer review and revisions to the > text. It's much easier to publish, than create the original > technical info. I have done my part, now it's someone else's turn to > complete the publishing process. That's why I turned to the doc > mailing list to solicit help in completing the project. I leave it > in your hands to follow through or drop it here. > The unfortunate part is that we are tired, busy, and overworked committers. Well, not all of us. Some people commit so much that I wonder about them. Yet, I used to be the same way so I can't pick on anyone in particular without pointing a at my own head. Honestly, enough joking aside, you get everything done to a point where you are happy with it and I'll look it over for you. I'm sure others will also. :) -- Tom Rhodes