Date: Fri, 24 Feb 2006 16:38:46 +0100 From: Joel Dahl <joel@FreeBSD.org> To: Mark Linimon <linimon@lonesome.com> Cc: doc@FreeBSD.org, Murray Stokely <murray@freebsdmall.com> Subject: Re: cvs commit: www/share/sgml includes.navdevelopers.sgml Message-ID: <1140795526.683.14.camel@dude.automatvapen.se> In-Reply-To: <20060224015854.GB16997@soaustin.net> References: <200602211929.k1LJTTAH060389@repoman.freebsd.org> <200602211556.34034.jhb@freebsd.org> <20060222011622.GB11099@freebsdmall.com> <1140617051.681.35.camel@dude.automatvapen.se> <20060222174523.GB64282@freebsdmall.com> <1140717189.681.22.camel@dude.automatvapen.se> <20060223193450.GA54855@freebsdmall.com> <20060224015854.GB16997@soaustin.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2006-02-23 at 19:58 -0600, Mark Linimon wrote: > I'm not 100% sure that having different ways to get to the same material > is really all that bad. However, I agree the navigation hierarchy should > be as clean as possible. Agreed. > > My proposals below describe ways to make this material accessible in > > fewer clicks than yours and with less clutter. > > I think we can all agree on these goals. Yes, absolutely. > If we change "Developers" to "Development" I think pushing the projects > down makes more sense, and might shift the emphasis more towards the > process and the product (of interest to users) than the people (primarily > of interest to the people themselves). e.g. break the links up into > who/what/where/when: > > Development -> release engineering (when) > Development -> current projects (what) > Development -> developer policies (who) > Development -> development resources (where) Hm, I like this idea. I can probably spend some time on this if this is considered an acceptable solution to the previous mentioned problems. > The resources would probably only be of interest to current developers, > but it _might_ be to prospective developers. (I know that I read through > all those pages when I was figuring out if I wanted to get more involved.) > The policies IMHO are _definitely_ of interest to prospective developers. Yes, I did the same thing. I read _everything_ related to FreeBSD in some way before I became a committer. Standards, policies, conventions, traditions - you name it. Making these things more accessible is a good thing. -- Joel - joel at FreeBSD dot org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1140795526.683.14.camel>