Multiple classes that do the same [extends 'We need another Auth']

i hope there will never be more than one package that does one thing. i think that a long time ago it was (commonly) agreed that PEAR was going to be a pool of classes which provides _one_ solution for each problem and not many as CPAN does. May be we should ask Stig, if that wasnt one of his goals for PEAR? i am sure having just one of each will improve easy-use and better overview. i think the Auth-discussion that has come up is giving even more reason to 'design' stuff before implementing and putting it in PEAR (i am not saying Auth was not 'designed' properly, i just mean that the discussion shows that some kind of 'design-process' is needed). I am not (exactly) going to suggest a process as Java has the 'Java Specification Process' or what it is called. but agreeing on the functionality and the way something gets implemented might be a good thing when starting to work on something. i am just saying that because i would really love to see PEAR becoming a project where people will say: 'look at PEAR that is nice code/design/work etc.' BTW i like the coding standards too, but i dont want to start a discussion on that now. thanks to everyone who makes life easier by providing PEAR-code, it really made my work much more efficient just my 2 cent -- Wolfram ... translating template engine .... http://sf.net/projects/simpletpl ... authentication system .... http://sf.net/projects/auth