> > I don't think it belongs in PEAR at all.  I could see the logic behind
> > distributing it with PHP, but don't see any reason to distribute it in
> > pear...
> 
> 
> Except that isn't this what PEAR was for all along?  A collection of classes
> and add-on modules to extend PHP's functionality?
> 
> I don't have anything against the Midguard folks personally, but isn't
> distributing Midguard with the main PHP distribution implicitly saying PHP
> supports/prefers the Midguard content management system over any other
> similar system?  What happens when someone else wants *their* system to be
> part of the main PHP distribution?  What criteria are we basing these
> decisions on?
> 
> There is also the license issue (which I know has been discussed before).
> But the first thing I read on the Midguard website is:
> 
>     Midgard will always implement an OS development to publishing
>     solution, future releases will include APIs for implementing
>     commercial applications.
> 
> Are we going to run into trouble down the road when this happens (and end up
> having to take Midguard out of PHP anyway)?
> 
> [There is also the fact that Midguard accepts donations and collects
> membership fees ... how is that going to change if Midguard is part of the
> main PHP distribution?]
> 
> And as for Alexander's comment:
> 
>     Shouldn't that means that almost all extensions from ext/
>     directory could be classified as PEAR thing?
> 
> My opinion is that yes they *could* be classified that way, but it doesn't
> make a lot of sense.  PHP users don't have a choice of which module they
> want to use for Blowfish encryption, for example ... so mcrypt is part of
> the standard distribution.  Perhaps the PDF modules should be, since we have
> several.  I don't know.
> 
> But, to me at least, Midguard seems to be code that is a "layer above" what
> I would feel belongs in the main PHP distribution.  In the same way the DB
> abstraction class is (even the C version of it) ... and that they both
> belong in PEAR.

Midgard is not exactly a layer above PHP, it's an extension to PHP, exactly like the 
session extension, or the gd extension.

Here is my own point of view (far from objective, cause I'm from the Midgard team ;):
Midgard is a CMS, like MySQL is a DBMS. MySQL has it's own module in php4/ext, as well 
as pgsql, oracle, etc... That gives users the choice of what DBMS they can use with 
PHP.
I don't mind *at all* if Zope, or Websphere or whatever other CMS has its own module 
in php4/ext (in fact, that would give users more choice, thus that'd be better).

My own 2 cents.

> Just my 2 cents (and given without intent to offend).
> 
> 
> --
> Colin Viebrock
> Co-Founder, easyDNS Technologies Inc.
> http://www.easyDNS.com/
> 

--
David


-- 
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to