> >We need a name for the things built with mod_perl, which people will
> >actually use. The name must be a good (suggestive) acronym.
Maybe. I always think it's best to let acronyms invent themselves.
> >Such a site would have:
> > * news on releases of all these software
> > * pointers to articles in TPJ, perlmonth, perl.com, the individual
> > sites, etc.
> > * case studies
> > * written-for-the-website tutorials and articles
>
> * API documentation
> * press releases
> * newsletter
> * management white papers
> * technical white papers
Yes, all these things. The key, IMHO would be for each area of the site to
have a sub editor who can look after it entirely - add/remove content, do
whatever they want, really. To me that's the only way of making it
manageable.
If we can create an architecture that allows us to do this easily that's
great, but I don't really want to make restrictions by forcing people to
learn Template::Toolkit, a big object model and a huge set of design
guidelines before they can help out.
> Intended audience:
>
> * IT management
> * developers
> (right?)
Yup. Also...
Journalists writing about this stuff. (God help us if anyone directs them to
perl.apache.org)
> Promotion:
>
> * cooperate with O'Reilly, TPC, ApacheCon etc. (just an idea)
> * get featured in e-commerce, Apache, Perl, XML etc. news sites
Yes, but marketing ourselves is kind of a secondary issue. We can worry
about that when we have some content.
> I'm going to have quite some spare time from December onwards
> and would be
> very interested in helping in the development of such a beast.
Goody goody goody.
So, how's our server coming along?
