From owner-freebsd-doc  Mon Jun 26  3:53: 0 2000
Delivered-To: freebsd-doc@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7423E37B808; Mon, 26 Jun 2000 03:52:52 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id MAA17148;
	Mon, 26 Jun 2000 12:52:43 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: Nik Clayton <nik@FreeBSD.org>
Cc: doc@FreeBSD.org, committers@FreeBSD.org, dgl@bsdi.com,
	jim@cdrom.com, papowell@astart.com, wpaul@FreeBSD.org,
	ceren@magnesium.net, ryan@ryan.net, murray@bsdi.com
Subject: Re: The website 
In-reply-to: Your message of "Sun, 25 Jun 2000 20:00:29 -0000."
             <20000625200029.I470@kilt.nothing-going-on.org> 
Date: Mon, 26 Jun 2000 12:52:43 +0200
Message-ID: <17146.962016763@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-doc@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Nik,

Go For It!

I think our web-page is lying badly about the activity level in the
project.

A few comments:

   * All your suggestions sound great.

   * Database driven content is OK, as long as it is not the main page,
     currently our cvs-web and search engines work OK in the overall
     mirror strategy.

   * Other topic for dynamic content: supported hardware.

   * Other topic for dynamic content: I would like if cvsweb somehow
     could locate all files relevant to a specific commit, I know this
     is somewhat difficult but It would be nice anyway.

   * Other topic for dynamic content: HTML'ed page with the last 24h
     of commit logs, ie: pointers into cvsweb to see the diffs.

   * Other topic for dynamic content: A place to keep track of patchsets
     up for review, test and comment.  Ie: submitter provides patch and
     comments and a page is created, linked to from the patchindex and
     it is added to the "new or updated" patches.  submitter can update
     patch as it develops.  One way would be to define a convention like:
	$HOME/review/$patchname/{README,*}
   
I would LOVE to see the day when www.freebsd.org would be the first
page I turn to in the morning. 

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message