Scooby
Priscilla posted meeting notes for the weekly Scooby meeting



Cosmo
Sheila described an UI problem with Cosmo's administrator UI.
Priscilla wrote up a UI review of Cosmo adminstrator UI: http://lists.osafoundation.org/pipermail/design/2006-February/004066.html with some further notes documented here...http://wiki.osafoundation.org/bin/view/Journal/UIDesignIssuesZeroDotThree


Dogfood
Priscilla posted a conversation with Leppy, who had problems importing data from his http://www.basecamphq.com account.


Mimi posted Dogfood feedback re: trouble configuring mail account information and auto-detecting events stored in UTC.

[Next action: Sheila and Mimi to pull together another Dogfood feedback summary this week and rationalize with Dogfood triage proposal.]


Planning
Sheila posted a first pass at triaging Calendar Dogfood bugs and enhancements from a usability perspective: http://lists.osafoundation.org/pipermail/design/2006-February/004065.html

Sheila posted a first pass at phasing 0.7 Scheduling and Invitations from a design perspective: http://lists.osafoundation.org/pipermail/design/2006-February/004105.html

Sheila posted a first pass at phasing 0.7 Plausible Dashboard from a design perspective: http://lists.osafoundation.org/pipermail/design/2006-February/004108.html

[Next action: Rationalize proposals with Bugzilla and embark on Spec-writing process.]


Design Proposals
Mimi summarized the 0.7 scheduling proposal thread. 

We continued to discuss implementation ideas for sections in 0.7 [Next action: Topic for post 0.7 planning Design Session.]

Mimi posted an interaction workflow proposal for tagging and labeling items with user-defined attributes: http://lists.osafoundation.org/pipermail/design/2006-February/004041.html

We continued to discuss Morgen's proposal for sharing work in 0.7, specifically wrt conflict notifications and resolution.

Mimi posted a proposal for a unified Activity Log: http://lists.osafoundation.org/pipermail/design/2006-February/004049.html [Next action: Needs to be properly phased and resourced.]

Mimi posted a proposal to decouple In/Outbound email account setup: http://lists.osafoundation.org/pipermail/design/2006-February/004085.html [Next action: Needs to be properly phased and resourced.]

Mimi posted proposals for the mark-up bar icons: http://lists.osafoundation.org/pipermail/design/2006-February/004077.html [Next action: Mimi to do another round of tweaks.]



Usage Scenarios
We had a design session to interview OSAF staff on how they keep track of tasks and information today: http://lists.osafoundation.org/pipermail/design/2006-February/004028.html [Next action: Mimi conducting user interviews.]

Marc Gibeault submitted a calendar use case for sharing resource availability: a high level view of what an individual contributor in a working group is working on at any given time.

Mimi forwarded a preview pane design issue from bugzilla re: what should Chandler display in the preview pane when users are in the Calendar app area? http://lists.osafoundation.org/pipermail/design/2006-February/004059.html [Next action: Awaiting feedback.]


Continued discussions
Visualizing data and Grokking information

Product research
Seth John posted a link to http://30boxes.com, a new AJAX calendar with social networking built-in.

Bear posted an article from Joel Spolsky on AJAX calendars, which spawned a discussion on flight use cases for calendar.

Announcements
Bear posted a reminder that we're moving our IRC chatrooms over to freenode.net
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design

Reply via email to