Agenda for October 3rd 2005.
- David Allen visit - review current agenda and drill down on details
- Attendees for full day: Mimi, Lisa, Katie, Mitch, Philippe
- Need to send Mitch a more specific day agenda - what we are talking about when.
- Lunch - is it just a working lunch for sm group or do we get lunch for everyone?
- What should we communicate to team about 3:00pm open session?
- ACL discussion - let Lisa drive this (high-level discussion only)
- Should we work on this in 0.7?
- Understand when Brian M needs decisions/requirements.
- What kind of requirements do we know about now?
- Stickie planning "part 2"
- Should we take another stab at reworking the stickie board?
- Dogfooding feedback
- We are getting quite a bit of feedback from various people who are dogfooding. How should we handle requests for design changes/enhancements that we get during the 0.6 timeframe.
- Scooby design
- Mimi is acting as the "temporary"? Scooby web designer. Should we be comminicating scooby design specifics/specs etc to a design list?
- Feedback on this page and status of on-going projects.
Notes
David Allen Prep
- ties in with virtuality paper
- simulate a day of extreme usability
- brainstorm of what he sees as his fundamental principles
- underlying philosophies that he uses
- this can ground the rest of the discussion
- overview of what we will do that day, agenda
- 1. DA concept brainstorm (10 - 10:30)
- 2. On the board sketch of Chandler's pieces - kinds, collections...the elements (10:30-11)
- 3. Launch into a discussion of workflows in Chandler (11 - 12:30)
- triage/ticklers
- stamping
- organization
- tasks/projects
- 4. Altitudes and how they apply to Chandler (1-2:45)
- triage
- project planning feedback loop
- clusters
- kinds
- label types
- attribute types
* 5. Get DA's feedback on what's missing from out design (3-5)
* @context
* quick entry
* automation
* alternate designs
* brainstorm about alternate designs for stuff that's missing
- evangelism of DA concepts and what we are doing in chandler
- proof of concept in collaborative design exercise - experiment with this
- start with a summary of what we did the rest of the day and what we learned.
Chi paper update
- use the structure of the da presentation for a 6 page paper for chi -> csg presentation
- then work on a more research paper
- Chandler elevator pitch (2 pages - aimed at users and passing interest)
- Chandler in a nutshell - explains virtuality and chandler's goals to an audience like CSG (6 pages)
- research - lengthy to designers - deep into conceptual ideas (long paper)
Dogfooding feedback
- lots of input based on dogfooding activities
- how are we going to deal with this
- people who are developers here
- people who are outside ie: creative commons etc
- encourage people to send design notes and feedback to design list
- 2 levels
- what blocks you being able to use 0.6
- what would make the calendar better
- have a weekly dogfood feedback review
- people submit this via the design list
- we go through this and talk about the appropriate next steps
- actions from the meeting could be assigning bugs, putting things on the design list
- send an email talking about our process for reviewing design feedback, usage notes etc
- get people to put design feedback/report in the list and we will have a dogfooding feedback session to discuss this...
ACL Discussion
- group of people - first collection that doesn't fit into our current model -> other types of collections in the sidebar
- contacts or directories
- should have this design ready because it's a fundamental missing piece
- low rent solution in the short-term - like gmail
- directory or email addresses and sharing account info
- clarify with mitch
- what are the requirements
- share my calendar - you get access to my free-busy
- can we make free busy publicly available to anybody with an account on the server
- do we need to use a ticket where there is an exchange of information
- what are the target use cases - org vs adhoc people
- dynamic groups - list changes but the group is available
- need to do a matrix of the different users/scenarios and what the options are
- see what the requirements are at mitch's perspective
- who the users' are and what the possible solutions are
- are there development risks for pushing back on acls until 0.8, 0.9?
- need to have the content model for a person by 0.8.
- sharing/people cluster and move free-busy to this rather than under the calendar track
- next steps: mimi and sheila will put together alternative proposals for free-busy