RE: [PHP-DEV] Lists

2002-02-06 Thread Zeev Suraski
At 10:42 PM 2/6/2002, Robinson, Mike wrote: >I reckon we've been through all this before. >Closing the list in any way is just a bad idea. It's just that never before did we lose actual contributors over people who make nothing but noise. Now it is happening. Zeev -- PHP Development Mailin

RE: [PHP-DEV] Lists

2002-02-06 Thread Robinson, Mike
Title: RE: [PHP-DEV] Lists I reckon we've been through all this before. Closing the list in any way is just a bad idea. Mike Robinson IT/Developer - Torstar Media Group Television Phone: 416.945.8786 Fax: 416.869.4566 Email: [EMAIL PROTECTED] > -Original Message

RE: [PHP-DEV] Lists

2002-02-06 Thread Zeev Suraski
I'm afraid php-dev-spam may become a bit more popular than you think :) At 06:58 PM 2/6/2002, Gary Benson wrote: >I've been thinking about this. What is really needed is some way to send >automated 'get lost' messages without requiring a list moderator. These >messages have got to be real easy t

RE: [PHP-DEV] Lists

2002-02-06 Thread Gary Benson
I've been thinking about this. What is really needed is some way to send automated 'get lost' messages without requiring a list moderator. These messages have got to be real easy to send to make this work. How about this: set up a list (php-dev-spam, say) that isn't archived or advertised any

RE: [PHP-DEV] Lists

2002-02-06 Thread James Cox
> Umm while this sounds like a good idea initially, why are you trying to > make PHP a closed development project? This maneuver will make it lots > more difficult to get any new developers in on the project, and for those > with one time questions to pose them. > > A moderated list might be a

Re: [PHP-DEV] Lists

2002-02-06 Thread Gary Benson
On Wed, 6 Feb 2002, Hartmut Holzgraefe wrote: > John Donagher wrote: > > This has probably been mentioned before, but I think the naming of php-dev is > > way misleading. It's funny that people get so ripped when someone sends an > > off-topic question to this list. Someone who doesn't read the

Re: [PHP-DEV] Lists

2002-02-06 Thread Hartmut Holzgraefe
John Donagher wrote: > This has probably been mentioned before, but I think the naming of php-dev is > way misleading. It's funny that people get so ripped when someone sends an > off-topic question to this list. Someone who doesn't read the descriptions may > very well take php-dev to mean PHP de

Re: [PHP-DEV] Lists

2002-02-05 Thread Lars Torben Wilson
On Tue, 2002-02-05 at 15:34, John Donagher wrote: > > This has probably been mentioned before, but I think the naming of php-dev is > way misleading. It's funny that people get so ripped when someone sends an > off-topic question to this list. Someone who doesn't read the descriptions may > very

Re: [PHP-DEV] Lists

2002-02-05 Thread John Donagher
This has probably been mentioned before, but I think the naming of php-dev is way misleading. It's funny that people get so ripped when someone sends an off-topic question to this list. Someone who doesn't read the descriptions may very well take php-dev to mean PHP development. This is ambiguous

Re: [PHP-DEV] Lists

2002-02-05 Thread Rasmus Lerdorf
I completely agree with Dan on these points. If you don't want to see certain types of posts, or posts from certain people, you are a simple procmail rule away from getting rid of them. Making php-dev a closed list is a horrible idea. -Rasmus On Tue, 5 Feb 2002, Dan Kalowsky wrote: > > >

Re: [PHP-DEV] Lists

2002-02-05 Thread Dan Kalowsky
On Wed, 6 Feb 2002, James Cox wrote: > I ask a simple question: > > how many more unsubscribed hard working developers does it take before we > realise that we need to ban certain people, and make php-dev (or it's > brother) subscribers only, and closed subscription? Umm while this sounds like

[PHP-DEV] Lists

2002-02-05 Thread James Cox
I ask a simple question: how many more unsubscribed hard working developers does it take before we realise that we need to ban certain people, and make php-dev (or it's brother) subscribers only, and closed subscription? - We need a place for developer discussion which is not interupted by user