I somehow find the software hierarchy odd... And I would expect build
instructions on the dev hierarchy. Should there be download hierarchy
for readily available binaries and other products?
I would also like to have redirects for all old URIs, regardless of what
some guideline says. Eventually people will update if you make the
redirect a bit slow, like 3-5 seconds instead of immediate ;)
Gervase Markham wrote:
> mozilla.org/
> |
> |--dev/ - all development-related information
> | |
> | |--tech/ - Mozilla technologies
> | | |
> | | |--xul/
> | | |
> | | |--js/
> | | |
> | | |--xpcom/
> | |
> | |--ports/ - Platform homepages
> | | |
> | | |--beos/
> | | |
> | | |--macosx/
> | |
> | |--_?_/ - Mozilla developers' stuff
> | |
> | |--web/ - Web Developer info - articles on writing pages for
> | | Mozilla, FAQ, show-off section, etc.
> | |
> | |--embed/ - info for potential embedders of Mozilla tech.
> |
> |--software/ - list of software released by mozilla.org w/ description
> | |
> | |--mozilla/ - intro & description for all of Mozilla
> | | |
> | | |--build/ - build instructions
> | | | | http://mozilla.org/build/
> | | | |--beos/
> | | | |
> | | | |--mac/
> | | | |
> | | | |--macosx/
> | | | |
> | | | |--os2/
> | | | |
> | | | |--unix/
> | | | |
> | | | |--win32/
> | | |
> | | |--distributors/ - link to Mozilla distributors
> | | | (e.g. Netscape, Beonex)
> | | |
> | | |--releases/ - Mozilla release info (one directory per
> | | | release)
> | | | http://mozilla.org/releases/
> | | |
> | | |--0.6/ - relnotes and stuff
> | |
> | |--bugzilla/ - for using Bugzilla on your own system
> | | (subdirectory structure similar to mozilla/,
> | | above)
> | |--etc.,
--
Heikki Toivonen
