The front page of blogs.perl.org is like an advert for the Perl
community. It reflects the diversity of interests that Perl programmers
have. We should try to make it as attractive as possible.
If the
first three posts on the front page are huge essays or massive code
listings then the front page doesn't look very attractive. It looks far
better if we post teaser extracts of posts to the front page and make
them enticing enough to encourage people to click through to the full
story.
Some of you may have noticed that the blogs.perl.org front page recently acquired a new “Page 2” link. This is a feature we’ve been wanting for quite some time, to help readers scan back through the thousands of entries our users have posted in the nearly three years we’ve been running.
As ever, we’d be delighted to hear about any problems you find with this (or any other aspect of the site), as well as your ideas for making the site better. Please get in touch with us, or raise a Github issue on blogs.perl.org.
The code that drives the pagination can also be found on Github, and we welcome your ideas, bug reports, and pull requests for that, too.
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.)
Someone registered an account called “corewebservices” on blogs.perl.org and posted a full verbatim copy-paste of of this entire VersionOne article with a text-only source link at the bottom and clickable links to milecore.com and their Facebook page and Twitter account below that.
If you do business with Milecore (“The Most Trusted Web Development Company” according to their homepage), be aware that they made, at the very least, a very poor choice in contracting marketing service.
By Ovid
on April 11, 2012 9:10 AM
meta is the “meta” blog for blogs.perl.org. It deals with issues surrounding this blog and not about Perl itself.
Recently we’ve seen some strong comments from a few people and we (Dave Cross, Aaron Crane, Aristotle and Ovid) have discussed what to do about it. We’re pretty much in firm agreement that the right answer is to do nothing. For now.
All of us agree that censorship is not something we care for but there have been some comments that are teetering over the line and are making blogs.perl.org a less pleasant place to be. So we refer you to the Blogger’s Code of Conduct
- Responsibility for our own words
- Nothing we wouldn’t say in person
- Connect privately first
- Take action against attacks
- a) No anonymous comments OR b) No pseudonymous comments
- Ignore the trolls
- Encourage enforcement of terms of service
- Keep our sources private
- Discretion to delete comments
- Do no harm
- Think twice — post once
The idea behind it is to try to create a an atmosphere where people can exchange ideas and not personal attacks. We do not plan to enforce this, but to suggest that you might want consider why the above points are sometimes helpful. Most people don’t have to told to be adults, but some do. Those that do sometimes have to have it patiently explained to them.
In particular, some of you may remember the threats against Kathy Sierra that let to Tim O’Reilly calling for such a code of conduct. Sometimes things get out of hand on the Web.
On a personal note, I have no problem with profanity, but if it’s used in anger, or if you cannot express yourself without it, maybe it’s a time to step away from the conversation.