[tor-dev] Coordination of censorship analysis tool

Tobias Rang tobiasrang at gmail.com
Wed Feb 5 19:42:52 UTC 2014

ons 2014-02-05 klockan 15:29 +0100 skrev Philipp Winter:
> Hi Deepak, Utsarga, Tobias, and Yiwen!
> The four of you recently expressed interest in the censorship analyser
> project [1].  At this point, we only have a paper which discusses what we
> want from the tool [2].  There is no official code repository but Tobias
> recently started experimenting with some modules [3].
> It would be great if you all could join forces and split the workload.  I
> understand that some of you have some constraints from your respective
> university.  As a result, could you please reply to this email (don't
> forget to CC tor-dev) and sum up what you can/want to do and if you are
> under any constraints such as a time-limited class project?  We can then
> see if and how we can divide the project into several sub projects.
> Regarding development and coordination: This mailing list is great for
> high-latency, broad, conceptual, and public discussions.  For low-latency
> questions, the #tor-dev channel on OFTC is better.  There's also #ooni for
> OONI-specific questions (most of the developers are in Europe, so you might
> have to wait for answers).  I am not sure how familiar you are with git but
> it is certainly the preferred version control system in and around Tor.  So
> this might be a good opportunity to learn how to use it :)
> [1] https://www.torproject.org/getinvolved/volunteer.html.en#censorshipAnalyzer
> [2] http://www.cs.kau.se/philwint/pdf/foci2013.pdf
> [3] https://tobiasrang.com/svn/analyser/
> Cheers,
> Philipp

Hey everyone.

I'm doing this in my spare time; not as part of anything school-related.
As such, I'm not under any real time constraints. 

As for what I can/want to do, I do have some prior experience with
Twisted, and I've familiarized myself a bit with ooni's API. If the
project is to be divided into sub-projects, perhaps the logical thing
would be for me to continue working on implementing tests. 

When it comes to version control, I agree that Git is the best option.
I've been meaning to set up a Git-repo on my server and use that instead
of my current svn-repo, so I guess that is one option. Although It might
be better to host it on Tors servers.

You can find me in #tor-dev under the nick edagar.


More information about the tor-dev mailing list