Re: WHAT is PHP's vision????

> Ultimately it is the job of the Core Developers to accept or decline patches, > as the end user you of course can choose to compile or not compile a module > you dislike. If you are diluding yourself into thinking that people will > voluntarily code what they are 'told' to code, they'll do what they like/need > or not do it at all. I would not say that 'telling' people is the way to go. We need leadership, and someone to sell the vision of 'better life with PHP' to people. > At least from my personal experience all the work I've done involving PHP > source came from having a certain need PHP could not adequantly fulfill > in my mind. Agreed. But there are positive sides to Open Source: there are thousands of developers out there. Chances are, no matter where you decide to take PHP, someone will want to go there. I like working on my own, for example, but I have decided to put my efforts into PEAR because that will benefit the community more then releasing 'yet another ACME PHP libary' to satisfy my ego. Bye, Ivan