urbia.com AG (a company of Gruner + Jahr AG & Co KG) operates the web community www.urbia.de targeting young families with topics like pregnancy, birth, baby and parenting at its core. www.urbia.de attracts 6,5 million visits and 2,3 million unique users per month which makes us the market leader in the parenting segment in Germany.
Perl has been proudly powering our platform since 1998. In the meantime we migrated our code base to Modern Perl making use of the Catalyst MVC framework, DBIx::Class, Template::Toolkit, Moose and tons of other wonderful CPAN modules without which we would have never been so successful. To thank the excellent community and show our continuing support, we decided to sponsor this year's YAPC::EU in Frankfurt. If you're interested in joining our team in Cologne, go to http://www.urbia.de/allgemein/jobs to check out our open positions and/or contact us at jobs@urbia.com.
Day 2 of YAPC::NA 2012 talks begin today at 9am sharp. The banquet was a huge success last night, and yesterday’s talks had the audience buzzing. Can’t wait to see what today brings. Hopefully you’re not all hung over from The Linode Beer Garden and the Perl Foundation party last night.
Don’t forget that you can watch live on the web for free:
It is with great pleasure that we officially announce a new sponsor for the CPAN Testers Project. Webfusion have provided us with Managed Hosting, for us to use with some of the supporting websites. As such, we will be using it for the Analytics and Matrix websites, as well as a secondary failover site for the Static Reports site.
Webfusion are the latest corporate sponsor to support CPAN Testers. If your company would like to support CPAN Testers, please get in touch. You can also donate to the project via the CPAN Testers Fund, managed by the Enlightened Perl Organisation.
I cannot decide if I was too harsh. I try not to let the usual drone of noobs on SO to get to me. My problem was that the OP is being both ignorant AND demanding. Read the post and let me know, I'm back and forth between being enraged and contrite.
Kip Hampton will give a talk at YAPC::NA 2012 described as:
Developing for the Web shouldn’t be hard. Yet, many smart developers make it more difficult than it needs to be by choosing tools and frameworks that do not fully take advantage of all that HTTP has to offer. This talk demonstrates how projects at all levels— from the simplest brochureware site to the most advanced Hypermedia APIs—can be made simpler by getting back to the basics of HTTP. We introduce Tamarou’s internal application development and publishing framework, Magpie (scheduled for public release to coincide with YAPC::NA) and step through a series of real-world examples to show how its resource-oriented approach to development keeps simple things simple and makes hard things easier.
Topics include:
* Why MVC is the wrong way to think about Web development.
* Why most frameworks that claim to be RESTful aren’t (and how that makes life harder)
* An brief introduction to Resource-oriented development.
* A series of production-tested Magpie recipes covering the gamut of Web-dev from simple templated sites through advanced Hypermedia applications.
May proved quite an interesting month. Firstly, I got several confused emails relating to the Status page on The CPAN Testers Reports site. Secondly, we ran out of slots in the namespace for Amazon. And then thirdly a very involved discussion on versions on the mailing list.
$ whois bonchon.com
Whois Server Version 2.0
Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.
...
=-=-=-=
Visit AboutUs.org for more information about bonchon.com
AboutUs: bonchon.com
Domain name: bonchon.com
Registrant Contact:
BonChon
Jinduk Seh ()
Fax:
213 W 35th Street
HASH(0x1030ba64)
New York, New York 10001
US
Administrative Contact:
BonChon
Jinduk Seh (bonchon@bonchon.com)
+1.2122739797
Fax: +1.2122739774
213 W 35th Street
HASH(0x1030ba64)
New York, New York 10001
US
Technical Contact:
BonChon
Jinduk Seh (bonchon@bonchon.com)
+1.2122739797
Fax: +1.2122739774
213 W 35th Street
HASH(0x1030ba64)
New York, New York 10001
US
Status: Locked
Name Servers:
ns1.ipage.com
ns2.ipage.com
...
This is just a reminder for you if you plan to submit a talk
to YAPC::Europe 2012 in Frankfurt.
The Talk submission deadline is 15th July 2012 (four weeks before the conference).
The latest approval notification is on 31st of July.
We will evaluate talk submissions every three weeks and accept a handful proposals. This doesn't mean that if your talk isn't approved right away, it won't be. However, the sooner you get your talk proposals in, the better chance you have of getting a talk approved and placed on the schedule.
Please also remember
that we'd like to print the proceedings, so talk handouts are important too! We think that proceedings are a good way to call back the talks you have heard and to get more information about topics you were unable to attend.
As people also had asked, the Early Bird offer will exprire early in July.
From guest contributor brian d foy for YAPC::NA 2012:
I’m setting up a decidedly low tech way to give newcomers special access to Perl celebrities without the risk that their conversation will be hijacked by all the other conference attendees who already know that person. So far, I’ve convinced Sinan Ünür, Randal Schwartz (merlyn), Ricardo Signes (rjbs), Karen Pauley, and Dave Rolsky to participate. If you’d like to be one of the Celebrities for these lunches, add your name to posterboard. There will be a posterboard in the conference registration area starting Wednesday morning. For each day, there will be some slots where someone with the Celebrity’s name and a meeting time (and maybe a food preference). Four people can put their name under the slot they’d like to attend (and maybe we’ll add a waiting list). Meet back at the posterboard at the chosen time and go to lunch at a place your group chooses. That group gets an exclusive lunch and conversation with the Perl Celebrity. Although I’m not requiring that the group cover the lunch tab, it might be a nice gesture. My only rule is that you should not have ever interacted with that person, online, offline, IRL, or in any other way.
I'm pleased to announce the release of mod_perl 2.0.7, available at
the following apache.org URL, along with a CPAN mirror near you
shortly, as well as http://perl.apache.org.
This release of mod_perl contains an update for perl 5.16, see the
change log below. Thanks to the code contributor and mod_perl dev team
members who made this quick release possible!
I was tweaking my procmailrc today. My procmailrc recognizes a number of common pattern-based spam items and logs those into logs that I rotate on a regular basis. Anything else gets fed into a Mail::Audit-based "Sortmail" script. As I was testing a minor tweak, I noticed that the logfile for Sortmail (driven by the Mail::Audit object) wasn't getting any messages.
Long story short... I had opened the Mail::Audit logfile as "-", because I wanted it to use stdout, which in my procmailrc I had directed to the proper log.
But RJBS recently changed Mail::Audit from using the two-arg open for this name to the three-arg open for this name, and this was only apparent once I had used the CPAN diff tools (only in the source, and not documented, sadly).
Yes, I had created a 30MB logfile named "-" in my home directory. After carefully removing that file, and using an explicit filename for logfile, all was good.
But this is a heads-up for anyone else who might have presumed that "-" means stdout in Mail::Audit... you might be logging somewhere odd right now. :)
I am not sure whose fault is, but Test::Pod now verifies for characters outside ASCII, and complains a missing =encoding directive. I like this check to be done, but I do not think that breaking half of the CPAN is a good idea. It would be better to just carp for the error, but not make it fail. This would give time to authors to fix their modules. In a later release, this could be a fatal error.
Now, we have Dancer, DBI and a lot of other modules broken, not installing cleanly from CPAN.
You're going to go to the Moose Hackathon? You arrive in Frankfurt a few days before the event? Then you might want to do something in Frankfurt. We've set up a wiki page with some suggestions...
Unicode is getting ready to release their next version, 6.2 (likely in September). It includes only a single new character, for the new Turkish currency symbol. But there are changes to the properties of existing characters, and some of these may be of concern to Perl programmers.
The issues I think are of most interest to Perlers are the proposed changes of the Unicode General Category for a number of ASCII characters. Follow this link for a list of them. An example is U+0040 ( @ ) COMMERCIAL AT. Unicode proposes to change this to be a Symbol, instead of Punctuation. Perl code is somewhat shielded from this change, as qr/[[:punct:]]/ matches both Symbols and Punctuation in the ASCII range. However, what qr/\p{Punct}/ and qr/\p{Symbol}/ match would change, as would qr//[:punct:]]/ for non-ASCII characters.
There are other changes proposed as well. Use the first link above to get the details.
Hold on to your hats, this is going to be a wild ride! See you all at the Lowell Center for the kick off this morning at 9am sharp! Registration opens at 7am.
Don’t forget that you can watch the streams live on the web for free:
Also, the videos are being recorded. We will be posting them somewhere, but we don’t have details yet. We’ll do another blog post after the conference to let you know where you can watch them.
Matt S Trout will give a talk at YAPC::Europe 2012 described as
Moose is one of my favourite things to happen to perl in the last five
years, but the startup overhead and additional dependencies can be hard
to justify for very small projects.
So I asked myself ... "what's the smallest portion of Moose that I could
get by with, that would be easy to build so that when I load Moose my
classes can transparently upgrade themselves?".
The result is Moo - which provides most of the basic syntax of Moose -
and rather than trying to reinvent the MOP part, remembers enough to
make you a Moose::Meta::Class if you decide you need one later.
In this talk, I'll go over exactly which bits of Moose it provides, which
bits it doesn't (this list is longer :), why, and how it's built from
the ground up to be the right answer to "I want something smaller than Moose".