Hi everyone,
I'm working on the censorship analyzer for a semester long independent research project. Because of this, I need to finish my work by May 6. Philipp has told me this isn't a terribly large amount of time, so it's great that there's a lot of us working on it. Does anyone have any ideas on how we can split up the work?
Thanks, Utsarga
On Fri, Feb 7, 2014 at 1:45 PM, Abhiram Chintangal < abhiram.chintangal@gmail.com> wrote:
On Thu, Feb 6, 2014 at 8:57 PM, Deepak Kathayat deepak.mk17@gmail.com wrote:
Hi everyone! Like Tobias, I am willing to devote my spare time to the tool and see through its completion and further maintenance. I am not really bounded
by
any time constraints. Currently I am familiarizing myself with Twisted and OONI and excited
about
kick-starting the project as soon as possible! Dividing the project into sub-parts seems like a nice idea. I welcome any suggestions on how we can go about it. Tobias: We could use git until we are good enough to push it on the Tor servers. What do you say? You can find me in #tor-dev as dkathayat.
Cheers. Deepak
On Thu, Feb 6, 2014 at 3:42 AM, Tobias Rang tobiasrang@gmail.com
wrote:
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.
Tobias
tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Hello Guys,
Until recently, I wasn't aware of the censorship analysis project that is being discussed here. I find it interesting and I would like to help out with the development during my free time.
Cheers!
-- Abhiram Chintangal _______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev