One of my next reviews is going to be web frameworks. I've posted my current plans on my new blog, where I'll be recording progress as I work through the review. I plan to implement the same application in each of the main frameworks I review, but would also be happy if others want to join in.
This is a collection of ideas for how we can encourage bloggers using blogs.perl.org to split their posts into an abstract and body. Attempts at education have largely failed, so I think we should try something else.
One of my problems related to Perl is that I'm not aware of a lot of things going on in the perl world, and there isn't a single place I can go to try and keep up. I suspect I'm not the only one. This post outlines an idea for a "perl community home page", where you could go to "keep up". I've whipped up a prototype, which is just a static page with a mashup of various feeds and static data.
To help CPAN authors keep track of who is using their modules, we could introduce two concepts: "follow module" and "I'm using this module". Both would be similar to the 'following' and +1 features found in nearly all social media services, and ++ in MetaCPAN.
This is an attempt to succinctly list all the different problems perceived with CPAN, and give them a name. No attempt at proposing solutions, or structuring a taxonomy / priority list, but data gathering.
Search this blog
- Reviewing web frameworks
- Encouraging bloggers to use the 'extended' feature
- Idea: perl community homepage
- The CPAN Unknown Usage problem
- What's wrong with CPAN?
- Don't release experiments to CPAN
- CPAN modules that (can) load other modules
- Perl programmer humour
- PAUSE permissions should be case-insensitive
- Creating a perl developer survey