Wiki ReTaxonomy Project Meeting Notes

Issues to discuss:

• Agenda: http://lists.osafoundation.org/pipermail/general/2007-April/000516.html
• RIGHTHAND NAV Issues: http://lists.osafoundation.org/pipermail/general/2007-April/000519.html
• Wiki Homepage Proposal: http://lists.osafoundation.org/pipermail/general/2007-April/000513.html
• Planning and Notes Area Proposal: http://lists.osafoundation.org/pipermail/general/2007-March/000510.html

Issue: RIGHTNAV

What goes into the Team Templates?: Take to General list.

• Role: People | Contributor Notes
• Blog links
• List links
• HILITES (NEWS)
• ACTIVE PROJECTS (NOW)

Do we want Wiki Area Templates?

• Product
• Planning
• Engineering
• Teams
• Notes

What would go into each Wiki Area RIGHTNAV Templates?: Take to General list.

• TEAM(S)
• ACTIVE PROJECTS (NOW)

Issue: Information Architecture

Global includes versus Area and Topic specific RIGHTNAV Templates?: Take to General list.

• NEWS
• NOW
• DEFERRED
• TEAM

LEFTHAND NAV: Take to General list.

• Link to Landing Page
• Download and Sign-up links to Desktop, Hub and Server
• Give us Feedback
• Report a Bug
• Get Involved
• For Developers

Main Wiki Area?: Take to General list.

• Where do the Homepage/Community stuff live?

Nomenclature

• What do we call the Cosmo Team/Project anyway? Cosmo? Chandler Server? Chandler Hub?
  • All things related to the Team and Project = Chandler Server
  • All things related to the Product = Chandler Hub
• PPD = Product and Design?: Take to General list.
• Team versus Work Group?: Take to General list.

Hierarchy: How many levels of pages do we have? How do we unify them visually?: Take to General list.

• Wiki Area: e.g. Planning - Use "---++" headers, Use sidebar
• Sub-Area Topic: Apps Team page - Don't use "---++" headers, Use sidebar
• Content Page: 0.7 Dashboard Spec - Don't use "---++" headers, No sidebar

Can Main.UserName = Contributor Notes page?: Take to General list.

• Let's address this after Preview.
• We could maybe link from the Main page to the Contributor Notes page

Content: What goes in...

• Planning: Process, Product Roadmap, Specs, Bugs
• Team Pages:
  • Description of team
  • Processes
  • Meeting Notes
  • Tools and Resources
  • Cross-links to pages in other Wiki Areas that your team accesses on a regular basis.
  • RIGHTNAV: See above.
• Chandler Server Team Page is for the Engineering Team, not the Cross-Project team members: PPD, QA, Build and Release, etc.
• Do we have a separate Chandler Desktop Team? Yes! for Engineering.
• Notes: Contributor Notes.

Next actions

Aparna:

• Garden QA Team Page: QualityAssuranceTeam
• Garden QA section on the Engineering Area Homepage: Developers

Bear

• Garden Build Team Page: BuildProject^?
• Garden Build section on the Engineering Area Homepage: Developers

Katie

• Garden Engineering Wiki Area Homepage: Developers
• Create and Garden Chandler Desktop Team Page:
• Garden Operations Team Page: OperationsTeam
• Garden Platform Team Page: DeveloperPlatformProject

Mimi

• Take remaining Wiki issues to the list.
  • RIGHTNAV issues
  • Information Architecture issues
• Create an Operations Team RIGHTNAV Template

Priss

• Garden Chandler Hub Product area: Product
• Garden Chandler Hub Planning area: Planning

Pieter

• Take an inventory of copy that needs to be written in the top-level Wiki Area pages listed here: WikiGardeningProject

Sheila

• Garden the Planning Wiki Area Homepage: http://wiki.osafoundation.org/Projects/PlanningArea
• Garden the Chandler Project and Chandler Desktop sections of the Planning Wiki Area
• Review the new PPD Team Page: Teams.PPDTeam

Ted:

• Consolidate CommunityHome and Projects.OSAFCommunity
• Refine Community Section on the Wiki Homepage: Projects
• Garden the Chandler Server Team page: CosmoTeam

-- MimiYin - 06 Apr 2007