Cosmo target user tenets - standalone and consultative
Google calendar comparison
Import - getting data into Chandler
Launch conversation
Branding
Notes
Design sessions
Chandler design reviews - have developers walk-through work (us and Aparna)
Dashboard
Edit/update - another big meeting to review workflows
Sheila will coordinate with Philippe on timing of these meeting
Search
Item creation vs search being default
Wants to add ability to save searches - not as simple as it sounds
Wants to bring back the view selector
Sheila will discuss with Philippe
Cosmo
Review of possible dashboard - no need for a spec
Talk about implementation steps - staged features
High-level run through of the proposal
Matthew is going to investigate graphics from setting design session
Wiki next steps
Jared can answer any questions while Priscilla is away
Structure - what's the first page on the wiki
How does the work we have done fit in with the curren structure
Do we need to circle back on wiki structure that Ted and Mimi put together
Mimi will revisit top-level pages
Sheila will help Mimi and get together the full product wiki area
Katie will send Mimi her pages to look at - with a list of questions
Non - code deliverables - main page
List of next actions
First draft of timeline
Mimi should talk to Pieter about screen-casts for Preview
New tenets for Cosmo
Consultative usage
Stand-alone usage
Google calendar comparison
It will be important at Preview time to understand the differences
Positioning - understanding our placement
Some forum for detailed analysis - did we have any reactions?
Are there things that will inform Cosmo or Chandler
Cosmo - aware with the world around you but can start using the app without being linked into that community. Useful pieces fitting together.
Different type of direction from OSAF.
It's worthwhile for PPD to have this type of thinking as part of our process. Ready to answer questions and deal with strategy issues.
Importing data into Chandler
Setup a separate discussion about this
Branding
Talk more about structure of branding in meetings
Priscilla and Trevor talked about process after the meeting
Did we give the other names a fair chance or did we always just compare everything to Chandler
If we can't use Chandler, do need to tweak our process? Yes
Since we have started to focus on a specific name, the process for coming up with backup names is not working
Should we continue to come up with a set of backup names with a smaller group
Backup names should be proposed with a visual treatment
Status
Sheila
Progress
Met with Bear and Mimi to discuss installers
Tracking edit/update process
Coordinating with QA on staged test plans
Cosmo 0.6 release
Bug councils
Testing
Checkin in with Priss before she leaves on vacation
Chandler
Bug councils
Dogfood tracking
Finalizing any remaining feature issues
Plans
Monitoring Cosmo in Priscilla's absence
Tracking Chandler Alpha5 bugs and issues
Dogfooding
Branding
Put together non-code deliverables timeline
Design list summaries
Wiki updating
Priscilla
Progress
Finish any non-development documentation for Cosmo 0.6 release: release notes, cosmo landing page content, help portal page.
Branding - Alternate names and plans on how to move forward with the visuals & alternate names.
Wiki portal project - sent an instruction page to the wiki gardening group to move forward with the side bar. Followed up Jared with instructions if anyone is lost. Will continue to make more tweaks upon my return.
Plans
Holiday
Mimi
Progress
Cosmo styleguide - Reviewed in Design Session
Finalized design of Chandler Accounts dialog with bkirsch
3 rounds of proposals for 'No data loss' workflow
Sorting through Triage status issues
Wrote up workflows for Dump and Reload after meeting with Bear and Sheila
Branding - Logo and Visual design, iterating on ideas
Brainstorm: Alternative names
Screencast scenarios and end-user documentation
Bugs, bugs and more dogfooding bugs
Plans
Additions to Cosmo styleguide: Button styles, Error messages
Review Dashboard with Cosmo team
Hopefully iron out recurrence issues related to the 'No data loss' proposal