Worth reading if you are curious if Perl6 can save us from the madness and chaos that is Perl5's version of the above :)
Hello Catalyst Community!
Well, its come to the end of another year! I know we've all done a ton of work over the past 12 months, so now is the time to brag about it, to show off newly learned skills and take the opportunity to say something in a forum that is going to reach a lot of people and become part of the legend and lore of our community.
We've opened a repository on github (https://github.com/perl-catalyst/2013-Advent-Staging/) to help you get started. It contains a nice template and has some examples of previous years successful contributions. So, here's your chance!
What.. you don't know what to write about? Oh. You think your code skillz are not up to it?
This year I want to invite people to go beyond the traditions of Perl Advent. Of course cookbooks style code examples with explanations are great to have. But I'd also love to just have articles about your successful Catalyst projects, new website launches, or any work you've done using Catalyst on the job, for personal use or for teaching.
So if you want to just write a short article about how you started working for a Perl shop that used Catalyst and how that ended up for you, go for it! Or you started a new website, I'd love to see that as well. Or you demoed Catalyst at an on the job or offsite presentation. Whatever, just something to do with Catalyst and around all the great stuff Catalyst brings to Perl and to our industry.
In particular I'd like to reach out to non programming or management members of our community. I know quite often our community conversation is overwhelmed by programmer talk, but non programming managers, recruiters, product developers and more are also Catalyst stakeholders and I'd be really happy to see an advent article that goes like "I'm a CEO of a company that uses Catalyst and its really worked out for us...".
I'm even open to seeing articles that are great, instructive - constructive criticism of Catalyst codebase or common practices. If it brings us to a good place in the end, just go for it!
So, this year lets try to broaden the conversation and be more inclusive of voices that are often ignored. Don't be afraid! And don't worry to ask for help or for review of anything you want to submit
I'm closing comments since its just being used for SPAM. Hey Typepad, can't we do something about all the SPAM users?...
Hello Catalyst Users and Hackers!
05 November 2013 marked the end of the Hamburg development cycle, which was kicked off back in June. This release is a bit longer in development than the past few, but as I expected, things got a bit slow over the summer (I'm Northern hemisphere located) and since we did a lot of development releases along the way I think the longer cycle worked out.
Now I am please to announce https://metacpan.org/release/JJNAPIORK/Catalyst-Runtime-5.90050 !
A number of people contributed to this release included two of my coworkers here at Campus Explorer (ether++, gerda++), n0body from IRC (who stepped up with a patch at the last moment that solved some testing problems in dev release 5) as well as many people who contributed via discussion, or doing code review (t0m++)
In general I think we hit most of the goals we set at the start of the hamburg. I'll do a full end retrospective later in the week. In no particular order of importance:
We also fixed up docs, modernized some of the Moose code, added experimental support for IO-Async based event loops for doing non blocking IO (web sockets, long polling, streaming, etc. see the example repo on github for nonblocking IO and websockets under Catalyst) And some other stuff, go check out the change log and view the diffs.
I'll blog more about some of these updates, and retrospect this development cycle a bit later. And there's nothing stopping any of the rest of you from playing with this and blogging as well!
What's next? I'm not setting the start of a new goal specific development cycle, but of course the repo is still open and you can branch the code and hack as you wish. If you are looking for some ideas, feel free to checkout our quest hub list: http://questhub.io/realm/perl/explore/latest/tag/catalyst
Remember, there's lots of ways to contribute. You can code of course, but we also need people that review proposals and ask questions or consider solutions (see the quest hub link above), as well as people to blog, review documentation and just generally help out people when they are stuck on IRC.
Thanks again for everyones help, and please don't be upset if I forgot to mention you by name.
Catalyst on CPAN : https://metacpan.org/release/JJNAPIORK/Catalyst-Runtime-5.90050
Git repo: git://git.shadowcat.co.uk/catagits/Catalyst-Runtime.git
This closes the hamburg branch. On a personal note, both my Hamburg hen and rooster were lost to predation over the summer, so this release will serve for me as a memorial to them. Thanks for checking in!