[epo-core] What are we going to -do- with this non-profit we have, anyway?

[Mike Whitaker]

> Ok, good to see there's general agreement on that.
>
> Marketing seems to be a dirty word in the perl community. Fuck 'em, if
> they just want to hack fine, and we can spend actual money on the  
> rest.

Amen. :)

>> We need, IMO, to be the ones who write that big standard, and the
>> hell with TMTOWTDI.
>
> Right. The key enperl project that's code related is  
> $extended_core_name
> - perigrin is kindly starting to prototype this in the form of  
> Task::Kensho
> so please do send suggestion to him about areas where there's too many
> ways to do it and an opinionated suggestion should be there.

Is peregrin on this list?

> Somebody (I'll try to have a play with this, but anybody else  
> interested
> should too) should start learning Perl::Critic policy writing as  
> well. I
> want an enperl coding standard that can be shared across the  
> community;
> the closest we currently have now is DBP and I Am Not Happy With That.

Module::Starter::EnPerl as well? :)

While we're at it...

Books.

The non-online and active part of the Perl community learns its Perl  
from books.
They therefore think the Llama and the Camel are the bible, and if  
you're very lucky, they believe in PBP and perhaps Conway's OO book.  
If miracles happen, they read the testing notebook!

To engage them, which I suspect represents a sizeable percentage of  
Perl programmers, we need better books that embrace $extended_core  
and writing modern Perl.

Question, though: what percentage of Perl programmers DO we think  
that is? It's pretty much 80% of my team, as a very small sample - if  
it wasn't for my every-Friday 'cool modern Perl' presentations,  
they'd still think Class::Std was cutting edge.