June 2015 Archives

I am pleased to announce that The Perl Foundation's Grants Committee has voted to treat Taiki Kawakami's grant to work on Perl::Lint as successfully completed.

Since our most recent report, Taiki has fixed a small bug.

To help fund more work like this, please donate to TPF's grants fund.

YAPC::NA::2015 Closes Sold-Out Conference

No Comments

As we close YAPC::NA in Salt Lake City, we want to thank everyone who attended, organized, and sponsored this year's conference. Without our community coming together in support, we wouldn't have such a great event! This year, YAPC sold-out at 340 attendees with a reported attendance of over 350.

Specifically, The Perl Foundation would like to thank our local organizing team for all of their hard work. David Oswald and his team from the Salt Lake Perl Mongers worked diligently to organize the local venue and local volunteers. We also want to thank the staff at Little America for all of their help and support.

With the introduction of our new sponsorship programs, we are excited to announce that YAPC this year boasted 14 sponsors! We'd like to thank each of our sponsors for helping make YAPC possible, and playing such an important role in our event. Our job fair offered a great opportunity for our participants to connect with all of our wonderful sponsors and learn about career openings.

We hope that everyone in attendance, as well as those who took part in YAPC via our live streaming, enjoyed the talks this year. We'd like to thank our speakers for their effort in preparing and presenting to such a high standard. Thank you to John Anderson and Jayce Hall for organizing our speakers this year.

We we like to thank our keynote presenters this year - Seth Johnson, Larry Wall, and Phil Windley. We would also like to thank Ricardo Signes for hosting the Q&A session with Larry.

This year we also introduced a beginner's track for new Perl developers. We'd like to thank Karen Pauley and Ya'akov Sloman for organizing the track.

We would like to say "thank you!" to our TPF volunteers, board members, and committee members, namely conference chair Health Bair for his work organizing YAPC, as well as board treasurer Dan Wright.

Perhaps most importantly, we want to thank YOU! Thank for you joining us this week in Salt Lake, and thank you for your commitment to The Perl Foundation and the Perl Community.

Dave Mitchell has requested an extension of $20,000 for his Maintaining the Perl 5 Core grant. This will allow him to dedicate another 400 hours to this work. During this grant he sent weekly reports to the p5p mailing list as well as providing monthly summary reports that have been published on this blog, the most recent of which are linked below:

Report for Month 19
Report for Month 17 and 18
Report for Month 16

Before we make a decision on this extension we would like to have a period of community consultation that will last for one week. Please leave feedback in the comments or if you prefer send email with your comments to karen at perlfoundation.org.

If successful this extension will be funded from the Perl 5 Core Maintenance Fund.

Tony Cook writes:

Approximately 40 tickets were reviewed or worked on, and 4 patches were applied.

This month blead allowed patches only for blockers, so there won't many patches applied to blead.

I spent much of my time working on blockers, both trying to solve them in blead, or to report issues to CPAN maintainers whose modules were broken.

Act Voyager Report

No Comments

The Act - Voyager project has not come to a halt, although it has been a bit silent. My apologies for those who had been waiting last month for the report.

Life has taken some turns, in my favour, and thanks to Rick Deller from Eligo, I got a nice job at Broadbean technologies in London - and yes, moved from my lovely little hometown to the Perl capital of the United Kingdom, and met some great people at work or during the London pm activities.

The few hours left, I kept pushing forward the project, little by little. And I am very happy with the direction it is going and below I will try to explain what has happend with the basics of the REST-api. But before that, I think I should mention that the Act-Voyager project will leave behind the legacy system. It has served the community for more than a decade and during that time changes have been made to fulfil the needs organisers had. But in that process some decisions also have led to not such nice solutions. Things will need to change and a nice REST-api should come from the drawing-board...

REST api's deal with resources, indicated by an URL... the new structure will be:

https://example.com/yapc_na/2015/...

The first level (which I called a syndicate) functions as a kind of aggregate for the events organised under that 'authority'... in this example... the 2015 edition of the YAPC-NA. In the future I would love to see it happen that we could use it also for the monthly pm-meetings, like

https://example.com/amsterdam-x/2015_12/...

So, in the future, the api will simply deliver the news about YAPC-NA at the resource:

https://example.com/yapc_na/news

and if you only want the news for the 2016 edition

https://example.com/yapc_na/2016

The design is slightly deviant from other URL patterns, normally it would be more tedious: https://example.com/syndicate/yapc_na/edition/2016/news or the other approach would be using tons of filters.

Another important thing in designing a REST-api is the decoupling between the REST resource representations and that actual data-store. In other words, the Act-Voyager REST resources are not being a 1 to 1 translation of the legacy-tables, but will be composed from different tables. At a few occasions in Cluj, Amsterdam-X, German Perlworkshop, I gave a presentation about multi-lingual REST api's and did address the decoupling and how a REST api should use a abstraction layer which does all the hard work - not your Dancer2 app.

Add on top of that the fact that Act has a 'rights' table that holds the information for a conference and a user and what rights he / she has, and it becomes obvious that it was not going to be a simple Dancer2 dispatch app. For the authentication I modified some previous work I did for a plugin: Dancer2::Plugin::HTTP::Auth::Extensible.

Bolting all things together, I came up with a REST::api::Handler... one that can do only very simple tasks... dispatch the work to the REST::api::Objects, REST::api::Collections or REST::api::DataStore. Now, instead of having all these different methods in one huge module, I put them in smaller modules, Moo::Roles to be more specific. And each of these roles will be applied to the Handler object, based on the context... a ResourceRoot and a ClientUser.

inside Dancer2, it looks just like:

post '/news' http_require_task 'insert_news' => sub { http_handler->insert_news(...) };

And the handler knows if and on what level to dispatch the request to the REST api datastore.

I personally think, Act Voyager is going to have a save journey now

NB: for the brave... check it out on Github

Theo van Hoesel

About TPF

The Perl Foundation - supporting the Perl community since 2000. Find out more at www.perlfoundation.org.

About this Archive

This page is an archive of entries from June 2015 listed from newest to oldest.

May 2015 is the previous archive.

July 2015 is the next archive.

Find recent content on the main index or look in the archives to find all content.

Pages

OpenID accepted here Learn more about OpenID
Powered by Movable Type 6.2.2