From owner-freebsd-doc@FreeBSD.ORG Sun Jun 4 07:30:45 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 9969E16A4CA; Sun, 4 Jun 2006 07:30:45 +0000 (UTC) (envelope-from joel@FreeBSD.org) Received: from av6-2-sn3.vrr.skanova.net (av6-2-sn3.vrr.skanova.net [81.228.9.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 479E243D70; Sun, 4 Jun 2006 07:30:38 +0000 (GMT) (envelope-from joel@FreeBSD.org) Received: by av6-2-sn3.vrr.skanova.net (Postfix, from userid 502) id E7987380A7; Sun, 4 Jun 2006 09:30:34 +0200 (CEST) Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net [81.228.9.101]) by av6-2-sn3.vrr.skanova.net (Postfix) with ESMTP id DA2843807F; Sun, 4 Jun 2006 09:30:34 +0200 (CEST) Received: from 213-65-29-216-no21.tbcn.telia.com (213-65-29-216-no21.tbcn.telia.com [213.65.29.216]) by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id C27F537E42; Sun, 4 Jun 2006 09:30:34 +0200 (CEST) From: Joel Dahl To: Doug Barton In-Reply-To: <20060603235511.F57378@znfgre.qbhto.arg> References: <20060603235511.F57378@znfgre.qbhto.arg> Content-Type: text/plain Date: Sun, 04 Jun 2006 09:30:34 +0200 Message-Id: <1149406234.677.15.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-doc@freebsd.org Subject: Re: Official Hats page is a wee bit out of date 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: Sun, 04 Jun 2006 07:30:45 -0000 On Sat, 2006-06-03 at 23:56 -0700, Doug Barton wrote: > I can take a pass at this if no one else gets around to it, but > http://www.freebsd.org/doc/en_US.ISO8859-1/books/dev-model/official-hats.html > is not tracking reality atm. Part of the problem is that we duplicate info about various teams, hats and responsibilities everywhere in our docs, which makes them a PITA to update. For example, if we change security-officer, the following docs needs an update: www/en/developers.sgml www/en/security/security.sgml doc/en_US.ISO8859-1/articles/contributors/ doc/en_US.ISO8859-1/articles/committers-guide/ doc/en_US.ISO8859-1/books/dev-model/ So, when a team/hat changes, you need to update at least 3-5 documents, which is way too much. One, or perhaps two, should be enough. -- Joel