From owner-freebsd-doc@FreeBSD.ORG Fri Sep 12 12:01:37 2003 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 6F18F16A4BF; Fri, 12 Sep 2003 12:01:37 -0700 (PDT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7821043FE3; Fri, 12 Sep 2003 12:01:36 -0700 (PDT) (envelope-from underway@comcast.net) Received: from localhost.localdomain (12-230-74-101.client.attbi.com[12.230.74.101](untrusted sender)) by attbi.com (rwcrmhc12) with ESMTP id <2003091218584001400opjpje>; Fri, 12 Sep 2003 18:58:40 +0000 Received: from localhost.localdomain (localhost [127.0.0.1]) by localhost.localdomain (8.12.9/8.12.9) with ESMTP id h8CIw14d058235; Fri, 12 Sep 2003 11:58:02 -0700 (PDT) (envelope-from underway@comcast.net) Received: (from jojo@localhost) by localhost.localdomain (8.12.9/8.12.9/Submit) id h8CIuWG2058218; Fri, 12 Sep 2003 11:56:32 -0700 (PDT) (envelope-from underway@comcast.net) To: j.el-rayes@daemon.li References: <200309120920.h8C9KGZ8091585@freefall.freebsd.org> <20030912093107.GH635@unixpages.org> <20030912093846.GK76802@submonkey.net> <20030912103331.GA388@FreeBSD.org> <20030912111813.GA75659@submonkey.net> <20030912141126.GC1068@daemon.li> From: underway@comcast.net (Gary W. Swearingen) Date: Fri, 12 Sep 2003 11:56:32 -0700 In-Reply-To: <20030912141126.GC1068@daemon.li> (Josef El-Rayes's message of "Fri, 12 Sep 2003 16:11:26 +0200") Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Portable Code, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-doc@FreeBSD.org cc: "Simon L. Nielsen" Subject: Re: docs/56729: [patch] artciles/pr-guidelines: explain meaning of MFC 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: Fri, 12 Sep 2003 19:01:37 -0000 > should there be a certain "treshhold" like, only use freebsd specific > terms or not trivial terms or should we include every term like "unix, > ports, packages..."? You're welcome to have the definitions from my old "jargon" web page: http://underway.home.comcast.net/jargon.html It was mostly created while I was using Linux and only has a couple of hundred entries, but some of them should be useful. The definitions were all composed by me and I waive my copyrights on them. There should be a couple of notices in the glossary: 1) Many definitions are incomplete and do not reflect all of the meanings used by the many FDP, manpage, and source code authors in every context. They are only meant to be clues for the clueless. 2) The FDP welcomes your contributions of new entries for this glossary, but must insist on this condition for all contributions: Contributors must own all copyrights for their contributions; even "fair use" copying must be avoided because one can't know what fair use copies from the same source have or will be contributed by others, which might be considered an unfair use. Of course, not everything is copyrightable, so some judgement can be required. A glossary could grow into an encyclopedia larger than the Handbook (because of number of entries and size of entries) so I've included a clue in notice "1" above that the definitions should be kept short. Perhaps this would be a good time to discuss the issue of whether standards and guidelines in FDP and other documentation should be (better) documented. Perhaps not -- there are good arguments for both sides of the issue. I'll not launch into the subject, except to note that the issue should be addressed in the glossary, as I did in number "1" above, documenting the status quo in which there is no recommended or official jargon.