The columns in this report contain the following information:

• Priority - A sense of how important it is to address this issue in the short term.
• Action Item - Concise description of the action item to be completed. Where relevant, Java package names of the primary classes involved are listed in [square brackets]
• Volunteers - Names and EMAIL addresses of those developers who have volunteered to assist in the design, implementation, testing, and documentation of this action item's changes to Slide.

Developers can nominate themselves to work on particular action items by asking a Committer to add their name and EMAIL address to those items. The developers working on each item should discuss and agree upon the approach to be used for implementing the item's changes to the project source code and documentation, prior to completing those changes. Such discussions should take place on the SLIDE-DEV mailing list so that everyone can stay apprised of what is going on, or chime in if they want to contribute ideas and suggestions.

This list is intended for Slide 1.1.

Priority	Action Item	Volunteers
Low	Improve compliance of the transaction manager with the JTA spec.	---

Priority	Action Item	Volunteers
Low	Add additional helper macros. [org.apache.slide.macro]	---
Medium	Add index helper. [org.apache.slide.index]	---

Priority	Action Item	Volunteers

Priority	Action Item	Volunteers
Medium	Filesystem based store for structure, sercurity, ...	---
Medium	Lucene based implementation of index store.	---

Priority	Action Item	Volunteers

Priority	Action Item	Volunteers
Medium	Add user management features.	---

Priority	Action Item	Volunteers
High	Add some test cases.	Juergen Pill

Priority	Action Item	Volunteers

Priority	Action Item	Volunteers
Medium	DASL support.	---
Medium	Delta V support.	---

Priority	Action Item	Volunteers
Medium	DAV ACL support.	Remy Maucherat
Medium	DASL support.	---
Medium	Delta V support.	---
Low	GUI based administration tool.	---

• Rewrite of the core and of most of the helpers. Objective : cleaner design with more functionality, while keeping the API mostly unchanged (if possible)).
• Make the helpers pluggable. [org.apache.slide.common]
• Design and implement a simple process engine to deal with approvals, acknowledgements, ...
• PVCS descriptors and content store.
• CVS descriptors and content store.
• Design and develop a Slide JSP Taglib (see the jakarta-taglibs project for more details).
• Develop a full-fledged application using Slide. Good candidates would be a portal kit, a discussion forum or an iDrive - like system.