I'm seeing a lot of convergence in what people want to work on and want to have in the toolkit next, but we collectively seem to not quite be making progress. How can we make these things happen for OpenACS 5.2, which implies code-complete by the end of June (6 weeks from now) for an August release? Each of these areas has actively interested coders and clients, spec work in progress in the forums, and often working code. What's missing varies, but none of these features has all of
- Reference documentation and tutorial entry
- committed code in HEAD which complies with current best practices
- General community buy-in as the preferred approach (Best Practice)
- test cases
- Examples of usage
Can we get an owner for each feature who commits to put in best efforts to get the feature finished for 5.2?
- TCL API for creating new cr_item subtypes and acs_object subtypes
- TCL API for manipulating (create, edit, retrieve, delete) cr_items and acs_objects
- Auto-generating forms (add, edit) for a specified object type.
- Data model changes in support of internationalized content
- Support for package maturity rating (I have responsibility for getting this one done, and PeterM and FrankB have done most of the work)
