MFoster / breeze

Django deployment for project codenamed breeze. For the group of make shit happathon winners now and forever.
BSD 3-Clause "New" or "Revised" License
1 stars 0 forks source link

Task Types #4

Open marshallworks opened 11 years ago

marshallworks commented 11 years ago

One of the ways we can save people time in entering tasks is to guess at the task type. Eventually it would be great if this was more flexible, but for now a basic list of types, and words that are associated with those types will be a great place to start.

Basic Types I'm envisioning: social create resolve obtain plan improve maintain research decide organize

Sure I'm missing some, but trying to keep these generic, then we can start making some more specific ones.

MFoster commented 11 years ago

communicate develop

marshallworks commented 11 years ago

Think we have a pretty good list here, but let me know if anyone thinks of anything else, otherwise, we can start brainstorming what words will be associated with what type. As in: email => communicate

hfionte commented 11 years ago

How will the words and types link? Will the app search through the text of the task name and pull out anything that matches? For example "Dinner with Emily" maps to a category called "social" because we have paired the word "dinner" with "social"...? (also, it might pair with "family" if the app recognizes that Emily is in my family.) Let me know if I'm going in the wrong direction here. I think if what I described above is what you had in mind, then we should brainstorm a list of possible tasks, and pick out keywords from those to map to categories.

I think we need beta-testers who we can steal task from. It seems like a huge task to brainstorm all common types of tasks. To-do: Read everyone's mind. Categorize under "magic".

marshallworks commented 11 years ago

MAGIC it is! LOL

Yes, your assumptions are correct. Names for now will probably be ignored, eventually that should become part of the "Context Cloud" that can include anything from available/current device, to location, to people, to amount of time, pre-requisites, etc.

I think for this version we can stick with this pretty generic system that tries to apply general types on super simple word to type matching. This can be changed by the user, and eventually I would like a crowed sourced super smart and customizable list... making the magic in the long run.

I'll have a few beta testers lined up, and as we progress we can just and anyone who's interested!