ooni-dev July 2013

ooni-dev@lists.torproject.org

8 participants
9 discussions

Start a nNew thread

Meeting today?
by Meredith Whittaker 31 Jul '13

31 Jul '13

IRC is quiet... -- Meredith Whittaker Program Manager, Google Research Google NYC

2 3

Connaught Summer Institute on Monitoring Internet Openness and Rights
by Meredith Whittaker 15 Jul '13

15 Jul '13

Hi all, For those of you in the meeting earlier, I mentioned this event<http://citizenlab.org/summerinstitute/program.html>, which I'll be attending next week. It's well within the OONI remit, and if there's anything particularly interesting to anyone, happy to report back. Cheers, Meredith -- Meredith Whittaker Program Manager, Google Research Google NYC

1 0

Team Meeting: 2013-07-15 0900 Pacific
by Tom Lowenthal 15 Jul '13

15 Jul '13

Hello beautiful shiny (mostly) human people. You know what's coming: it's a meeting agenda. But wait: there's more! This week, we have the lovely beauty of a Milestone; let's talk about that! 0900 Convene: how are folks feeling, how's it going? 0905 Report: core team, what did you do this week, and what are you planning? 0920 Assess: how close are we to being fully specified; what does each of us have to do to get there? 0935 Plan: how do we go from fully specified to feature complete? 0955 Prospective: What Ooni-stuff will be done this week? 1010 Adjourn See y'all Monday!

4 3

detailed meeting notes 2013-07-08
by Nathan Wilcox 08 Jul '13

08 Jul '13

Arturo: We're working on specification tasks. We completed backend spec; including specifying collector policy for both inputs and net-tests. Stephen reviewed the spec: https://github.com/TheTorProject/ooni-spec/blob/master/oonib.md Two points of discussion: S 2.5 how we publish reports - Ooni suggested scp, but MLab may be different. We should leave that out of the backend spec, because it depends on the backend infrastructure. How will the test_helper learn effective probe IP address? Stephen and Arturo realize they misunderstood the issue, and this should already be handled by ooni (see: https://github.com/TheTorProject/ooni-probe/issues/90). Daira discussed alternatives with Arturo. Why is the collector exposed by https and tor hidden service is answered in the spec. Added a feature which exposes inputs / decks from the backend. Added a "bouncer" in the spec which aids in discovery for test helpers and collectors. This is similar to mlab-ns. Some aspects might be implemented by mlab-ns. There's a need for ooni to provide requirements for mlab-ns. Stephen will review that spec and send questions about "bouncer" to understand how similar it is to mlab-ns. We improved some charts: backend dataflow diagram. Stephen will do something similar for MLab. See: https://github.com/TheTorProject/ooni-spec/blob/master/diagrams/ooni-backen… Nathan asks: Should the ooni-spec and ooni-probe wiki be merged? Arturo suggests we (Arturo & Aaron) should consolidate ooni-spec, should migrate to the wiki. Nathan gives a Threat Model presentation. That's me! -so I didn't take notes on that section. It was an overview of this wiki: https://github.com/TheTorProject/ooni-probe/wiki/Threat-Model As is apparently now our custom: "Toodles!" -- Nathan Wilcox Least Authoritarian GPG id: CBA48BDD GPG fingerprint: 9309 EB72 87D4 192F 0D7E 0F16 1191 AF31 CBA4 8BDD

2 1

Team Meeting: 2003-07-08 1800 CET
by Arturo Filastò 08 Jul '13

08 Jul '13

Since no meeting schedule was posted for this weeks meeting I am going to propose the following schedule for this weeks meeting. It's mainly a copy-pasta job from the excellent schedule Tom has been proposing us every week. The main addition we have this week is a special presentation by the Least Authority team on the OONI threat model. This will make the meeting last 1 hour more than usual. Here we go: 18:00 Convene: how are folks feeling, how's it going? 18:05 Report: core team, what did you do this week, and what are you planning? 18:20 Assess: how close are we to our nearest deliverable, what does each of us have to do to get there? 18:35 Dependencies: Is there anything that you {will|do} need from someone else? 18:55 Prospective: What Ooni-stuff will be done this week? 19:10 The Least Authority Team will do a presentation on the OONI threat model they have been working on. 20:10 Adjourn If you have comments, suggestions and such feel free to reply. ~ Art.

3 3

Collector Policy [reply requested]
by Tom Lowenthal 08 Jul '13

08 Jul '13

