Hi all. Work and life is conspiring to keep me busier than usual. What time was left this November mostly went toward non-development activities. I miss coding...
====================================================================== Tor Ecosystem Presentation ======================================================================
On 11/18 I gave a presentation at Seattle's TA3M overviewing projects in the Tor ecosystem, with an eye toward getting more developers involved...
Presentation: https://archive.org/download/t3am-seattle-nov2013/damian_johnson.mp4 Slides: https://www.atagar.com/transfer/tor_ecosystem/
Preparing for this gobbled up a surprising amount of time (I don't do much public speaking), but I'm really happy with how it turned out. I'll likely give this presentation again at other local venues, such as LinuxFest Northwest in the spring.
====================================================================== Email List Management ======================================================================
Much of this last month went toward managing our lists and leading a discussion about what we'd like to do with our non-public lists. Work on this is ongoing, but at the very least we'll finally get a public, documented process for adding folks...
https://trac.torproject.org/projects/tor/wiki/doc/internalLists
I also sunk several hours into a frustrating GMail issue where it bounces Mailman's moderator queue as spam...
https://productforums.google.com/forum/#!category-topic/gmail/ask-a-how-to-q...
At one point this seems to have been responsible for unsubscribing everyone using GMail from tor-assistants@. I've changed Mailman's configuration so this hopefully won't happen again, but I'm out of ideas for the GMail bounces.
======================================================================
Other news this month includes...
* Fixed an important Stem ImportError under Windows. This resulted in a hotfix release of Stem (version 1.1.1). [1] * Added Stem support for the new event types from proposal 218. [2] * Code reviewed Philipp's ExitMap project. [3] * Read over tbbscraper and added to Stem's examples page. [4] * Helped provide stats for the impact of changing tor's default exit policy. [5]
Cheers! -Damian
[1] https://trac.torproject.org/10072 [2] https://gitweb.torproject.org/stem.git/commitdiff/e8c916b?hp=ae6d978 [3] https://lists.torproject.org/pipermail/tor-dev/2013-December/005889.html [4] https://github.com/zackw/tbbscraper/blob/master/controller/controller.py [5] https://trac.torproject.org/10067#comment:6
On 12/8/13 9:12 PM, Damian Johnson wrote:
- Helped provide stats for the impact of changing tor's default exit policy. [5]
Hi Damian,
do you want to add the code produced for this analysis to metrics-tasks.git? This could happen now or when all analysis for this ticket is done. I'm aware that it may take a bit of time to clean up code (though I haven't looked at your code). But the advantage is that people who're planning to do a similar analysis can `git grep foo` metrics-tasks.git and find your code. If the code is only on a Trac ticket, it's very likely lost once the ticket is closed.
https://gitweb.torproject.org/metrics-tasks.git/blob/HEAD:/README
All the best, Karsten
[5] https://trac.torproject.org/10067#comment:6 _______________________________________________ tor-reports mailing list tor-reports@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-reports
Hi Damian,
do you want to add the code produced for this analysis to metrics-tasks.git? This could happen now or when all analysis for this ticket is done. I'm aware that it may take a bit of time to clean up code (though I haven't looked at your code). But the advantage is that people who're planning to do a similar analysis can `git grep foo` metrics-tasks.git and find your code. If the code is only on a Trac ticket, it's very likely lost once the ticket is closed.
https://gitweb.torproject.org/metrics-tasks.git/blob/HEAD:/README
You're certainly welcome to. My conclusion from writing it was actually that Stem needs some helper methods to better handle the prefixed 'private' exit policy...
https://trac.torproject.org/projects/tor/ticket/10107
If we had that then the script would have been pretty trivial.
Cheers! -Damian
On 12/9/13 5:45 PM, Damian Johnson wrote:
Hi Damian,
do you want to add the code produced for this analysis to metrics-tasks.git? This could happen now or when all analysis for this ticket is done. I'm aware that it may take a bit of time to clean up code (though I haven't looked at your code). But the advantage is that people who're planning to do a similar analysis can `git grep foo` metrics-tasks.git and find your code. If the code is only on a Trac ticket, it's very likely lost once the ticket is closed.
https://gitweb.torproject.org/metrics-tasks.git/blob/HEAD:/README
You're certainly welcome to. My conclusion from writing it was actually that Stem needs some helper methods to better handle the prefixed 'private' exit policy...
https://trac.torproject.org/projects/tor/ticket/10107
If we had that then the script would have been pretty trivial.
Well, what do you suggest? Add to metrics-tasks or not?
If you think we should add something, would you mind sending me a metrics-tasks patch, or a link to your metrics-tasks branch? I wouldn't know what files to add and how to describe it accurately in a short README file. Thanks!
All the best, Karsten
-
Damian Johnson -
Karsten Loesing