Re: [Everydevel-opers] Two Points

[Petruchio <pet...@pe...>]

First off, I think you should fork, rename, or fillet the project as
you see fit... and I doubt anyone would disagree.  You've been laboring
in the wilderness on this for a long time, now; why you should feel
constrained by the opinions of others (even if you were receiving any),
I have no idea.

> > On Jan 9, 2009, at 4:31 AM, pau...@us... wrote:
> > 
> >> POINT TWO
> >> =========
> >>
> >> I'm not sure there's any point posting to this list any more, because
> >> I get barely any response and never any assistance .... then some
> >> smartarse wonders why things are going so slowly....
> >>
> >> Nonetheless, I'd really like to create enthusiasm for everydevel.  It is
> >> afterall one of the few CMS which are perl based in a world where PHP
> >> rules in the space.

Not only are there few CMSes in Perl, there are few application in
Perl.  Perl people tend not to write end-user software; they write
libraries, and they tinker with other people's libraries.  PHP people,
on the other hand, write applications, and have a wonderful attention
to detail.  One is inclined to say that this is because details are
all most of them understand, but it's important to keep in mind that
they're succeeding admirably even so.

> >> The question is how to create this enthusiasm and where.
> >>
> >> Experience suggests it isn't here. But where?

IMO, you put your finger on it here:

> As for being better than Drupal, I actually think Everything is already 
> better in the fact it is far more flexible.  Drupal is easier for 
> novices to get up and running with though.

I think that to make this project popular would require a radical
change in direction.  Installation is unquestionably the biggest
issue.  Requiring Apache configuration or mod_perl is death.  Even
requiring shell access to get the thing running is unacceptable.
If you got this to be as easy to install as WordPress, I think you'd
find it was all downhill from there, and that popularity came easily.

I also think it's very important that something like this look very
pretty by default, and that it make it as easy as possible for the
average user to do average-user tasks without configuration.  But
if you made it simple to install, you'd probably get other people to
help with those goals.

Where I think a CMS could kick the opposition's collective ass would
be in fully automating the installation of updates, themes, and plugins.
But architectural features don't matter much until there are users.

That having been said, I can't say I'll be much help even if you take
up my suggestions.  But I admire your tenacity, and wish you well.

--
Petruchio