Notes

Setting the stage and agenda

• Ground rules for brainstorming
• Motivation and next steps
• Brainstorm topics
  • What's on your mind
  • stage
  • date
  • markup
  • groupings
  • level of us
• Were we are....linear map
  • Research
  • Framework
    • cross kind views
    • central collection bin
    • adding semantics
    • lifecycle
    • common pim tasks brainstorm
  • Specific Designs
  • between framework and specific designs stages
    • tight feedback loops based on real usage

Brainstorming

• Task: write down a list of 10 things on your mind
• Task: jot down last 5 emails in your inbox

• examine the different stages and what tasks fit into each stage...

• Things to delete
• Katie: Lunch asquew grill
• Morgen: DVD Sale amazon
• Pieter: apple enews
• Pieter: IETF CALDAV digest

• Things to do in 2 min
• Lisa: server mtg agenda
• Morgen: jury duty form
• Ted: moderate issue on message list
• Jeffrey: print out email
• Bryan: bring 5 emails to meeting
• Pieter: sheila wants link

• Things to research
• Jed: big truck to move
• Alec: find a dumpster
• Bryan: employee donation match (by x-mas)
• Ted: filter 10 days worth of paper mail
• Morgen: research a bug
• Jeffrey: benefits, address thank you note

• Black holes
• Holiday shopping
• Lisa: 2:30pm pick up in SJ
• Lisa: ACL
• Katie: 20% self assignment (january)
• AlecF^?: remodel kitchen (sometime in the next 3 months)
• Jeffrey: 2006 budget
• Bryan/David: HC choices for next year

• Waiting for
• Ted: weekend plans
• Morgen: take son to library (2:05pm)
• Ted: apache con t-shirts
• Lisa: BCM job description and podcast
• Katie: Run later (8:00pm)
• Pieter: contrib cleanup and review landing page (Monday @11am)

• Don't have time
• Lisa webdav draft vision
• Personal accounting (April 6 2006)
• Fix cordless mouse
• Christmas cards - (by new year's)
• Ted : healthplan (tonight after dinner)
• Blogs, posts
• Ubuntu pack (Friday 6:00pm)
• Jeffrey: swiss people (anytime between now and wed)
• David : wx guildelines (by the end of the year)
• Katie: feedback on lisa's draft

• life-cycle of tasks evolve over time, we keep things around over time but don't have a sense of how much progress has been made
• what time frames do we typically associate with tasks like this - do a quick pass on items above

• sum up and order the stages in a linear time line...from top to bottom
• TOP
  • no action
  • 2 minute - gtd -> show do them
  • things you can do now
  • waiting for someone
  • waiting for time
  • waiting for context
  • research
  • no time now
  • black box
• BOTTON

• 2 axis - substance of the task vs can-do-ness (must do)
  • there is some grey area in this...don't know how long it will take
  • degrations of can-do-ness
    • ie: today, tonight, this week
    • different people will have diff granularities on how they want to define this

• can-do-ness is trying to answer...what should I do now?
  • this is what a pim is trying to address

• Done, Now, Later triage came from helping people decide what do to now
• a big list of things can fall into a Done, Now, Later framework
• threshold between now and later is harder
  • why are you writing this down - accessible (now), getting it out of your head (later)

• think about task & projects and the transition
  • part of the iterative process is to tease out the tasks that are part of a larger project

• Types of times - categories
  • starting from - not until (and/or) -> depends on other things to happen
  • specific - calendar dates, opportunities
  • deadlines
  • time ranges
  • time of day
  • part of week
  • first thing
  • now - asap
  • proscrastinate
• we will be taking a discussion of times to the mailing list
• these can translate into date/time improvments for 0.7(?) and possible a proposal for ticklers

• think about levels of use - in terms of adding semantics
  • bucketizing the different ways of marking an item and how easily we can prioritize them

Next Steps

• take a discussion to the mailing list - will start now but probably wait until after Jan 1
  • how to mark up items
  • grouping semantics into high-level
  • bucketizing semantics into levels of use
• schedule a follow-up discussion after the new year