At 10:24 PM 7/9/2001 -0700, Frank M. Kromann wrote:

> > On Tue, Jul 10, 2001 at 07:51:14AM +0300, Andi Gutmans wrote:
> >
> > > I think it's something we should consider. From what Joey wrote it 
> sounds
> > > as if the PHP Group is perceived as something *above* php-dev in the
> > > community. I don't think this is a good thing and therefore most
> > > discussions (forget the current one) are held on php-dev. The PHP Group
> > > does mostly administrative stuff so maybe we could just have 
> something like
> > > a PHP UNIX system group, a PHP license group, a PHP web group and so on.
> >
> > I think it would be pretty interesting to at least discuss the
> > possibility of organizing the masses into a handful of working
> > groups (or special interest groups).
>The number of mailing lists has allready increased (PHP-DB, PHP-WINDOWS 
>and so on) Most of the trafic on these lists are either specific to a few 
>extensions or user questions. The development list (if we filter out most 
>of the bug-messages) is where most of the development is discussed.
>I think we still need the general list to make sure we are serving all 
>supported platfforms/web servers/...
>I would like to see more team work arround specific issues (windows ISAPI 
>stability, generalized function naming core and extensions, improved OO 
>just to mention a few). This could be dynamic groups with a few key 
>members to drive the effort.
>The PHP Group could then take a more coordinating role and make sure all 
>areas are covered etc.

What I meant is that the PHP Group is maybe not the right solution for 
what's happening today. Some of its members are barely active and we could 
benefit a lot of having more people involved. I know some of the PHP 
developers feel left out and don't understand what the PHP Group does. I 
don't think adding another X members to the PHP Group will solve this. 
Rather maybe splitting it up and not having once central place of X elite 
people might be a better idea. As what it does is mainly administrative 
work and coordination we could split this up to working groups. It doesn't 
mean you have to be on those mailing lists but as it is now I think it 
might be a good idea to split the PHP Group into different working groups. 
For example, system,  web site, development.
You wouldn't have to be on the mailing list unless you'd be on one of the 
working groups.

(Still half asleep Andi)

PHP Development Mailing List <>
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