[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] r22514: {arm} Revised roadmap items. (arm/trunk)
Author: atagar
Date: 2010-06-16 16:15:01 +0000 (Wed, 16 Jun 2010)
New Revision: 22514
Modified:
arm/trunk/TODO
Log:
Revised roadmap items.
Modified: arm/trunk/TODO
===================================================================
--- arm/trunk/TODO 2010-06-16 01:29:45 UTC (rev 22513)
+++ arm/trunk/TODO 2010-06-16 16:15:01 UTC (rev 22514)
@@ -1,15 +1,15 @@
TODO
- Roadmap for next release (1.3.6)
- * refactor panels
+ [ ] refactor panels
Currently the interface is a bit of a rat's nest (especially the
controller). The goal is to use better modularization to both simplify
the codebase and make it possible to use smarter caching to improve
performance (far too much is done in the ui logic). This work is in
progress - /init and /util are done and /interface is in progress. Known
bugs are being fixed while refactoring.
- * <done> header panel
- * graph panel
+ [X] header panel
+ [ ] graph panel
- revise effective bandwidth
Take into account 'MaxAdvertisedBandwidth', as per:
http://paste.debian.net/76254/
@@ -22,19 +22,19 @@
- How frequently are the bandwidth values in the state file
updated?
- Is it every second, matching the last BW events?
- * log panel
+ [ ] log panel
- option to clear log
- allow home/end keys to jump to start/end
also do this for the conn panel and conf panel (request by dun)
- make log parsing script stand alone, with syntax hilighting, regex,
sorting, etc
- * conf panel
+ [ ] conf panel
- move torrc validation into util
- condense tor/arm log listing types if they're the same
Ie, make default "TOR/ARM NOTICE - ERR"
- fetch text via getinfo rather than reading directly?
conn.get_info("config-text")
- * conn panel (for version 1.3.7)
+ [-] conn panel (for version 1.3.7)
- check family connections to see if they're alive (VERSION cell
handshake?)
- fallback when pid or connection querying via pid is unavailable
@@ -44,26 +44,27 @@
- connection uptime to associate inbound/outbound connections?
- Identify controller connections (if it's arm, vidalia, etc) with
special detail page for them
- * controller (for version 1.3.7)
- * provide performance ARM-DEBUG events
+ [-] controller (for version 1.3.7)
+ [ ] provide performance ARM-DEBUG events
Help with diagnosing performance bottlenecks. This is pending the
codebase revisions to figure out the low hanging fruit for caching.
- * <done> user customizable armrc
- * tor util
- * <done> wrapper for accessing torctl
- * allow arm to resume after restarting tor (attaching to a new torctl
- instance)
- * setup scripts for arm
- * setup scrpt to add to /usr/bin/arm (requested by ioerror)
- * provide Debian repository
- Look into debian packaging, note system call dependencies, and mail
- submit@xxxxxxxxxxxxxxx with subject "RFP: arm" and starting with a line
- "Package: wnpp". Also add to 'deb.torprojec.org'. (requested by helmut)
- * look into CAPs to get around permission issues for connection listing
- sudo wrapper for arm to help arm run as the same user as tor?
- irc suggestions:
- - man capabilities
- - http://www.linuxjournal.com/article/5737
+ [X] user customizable armrc
+ [ ] tor util
+ [X] wrapper for accessing torctl
+ [ ] allow arm to resume after restarting tor (attaching to a new torctl
+ instance)
+ [ ] setup scripts for arm
+ [ ] setup scrpt to add to /usr/bin/arm (requested by ioerror)
+ [ ] look into CAPs to get around permission issues for connection
+ listing sudo wrapper for arm to help arm run as the same user as
+ tor? Irc suggestions:
+ - man capabilities
+ - http://www.linuxjournal.com/article/5737
+ [-] provide Debian repository (for version 1.4.0)
+ Look into debian packaging, note system call dependencies, and mail
+ submit@xxxxxxxxxxxxxxx with subject "RFP: arm" and starting with a
+ line "Package: wnpp". Also add to 'deb.torprojec.org'. (requested
+ by helmut)
* release prep
* check performance of this version vs last version (general screen refresh
times)
@@ -75,7 +76,7 @@
* not catching events unexpected by arm
Future tor and TorCtl revisions could provide new events - these should
be given the "UNKNOWN" type.
- * regex fails for multiline log entries
+ * regex fails for multiline log entries (works for two lines, but not more)
* test that torctl events are being caught (not spotting them...)
* torctl events have their own configurable runlevels (provide options for
this)
@@ -117,6 +118,7 @@
http://www.codexon.com/posts/clearing-passwords-in-memory-with-python
* try/catch check when starting for curses support?
* excaping function for uiTools' formatted strings
+ * tor-weather like functionality (email notices)
* provide bridge / client country statistics
- Include bridge related data via GETINFO option (feature request by
waltman).