> I would prefer instead that we jointly agree to prefix [JOB] on any > job offers. Those who care to do so can filter them out.
> Multiple lists for small groups has never seemed to work well in my > experiences.
> AJ ONeal
+1 I agree w/AJ
I'd also like it if people replying to job offers with personal info like resumes, qualifications and such would send it to the OP, and not to the whole list.
One problem I think we may have, whether creating a separate list or prefixing posts with [JOB], is that less-frequent posters/list viewers [like myself] would not be aware of the separate list or the subject prefix requested...so the group is likely to keep getting them regardless. Certainly, with time, more and more people would catch on, and the volume of such postings would likely decrease (and perhaps that's good enough), but I think it'd still continue.
Do any of the other local user group lists break job requests out? Why (or why not)? We might be able to learn from how some of the other group have handled this.
I've posted a few contract or job requests to the board, and I'm all for handling those however the group collectively would like them to be handled, but I only noticed this post because I happened to see that JT (my friend & business partner) had posted to it. Had he not, I may have overlooked this, and posted again in the future without knowing the "proper protocol". It'd be interesting to take a straw poll and see how many of the people who have recently posted jobs to the group saw this...maybe most of the job postings are regulars who would see it...but maybe not.
> wrote: > One problem I think we may have, whether creating a separate list or > prefixing posts with [JOB], is that less-frequent posters/list viewers [like > myself] would not be aware of the separate list or the subject prefix > requested...so the group is likely to keep getting them regardless. > Certainly, with time, more and more people would catch on, and the volume of > such postings would likely decrease (and perhaps that's good enough), but I > think it'd still continue.
> Do any of the other local user group lists break job requests out? Why (or > why not)? We might be able to learn from how some of the other group have > handled this.
> I've posted a few contract or job requests to the board, and I'm all for > handling those however the group collectively would like them to be handled, > but I only noticed this post because I happened to see that JT (my friend & > business partner) had posted to it. Had he not, I may have overlooked this, > and posted again in the future without knowing the "proper protocol". It'd > be interesting to take a straw poll and see how many of the people who have > recently posted jobs to the group saw this...maybe most of the job postings > are regulars who would see it...but maybe not.
> Anyway, that's just my $.02 worth...
The URUG mailing list is a great resource for people to find ruby talent. I don't see any problem keeping the job messages here, they are low enough volume that they don't dominate. I vote to just leave things be, or encourage the use of the [job] tag, so the annoyed may filter.
I vote to leave things be, and add a jobs tag to title (but lets be
honest there will be people unfamiliar with the list that will break
this rule). I don't mind the job postings, but as someone else has
noted I'd appreciate it if "Reply-all" was kept to a minimum when
corresponding with the job poster.
On Sat, Oct 31, 2009 at 11:37 PM, Tim Harper <timchar...@gmail.com> wrote:
> On Sat, Oct 31, 2009 at 10:45 PM, Charlie Sumpter
> <charlie.sump...@gmail.com> wrote:
>> One problem I think we may have, whether creating a separate list or
>> prefixing posts with [JOB], is that less-frequent posters/list viewers [like
>> myself] would not be aware of the separate list or the subject prefix
>> requested...so the group is likely to keep getting them regardless.
>> Certainly, with time, more and more people would catch on, and the volume of
>> such postings would likely decrease (and perhaps that's good enough), but I
>> think it'd still continue.
>> Do any of the other local user group lists break job requests out? Why (or
>> why not)? We might be able to learn from how some of the other group have
>> handled this.
>> I've posted a few contract or job requests to the board, and I'm all for
>> handling those however the group collectively would like them to be handled,
>> but I only noticed this post because I happened to see that JT (my friend &
>> business partner) had posted to it. Had he not, I may have overlooked this,
>> and posted again in the future without knowing the "proper protocol". It'd
>> be interesting to take a straw poll and see how many of the people who have
>> recently posted jobs to the group saw this...maybe most of the job postings
>> are regulars who would see it...but maybe not.
>> Anyway, that's just my $.02 worth...
> The URUG mailing list is a great resource for people to find ruby talent. I
> don't see any problem keeping the job messages here, they are low enough
> volume that they don't dominate. I vote to just leave things be, or
> encourage the use of the [job] tag, so the annoyed may filter.
> Tim
> On Sat, Oct 31, 2009 at 10:45 PM, Charlie Sumpter <charlie.sump...@gmail.com
> > wrote:
> > One problem I think we may have, whether creating a separate list or
> > prefixing posts with [JOB], is that less-frequent posters/list viewers [like
> > myself] would not be aware of the separate list or the subject prefix
> > requested...so the group is likely to keep getting them regardless.
> > Certainly, with time, more and more people would catch on, and the volume of
> > such postings would likely decrease (and perhaps that's good enough), but I
> > think it'd still continue.
> > Do any of the other local user group lists break job requests out? Why (or
> > why not)? We might be able to learn from how some of the other group have
> > handled this.
> > I've posted a few contract or job requests to the board, and I'm all for
> > handling those however the group collectively would like them to be handled,
> > but I only noticed this post because I happened to see that JT (my friend &
> > business partner) had posted to it. Had he not, I may have overlooked this,
> > and posted again in the future without knowing the "proper protocol". It'd
> > be interesting to take a straw poll and see how many of the people who have
> > recently posted jobs to the group saw this...maybe most of the job postings
> > are regulars who would see it...but maybe not.
> > Anyway, that's just my $.02 worth...
> The URUG mailing list is a great resource for people to find ruby talent. I
> don't see any problem keeping the job messages here, they are low enough
> volume that they don't dominate. I vote to just leave things be, or
> encourage the use of the [job] tag, so the annoyed may filter.
|
