Question What about the Glossary?

Next action: Brainstorm content from each audience's perspective.

Ted's prioritization of what we need to fix:

• People coming in from the outside
• Stuff for internal stuff
• Some overlap

Potential approaches:

• Overarching taxonomy
• Consolidate website and wiki
• Use blog for Journalling

PriscillaChung - Perhaps we can go over the positives and negatives of each approach.

Audience/Owner

• New people
• Passive community
• Day-to-day contributors
• Staff: Open issue: split up staff?
  • PPD
  • Apps
  • Services
  • Platform
  • QA
  • Community
  • Ops
• Mitch
• Board
• Potential sponsors (e.g. CSG)

Focus, across all Topics and for each Topic

• Never
• Future
• Specify dot release
• NOW
• Urgent!

Projects

• Chandler
• Cosmo
• Scooby

Teams and Individuals

• Team pages
  • Team members
  • Team member status
  • Team status
  • Projects and Issues by Team
• Individual Contributor notes

Topics

• Product Management
  • Product definition
  • Vision
  • Roadmap
  • Tenets
  • Competitive Analysis
  • Prioritization and triage
• Design Research
  • PIM
  • Library Science / Semantic Web
  • Cognitive Psychology
  • Usability
  • Visual design
  • Community feedback (on the products/feature requests)
• Design Documents
  • Usage Scenarios & Workflows
    • Triage/GTD
    • Organization
    • Communications/Sharing/Collaboration
    • Calendaring
  • Specs for:
    • Interaction design
    • Visual design
  • Guidelines
    • Visual style guide
    • Interactions design patterns

These Topics need to be filled out by people who know

• Development
  • Bugzilla Components
  • Development Projects

• QA

• Build/Release

• Community
  • StarterProjects -type pages - entry portal for both engineers and non-engineers who want to know what needs to be done and how to get started AND registry for who is working on what.
  • Localization coordination and oversight
  • Parcel/Plug-in/Extension registry

Content type

• Landing pages
• New hire pages

• Logistics
  • Mailing lists
  • IRC
  • Bugzilla

• Announcements - (not sure announcements should be made on the wiki, the mail lists, website, and blog are the more appropriate push and pull channels for announcements - PieterHartsook)
• Personal notes
• Meeting notes

• Research & Information Gathering
  • Research write-ups
  • Brainstorms (Random ideas)
• Proposals
  • Release Plans
  • Use cases & Workflows
  • Comps
  • Artwork
• Discussions
• Decision write-ups
• Dogfood feedback

• Design/Engineering Specs
• Developer docs
  • Known Bugs
  • Scheduled Features
  • Module page
    • Architectural overview
    • API doc
    • Engineering Specs
• QA
  • Test Plan
• Build/Release
  • How to get the source code
  • How to build stuff
• End-user docs
• FAQs

Topic status

• Open issues
• Proposals
• Discussions
• Final decision
• Discarded
• Superceded

Support content

• Glossary
• Contributor profiles