Jayson Minard, head of the Zend Framework development team, posted a message to the framework mailing list last night announcing 2 weeks of concentrated focus on community and internal proposals for the Zend Framework. Fire up those word processors and start submitting!

For those of you who do not subscribe to the framework mailing-list, here’s the full text of the message. Fire up those wordprocessors and let the floodgates of the proposals be thrown open wide. (Remember to check the FAQ before submitting and if you haven’t already, submit your CLA)

=C=
——-

Starting Monday, June 12th, we would like to focus the community on proposal submissions and comments and at the same time focus the core team on reviewing and moving proposals and associated code into the repositories. We will introduce the Laboratory repository during this time frame for proposals that are not yet accepted to the core framework or are in a pending status. All accepted proposals will end up in the proper place before we move on to 0.2.0 development (expect 0.1.4 soon <g>).

Our goals for next week (and the week after) are to get in a good solid list of proposals that fill in remaining gaps in the framework, mainly looking at the chain of events that occur from receiving a request through rendering the view. Secondary areas of concern are alternative search implementations (i.e. Full text in database) to help develop the abstract search base, and additional coverage of the vast amount of public service API’s (XML/RPC and Web Services). Lastly, filling in some possible alternate implementations of components such as Zend_Config (i.e. Other configuration file formats) would be helpful as well to test the original API’s from multiple viewpoints.

We will also be proposing a few ourselves including a new ActiveRecord / DataObject proposal and a few changes to the database layers to cover cases where auto-quoting of parameters isn’t desired (i.e. Literal value or database function used).

If you had submitted a prior proposal, they will be reviewed again to see how they fit into the current mindset of the framework roadmap. If you have updates, please have them ready to go and we’ll take another crack at the proposals. If you have a current proposal, then they will start to get the team’s attention as well so they can be wrapped up quickly. If you have an approved or pending proposal, expect for it to move into incubator.

Also during these two weeks, we will be upgrading our infrastructure to make the process of contributing much smoother and add more to the environment to help us all know what is going on, how to contribute, how to communicate, and anything else that buys us a much easier path to reach 1.0 and beyond. Keep in mind we are looking for the best current tool set that supports open-source development teams. Looking for a set that delivers the requirements of a fairly complicated model (due to the contributors agreement and pushing out ownership to so many component leads). We will not limit ourselves in these choices other than by what problems we want solved.

Part of the changes we are making will make the proposal process easier, but it will come in late in the process so we’ll make due with the mailing list in the meantime. So have at it, and we’ll talk more over some nice juicy proposals.

––j