Re: Something about PEAR policy

On Sun, 22 Jul 2001, Stig S. Bakken wrote: > > >So to get out of this mess we need to define PEAR more clearly. Maybe > > >we could have avoided this situation if I had been more into writing > > >philosophy instead of coding in the beginning, but today that's not my > > >job anymore, it's ours. > > > > I think a lack of documentation is the real problem. Most coders are not > > familiar with the api documentation that is currently used. > > I agree totally, but lack of (easily accessible) documentation is a > bigger problem for "end users". The situation I was trying to describe > was the one among code contributors. > Yes, exactly. The philosphy needs to be created and we all need to stick to it. Stig, I think we are on the same page, finally. Can we all put an end to the ballyhoo of porting PHPLib into PEAR? Let's let PEAR figure its self out and let PHPLib become easier to migrate until the time that the two can be *easily* merged. This will, in the end, benifit both PHPLib users and PEAR users -- it'll just take a bit longer to work out than originally expected. I think I have stated the issues I have with PEAR, if y'all would like to address those (or not, either way) great, I think they reflect the opnion of a lot of other PHP developers who would like to contribute but are scared or hesitant about giving their code to the PEAR group. Minimally, it should be note *somewhere* (and soon) that PEAR code doesn't need to be licensed under the PHP-2.02 license and that the group is working on philosphy and contributions are welcome. -n -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- nathan hruby / digital statement nathan@dstatement.com http://www.dstatement.com/ Public GPG key can be found at: http://www.dstatement.com/nathan-gpg-key.txt ED54 9A5E 132D BD01 9103 EEF3 E1B9 4738 EC90 801B -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-