Although YAPC::Europe::2013 preparations are well underway in Kiev,
it is time for the venue committee of the YAPC::Europe Foundation (YEF)
to think about the location of the 2014 conference. YAPC::Europe
wouldn't exist without dedicated teams of volunteers, and we are always
excited to see the enthusiasm and learn about the new ideas the
community has to offer.
Further information about preparing a complete application can be
found at http://www.yapceurope.org/organizers/index.html .
Proposals submitted to the venue committee will be added to this public
repository (you may provide private information separately) to benefit
future organizers.
The deadlines which apply to this portion of the procedure are:
Saturday, 13 April: Deadline for sending a letter of intent. This
letter simply expresses interest in hosting the conference and provides
contact information (both email and telephone) for at least two organizers.
This is an optional step but it can be to your advantage to alert the
venue committee of your proposal.
Thursday, 27 June: Deadline for sending proposals to host YAPC::Europe
2014.
If you do not receive a confirmation for your letter of intent or proposal
within a couple of days, please personally contact a member of the venue
committee.
Please send your questions, letters of intent, and proposals to
venue@yapceurope.org.
A couple of weeks ago I asked for a show of hands to gather interest in restarting the Thames Valley Perl Mongers. The positive response we received is an encouraging sign that TVPMs are still out there (at least 30 of you) and interested in meeting up!
The meeting will be held on Wednesday 20th March at 7pm, and for this first occasion we hope to have two talks with a short break.
The venue is Reading Enterprise Centre on the University of Reading main campus. Refreshments and light snacks will kindly be provided on the evening by our hosts, Opsview:
Please confirm your interest in attending by dropping a note to peter.finnan@opsview.com, including your full name (required for access to the building). If you wish to volunteer a talk of up to 25 minutes, please also provide a summary and the title.
I also urge you to join our mailing list to keep up to date with this and future plans:
I used to work with DBIx::Class::Schema::Versioned to upgrade my DBIC Schema but soon I needed more then it offered.
Starting with DBIx::Class::DeploymentHandler was a bit troublesome because I had a hard-ish time understanding the extensive documentation.
Now that I moved past that phase I want to present my way of using DeploymentHandler and hopefully spare you some of the burden.
Note: I write my DBIC schema resultclasses by hand and deploy to whatever database system I need.
Feature list
* each schema version should be installable to a clean/empty database
* single step upgrades of schema versions
* create pl scripts that do something on the schema before and/or after upgrade
Let's try to predict when we will be able to {conveniently,realistically,sensibly} use Perl 6 to build real-world applications. Note: this post is just the result of its author's pondering and is not meant to be negative towards Perl 6.
Jenkins - is well known continues integration server. One of it's great features - one may extend it by writing custom plug-ins.
Recently I have create one plug-in to build and make distributive of perl applications.
It implements standard build scheme:
look up source directory
install dependencies into local directory
create distributive
Other features are:
find 'tagged' directory with maximum version number ( implementing install from subversion tags )
applying different patches (install other cpan modules)
color output
... and some others
For now it's only Module::Build compatible.
Links:
New York Perlmongers held a successful hackathon this past weekend at an event hosted by Rubenstein Tech in lower Manhattan. By our count, at least 24 people participated, coming from as far away as Harrisburg PA and eastern Connecticut.. Participants ranged from people making their first contributions to Perl-related open source software projects to current and former Perl 5 release managers and pumpkings. Every participant contributed, in part or in whole, to at least one patch to an open source project. When all patches are applied, at least six people will have made their first contributions to the Perl 5 core distribution. Other projects receiving contributions included HTTP::Tiny, Term::Readline::Perl, Module::Metadata and Catalyst, along with more streamlined procedures for creation of .rpm files for CPAN distributions and improvements in PAUSE, the Perl Authors Upload Server.
Special thanks go to Jaron Rubenstein of Rubenstein Tech — they’re hiring! — and the five other Rubenstein staffers who participated in the hackathon.
OK,
so sometimes you decide you're going to stop using some module X,
maybe because something better has come along.
Let's say I want to track down all my CPAN modules that use Any::Moose because my goal is to port each of them to either Moose or Moo.
MetaCPAN has all the dependency information,
but I don't want to click through each of my distributions.
Enter the MetaCPAN API...
I have enjoyed actively participating in the Los Angeles Perl Mongers and Thousand Oaks Perl Mongers groups, but recently relocated to Salt Lake City, UT. So, what stands between Salt Lake City and a Perl Mongers group? You (you know who you are). Anyone interested in participating in a Perl Mongers group in Salt Lake City, please follow-up here or get in touch with me via email.
A request has been submitted to the folks at pm.org for a mailing list, a pm.org hosted site, and a link to the main pm.org map page. Since those nuts and bolts are fastened by volunteers it takes awhile. But we don't have to wait. The time to start organizing something is now.
Perl Mongers groups provide excellent opportunities to get to know others in the local Perl community, to introduce newcomers to Perl's many ways to do it, to learn, to share, and to socialize.
Just a little note to announce the release of Galileo version 0.023. Galileo is my CMS that aims to be 100% CPAN installable, all you have to do is this:
$ cpanm Galileo
$ galileo setup
$ galileo daemon
This release makes installing even better, because now when you run galileo setup you get a web interface to configure your CMS and then install the database!
Ok that image is just slightly ahead of what is now on CPAN, but its close :-)
We are proud to announce the full schedule of talks at Swiss Perl Workshop 1. As you'll see,
there is a very interesting range of speakers and topics through the day.
There are a few small and big things that we did last week for the conference. Let us tell you about them.
First of all, we signed a contract with the river cruise boat and are thinking now of the best possible route so that we can both see the incredible Kiev landscape from water and have enough time for the social part on board. Also, we are working on the buffet menu. All in all, the cruise is going to be an amazing conference experience. Just take a look at their official video.
Let us also remind that less than a month is left until the Early Bird price expires. If you buy a ticket today, you can save 18% of its price. This is only possible before 1 April.
At the moment, I'm writing a presentation about Mason2. The goal is to somehow convince my colleagues to consider using Mason. Instead of Template Toolkit.
As part of it, I thought I'd do a bit of performance benchmarking against Template Toolkit. So I put together a reasonably complex mini set of templates using both systems. Well, as complex as TT can take in reality. Which is not very much.
Notes from a Newbie document the creation and deployment of yardbirdfanclub.org with Perl Catalyst on shared hosting. They are intended for a Perl Catalyst Newbie who would like to study the creation and deployment of a simple Perl Catalyst application.
Now that we've experimented a little and are confident in what we're doing, we'll start over from scratch, beginning with authentication and authorization as explained in the Catalyst tutorials.
Let's compare the latest constant.pm to a minimal equivalent:
$ ./perl -Ilib -le 'print $^V'; /usr/bin/time -l ./perl -Ilib -le 'use constant X => 1..5; print X' 2>&1 | grep 'maximum resident'
v5.17.10
3829760 maximum resident set size
$ /usr/bin/time -l ./perl -I/tmp -le 'use constant X => 1..5; print X' 2>&1 | grep 'maximum resident'
1200128 maximum resident set size
That's 2.6MB bloat to define a constant. (The culprit turns out to be
utf8, natch, to handle Unicode constants. (Why, God?!)). For reference,
/tmp/constant.pm
, which does most useful constant-type stuff, is here:
If you are still undecided on joining us at Swiss Perl Workshop in Bern on March 22, it's probably because you are worried that the venue may be hard to reach. You can put your mind at rest. :-)
This was the second course I've attended from Dave Cross, and the first one under the Perl School banner. Dave has been using Perl heavily for around two decades up to and including this year, which gives him a very deep knowledge that is also firmly up-to-date. He is also an excellent presenter and trainer, so all that knowledge I just mentioned comes pouring out freely in a way that is easy to understand.