On Mon, Jun 30, 2008 at 11:06 AM, Ricker, William <[EMAIL PROTECTED]> wrote: >> i may be evil but not THAT evil! :) > > Uri, it's not about any actual evil. I would really really like to say > Yes to your kind offer. But Sean and I have to worry about the > *perception* of evil even where it isn't.
There are other ways to address that. As a random one, you could publicly archive the list of requested job postings and the response on each one. That way companies can look through it and see that there is no bias. > Local companies, some of whom sponsor Boston.PM, expect postings to the > list via the volunteer screener will avoid paying a headhunting fee. > Having a headhunter screen the messages would make them expect evil. Unless they are really clued in to Boston.PM, they will not know that Uri is a headhunter. If they are clued in, they know enough about Uri to not worry. Where is the problem? I would suggest not worrying about it until you have actual complaints from actual people. At which point you deal with it then. Assuming that it happens. >> and doing anything wrong with the local leads would be >> counterproductive to me and my stellar reputation! :) > > Yes, *We* know you you're schizophrenic enough to handle it and > committed enough to the Perl Community do the right thing for the > organization and community (and thus for your own *longterm* good) -- > And the Perl folks at the companies may even know that. > But the HR departments only know (fulltime) headhunters in general and > will expect otherwise, no matter what we know or expect ourselves. > > We don't want our sponsors to walk on us. > We don't want local companies to be scared off submitting jobs for > review. Then you take my suggestion of making a publicly accessible archive of past submissions and the outcomes so they can see for themselves that there is no abuse. It can even be set up with an autoresponder. You email your job submission, and get a message saying your submission has been accepted, and where you can find the job submissions. [...] > Or we could consider a change of policy to just allow posting (with same > caveat of locality and relevance), thus avoiding the issue entirely. You'd also need a caveat that the post must be from the company offering the job. Else you'll have a constant stream of thinly veiled ads from headhunters. Another alternative is to entirely disallow job posting, but regularly make a post listing any recent jobs.perl.org offerings in the Boston area. The more I think about it, the better that option looks. Particularly if you can write an automated script to search for those recent offerings every week or so. Ben _______________________________________________ Boston-pm mailing list Boston-pm@mail.pm.org http://mail.pm.org/mailman/listinfo/boston-pm
