Re: Some PEAR remarks

le 28/04/02 23:00, Manuel Lemos à mlemos@acm.org a écrit : > You are pretty wrong! I was not supposed to talk about this before I can > confirm that the plan is viable, but since you are questioning my good > intentions, be aware that my intention is that if PEAR becomes the > standard library of components as PHP needs, is to ship PEAR > distribution within a PHP Classes CD that is meant to be released every > three months. > > This means more value for the CD subscribers and more awareness for the > whole PEAR project. You keep on criticising our work and now you want to use it on your CD and probably make money with it. I don't agree. > It is too bad that you see the PHP Classes as a threat to PEAR as you > always did since the beginning 2 years ago when you even attempted to > discourage me to release Metabase that had already over 1 year of > development and was going to released publically for the first time. Personally, I don't see your PHP classes site as a treat for PEAR. A lot of code in there is crap. Even if there were some good classes, they would be hard to find among the rest. Furthermore, your site is ugly and lacks a whole bunch of features. > Then you also refused to cooperate in the development of single PHP > components repository because you thought you would always do better > without my help. And this is probably the best decision we have taken. We don't have the same standards of quality. In PEAR, people are maintaining their code, in PHP classes, most people submit once and then disappear. They don't have access to CVS. > It is funny that now you claim that just want to compete when it was you > that forked your own projects to compete with mine, both Metabase and > the PHP Classes site, instead of cooperating! Now I see through. Here is the grief ! Here is where your anger comes from, poor child... > The PHP Classes site was always a done on my free time. The problem is > that it has grown to a point that it consumes all my time to support and > develop. If it was better thought from the beginning, it wouldn't take you as much time. Look at what we've done for PEAR and maybe you will learn. PEAR doesn't take US all OUR time. We are a community and we all work as volunteers to make it better. And you, you are all alone (I wonder why, really). > I have been away from the work market at my expense, but I can't remain > this way forever. So, my options get back to a proper job and have > little or no free time to maintain the site properly, or try to make it > generate some income from it and continue to develop the site. > So, what is your problem with this? You are the one with a problem. > Maybe you would be satisfied that I just closed the site and get back to > a well paid suit's job!? Again, this is your problem. I don't see why you are so frustrated. Maybe because the PEAR project won't make your own project look as good as it could. Excuse me, but that's not our problem. This is open-source and this is competition if you feel we are competing. Personally, I don't see competition here as we are volunteers and don't reason in your capitalistic way. This is the same thing that makes Microsoft so bad when it comes to Linux. > But, as I always say, I don't want to go where I am not wanted. If you > do not want to benefit from Metabase capabilities because of some silly > accusation of self promotion, hey, be a man and tell me in the face and > I'll just drop it. I don't care. PEAR DB works fine for me. It definitely can be improved but we are not bound to MEatabase. There are plenty ways to make one thing. > That makes you look stupidly arrogant when you should be thankful when > somebody tries to contribute to your project. I wonder if you ever think > how are you been seen by the community. It doesn't seem you do. Ah ! Ah ! Who is arrogant ? It happens that sometimes, the submitted code is not as good as it could be.. If we want to keep a certain level of quality, we can't accept it in PEAR, especially if we think there are better implementations possible. But it is always hard to say to someone that his code doesn't suit the quality standard we want or that it simply doesn't fit in PEAR (most of the time because it is a complete application or a framework). What you said was probably right at the beginning of PEAR. This is because things where getting organised and it was quite difficult to handle all the submissions plus the strategy of the project. But I see now more and more comments and critics on new submissions. They are not always as concrete as they should but I hope they will improve with time. So for this point, I sort of agree with you. We should try not to make submitters feel alone and help them to improve their code if we can or just let them know directly that their code does not suit PEAR standards. Bertrand Mansion Mamasam