Although not always visible due to the infrequent release of new framework packages, there has been a lot of progress in the past few months. More than 100 community members(!) have joined the effort by singing the CLA, and are contributing via proposals, comments, patches, code contributions or documentation improvements.

Now the Summer is over and everyone is back at work, we feel it's the right time to finish planning the 1.0 release. We believe that in order to make a successfull release and get closure on the various aspects, it makes most sense to break up the framework into a limited number of subject areas and form project teams around these areas instead of components.

The following is a list of such areas and the components we believe we should focus on for 1.0. As you can see, a large amount of the work has already been done, but we now have to focus on getting closure on them and tying up loose ends.

Some of the components they've listed fall under the categories of:

• Web & Web Services
• MVC & related
• Authentication & authorization
• Databases
• Documentation & translation

There is also a high-level look at what version 0.2 of the framework will contain and a return to the "post often" methodology they had before.

I've run into an issue, or rather a friend of mine has. He asked me for advice, I gave it to him, but I'm curious how others would do this. The problem is this:

Team A, has been working on some code for a few months, Team A has a class called "SomeClass". Team B, is an "outsourced" team, who is writing a SOAP interface to Team A's code. Somehow, due to whatever reasons, Team A and Team B developers didn't talk.

Team B also created a class and called it "SomeClass". These classes are in files called "Aclass.class.php" and "Bclass.class.php" . There are some files, that include both files.. obviously, you end up with a "cannot redeclare class" fatal error.

Vidyut's suggestion was to just to change the class names. Unfortunately, this might not work if there is no communication between the two parties - they cannot come to a compromise on the naming.

He question to the community is "How do you handle an issue of single namespace, or rather no namespace ?"]]> Wed, 01 Mar 2006 07:04:27 -0600