[Tcs] [VOTE] Remove UI requirements/recommendations

zero-one zero-one at tox.chat
Sat Dec 5 18:02:36 PST 2015

This is directly from subliun's pull request, discussed here:
https://github.com/Tox/Tox-Client-Standard/pull/21 . I've made no
changes, as I think the PR works fine as-is. It removes UI requirements
that have nothing to do with interoperability or security, and makes a
few small style corrections.

Vote to merge into master. All in favor, say "aye", all opposed say "nay".


diff --git a/README.md b/README.md
index 4c9fed6..859b88a 100644
--- a/README.md
+++ b/README.md
@@ -9,11 +9,6 @@ Introduction
   minimum, comply with every ![](badge/req.png) point in this document (except
   where otherwise stated).  For this reason, things that are ![](badge/req.png)
   should not be needlessly specific.
-    - For example, this is a **bad** ![](badge/req.png) point: *A Tox client
-      will show a message timestamp in the format HH:MM:SS, to the left of each
-      message, with 10 pixels of whitespace between.*
-    - A better point would be: *A Tox client will allow users to see when a
-      message was received.*
 - Sometimes, it is not immediately obvious why certain points exist in this
   document. For this purpose, there is a Rationale section, where explanations
diff --git a/SUMMARY.md b/SUMMARY.md
index ca7cb35..2f43aca 100644
--- a/SUMMARY.md
+++ b/SUMMARY.md
@@ -4,7 +4,6 @@
 * [General Requirements](general_requirements/general_requirements.md)
 * [User Identification]()
     * [Tox ID](user_identification/tox_id.md)
-    * [User Status](user_identification/user_status.md)
     * [Avatar](user_identification/avatar.md)
 * [Communication]()
     * [Friend Requests](communication/friend_requests.md)
diff --git a/rationale/rationale.md b/rationale/rationale.md
index 6f78529..f127b56 100644
--- a/rationale/rationale.md
+++ b/rationale/rationale.md
@@ -22,9 +22,6 @@ response to questions or confusion within the Tox development community.
   functionality made available via the Tox API) without being forced to use
   third party services.
-- **2.2.2** This is to account for colour blindness; the recommended user
-  status colours are not colour-blind friendly.
 - **2.3.3** PNG images are currently the only image type supported by the Tox
   core library.
diff --git a/user_identification/tox_id.md b/user_identification/tox_id.md
index 12627fe..31e8c1c 100644
--- a/user_identification/tox_id.md
+++ b/user_identification/tox_id.md
@@ -2,9 +2,7 @@ Tox ID
 - **2.1.1** ![](/badge/req.png) The Tox ID must be represented as a 76-character
-  hexadecimal string. Alternative forms are acceptable, but you must
+  hexadecimal string. Alternative forms are acceptable, but the client must
   expose this standard form somewhere.
-- **2.1.2** ![](/badge/rec.png) A QR encoded Tox URI should be available to the user.
-- **2.1.3** ![](/badge/req.png) You must clearly expose functionality to allow the user to change their nospam identifier
+- **2.1.2** ![](/badge/req.png) A client must clearly expose functionality to allow the user to change their nospam identifier
diff --git a/user_identification/user_status.md b/user_identification/user_status.md
deleted file mode 100644
index 95b098c..0000000
--- a/user_identification/user_status.md
+++ /dev/null
@@ -1,10 +0,0 @@
-User Status
-- **2.2.1** ![](/badge/rec.png) A Tox user status symbol should be colour-coded as follows:
-  - Online/None   : Green
-  - Away          : Yellow
-  - Busy          : Red
-- **2.2.2** ![](/badge/rec.png) User status symbol shapes should be distinct from one
-  another.

More information about the Tcs mailing list