You're all just proving my point by replying to this stupid thread. Thank you for that. :D
--Jani On Thu, 2007-12-13 at 10:09 -0500, Daniel Brown wrote: > I would say, if anything, there are two viable choices that > wouldn't adversely affect the PHP project: > > 1.) Have the Internals list read-only by all but (a) > developers/contributors and (b) people granted permission after having > posted useful information via the General list. > > 2.) Probably a better idea, just click that DELETE button on any > emails you don't feel like reading or responding to. I find that, in > a case study performed by myself just now, it takes me about a > half-second to achieve success with this method. > > By silencing the masses, you offer them little choice but to find > an alternative solution. By closing out the discussions, even just > that much, you're turning PHP from a completely open source project, > in which all can participate and help mold the future of the language, > into a partially open source language. Yes, the source code itself, > as created by the core developers, will still be available to the > public at large.... but any discussion on implementation of new ideas > could only really be achieved through a fork of the project. Further, > how would you encourage new developers to join on if they couldn't > interact with - and get a feel for - those who actively post on this > list as it is? By only allowing them to read the threads posted, > without the ability to ask questions, it's like reading a manual. And > how often does the discussion in a published book evolve without > requiring a full reprint? > > -- > Daniel P. Brown > [Phone Numbers Go Here!] > [They're Hidden From View!] > > If at first you don't succeed, stick to what you know best so that you > can make enough money to pay someone else to do it for you. > -- Patches/Donations: http://pecl.php.net/~jani/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
