Hi all, I've been up to my old tricks archiving proposals and messing with the issue tracker. This time the casualties include some proposals that haven't been updated in months, some that were never updated from the template, and IT projects that are not currently in use. A few notes about the proposal so that we can all help keep this process flowing as efficiently as possible:
1) Please archive your proposal if you are not currently working on it and have no immediate plans to get back to it. You can always un-archive it later. 2) Please do *not* create 'placeholder' proposals with no content. This may discourage others who might develop similar components from creating their own proposals. I will delete (not archive!) such proposals as I find them. The reason these proposals will be deleted is to maintain the usefulness of the archive itself (which is a good source of historical and other information). 3) Remember to re-parent your proposal to 'Ready for Review' when it is, in fact, ready for review! :) At this time, you should also mail the community with a link so everyone knows to take a look at it. Although we are here to help everyone with their proposals, you should assume it is your responsibility to make sure your own proposal makes it through the process. On the flip-side of the coin, I know we have to improve our responsiveness for proposals that are ready for review and under review. We have been working on some mechanisms to guarantee responsiveness that will be announced shortly after 1.5. Until that time, please be patient with us as we've got our plates overflowing with 1.5 items. We're looking forward to going through the many new proposals soon! Thanks. ,Wil
