On Tue, Sep 18, 2007 at 02:21:21PM +0000, Ed Grimm wrote:
> I would have no problem with an additional package that bundled the two,
> and was maintained by both orgs.  I think that would be great.  However,
> I feel that merging the groups and the products, and not releasing
> stand-alone versions of either would alienate a number of current, loyal
> users.
> 
> For what it's worth, I am in the camp of using EmbPerl in a standalone
> fashion.  I am only speaking about the mod_perl without EmbPerl camp
> because I know it exists, and I believe strongly that it would also be
> opposed to a full merge of the two products.

I agree; this is a very good point.  I am reminded of what happened with
AxKit when the developers decided that it was more "efficient" to turn
it into a standalone server (AxKit2) rather than port it to working with
mod_perl2; they made assumptions about what people would want, and threw
away advantages that the earlier version had (such as being able to use
non-AxKit Apache features rather than having to reinvent the wheel).

My other concern about this proposed merge is who the heck is
volunteering to do all the work?  The mod_perl people wouldn't be
interested, they've got their own concerns.  They'd probably feel as if
mod_perl was being hijacked by outsiders.

I think a better proposal is simply to recruit Embperl developers (from
where?  I don't know) to assist in the improvement of Embperl because
Gerald is swamped and needs help.  Recruiting people to improve the
documentation is probably a good idea too.

Think big, but start small.

Kathryn Andersen
-- 
 _--_|\     | Kathryn Andersen  <http://www.katspace.com>
/      \    | 
\_.--.*/    | GenFicCrit mailing list <http://www.katspace.com/gen_fic_crit/>
      v     | 
------------| Melbourne -> Victoria -> Australia -> Southern Hemisphere
Maranatha!  |   -> Earth -> Sol -> Milky Way Galaxy -> Universe

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to