For those of you who have been keeping up-to-date with things we are working on a new version of the Ironman feed which will be called all.things.per.ly and is currently being developed as Ironboy by the members of northwestengland.pm and their associated friends who hang out on irc.perl.org in the #northwestengland.pm. channel.

This post is just to let you know that we have finally worked through a lot of the issues we were having with feed subscriptions (language issues) and working to weed out spam signups as well as developing code for the Perlanet which is replacing Plagger as the code the site runs on (well, sort of, there’s Catalyst and stuff in there as well, but someone else will be outlining the tech specs in a future post).

The eventual plan for the Ironboy code, once it is up and powering all-things.per.ly is to rip out Plagger from the current ironman.enlightenedperl.org and replace it with Ironboy (using Perlanet) this should help us to fix some issues such as the badge updates (finally).

Well keep watching as this will soon be a reality and we can all gush and say cool, now let’s have this feature…

If you want to help us bring the next generation of Ironman into existence then join the channel mentioned above and state you want to help.

I should not that my co-conspirator-leader Ian Norton (idn on irc) has been the principal force and focus for this project and all extra bits of kudos that are left over from praising all the people who are working on this should be gathered up and heaped on his impressive shoulders.

Just wondering if you can expand on the thinking behind Perlanet vs. Plagger? As someone who’s only poked around with Plagger, I’m curious about what the trade-offs are?

Phillip.

http://www.shadowcat.co.uk mdk

Hi Phillip. The main issues with Plagger that I was aware of during the choice to move were mostly to do with flexibility and size. Plagger installs a number of dependencies and we were concerned about the size as it was making Plagger a little inflexible and we needed to bring some flexibility into the system as we were moving towards integrating into a Catalyst framework for future development. Perlanet allowed us to use a system that was smaller and more mutable for fitting into the architectural choices we were making. I would say that if you pop into the #northwestengland.pm channel on irc.perl.org you’ll get a better understanding of some of the issues if you speak to Carl (fade), Ian (idn) and Matt (mst).