Qiang has serious plans about keeping the core framework extremely minimal and implement optional, yet very useful components as official extensions.
I think he’d be happy if we listed all recommended libraries here. Many developers already use third-party classes (aka vendor libraries) in order to extend Yii’s capabilities, and they are should be listed here as well.
At this time I can think of the following modules:
You dug this out! Thanks for starting this topic to gather ideas.
Yes, the general principle is that we’d like to keep the core relatively compact and stable while using the zii project to maintain self-contained components that accomplish commonly needed tasks.
We have not decided how zii should be developed, documented and released. One thing for sure is that it would involve tremendous effort and we will recruit new team members to work on this. At the same time, the zii project should also be very fun.
Unfortunately I personally don’t have much experience with leading community-driven open source projects, but here’s my $.02:
If you wish to allow anonymous/non-official developer contribution (with admin approval of course), a separate forum category would be fine to help responsible administrators review code.
In order to keep components compatible, they should be organized and tagged similarly to Yii. I suppose it is highly recommended to keep extensions compatible with the latest major Yii branch; so minor Yii versions must not introduce changes that would cause any compatibility issue with any extension.
Can it be possible so that extensions generate the same quality documentation that core does? I mean, every extension has its own introductory and api page here at yiiframework.com/extensions.
I’m quite sure that extensions will be far more popular if they were accessible through this site, and not only from Google Code.
This zii library is called official extension library. That means, it will be treated with the same quality control including its documentation and maintenance And of course, we will package it well in release files, just like the yii core. No, we don’t allow anonymous contributions, and we also don’t allow non-official developer contribution (that belongs to the current extension library). As time goes, we expect to gradually expand the team size maintaining zii.
Many tickets have been created regarding non-essential classes and features (they are mostly planned for milestone 1.1a). May they be collected here and transferred manually to zii project to cleanse Yii issues?