Luke wrote:
>
> /develop/build/ not /software/mozilla/build/
> (How many non-developers really build Mozilla? I sure
> don't.)
/software/mozilla should contain all the info needed to
get Mozilla up and running. As the main product here is
source code, this includes build instructions.
You said you're into UE -- analyze this organization from
the visitor's standpoint. Remember that although the
navigation is not restricted by the URI hierarchy, the
navigational hierarchy does coincide with it. You're trying
to download/install Mozilla--should the build instructions
transport you to the developers' hierarchy?
> 2) My main problem: I don't like the /software/ hierarchy.
> It's trying to do 2 things at once.
Which 2 things? A directory grouping both software download
and software development is doing two things at once, and
that's been purposely avoided here.
/dev takes care of development
/software takes care of download/install
i.e.
> 1 - /software/mozilla/ = here's the software (i.e. the
> actual files) to download &
> build
If you don't like the name "software", that's another issue.
Would "products" suit better?
> I'd do one hierarchy for downloading Mozilla and another
> for other software projects:
Your justification for this separation?
If it's "only Mozilla should get the spotlight," then I'd
tell you to write your content to that bias, not your URIs.
> - All this talk about URIs being static for eternity is
> bollocks. Great idea, but don't sweat it too much, or
> we'll keep moving too slow.
Eternity, no. But if the URI is planned extensibly, with
likely future changes in mind, it makes things easier in
the long run.
[OT]
> (newsgroup hierachy?)
The newsgroup hierarchy is held up by server issues,
not by the design effort, which, IIRC, finalized a spec
with general consensus _last year_.
