Fabian Guisset wrote:
>
> fantasai wrote:
>...
> > Ah, so you've basically taken the all Mozilla's software development
> > projects from http://mozilla.org/projects/ and put them in
> > /dev/tech.
> >
> > So, extending the list, I add
> >
> > browser
> no
> > editor
> no
> > irc
> no
> > p3p
> yes
> > vixen
> no
> > xpconnect
> yes
>...
> All those I labeled with a no are "products" which we may want to
> separate from Mozilla in the future.
I think that if the Mozilla Organization decided to separate the
browser/ from Mozilla in the future, they would have lost the plot so
severely that it wouldn't matter what their site's URI structure was.
:-)
> /dev/tech, as I see it, and as we
> discussed it before, are the raw technologies developed in Mozilla.
> The browser is not a technology, it makes uses of a set of technology,
> same goes for editor and chatzilla and vixen. The P3P however is a
> technology in itself,
>...
P3P could conceivably get a standalone UI in the future (after all, Web
browsers aren't the only apps which accept cookies, so a `P3P Manager'
could protect your entire OS profile), whereupon it would suddenly
change from being a `technology' to being a `product' with a misleading URI.
Is PSM a `product', or a `technology'?
You may be able to make the distinction between `products' and
`technologies' today, and such a distinction would possibly be useful to
convey in various sections on the /develop/mozilla/ index page. But
trying to hardwire that distinction into the URI is something I think
would end in tears later on when modules jumped from one category to the other.
--
Matthew `mpt' Thomas, Mozilla UI Design component default assignee thing
<http://mozilla.org/>
