I think the overall observations of "too many top level components" and
"lack of focus" are understandable perceptions that should be clearly
addressed in our documentation.
Component names are selected based on compromise between logical
hierarchy and convenience (i.e. less typing). The decision was
intentional, and will give an appearance of many "top level" components,
but reduces the burden on developers for memorizing longer or more
complex names or typing more.
Regarding focus, the Zend team decided to focus on general areas, such
as MVC and i18n/l10n. Instead of skipping around concentrating on
individual proposals based purely on perceived general applicability, we
also factor in the overall importance of completeness for a general
suite of components.
For topics of obvious value (e.g. form related components) that have not
yet received our full focus of attention, we are encouraging and
supporting community members to coordinate, submit proposals,
demonstrate some level of quality or community acceptance sufficient for
admittance to the ZF Lab, as described below:
http://framework.zend.com/wiki/display/ZFPROP
Cheers,
Gavin
