Packages and voting

I'm sure this must have been discussed some time ago if so please accept my apologies and send me some summary of what was decided. I just thought that it can be a good idea to split PEAR packages in two categories: "PEAR core packages" and "PEAR user packages" the only distinction will be how packages are approved. You can use the actual method for "core packages" with some additional restrictions and a very light approval method for "user packages" In this process there won't be two "cache" packages in the core but there can be many in the user packages. This will reduce the number of packages in the "core" to make it easier for users to browse, read docs and use them and if they don't find what they need there or want to see alternatives they can then browse the "user level packages" It can also improve the burocrartic manouvers for package inclusion since some users may just want to submit their code to the "user packages" categories knowing that their code is not a must-have for the PEAR core but may be useful to someone. We can think that the "user packages" are like CPAN and that the "core packages" are the PEAR SDK like the Java Classes in the SDK. Just some thoughts. Luis.