From owner-freebsd-doc Thu Feb 6 15:40:48 2003 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 A6AC137B401 for ; Thu, 6 Feb 2003 15:40:46 -0800 (PST) Received: from pittgoth.com (14.zlnp1.xdsl.nauticom.net [209.195.149.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D08B43FAF for ; Thu, 6 Feb 2003 15:40:45 -0800 (PST) (envelope-from trhodes@FreeBSD.org) Received: from mobile.pittgoth.com (acs-24-154-229-196.zoominternet.net [24.154.229.196]) by pittgoth.com (8.12.6/8.12.6) with SMTP id h16NehfI030252; Thu, 6 Feb 2003 18:40:44 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Thu, 6 Feb 2003 18:40:47 -0500 From: Tom Rhodes To: Ceri Davies Cc: doc@FreeBSD.org Subject: Re: Documenting FreeBSD Officers, Hats, and Working Groups Message-Id: <20030206184047.4b08943a.trhodes@FreeBSD.org> In-Reply-To: <20030206230229.GD18106@submonkey.net> References: <20030128040205.GO18752@freebsdmall.com> <20030206214853.GB17028@submonkey.net> <20030206165535.1503ff12.trhodes@FreeBSD.org> <20030206221455.GC17028@submonkey.net> <20030206174120.0075fcd5.trhodes@FreeBSD.org> <20030206230229.GD18106@submonkey.net> X-Mailer: Sylpheed version 0.8.9claws (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 6 Feb 2003 23:02:29 +0000 Ceri Davies wrote: > On Thu, Feb 06, 2003 at 05:41:20PM -0500, Tom Rhodes wrote: > > On Thu, 6 Feb 2003 22:14:55 +0000 > > Ceri Davies wrote: > > > > > On Thu, Feb 06, 2003 at 04:55:35PM -0500, Tom Rhodes wrote: > > > > > > > > I've already began > > > > to think about how I want to set this up. I want to define > > > > entities so we can do things like: > > > > > > > > &donations; > > > > &so; > > > > &so-team; > > > > > > > > However, developer entities already exist without email > > > > addresses, I'm about to just include email addresses into the > > > > existing entities and let it go throughout the site. Thats the > > > > most logical way IMHO, however I'm still looking at a few other > > > > options, which include just not using email addresses, yet that > > > > would be a bad idea... > > > > > > I think it would be useful to have a list of all the hats and > > > their members in one place though - I saw at least two people > > > state they didn't know who was in the TRB this week. > > > > Actually, I thought of this so they can be used at the internal > > area, and then in the places (like releng) we can use entities and > > just keep one file current. Perhaps hats.ent in the internal area > > would be a better idea than developers... > > We *might* be talking about the same thing here, but I'm not sure. > With the addition of the entities you mention above, I had in mind > something like (in whereever it ends up). The entire thing is > mutable, but it shows what I am talking about quite well: > > > The following teams exist within the FreeBSD > organization. > We are extremely close. However, you seem to be looking more at doing this in an article sort of fasion. Let me paint a picture for you with an idea: We have places throughout the website where we list team members/hats. the re area is one. We have other places which list re members and other hats. Why not define these teams in a single file. Then call that file from the other places (ie: parts of the site, hat listings, etc) and then put up a specific page in internal which just lists the hats. I think this would make life much easier for everyone. Ideas? -- Tom Rhodes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message