Job postings on blogs.perl.org
The question of what standing job postings have on blogs.perl.org has come up a few times over the lifetime of the site. We discussed it informally among the team, but in the interest of clarity for everyone, we wanted to set something down in writing. These are our rules of thumb:
In general, we welcome job postings put up by developers or other technical members of the team being recruited for. If you want to put up a job posting on this site, chances are high that you are in this group by default. Particularly if you have a say in the hiring process for the job, please feel entirely free to post.
If however you are a HR person or recruiter, may we suggest jobs.perl.org as an appropriate venue to you?
We do not have hard and fast rules for cases that fall outside these clear buckets. Use your judgement; above all, don’t be annoying.
If you really feel unsure about whether your job posting is OK, feel free to get in touch with us directly via email to contact@blogs.perl.org. (Please do not use the comments on this post for this purpose. Among other reasons, you may go unnoticed.)
Waxing philosophical
Thanks for the clarification, very relieved to hear my post wasn't against the rules. Although maybe when I posted it it would have been better to get in touch first given that this clarification didn't exist at the time, so sorry for jumping the gun a bit there.
Perhaps there could be a general "rules for blogging" or "FAQ" post that could be linked to from the "About blogs.perl.org" section on the homepage? I looked for one before posting and if there had been one that said "for any other questions contact us at contact@blogs.perl.org" I would have.
Thanks for thinking about these things and for generally running the show. This platform is fantastic! :-)
That would have been difficult because we only set up contact@blogs.perl.org yesterday. :-) As a dependency for this entry, in fact. (We already have an issue tracker on GitHub for handling support requests in general, so this never really came up.)
We don’t really have any set of pre-formulated rules we could post, it’s pretty laissez-faire and informal. As far as possible we’d like to keep it that way; if you aren’t doing anything that feels obviously wrong to yourself then chances are you aren’t doing anything wrong. Where clarification is necessary we’ll deal with things as they come up.
There are likely annoying blog posts on this site which are non job related (probably at least one or more of mine have been at some point). Glad to see that a liberal approach to user content is being taken here and that no policing of content is taking place.
If you're a Perl programmer and you post job links here to the point of being annoying, you're probably reducing the chances of being able to hire someone. On the other hand, if you're a recruiter and you solely post creative and entertaining job posts here, then I'd say you're probably a smart recruiter (experience has shown these are very rare).
I moderate a couple of other local Perl related content areas, and I don't remove posts except when they are solely off topic job posts. In those cases, it's pretty clear that a recruiter signed up for our Meetup group for the sole purpose of posting non Perl related job posts.
We just don’t want the place to get littered with spam, and we want to keep it communal. That’s all.
“Annoying” was code for other words. :-) Basically, don’t do things that will cause other people to come to us with legitimate complaints. We will act if we have to, so we’d rather not have to. Everyone is better off that way.
Thankfully so far we have had only a handful of very minor incidents to address, so we’ve been able to run a… loose ship. Fingers crossed that it stays that way.