<div dir="ltr">Hi everyone!<div>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.</div><div>Currently I am familiarizing myself with Twisted and OONI and excited about kick-starting the project as soon as possible!</div>
<div>Dividing the project into sub-parts seems like a nice idea. I welcome any suggestions on how we can go about it.</div><div>Tobias: We could use git until we are good enough to push it on the Tor servers. What do you say?</div>
<div>You can find me in #tor-dev as dkathayat.</div><div><br></div><div>Cheers.</div><div>Deepak</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Feb 6, 2014 at 3:42 AM, Tobias Rang <span dir="ltr"><<a href="mailto:tobiasrang@gmail.com" target="_blank">tobiasrang@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">ons 2014-02-05 klockan 15:29 +0100 skrev Philipp Winter:<br>
<div><div class="h5">> Hi Deepak, Utsarga, Tobias, and Yiwen!<br>
><br>
> The four of you recently expressed interest in the censorship analyser<br>
> project [1]. At this point, we only have a paper which discusses what we<br>
> want from the tool [2]. There is no official code repository but Tobias<br>
> recently started experimenting with some modules [3].<br>
><br>
> It would be great if you all could join forces and split the workload. I<br>
> understand that some of you have some constraints from your respective<br>
> university. As a result, could you please reply to this email (don't<br>
> forget to CC tor-dev) and sum up what you can/want to do and if you are<br>
> under any constraints such as a time-limited class project? We can then<br>
> see if and how we can divide the project into several sub projects.<br>
><br>
> Regarding development and coordination: This mailing list is great for<br>
> high-latency, broad, conceptual, and public discussions. For low-latency<br>
> questions, the #tor-dev channel on OFTC is better. There's also #ooni for<br>
> OONI-specific questions (most of the developers are in Europe, so you might<br>
> have to wait for answers). I am not sure how familiar you are with git but<br>
> it is certainly the preferred version control system in and around Tor. So<br>
> this might be a good opportunity to learn how to use it :)<br>
><br>
> [1] <a href="https://www.torproject.org/getinvolved/volunteer.html.en#censorshipAnalyzer" target="_blank">https://www.torproject.org/getinvolved/volunteer.html.en#censorshipAnalyzer</a><br>
> [2] <a href="http://www.cs.kau.se/philwint/pdf/foci2013.pdf" target="_blank">http://www.cs.kau.se/philwint/pdf/foci2013.pdf</a><br>
> [3] <a href="https://tobiasrang.com/svn/analyser/" target="_blank">https://tobiasrang.com/svn/analyser/</a><br>
><br>
> Cheers,<br>
> Philipp<br>
<br>
</div></div>Hey everyone.<br>
<br>
I'm doing this in my spare time; not as part of anything school-related.<br>
As such, I'm not under any real time constraints.<br>
<br>
As for what I can/want to do, I do have some prior experience with<br>
Twisted, and I've familiarized myself a bit with ooni's API. If the<br>
project is to be divided into sub-projects, perhaps the logical thing<br>
would be for me to continue working on implementing tests.<br>
<br>
When it comes to version control, I agree that Git is the best option.<br>
I've been meaning to set up a Git-repo on my server and use that instead<br>
of my current svn-repo, so I guess that is one option. Although It might<br>
be better to host it on Tors servers.<br>
<br>
You can find me in #tor-dev under the nick edagar.<br>
<br>
Tobias<br>
<br>
<br>
<br>
_______________________________________________<br>
tor-dev mailing list<br>
<a href="mailto:tor-dev@lists.torproject.org">tor-dev@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev</a><br>
</blockquote></div><br></div>