Olivier Hill wrote:
Why not just letting people with @php.net accounts post to the list as
well as people having the Zend Certification.
That would push the certification incentives to a new high. So you
either contribute or pay to write emails here :)
Olivier
btw: I'm joking, but yes, Jani is right on the SNR. Just don't know
the right way to fix this.
Just ignore it and get on with your work. That's the attitude I take
with my own project mailing lists. Threading helps, then you can ignore
replies to a non-interesting post. Make announcements when you've done
something significant. Discuss design decisions in private, say by IM,
with individuals or small groups who you know to be competent in the
specific area of interest. It's not a cabal, it's a do-ocracy. The
rabble doesn't make the decisions, because they don't write the code.
Public mailing lists are a pain, but they're a necessary pain. They help
to attract developers from the user community. They support juniors and
small-scale developers who ask simple questions and get help from others
who are on a similar level of competency. And they help to keep the user
community informed about upcoming changes. I'm not aware of any better
system.
-- Tim Starling
P.S.: Reply-To header munging is good too.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
