<div dir="ltr"><div>Hi all:<br><br>It's been about a month or so since I've been doing the UX weekly meetings, and I've realized that the meetings could be improved. I'm new to running a team, so thanks for being patient with me. </div><div><br></div><div>I propose the following changes: </div><div><div><ul><li>each of us write down what we have done the past week, put it on a shared pad, and discuss during the meeting<br></li><li>we each write down what we will do next week, put it on a shared pad, and decide prioritize during the meeting <br></li><li>schedule the meeting to be NOT on Monday or Friday (lots of flying/days off/holidays) <br></li><li>switch to having meetings on IRC at (some people are uncomfortable with voice or video, we can log our meetings with meetbot)</li></ul></div></div><div>The main thing I would want from the meeting are weekly updates from people at the meeting, and to decide on what we will do for next week. I try to do this in an informal way, but I don't think it's been working out as well as I would like. I would like it written down too. I'm taking inspiration from the Network team, and how they run their meetings (see the forwarded message below). </div><div><br></div><div>New meeting slots available are: </div><div><ul><li>Wednesday @1500 UTC</li><li>Wednesday @1600 UTC</li><li>Thursday @1500 UTC</li><li>Thursday @1600 UTC</li></ul></div><div><br></div><div>Email this thread back with: </div><div><ol><li>if you have any concerns or suggestions with the proposed changes </li><li>times slots from the list when you are available, listed in the order you prefer </li></ol><div>If you don't reply to this email before 5/30 (just over a week of time), I'll assume that you are okay with these changes. </div></div><div><br></div><div><br></div><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Nick Mathewson</b> <span dir="ltr"><<a href="mailto:nickm@freehaven.net">nickm@freehaven.net</a>></span><br>Date: Mon, May 22, 2017 at 12:59 PM<br>Subject: [tor-project] Weekly network-team meeting: notes and logs from 5/22<br>To: <a href="mailto:tor-project@lists.torproject.org">tor-project@lists.torproject.org</a><br><br><br>Hi, all!<br>
<br>
You can find the transcript of our regular network team meeting here:<br>
<br>
<a href="http://meetbot.debian.net/tor-dev/2017/tor-dev.2017-05-22-17.00.html" rel="noreferrer" target="_blank">http://meetbot.debian.net/tor-<wbr>dev/2017/tor-dev.2017-05-22-<wbr>17.00.html</a><br>
<br>
Below are the contents of our meeting pad.<br>
<br>
=========================<br>
Network team status updates, 2017 May 22<br>
<br>
Discussion topics:<br>
- What is blocking 0.3.1.1-alpha, if anything?<br>
- What do we want to know about onion services?<br>
(teor is writing code to collect onion service stats on relays)<br>
- How do we make sure that the bugs get fixed? (in 0.3.1.x) (and in 0.3.0.x)<br>
- We should do more to test out <a href="http://oniongit.eu" rel="noreferrer" target="_blank">oniongit.eu</a>. What?<br>
- Can we publicize our 'easy' tickets for new/volunteer devs, and<br>
put more tickets in that category?<br>
- And remove ones that aren't so "easy"<br>
<br>
<br>
<br>
========<br>
Updates<br>
========<br>
<br>
teor:<br>
Last Week<br>
- Feature freeze for PrivCount 1.0.0<br>
(PrivCount collects tor stats and aggregates them securely.)<br>
Paper: <a href="http://www.robgjansen.com/talks/privcount-ccs-20161027.pdf" rel="noreferrer" target="_blank">http://www.robgjansen.com/<wbr>talks/privcount-ccs-20161027.<wbr>pdf</a><br>
Source: <a href="https://github.com/privcount" rel="noreferrer" target="_blank">https://github.com/privcount</a><br>
- So much PrivCount testing, fixed several counting and reliability bugs<br>
- Found a PrivCount scaling issue that will probably need a<br>
protocol redesign to fix<br>
- Refresh the fallback directory mirror list:<br>
<a href="https://lists.torproject.org/pipermail/tor-relays/2017-May/012285.html" rel="noreferrer" target="_blank">https://lists.torproject.org/<wbr>pipermail/tor-relays/2017-May/<wbr>012285.html</a><br>
This Week<br>
- Update the PrivCount README (set up a live privcount network and<br>
make sure it works)<br>
- All going well, release PrivCount 1.0.0<br>
- Start configuration and deployment for the next PrivCount<br>
collection run (maybe?)<br>
- Do some tor or chutney work: anyone have any suggestions?<br>
I might revise the chutney DNS thing -<br>
<a href="https://trac.torproject.org/projects/tor/ticket/21903" rel="noreferrer" target="_blank">https://trac.torproject.org/<wbr>projects/tor/ticket/21903</a><br>
- Work on the PrivCount Onion Service collection design: what do<br>
we want to know about onion services?<br>
<br>
<br>
Nick<br>
Last week:<br>
* released 0.3.0.7<br>
* froze 0.3.0<br>
* dubious merges wrt timing: #1922, rust. Should I not have?<br>
* prepared for 0.3.1.1-alpha (changelog, testing, cleanup, etc etc)<br>
* worked on bugfixes<br>
* tried to get proposal status right on more proposals<br>
* distracted by AC installation (heat pumps are nifty)<br>
This week:<br>
* release 0.3.1.1-alpha<br>
* try to get us focused on bugfix-mode for 0.3.1.x<br>
* start prep for 0.3.2.x<br>
<br>
* Try to get more progress w/ catalyst on the Tor side of UX improvements.<br>
<br>
<br>
Roger:<br>
This weekend: I started plowing through old trac tickets, to give<br>
opinions on many of them so people can move forward.<br>
This week: Continue doing more trac tickets, especially around the new<br>
guard-spec design, and related future guard designs.<br>
<br>
asn<br>
[Will not be around for the actual meeting :(. Have to attend a birthday dinner.<br>
Feel free to leave stuff for me on IRC and I will pick it up tomorrow]<br>
[*] Last week:<br>
- Lots of debugging/testing on #21969. Finally submitted a patch<br>
for the bridge case today.<br>
<br>
- Posted a list of open topics for HS guard discovery research:<br>
<a href="https://lists.torproject.org/pipermail/tor-dev/2017-May/012260.html" rel="noreferrer" target="_blank">https://lists.torproject.org/<wbr>pipermail/tor-dev/2017-May/<wbr>012260.html</a><br>
<br>
- Worked with Mike to make schedule for the guard parts of the June network<br>
team meetup. Need more feedback/brainstorming/<wbr>thought.<br>
<br>
- More work on prop224 client-side descriptor fetching (#21403).<br>
<br>
- Updated guard-spec.txt based on feedback by Roger:<br>
<a href="https://lists.torproject.org/pipermail/tor-dev/2017-May/012265.html" rel="noreferrer" target="_blank">https://lists.torproject.org/<wbr>pipermail/tor-dev/2017-May/<wbr>012265.html</a><br>
<br>
[*] This week:<br>
- Finalize #21403, or bring it very close to the end<br>
<br>
- Hopefully debug/fix the non-bridge case of #21969 as well.<br>
<br>
- More preparation for the network team hackfest.<br>
<br>
catalyst:<br>
<br>
* Last week:<br>
<br>
- based on IRC discussion #7869 needs some more work, including spec<br>
<br>
changes for a new consensus method<br>
<br>
- reviewed #21872 fixup patch<br>
<br>
- helped toby_ with test stuff. discovered that test-stem doesn't<br>
really work; filed #22301 about that<br>
<br>
- found a shell arithmetic syntax error in chutney proposed a patch in #22302<br>
<br>
- during some background research on bootstrapping found glossary<br>
needed some additional definitions; added in #22296<br>
<br>
- looked at some torbrowser-launcher stuff (sig verification and maybe<br>
<br>
pushing fixes for that into Debian/Ubuntu)<br>
<br>
* This week:<br>
<br>
- review #21969 stuff some more<br>
<br>
- document bootstrap process<br>
<br>
- make more progress on bootstrap UX improvements<br>
<br>
- sort out some apparently conflicting mental models of bootstrap, e.g., #22266<br>
<br>
- give feedback on #7869<br>
<br>
<br>
ahf:<br>
<br>
Last week (unordered):<br>
<br>
Sponsor 4:<br>
- Got the consdiff and directory code to work together and landed<br>
it (#21667).<br>
- Fixed issue: #22305.<br>
- Did a lot of testing with Chutney locally with current Tor HEAD + older<br>
releases.<br>
- Started to look into merging prop #278 changes to dir-spec.txt<br>
- Reviewed some patches for prop#140.<br>
Misc:<br>
- Read up on prop #247 + its discussion as preparation for the upcoming<br>
meeting.<br>
- Got trip booked for the upcoming team meeting.<br>
<br>
<br>
This week (ordered):<br>
<br>
Sponsor 4:<br>
- Finish the merging of prop #278 to dir-spec.txt (#22275)<br>
- Fix issues with #22286<br>
- Testing/bugfixing of 0.3.1-alpha release.<br>
Misc:<br>
- Need to spend some additional time wrapping my head around the guard<br>
proposal for the upcoming meeting.<br>
<br>
komlo:<br>
- Last week:<br>
- Created a separate branch for rust_smartlist for review/to build upon.<br>
- Worked with manishearth for a POC to handle strings between<br>
Rust/C. This uses malloc and free, which would keep the Rust/C<br>
boundary more decoupled. We can re-review as we get further into Rust<br>
implementation: <a href="http://github.com/Manishearth/freestring" rel="noreferrer" target="_blank">github.com/Manishearth/<wbr>freestring</a><br>
- This week:<br>
- Finish implementing protover_is_supported_here and<br>
protover_compute_for_old_tor (will be ready for review after these)<br>
<br>
<br>
isis:<br>
Last Week:<br>
- Emails about contracting/employment<br>
- Spec'd #18329 and tried to move it forward<br>
- Did other things in my time off<br>
This Week:<br>
- Doing other things, let me know if help is needed somewhere urgently<br>
<br>
haxxpop:<br>
Previously: I didn't do anything 'cause my paid job.<br>
This Week: I think I have more time now. I will find something to do.<br>
<br>
pastly:<br>
- boring new-hire NRL travel stuff. Hopefully will get done before<br>
Wilmington<br>
- running experiments to determine if high priority traffic is<br>
correctly being<br>
prioritized over low priority traffic. Inconclusive so far. Is it<br>
network variance?<br>
Shadow is so nice. So hard to be sure of things on a live relay.<br>
- for the above point, looking at EWMA cell_count values vs Tor<br>
application queuing delay.<br>
Also looking at TCP information.<br>
This week:<br>
- more of the same prioritization verification<br>
- time to make serious efforts at documentation/tests for kist code<br>
<br>
<br>
mike:<br>
Last week:<br>
- Worked on Guard meeting agenda with asn<br>
- Discussion of catalyst and nick's bootstrap doc<br>
- Planning travel<br>
- Padding branch work<br>
This week:<br>
- Moar travel logistics<br>
- Padding<br>
<br>
Sebastian:<br>
- reviewed a bunch of Rust code, preparing future branches for<br>
smartlists/consdiff<br>
- not that much time atm :/<br>
<br>
isabela:<br>
- last week: was sick for most of it, but sent out sponsor4 report<br>
and worked on invoices for sponsor4 and R<br>
- this week: i worked last week on my notes about the tor launcher<br>
whiteboarding session i had with mike and isis, i hope to finish that<br>
this week and share with people (from the launcher automation email<br>
thread) and schedule a meeting to pick up on that, discuss my notes<br>
and hopeflly answer some open questions I have.<br>
______________________________<wbr>_________________<br>
tor-project mailing list<br>
<a href="mailto:tor-project@lists.torproject.org">tor-project@lists.torproject.<wbr>org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project" rel="noreferrer" target="_blank">https://lists.torproject.org/<wbr>cgi-bin/mailman/listinfo/tor-<wbr>project</a><br>
</div><br></div>