I've updated the old Oracle PHP FAQ and the Oracle PHP Troubleshooting FAQs that were hosted by Oracle Technology Network (OTN). We've redirected the old FAQ pages to a new wiki page: http://wiki.oracle.com/page/PHP+Oracle+FAQ with the updated content. Feel free to create an account and make updates. Hosting the FAQ on a wiki seems appropriate because PHP is open source and grows by the value of everyone's contributions.

Questions so far include some of the basics (connecting, querying, etc) and a few more complicated issues like pre-fetching, LOBS and new information for using the Zend Server to connect to your Oracle databases.

The PEAR Blog has posted a request for ideas to help work up a new developer FAQ they can hand out to potential PEAR developers as a "jumpstart" guide to working with the package repository.

New developers need quite a time to familiarize themselves with the rules and conventions in PEAR. With the new role of mentors in PEAR2, they will have a contact person they can ask in that cases. But in many cases the same questions will get asked which will get boring for the mentoring developer, so we need a Mini-FAQ with a list of things the newbie should know.

They're looking for comments posted to the entry to help define this guide. So far, a suggested outline has been proposed by David Coallier for both general information and developer-specific details.

The PEAR Blog has posted a request for ideas to help work up a new developer FAQ they can hand out to potential PEAR developers as a "jumpstart" guide to working with the package repository.

New developers need quite a time to familiarize themselves with the rules and conventions in PEAR. With the new role of mentors in PEAR2, they will have a contact person they can ask in that cases. But in many cases the same questions will get asked which will get boring for the mentoring developer, so we need a Mini-FAQ with a list of things the newbie should know.

They're looking for comments posted to the entry to help define this guide. So far, a suggested outline has been proposed by David Coallier for both general information and developer-specific details.