[or-cvs] r22494: {weather} Update the TODO list from the Wesleyan HFOSS meeting today. (weather/trunk)

[Andrew Lewman <andrew@xxxxxxxxxxxxxx>]

Author: phobos
Date: 2010-06-08 22:57:15 +0000 (Tue, 08 Jun 2010)
New Revision: 22494

Modified:
   weather/trunk/TODO
Log:
Update the TODO list from the Wesleyan HFOSS meeting today.


Modified: weather/trunk/TODO
===================================================================
--- weather/trunk/TODO	2010-06-08 17:58:12 UTC (rev 22493)
+++ weather/trunk/TODO	2010-06-08 22:57:15 UTC (rev 22494)
@@ -4,7 +4,18 @@
 
 * add /usr/sbin/sendmail support for sending email 
 
+* zero everybody when new weather is deployed, everyone after getting
+* the Stable flag gets the initial email to re-subscribe to weather
+  * is forcing a re-subscribe smart?
+  * or shall we take the current subscribers and set them to "up/down"
+  * alerts only? (this is all they have now)
+
+* Run check process hourly
+
+* What to do about hibernating relays? Most likely ignore them.
+
 * Let's also look at server versions and alert admins when they should upgrade.
+  * pay attention to the published recommended versions 
 
 * Notice when new relays, with contact info, are up for a few days. Send
 * them a welcome email with pointers to tor-relays. If an exit node, send
@@ -15,3 +26,8 @@
 * notice when a relay with contact info goes offline for a few days,
  do we bombard them with emails about their relay being offline or send
 them a final "hey, did you know your relay has been offline since X?"
+
+* subscribers should have the ability to choose from at least two level
+* of service:  1) up/down status, 2) up with Running and Stable flags
+* but below 50KB/s bandwidth.  Are there more options to track?  The
+* options need to be actionable by the relay operator.