>>(sigh) This used to be one of the only lists where do you have to see all
>>those "this is not appropriate for this list" messages. Perhaps we should
>>create www-chatter?
Actually, that was a mistake on my part -- I sent the mail without
checking the addresses first, and only meant to send it to Nick.
We already have a www-chatter -- it is called netnews.
>These were interesting announcements and appropriate to a www "talk"
>stream. If there is to be a list restricted to software development
>then perhaps it should have a name that reflects that.
Folks, ALL of the www-* lists at w3.org are restricted to software
development. That is why they exist, and why people are willing to
read them. If we don't restrict them, then the people doing development
won't have time to read them at all, just as I have no time to read
netnews any more.
This list is called www-talk because it is for developers to talk
about Web technology in general and not tied to a specific protocol
or project. We considered changing it to www-developers a long time
ago, but decided that it wouldn't help the situation much (and we'd
have to change all the documentation that pointed to it).
In actuality, there is nothing restrictive about these "rules".
If you want to let other developers know about an upcoming event
or announcement, just provide enough supplemental information to
make it a useful basis for technical discussion. For example,
if a particular API is involved, discuss some of the aspects of
that API and what technical (not marketing) advantages it has over
some other API. If it is a new product, discuss some of the features
from the viewpoint of a developer (i.e., the design choices made in
preferring one implementation over another).
Is this too much to ask?
....Roy T. Fielding Department of ICS, University of California, Irvine USA
Visiting Scholar, MIT/LCS + World-Wide Web Consortium
(fielding@w3.org) (fielding@ics.uci.edu)