Scooby 0.2 Planning

Proposal for 0.2 Tenets

• Target audience is potential community contributor/developer, volunteer. No target user will be identified since this is still not intended on being a "usable' release.
  • Not for general use. Still mainly target for a narrow audience. Users interested in web technologies, AJAX and/or calendaring.
  • Chandler users may be casual users of Scooby.
• Small re-factoring from Scooby 0.1.
• Flush out navigation for the week view. ie. Mini Cal. Moving between weeks smoothly.
• Revise layout to more closely resemble Chandler. It should feel like home to a Chandler users.
• To exhibit the beginnings of a high quality consumer application. ie. Scooby logo, consistent icon set, small aesthetics tweeks.
• Community goal: to show progress from 0.1 in order to raise excitement in the developer community.

Notes on Scheduling and Priorities

• What is the plan for any given release? Should it be time-based (1 month) release or feature based release?
• When do you want to bring in community? Would there be a blocked off time allocated for documentation and refactor for the community?
• Re-factoring: Look at what worked and what didn't? After 0.2, will there be pieces ready for outside contributors? We will need to stick with the API for a little while, and interfaces need to be well documented.

Example of agile development schedule:

Release every 30 days (+/- holidays). The SWAG will include documentation and re-factoring.

Example of a suto-agile development schedule proposal:

Release every 30 days (+/- holidays). Require one week afterward to document and re-factoring.

Evaluate Scooby 0.1 release cycle:

• How many days test around?
• Was there minimal enough information for the community/contributors to understand what's going on? How much documentation SWAG time is really needed?
  • Is Bobby's code well documented in java doc?
  • Is Matthew's code well written not only in the comments, but to transfer on the wiki?
• Did everything estimated in Scooby 0.1 get done?
  • How many additional SWAG would it take and include estimates in Scooby 0.2.

Mile stone planning:

• Do we shoot for mile stones in the planning? Is it necessary or should we just go for the 30 days release cycle?
• Example of Cosmo mile stone planning: Cosmo 0.2 Planning

How does UI/Design fit into this aggressive schedule?

(Using example of the 30 day release cycle)

• 5 days a month�Non-Design/UI Tasks
  • going through the bug list in bugzilla
  • user response/usability testing

• 5 days/mo � Strategic design
  • Design for the next release
  • Design proposals, sketches sent to the list, low fidelity prototyping
  • Hold design session meetings

• 10 days/mo�Tactical design
  • Support development�UI issues that can come up
  • HTML wrangling for image assets
  • Graphic production work, icon, button variations?

Status and Release Date

• Current planning of 0.2 in progress. No release date has been set.

Specs and Proposals

• Coming soon!