RE: [PEAR-DEV] PFC-RFC

> One concern remains, though: I haven´t yet read any rule about duplicate > packages in the PFC... Hmm a concern for me too! I'm all for PFC, subject to the above issue being addressed. I switched to using PEAR code because I hoped... - The code would be of a very high standard - The code would be well maintained - The code would be well documented - There would be packages to scratch most of the itches I had - There was a level of consitancy (using PEAR_Error etc) - Eventually most low level functions of any app would have a PEAR package effectivly making PEAR a 'loose' app framework - PEAR packages were the preferred/technically best/most sensible way of doing things - I could add to, improve and extend what is already there (have already done so for Date and Date_calc) So to summarise. I'm up for PFC as long as there are clear guidelines for duplicate packages. Dean