Re: [cgiapp] Marketing

[Peter Masiar <suppressed>]

Quoting Michael Peters <suppressed>:

> > Marketing,  Better marketing,  PR, call it what you want, should benefit us
> all in some way - all eminating from wider use of C:A.

..starting with better name.
CGI::Application::Plugin::BlahBlah is awfully long name, IMHO.
If BREAD or some other catchy name can be made a center of integration
of all features and plugins...
As old proverb says, you have only one opportunity to make first impression. :-)
So don't ever call anything CRUD, IMHO. Unless it is real crud.

> I know that Perl programmers might not be the prime target of this
> marketing effort (since most of them know about C::A anyway)

Most perl programmers know there are many web app frameworks,
C::A is just one of them, and it is not obvious why is the best.
It is task for C::A developers to explain them when and why
C::A is best solution. Evangelize.

> > There are loads of ways of marketing but I think one of the most important
> signs that something is "for real" is the availability of a book.  Yes you
> can read it all on-line/pod/wiki etc but nothing quite beats reading a real
> book on the train,

Wide usage of a system precedes The Book, IMHO.
So system which is widely used has lot of FAQ and how-to articles,
step-by-step recipes, which are easy to find and useful.

I know many people insist on perl's TIMTOWDI, but IMHO until you know
how to make "it" in many ways, one way which works in 80% cases is
*much* better than none. :-)

That's why I suggested a promoted wiki - as a repository of
knowledge, sorted and organized, unlike mailing list archives.
Repository created and improved by all interested. As almost-painless
accomodation of knowledge and best practices.

Let's face it, it is not easy to find time to dig into old archives,
to extract, distill and agregate wisdom out of old postings.
And for newbie, it is so time consuming to search through old archives,
ever wondering if you are missing real solution which would
appear if you changed your google query slightly.

These wiki how-to pages could be a base for the The Book later.
Like ActiveState published a book from most highly recommended
how-to postings.

For this to happen, somebody (more knowledgeable than me) needs
to summarize discussions from email list and put it to a wiki page,
and post link back to list, so people can comment on it untill page
is good enough (for some definitions of "good" and "enough" :)

Or, as option, write on wiki and publist to list link to page.

I do not want to force you guys to use wiki. Or even wiki site
I host for C:A here:
http://twiki.med.yale.edu/twiki2/bin/view/CGIapp/WebHome

As matter of fact I would have no problems if someone took over this
C::A wiki - BREAD project has another wiki, is it good?
Because recently I have hardly time to follow discussions on [cgiapp].

But I do see wiki as the easiest way to accumulate knowledge and
how-to recipies to make C::A adoption easier. I know it takes
little extra effort, and is not as easy as email. I know 90% of people
just does not get it - are not excited about possibility of editing pages.

But if enought people is involved - see wikipedia, free encyclopedia
bigger than Encyclopedia Britannica.

I am sorry I cannot contribute code, just suggestions.

Just my 0.02

> While this is true that a book does help, I'm not completely sure that
> C::A would be enough for a book. But I do think that a book about
> C::A/CDBI/TT(H::T)/D::FV, etc is well overdue.

WWW::Mechanize, WWW:Recorder, and testing framework, with examples, please.

-- 
Peter Masiar, suppressed,
Yale Center for Medical Informatics (YCMI), http://ycmi.med.yale.edu
I am not a lawyer. My ideas are NOT binding for University.
In doubt, Yale policy right: http://www.yale.edu/policy/itaup.html

---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed