Re: Adoption of Metabase (was Re: [PEAR-DEV]Re:Comparing ADODB with PEAR DB, Metabase andNative MySQL)

> Aw shit! Why do people always have to pull that "stop whining and do it > yourselves"? I mean, just because I'm not a PEAR developer am I not entitled > to an opinion? If users didn't criticize the work done by the developers, > then how would they get any feedback? I would be glad to help if I felt that > there was anything I could do, but I can't go in and start replacing PEAR-DB > with Metabase now can I? The way to get a voice in opensource is to start doing things, noone here really has any authority over what exactly is going to happen and thats the way PHP/PEAR/PECL works, if I get sick and tired of PEAR not having a decent installer yet then I either need to push stig and begin to ask what can I do to help etc or write one myself. The fact that Metabase's integration is being questioned is due to the fact it needs some work before it would fit into the famework and as far as I can see manuel is unwilling to do this. People in the Open Source comunity dont like being told what to do as they do it in their spare time, I can promise you if someone says you need to do this that and the other I immediatly think why dont you do it yourself. I do what I enjoy doing, that is programming, if I have programmed somthing then I am quite willing to act on feedback or fix bugs in it but Im not going to be dictated to about what I should be developing in the first place. Another way of really upsetting people is saying look why are you doing this my application is far better we should ignore all the work youve done and use this instead, PHP has several PDF modules, a couple of generic database api's, two XSLT modules (until last week) among others, this is due to the fact that one system suits one developer better than the other. There is no reason why we cannot have Metabase and PEAR-DB and others if needed all in pear then the user can choose which api they prefer and which abstraction layer suits them better. Manuel if you want Metabase in PEAR then get it to adhere to the standards to a decent level so that it is compatible with other PEAR elements, the idea behind pear is to create a framework that has a constant system of error reporting and dependencies. Metabase certainly doesnt adhere to this framework at the moment and that is where the main problem with it is. If you came back and said look Metabase now works with PEAR and adheres to the standards set down by the PEAR development team (which are there for good reasons). Then Im sure there would be no problem incorporating it into PEAR, also if you feel its too much work to do all by yourself try and recruit a few other people to help you. Dont expect to say this is the way things should be and I want you to do it for me (I dont actually think you said that from what Ive read of this discussion but it has come accross like that). You need to start doing it yourself and work from there. FInally I hope you do port Metabase to PEAR as it will benifit both Metabase and PEAR, metabase due to the fact you will have more developers working on it and PEAR due to the fact that it will have a new database abstration layer which may suit some users better than the current PEAR-DB API. - James -- James Moore jmoore@php.net