[Telepathy-commits] [telepathy-spec/master] Add a list of open issues

[Simon McVittie]

20080625164806-53eee-d0c50f8ee519a477655ba04a963e0f9a363437f8.gz
---
 doc/open-issues.txt |   58 +++++++++++++++++++++++++++++++++++++++++++++++++++
 1 files changed, 58 insertions(+), 0 deletions(-)
 create mode 100644 doc/open-issues.txt

diff --git a/doc/open-issues.txt b/doc/open-issues.txt
new file mode 100644
index 0000000..f761df3
--- /dev/null
+++ b/doc/open-issues.txt
@@ -0,0 +1,58 @@
+Open issues in this branch
+==========================
+
+Major
+-----
+
+Does it ever make sense to share channels that are not contact lists?
+
+req1_: how do we tell the CM about our new vs existing requirements?
+
+req3_: can we safely disallow creating new channels with the wrong bundle ID?
+
+req26b_: mid-air collision where local and remote try to reopen the same
+conversation
+
+req5_: is this proposed implementation OK?
+
+req7_: how do chatroom threads work?
+
+dis2_: what happens when a Text channel-handler crashes?
+
+.. _dis2: dispatch.html#dis2
+
+dis5d_: how do we know a suppress-handler request should go to a particular
+client?
+
+.. _dis5d: dispatch.html#dis5d
+
+req22_, dis20_: increased importance of getting FTs handled by
+collaborative app if they are part of the collab protocol
+
+.. _dis20: dispatch.html#dis20
+.. _req22: request.html#req22
+
+dis26_: how do approvers interact with non-incoming channels? Particularly,
+unknown directionality => pain
+
+.. _dis26: dispatch.html#dis26
+
+req36_: cancelling an outgoing call (just needs writing)
+
+.. _req36: request.html#req36
+
+Minor/corner-case
+-----------------
+
+req29_, req30_: two contacts call each other simultaneously
+
+dis12_: how do we know when all groups have arrived?
+
+.. _dis12: dispatch.html#dis12
+
+dis14_: forcibly joining chatrooms, psychic mode
+
+.. _dis14: dispatch.html#dis14
+
+..
+  vim:set sw=4 sts=4 et:
-- 
1.5.6.5