Re: PEAR's mission statement - let the fun begin

Daniel and Ian, > To get code into PEAR, it has to run a gauntlet of picky, fussy developers > who will be against a package going into pear for very minor deviations > from coding style. > PEAR should be more 'open', and relax standards in terms of getting > packages in What I like at PEAR is that there actually are coding standards, and the (even if light) enforcement to document your code. I really appreciate that code in PEAR isn't some hackety-hacked-files that are unmaintainable, but you really have a base you can work with. > I think PEAR should concentrate on some niche packages also > - i.e. Web Services is a good example. > So instead of waiting for proposals a list of all > the possible Web services should be gathered and then > a call for developers to code these. That's the wrong approach in my eyes. I develop and put code into PEAR because I actually need it, and not because someone out there needs it and not me. That is what paid work is for. -- Regards/MfG, Christian Weiske

Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc