The goal of this lens on the Wiki is to have a place where potential Community members can find out What they can do and How to go about doing it in a way that is consistent with OSAF

• Culture
• Process and
• Design, Technical and QA standards.

Status

• Product plan/Roadmap/Timeline
• Weekly overview
• Working groups
• Individuals
• Projects

Outreach & Communications (link to CommunityWikiArea)

For Contributors (Chandler | Scooby | Cosmo)

• Design Overview
• Overall Architecture of The Chandler System

Projects

• Design
  • Dogfood The Chandler System and document your user experience
  • Provide feedback on user surveys
  • Participate in brainstorming exercises
  • Help with competitive analysis, keep us informed of new products in the PIM and Collaboration space
  • Write summaries of design list discussions
  • Maintain the design FAQ
  • Conduct and document user tests
  • Conduct and document user interviews
  • Conduct and document target user, usage scenarios, use cases and workflow analyses
  • Mock-up visual designs and visual specs
  • Icon design and production
• Implementing new features
  • Port to a new platform (Mobile?)
• Fix bugs
• Testing
  • Write new unit tests
  • Write new functional tests
  • Help test and log bugs
• Author a tutorial, podcast, screencast
• Extend Chandler

Getting Set-up (Links to ProductWikiArea^? and EngineeringWikiArea)

For people interested in participating in the Design process

• Design Process
• Planning and Specs
• Communications: Design mailing list
• Bugzilla

For developers: How to build Chandler (Chandler | Scooby | Cosmo)

• Development Process
• Communications: Dev lists and IRC
• Tutorials
• Builds
• Tools

Quality Assurance and Testing (Chandler | Scooby | Cosmo)

• QA Process
• Unit tests and Functional tests
• Tools

Writers ???

-- MimiYin - 17 Apr 2006