Re: Some PEAR remarks

> Anyway, my message was not meant to be replied. It was just meant for > you to reflect upon the reasons that were presented for the fact that > PEAR is a failure in terms of acceptance. You may bother to deny it, but > that does not change that fact. > > For once and for all, at least once in PEAR history, use your brain > instead of your ego, be humbl and try to listen when people are trying > to help you to make PEAR succeed instead of just keep being hostile. You > will never succeed in building a community if you keep rejecting the > members attempts to contribute to your project success. > Regards, > Manuel Lemos Hello, I've recently adopted pear into my projects. > You > will never succeed in building a community if you keep rejecting the > members attempts to contribute to your project success. A few days ago I had mentioned that I'd like a method to be able to test whether an object was a pear DB connection object and Stig thought it would be a good idea so he said he'd write a method for it into CVS. I think the PEAR team is responsive, and so have decided to adopt PEAR. Any open source project is no small undertaking. The makers of pear have generously decided to donate their time trying to create something that everyone can use. They put their time in to these things so you don't have to. Everyone is going to find fault with one thing or another. It's one thing to say: "No No No... you've designed that class all wrong" and another to say: "I think you've designed that class wrong, take a look at this rewrite I coded, I think you'll find it works better" Supporting facts for your arguments are good. Supporting code for your arguments are great. If you're concerned with building the strength of an open source project, and it's community... try the latter.