RE: [PEAR-DEV] PFC-RFC

I like the general idea (then again I attended at least part of said discussion on IRC). A few general comments: - I am not so worried about the voting process or peer review of PFC classes. - I don't see a new PFC every week, so I don't think we will have people give votes because they are in a hurry - Most likely these will be PEAR classes that have reached a certain level of maturity. I only rarely see that a class is designed from scratch to be a PFC (we are not SUN after all that can do lengthy RFC's and then ensure that we still have someone willing to implement it). - I also think that proper docs and test suite are a must for PFC's - PFC's should also try to follow a common API concept - the developers of a PFC must accept the fact that they are running this thing for the community and not so much for their immediate development goals ... of course they will be a major factor in the future direction, but large changes would be up to debate in the pear community etc .. the benefit of course is probably a large userbase and that worm fuzzy feeling (which might convert into paying clients) - I also agree that in the PFC's we should really try to minimize all redundancy regards, Lukas