On Mon, Jul 1, 2013 at 6:40 PM, Meredith Whittaker <meredithrachel(a)google.com> wrote: > The collector policy implementation is a blocker for deployment on M-Lab. On 1 July 2013 13:08, Aaron <aagbsn(a)torproject.org> wrote: > Tom, can we agree that this is an issue we must address for release 1.0 and factor this into our release agenda? I'd like to see a specification for this feature as soon as possible, since I suspect that there are number of guarantees which it would be prohibitively difficult to have a feature like this make. Aaron, Arturo: who's the right person to take this on, and can it be done in time with the rest of the specifications? -Tom

2 1

Threat Model overview
by Nathan Wilcox 08 Jul '13

08 Jul '13

Greetings Oonitarians, We Least Authoritarians have been fleshing out the Threat Model a bit, and I suggested previously that we could give an presentation next week. There are two knobs and a switch we can collectively turn and flip, according to our groupmind's desires: Presentation Depth Knob - If we give a detailed presentation, it might involve a fair amount of time, perhaps 45 minutes, or perhaps 90 minutes. We could also give a more brief (say 15-20 minutes) overview of the structure and process, and then individuals can examine the details on their own. The Meeting Switch: Weekly/Separate - Flipping this one way will result in a presentation being delivered at a Weekly Meeting. Flipping it the other will result in me or Tom arranging a separate meeting. Consider how this interacts with the knob above. Early/Often or Later/Polished Knob - There are still currently incomplete areas, so we could either present early (such as on Monday's weekly meeting) with less completeness, or later in the week with more completeness. Clever consumers can crack open the case and completely bypass the knobs and switches to hack something else together, such as splitting our presentation into separate bite-sized chunks delivered in the weekly meeting. My personal preference is to turn presentation depth up, turn towards Later (towards the end of the week), and to flip the "Meeting" switch to "outside of the weekly meeting". We are flexible though and can roll any which way. -- Nathan Wilcox Least Authoritarian GPG id: CBA48BDD GPG fingerprint: 9309 EB72 87D4 192F 0D7E 0F16 1191 AF31 CBA4 8BDD

2 2

Notes from meeting today
by Aaron 02 Jul '13

02 Jul '13

Present in call: Tom, Aaron, Arturo, Johannes What we have worked on this week: Arturo worked on twisted socks client support and NetTest specification Aaron worked on specification and implementation of the test deck and test input api for ooni-probe and ooni-backend (117, 115, 109). Are there any items blocking? No blocking items were raised. Are we on track to make the first milestone (Fully Specified) Aaron and Arturo say yes. What are we working on this week: Aaron and Arturo will be working on issues 115, 117, 91, and 90 this week. Issues that we discussed on the call: Tom states that collector policy implementation (issue 109) is not part of the feature complete milestone and instead should be in future versions. Aaron and Arturo believe that collector policy was a blocking issue for MLAB deployment as discussed at the Berlin meeting. We would like to request feedback from MLAB on this point. Arturo asked for clarification on issue 107 (do we need to specify each unit test?) The resolution was that the unit test spec should be replaced with a code coverage report as per Nathan's suggestion. Johannes suggests coveralls.io which writes a code coverage report into the README.md. We discussed alternatives to using Google Hangout for our weekly meetings Johannes suggests: Mumble. Tom suggests: phones. Can we expose a phone number for call ins into the Google chat? No, but it can dial out worldwide (US and Canada free). Aaron Tom and Arturo agree that video chat is nice. Mumble now has a voice-activation feature and Johannes has a mumble server that we can use. Google Hangout has some issues on Johannes computer (system load > 4). We agree that the four of us cannot reach a consensus without others present and will take this discussion to the mailing list. See you all next week! --Aaron

4 4

Team Meeting: 2003-07-01 0900 PDT
by Tom Lowenthal 01 Jul '13

01 Jul '13

Greetings people of Earth! On Monday, in keeping with the ancient customs of our ancestors, we will meet to pay reverence to the Dreaded Ooni. Sacrifices are welcome. Here's my proposal for an agenda. It may look familiar. If you wish to wrangle it, please get in touch by email before 1700 PDT on 2013-06-28. If you wish to get in touch after that time, or wish to propose an alternate time for the meeting, please do not rely on email, but telephone me instead. 0900 Convene: how are folks feeling, how's it going? 0905 Report: core team, what did you do this week, and what are you planning? 0920 Assess: how close are we to our nearest deliverable, what does each of us have to do to get there? 0935 Dependencies: Is there anything that you {will|do} need from someone else? 0955 Prospective: What Ooni-stuff will be done this week? 1010 Adjourn See you Monday, -Tom

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

ooni-dev July 2013