O HAI
The Google Summer of Code (GSoC) has started! Yay! In the last minute I submitted my proposal which was accepted by the majority in The Perl Foundation. Thank you very much. Here’s the abstract:
Bulletproofing the Mojolicious unit and integration test suite
Mojolicious test suite is at the moment a nice mixture of unit and integration tests and does what it is expected to do. But its error messages aren’t very user friendly (if they exist) and there are many things that can go wrong in the web communication world. My goal is to close the leaks and to improve the whole test suite to be bulletproof and user friendly.
In the next few months I’ll document my journey in this blog. Sorry for my bad english, I learned some at school, but that was years ago. If you can’t understand it, it’s my fault. If you find a sentence that makes sense, it’s the excellent work of Ms. Mackenroth.
The blog story
I really like bootylicious (one file markdown file-based blog engine on mojo steroids by vti), but my shared hoster doesn’t. Actually, I think he doesn’t love Mojolicious. And not perl. And not git. And not whoami(1). No problem, I have a virtual server, but … no good domain names, or what do you think about gsoc.netzverwaltung.info? The best domain for this blog (gsoc.memowe.de) is not available for my server because it sits on my shared hoster because of … mail … and … no time to change that. So for now, I hope tumblr will work.
The Mojolicious story
I really like Mojolicious. I like the simplicity and elegance of sri’s code. I like the Simpsons quotes. I like the sinatraness of Mojolicious::Lite. And I like the community, which seems to be 95% russian for some reasons, if you look at the ML. I need to rewrite all of my webdesign shit to work with Mojolicious, now. But first, there’s something about Google.
