Good morning, Portland Ruby Brigade!
In this highly developer-friendly job market, there are a lot of [JOB]
posts to this list. We also have this mailing list configured to
change the "Reply-To" header so that replies are sent to THE ENTIRE
LIST by default. (Last I heard, there were 700+ email addresses on
the main pdxruby list.)
There are strong opinions on both sides of the "Reply-To" debate.
THIS IS NOT THAT DEBATE. If you'd like to rehash it, by all means
feel free to set up a form where people can vote, and link to it.
Rather, my purpose this morning is to highlight a lovely edit made
this morning by Ben Cullen-Kerney to our "Job Guidelines" page.
(Incidentally, did you know the
pdxruby.org site was a wiki, hint
hint?)
You can see the full text at
http://pdxruby.org/job_guidelines, but
the upshot is that the best way to avoid committing the classic
"announce to hundreds of people that you're not completely satisfied
with your current arrangement" blunder is to compose a new email when
responding to job posts.
Thanks, Ben!
-Sam