summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorLuiz Augusto von Dentz <luiz.dentz-von@nokia.com>2011-03-18 13:52:46 -0300
committerJohan Hedberg <johan.hedberg@nokia.com>2011-03-20 01:19:47 +0200
commit038e14194841244f8706980869510bb70f651851 (patch)
treea6b7efec9e172875562fe540da4b21e7f1b8c2a6 /TODO
parentb9566de1ecd562c7bca6546a0fcb1082e210c4a5 (diff)
downloadobexd-038e14194841244f8706980869510bb70f651851.tar.gz
Add action commands support to TODO
Diffstat (limited to 'TODO')
-rw-r--r--TODO26
1 files changed, 26 insertions, 0 deletions
diff --git a/TODO b/TODO
new file mode 100644
index 0000000..d2bbd1a
--- /dev/null
+++ b/TODO
@@ -0,0 +1,26 @@
+Background
+==========
+
+- Priority scale: High, Medium and Low
+
+- Complexity scale: C1, C2, C4 and C8. The complexity scale is exponential,
+ with complexity 1 being the lowest complexity. Complexity is a function
+ of both task 'complexity' and task 'scope'.
+
+ The general rule of thumb is that a complexity 1 task should take 1-2 weeks
+ for a person very familiar with BlueZ codebase. Higher complexity tasks
+ require more time and have higher uncertainty.
+
+ Higher complexity tasks should be refined into several lower complexity tasks
+ once the task is better understood.
+
+General
+==========
+
+- OBEX Actions are used to perform actions not primarily defined as OBEX
+ commands. This actions include, for example, moving, copying and setting the
+ permissions of objects. OBEX actions would be very useful when implementing
+ virtual filesystems over OBEX.
+
+ Priority: Medium
+ Complexity: C2