This is the home of Webware development sub-projects. These projects are used to discuss and implement specific items on the ToDo list or the WishList. We are using dev.zope.org's FishBowl process as a model for these projects. Here is some more info on that process.
TavisRudd is responsible for maintaining this page, but feel free to edit it.
Project Proposals
Active Projects
Implementing a comprehensive UnitTesting framework for Webware, that verifies its core behaviour and can also be used for unit testing of user applications.
Implementing a flexible and seamless framework for handling authentication and authorization. The WebwareUserManager application will be built on top of this framework.
Creating a BatteriesIncluded distribution of Webware that comes with other related tools, such as Cheetah, FunFormKit, XmlForms, the database adaptors, etc.
If you want to start new project add a link to the list of project proposals and create a summary page following the guidelines below. You might also want to use Python's PEP's as a guide for developing your proposal (http://python.sourceforge.net/peps/). Once you've completed the summary page, announce the proposal on the webware-discuss email list to get some initial feedback and recruit volunteers. If you decide to continue with the project after the initial feedback move the project link from 'Proposed Projects' to 'Active Projects'. If you decide not to continue, move the link to 'Withdrawn/abandoned Projects' instead.
All active projects should have summary page that addresses the following:
Who is the project moderator and who else is working on it?
What is its current status?
What is the problem being solved?
What (broadly) is the proposed solution?
What are the major project risks?
What is the scope of the project? (what will, and will not be addressed)
What are the deliverables of the project?
What is the delivery target (a date or Webware release number)?
just some quick notes for now:
use the wiki to keep the discussion open
keep the project's summary page current.
occasionally post an update to the webware-discuss email list for people who aren't following the project's wiki directly.
if you are doing any coding, make sure you coordinate your activities with the other developers. Keep them informed about what you are doing via the webware-devel list.
-- TavisRudd - 31 Oct 2001