Provide an overview of Analysis ticket results for researchers
peer came up with a list of analysis ticket results and asks in #7241 (moved):
How are the blurbs at doc/AnalysisTicketResults (for metrics-tasks)? Were any tickets misinterpreted?
Looks great! I didn't read all descriptions in detail, but I think it's a good start for people, and if something is wrong, they can always fix it.
A few ideas:
- Should tickets be listed in descending order, from newest to oldest?
- Should we add a header saying that code for most of the tickets is available in the metrics-tasks.git repository?
- Should we link to this wiki page from http://research.torproject.org/index.html, in particular in the "We're building a repository of tools" part, and throw out the link to the tools.html page?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information