Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 Feb 2006 17:16:22 -0800
From:      Murray Stokely <murray@freebsdmall.com>
To:        John Baldwin <jhb@freebsd.org>
Cc:        doc-committers@freebsd.org, cvs-doc@freebsd.org, cvs-all@freebsd.org, Joel Dahl <joel@freebsd.org>
Subject:   Re: cvs commit: www/share/sgml includes.navdevelopers.sgml
Message-ID:  <20060222011622.GB11099@freebsdmall.com>
In-Reply-To: <200602211556.34034.jhb@freebsd.org>
References:  <200602211929.k1LJTTAH060389@repoman.freebsd.org> <200602211556.34034.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 21, 2006 at 03:56:31PM -0500, John Baldwin wrote:
> On Tuesday 21 February 2006 14:29, Joel Dahl wrote:
> > joel        2006-02-21 19:29:29 UTC
> >
> >   FreeBSD doc repository
> >
> >   Modified files:
> >     share/sgml           includes.navdevelopers.sgml
> >   Log:
> >   Ok, it's almost impossible to find the FreeBSD internal pages, so add a
> > link to the bottom of the navigation table.
> 
> I always thought the lack of a link was on purpose to be honest.  Not there's 
> anything sUp3r secret under internal/.

Agreed.  It shouldn't be almost impossible but completely impossible.
/internal pages have never been linked from the external pages on
purpose.  It is for internal communications just as the developers@
list is and not for public consumption.  This assumption shouldn't be
changed without a wider discussion.  Please back this out.

Is there individual content that is in internal that you think should
be made more visible?  The release engineering schedules, todo lists,
and procedures used to live in internal but migrated to the public
areas when I realized the much broader audience interested in that
material.  It is likely that other material may also be due for a
migration into more public areas.

  - Murray



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060222011622.GB11099>