<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 1, 2013 at 6:40 PM, Meredith Whittaker <span dir="ltr"><<a href="mailto:meredithrachel@google.com" target="_blank">meredithrachel@google.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Aaron, <div><br></div><div>Thanks for these notes! From vacation, I'll answer your M-Lab questions quickly (also adding Stephen). </div>
<div><br></div><div>The collector policy implementation is a blocker for deployment on M-Lab. To complete deployment, it will be necessary for M-Lab to configure this collector policy, to ensure that the broader M-Lab privacy/openness policies are adhered to. Thus, I believe it should be a part of this feature-complete milestone, since it is fundamental to launch. </div>
<div><br></div><div>I can review the M-Lab policies, if that's helpful. However, I don't think the collector policy should be designed for M-Lab, but should be designed to allow M-Lab and any other collector to implement their own policies, per their legal/organizational requirements. </div>
<div><br></div><div>Let me know if you have any questions here. Happy to discuss further. </div></div></blockquote><div><br></div><div>Ok, that's what I thought and believed was part of the discussion that we had in Berlin. <br>
<br>Tom, can we agree that this is an issue we must address for release 1.0 and factor this into our release agenda?<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><br></div><div>In the meantime, on the topic of changing the meeting from Hangouts to "other" -- I have a phone bridge with international dail-in numbers. If it's helpful we can use it. </div>
<div><br></div><div>Cheers,</div><div>M</div></div></blockquote><div><br></div><div>Thank you for taking time from your vacation to reply. Hope you are having a blast :-)<br><br></div><div>--Aaron <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Mon, Jul 1, 2013 at 12:58 PM, Aaron <span dir="ltr"><<a href="mailto:aagbsn@torproject.org" target="_blank">aagbsn@torproject.org</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Present in call:<br><br> Tom, Aaron, Arturo, Johannes<br><br><br>What we have worked on this week:<br>
<br>
Arturo worked on twisted socks client support and NetTest specification<br> Aaron worked on specification and implementation of the test deck and test input api for ooni-probe and ooni-backend (117, 115, 109).<br>
<br><br>Are there any items blocking?<br><br> No blocking items were raised.<br><br><br>Are we on track to make the first milestone (Fully Specified)<br><br> Aaron and Arturo say yes.<br><br><br>What are we working on this week:<br>
<br> Aaron and Arturo will be working on issues 115, 117, 91, and 90 this week.<br><br><br>Issues that we discussed on the call:<br><br> Tom states that collector policy implementation (issue 109) is not part of the feature complete milestone and instead<br>
should be in future versions. Aaron and Arturo believe that collector policy was a blocking issue for MLAB deployment<br> as discussed at the Berlin meeting. We would like to request feedback from MLAB on this point.<br>
<br> Arturo asked for clarification on issue 107 (do we need to specify each unit test?)<br> The resolution was that the unit test spec should be replaced with a code coverage report as per Nathan's suggestion.<br>
Johannes suggests <a href="http://coveralls.io" target="_blank">coveralls.io</a> which writes a code coverage report into the README.md.<br>
<br> We discussed alternatives to using Google Hangout for our weekly meetings<br> Johannes suggests: Mumble.<br> Tom suggests: phones.<br> Can we expose a phone number for call ins into the Google chat? No, but it can dial out worldwide (US and Canada free).<br>
Aaron Tom and Arturo agree that video chat is nice.<br> Mumble now has a voice-activation feature and Johannes has a mumble server that we can use.<br> Google Hangout has some issues on Johannes computer (system load > 4).<br>
We agree that the four of us cannot reach a consensus without others present and will take this discussion to the mailing list.<br><br><br>See you all next week!<span><font color="#888888"><br><br><br>--Aaron<br>
<br></font></span></div>
<br></div></div><div class="im">_______________________________________________<br>
ooni-dev mailing list<br>
<a href="mailto:ooni-dev@lists.torproject.org" target="_blank">ooni-dev@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/ooni-dev" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/ooni-dev</a><br>
<br></div></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div><br></div>Meredith Whittaker<br>Program Manager, Google Research<div>Google NYC<br></div><div><br></div>
<div><div><br></div><div><br></div></div>
</font></span></div>
</blockquote></div><br></div></div>