Bill,
A simple request, but worth mentioning: Any chance of us getting
reply-to: header in emails being sent from the list? That way, by
default, clicking reply would simply send back to the list and that
people would have to reply-all if they feel it nessessary to send the
same message to the poster as well...
A simple google search dug this up:
http://www.tech-geeks.org/geeklog/article.php?story=20020406140917734
but perhaps its a simple checkbox in whatever management software zend
uses.. ?
Thanks,
Ralph
Bill Karwin wrote:
I don't think there's been any official policy stated. For a while it
seemed like the community used fw-general only, and now people are
posting to more specific lists, but I assume they are cross-posting just
in case there are still community members who are subscribed only to
fw-general.
I would encourage us all to use the specific lists now by default.
Assume that community members know to read the lists in which they are
interested. Cross-post rarely, and perhaps only to indicate that an
important thread is in the specific list.
For example, when Darby recently wrote a post about Zend_Auth, I
encouraged him to cross-post not the whole posting, but just post to
fw-general a reminder for people who are interested to go read fw-auth.
That at least helps to prevent the whole discussion from being
cross-posted to both groups.
There will always be exceptions. I think when Matthew announced that
the new MVC architecture had move from incubator to core it was
appropriate to make that as a general announcement. Likewise Shahar's
announcement of Http_Client moving from incubator to core. In both of
these cases, there may be minor code changes required in application
code, so it's important to publicize the differences well.
Regards,
Bill Karwin
Matthew Ratzloff wrote:
I'm subscribed to just about every list, but it seems that more often
than not messages that are sent to a specific topic list (most
recently, fw-mvc and fw-webservices) are just CCed to fw-general
anyway. This results in me getting lots of duplicate e-mails, and
seems to defeat the point of having separate lists grouped by topic.
What's the policy on this?
-Matt