Following our meeting, I got the impression that there are two very
different problem associated with adoption of the perl architecture for
websites (henceforce PAW).
p1. You have to put it together youself from Apache, mod_perl, TT, DBI,
Apache::Session etc etc etc and this takes forever and is intimidating.
p2. at first glance, perl.apache.org re-enforces any doubts you might have
had in the first place.*
So, I see two entirely seperate solutions required.
s1. Lots of lovely programming technical stuff so that getting set up with
what you need becomes a simpler process.
s2. Lots of lovely content/marketing/co-ordination/communication/creative
writing/ to support THE USERS OF both what we have and what we might have in
the future. That's THE USERS OF not THE CREATORS OF.
USER is defined as anyone who's working life is affected by it, e.g. junior
programmer, senior programmer, sysadmin, CTO, bloke who has to give a
presentation to the board on why they are still using Perl, etc, etc.
If we need something to support the CREATORS of s1 then Sourceforge is there
waiting.
As a non-programming** member of London.pm I'm obviously more interested in
s2 - but.... is anyone else?
-------
*Not a criticism of perl.apache.org. That site is concerned only with
mod_perl and not what runs on top of it.
** That's as in "doesn't" rather than "can't". I think :-)
----
Jonathan Peterson Ideas Hub Ltd
(t) +44 (0)20 7487 1310
www.ideashub.com
