Hi Jeff,
thanks for your precious opinion,
If you look at the previous post in this newsgroup made by Gerv, called
"mozilla.org URI structure", you will see that the /dev directory
already includes both a /tech subdir, and a /web subdir. /tech will
include (at least that's my understanding) informations for the mozilla
developers and people interested in embedding the technologies (your
mozilla/tech group). The end-user documentation will probably go in a
"User's guide" that we have been discussing in the mailing list.
/web will contain all the information necessary to web developers to
make their webpages compatible with Mozilla, references, etc etc.
However this is not the point of our discussion between technologies and
products. The discussion is: What goes under dev/ and what goes under
/software (which will probably be renamed /projects or something like
that). I tried to give a clear definition of what goes under which
directory, now I'm waiting for fantasai's answer :-)
Thanks for your input,
-Fabian.
Jeff Yates wrote:
> Hey, that's me:)
>
> Let me tell you my opinion of what I have been listening to in this thread.
> You all have been splitting hairs on categorizing where these belong, but
> the real issue is your target audience. (this does apply to the quote
> above).
>
> I see 4 groups of people who will be going to these pages.
>
> 1) C++ and other developers who want to join Mozilla's development team and
> need to have references on how things work at a very low level. (lets just
> call this group "mozilla/dev")
>
> 2) Software developers who wish to "re-use" Mozilla's technologies within
> their own applications. (lets just call this group "mozilla/tech")
>
> 3) Web page developers. (lets just call this group "mozilla/web")
>
> 4) Mozilla browser end user's. (lets just call this group "mozilla/user")
>
> I feel that ALL of the site should be structured (not necessarily the URI's,
> but at least the web links) so that each of the above 4 types of people can
> quickly get to what they need.
>
> Now, as a JS person, I do not care whether the JS engine is SpiderMonkey or
> Rhino (other than the differences to the properties and methods available to
> the JS programmer and which browser this is the case). Bringing up these to
> the JS programmer is just confusing the issue. We don't care!
>
> So, my opinion is that you should have relevant documentation available in 3
> groups, under mozilla/dev for those who wish to help in it's development,
> mozilla/tech for those who wish to embed the engine in their own product,
> and mozilla/web for the web page developer.
>
> Under this scheme of course you need to separate the content into the three
> categories with cross-links to relevant information that is under the other
> categories.
>
> Jeff Yates
> http://www.pbwizard.com
>
>
>
>
