For those of you following my blog, you should remember that I promised an "update" regarding best practices with opcode caches in PHP. I went ahead and poked some people at Zend and phparch if they would not like to organize a webcast on this topic. Then I leaned back and waited until they finalized a date for a webcast. As you probably guessed by now .. there is a date set, which is March 16th. Only 4 more days so register quickly if you want to attend.

Just a short heads up. I think the PEAR constitution elections are a good thing (tm). I know its sounds corny, but PEAR is mainly suffering from its own success. Its simply a huge project, with so many active developers, packages and downloads. I am confident that both of the proposals will help in improving collaboration in PEAR, mainly because they basically provide the same organization we used to have for all of PEAR (which worked great in the beginning), now for categories of related packages. I think this is exciting and with casting your vote (anyone who has a PEAR developer account, which is quite a lot of all of the people with php.net email accounts) you give the entire effort more credibility.

I was talking with Konsta from Doctrine on IRC about all the different authors of the various database abstraction related php libraries when I had a sudden inspiration: Wouldn't it be cool if we could get all of these authors on a single mailing list, where we could all discuss best practices, new discoveries, challenges etc.?

Matt Asay proposes the following definition to the answer what consititudes an "open source company" that I blogged about yesterday: "An open source company is one that, as its core revenue-generating business, actively produces, distributes, and sells (or sells services around) software under an OSI-approved license."

So the blogosphere seems to be in an uproar regarding what constitutes an "open source company" and what doesn't. This seems to have been spawned by a blog post by Nat Torkington. While working on the OSCON program he stumbled over what he deems as questionable entries, since he does not feel the relevant backing companies are sufficiently "open source".