Luke wrote:
> 1) I have a strong opinion on these bits:
>
> /contribute/community/ not /about/community/
But you don't contribute to the community. At least, not in the sense
that you contribute to Mozilla. If all we're doing is rephrasing the
current /community.html (which seems likely) then /about/community is
fine. The community is not on the website, in one sense - and in the
sense that it is on the website, it's on the whole thing.
> /contribute/documentation/ not /contribute/writing/
All documentation is writing, but not all writing is documentation. If
you were contributing an op-ed piece, you'd still need to reference the
style guidelines in here.
> /news/events/ not /events/
See my previous post.
> /develop/ not /dev/
Loads of other projects use /dev/. It's understood, and it's easier to
type. It also matches the newsgroup spec.
> 2) My main problem: I don't like the /software/ hierarchy. It's trying
> to do 2 things at once.
>
> The 2 meanings of the word "software" are being blurred.
>
> 1 - /software/mozilla/ = here's the software (i.e. the actual files)
> to download & build
> 2 - /software/bugzilla/ = everything about bugzilla, the project
You are right.
My idea was:
For meaning 2:
/projects
/projects/bugzilla/
/projects/browser/
/projects/mailnews/
/projects/irc/
And, for downloading stuff (meaning 1), /releases/.
/releases/mozilla/0.9.3/
/releases/mozilla/nightlies/
/releases/bugzilla/2.14/
etc.
Build instructions live under /dev, but are linked from the /releases/ area.
Almost exactly like you said, in fact :-)
> 5) Where do theme developers go? is /develop/tech/xul/themes/ too deep?
Probably in their personal space under /Members. And no, you weren't
supposed to know about that unless you know Zope. ;-)
Gerv
