From owner-cvs-doc@FreeBSD.ORG Mon Jul 24 16:37:53 2006 Return-Path: X-Original-To: cvs-doc@FreeBSD.org Delivered-To: cvs-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 245B816A4F2; Mon, 24 Jul 2006 16:37:53 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from mx.nitro.dk (zarniwoop.nitro.dk [83.92.207.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65D5443D6B; Mon, 24 Jul 2006 16:37:44 +0000 (GMT) (envelope-from simon@zaphod.nitro.dk) Received: from zaphod.nitro.dk (unknown [192.168.3.39]) by mx.nitro.dk (Postfix) with ESMTP id 99C562D4A7B; Mon, 24 Jul 2006 16:37:43 +0000 (UTC) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id 9B39911444; Mon, 24 Jul 2006 18:37:43 +0200 (CEST) Date: Mon, 24 Jul 2006 18:37:43 +0200 From: "Simon L. Nielsen" To: Hiroki Sato Message-ID: <20060724163742.GE1091@zaphod.nitro.dk> References: <200607141802.k6EI2L2D019407@repoman.freebsd.org> <20060724153822.GA5102@tara.freenix.org> <20060725.005910.21928068.hrs@allbsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060725.005910.21928068.hrs@allbsd.org> User-Agent: Mutt/1.5.11 Cc: roberto@keltia.freenix.fr, doc-committers@FreeBSD.org, cvs-doc@FreeBSD.org, joel@FreeBSD.org Subject: Re: cvs commit: www/en/projects projects.sgml X-BeenThere: cvs-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the doc and www trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 16:37:53 -0000 On 2006.07.25 00:59:10 +0900, Hiroki Sato wrote: > Ollivier Robert wrote > in <20060724153822.GA5102@tara.freenix.org>: > > ro> According to Joel Dahl: > ro> > Log: > ro> > Update the projects page a bit. I've removed a bunch of links, some of them > ro> > were dead and some of them linked to unmaintained projects. This is just > ro> > the first step though -- I'm working on a complete rewrite of the projects > ro> > page. > ro> > ro> What about splitting it into a two steps process, one to put data into a > ro> to-be-specified format (YAML?) and the other that generate the SGML? > ro> > ro> That would make it easier to add/remove/edit w/o having to write (and > ro> check) the full SGML/XML "page"... > > I also think that idea is reasonable. We are already using some XML > databases for the purpose, and splitting the page into design and > its contents should make the maintenance easy (and also the > translators happy by using the existing usergroups.xml model, for > example). Considering it's just a long list with a few sections which is only displayed in one place isn't that a bit overkill? I'm not going to complain if anyone does it, but it just seems a bit like overkill to me. -- Simon L. Nielsen