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; it doesn't make any distinction between developing with php and developing the language itself. Whining about people not reading the descriptions won't change it; get over it. Before taking a huge step like making the list moderated or (gasp!) subscription only, why not just rename the list to something less inviting to people who either a) don't care to read the list descriptions or b) have a poor grasp of English/programming and don't comprehend the difference.
php-evo (php evolution)? php-int-design php-improvement php-future I know all of these are corny and stupid; they are the product of 5 seconds of thought. I'm sure a better end result could be gained with more thought. But even these are much more likely to appeal less to people looking for the general (or whatever) list. John On Tue, 5 Feb 2002, Rasmus Lerdorf wrote: > 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: > > > > > > > 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 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 feasible option, but by making a closed > > subscrition system you basically end the open source project ideal. > > > > > - We need a place for developer discussion which is not interupted by users > > > who can't read the support guidelines. > > > > Yes this is a problem in almost every project. You can read many lists > > and find the same problem. There is no answer to this. > > > > > - We need respite from certain individuals who are not helping PHP, but > > > instead turning good developers away. > > > > There are killfilies for this very reason. > > > > > - We need to have a list that is not full of bugs junk and cvs junk - > > > something for plain developer discussion. > > > > I disagree with this too. While the bug notifications are annoying, they > > provide at least an oppertunity to have more developers see them. Thats > > the best chance given to the project to keep the bug count down. Be > > honest, how many people write bug free code, or more specifically test on > > platforms other than their primary development choice? Not many. > > > > A big -1 on this suggestion. > > > > >---------------------------------------------------------------< > > Dan Kalowsky "Tonight I think I'll walk alone. > > http://www.deadmime.org/~dank I'll find soul as I go home." > > [EMAIL PROTECTED] - "Temptation", New Order > > > > > > > > > -- John Donagher Public key available off http://www.keyserver.net Key fingerprint = 4024 DF50 56EE 19A3 258A D628 22DE AD56 EEBE 8DDD -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
