[gnome-talos] README: Flesh out a bit

[Colin Walters <walters src gnome org>]

commit c4eee8798466bb07d5f3f1bde8de7ea050b83d49
Author: Colin Walters <walters verbum org>
Date:   Thu Sep 29 13:28:53 2011 -0400

    README: Flesh out a bit

 README |   41 ++++++++++++++++++++++++++++++++++++++++-
 1 files changed, 40 insertions(+), 1 deletions(-)
---
diff --git a/README b/README
index 31ca0f5..fd3ffc6 100644
--- a/README
+++ b/README
@@ -1,2 +1,41 @@
-A set of performance tests.
+A set of performance tests; the name is inspired by Mozilla's Talos:
+
+https://wiki.mozilla.org/StandaloneTalos
+
+There is no code shared though.
+
+gnome-talos has as a primary goal repeatable performance tracking.
+It has two parts:
+
+1) A data-gathering process, where "data" includes memory/CPU/GPU use,
+   and eventually other detailed stats like number of open X windows,
+   monitor configuration, etc.  Currently outputs JSON.
+2) A HTML-based visualization of the data
+
+Currently there are no scripts to create specific reproducible
+scenarios, e.g. Epiphany open to a local cached version of Wikipedia,
+opening and closing windows, etc.  Ideally we have a script which
+generates a few real-world usage scenarios.
+
+TODO:
+
+- CPU monitoring
+- Add a way for all components to inject events into the daemon.  This would
+  take the place of gnome-shell's src/shell-perf-log.h basically.
+
+OPEN QUESTIONS:
+- Should gnome-talos also take some of the role of Mozilla' Telemetry?
+  We could ask people to run it on their own machines.  One thing I am
+  trying hard to do though is keep the data gathered as anonymous as
+  possible.  For example, we generate a SHA256 hash of the DBus
+  machine UUID (which is itself anonymous).  We do not gather the
+  arguments to process binaries, and don't expose the username (and we
+  probably shouldn't expose the pid/uid either).
+
+  This would need a server to accept data.
+
+
+
+
+