Hi!
Yesterday we had our weekly Tor Browser meeting. The IRC log can be found at:
http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-09-10-18.00.log....
The notes from our pad are:
Tor Browser Meeting Notes
Monday September 10, 2018 Discussion: -User Agent (GeKo: https://trac.torproject.org/projects/tor/ticket/26146#comment:33 has our current plan) -State of the Onion at the dev meeting (GeKo: We'll mull over what to talk about and decide next Monday who will be presenting on behalf of the team) -Mozilla/Tor TB8 Retrospective (GeKo: Good idea, let's do it after Mexico (see https://lists.torproject.org/pipermail/tbb-dev/2018-September/000908.html))
GeKo: Last week: -help with getting our releases out (8.0, 8.5a1 and 1.0a1 for mobile) We did it! \o/ -started organizing issues with the tbb-8.0-issues keyword (https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~...) -begin of the month admin stuff -help with new DRL proposal -created new gpg subkeys This week: -tbb-8.0-issues (GeKo: The plan is to get a 8.0.1 release out next week, tackling issues marked with tbb-8.0.1-can) -tor browser for mobile planning (GeKo: the meeting is on 9/11 at 1800 UTC, presumably in #tor-meeting) -could need a second look at rust proxy safety (sysrqb: could you help with that? gk: sure)
tjr - So close to landing a mingw-clang x64 browser build job in -central. 2 patches need r+'s
- Outstanding things to be done for mingw-clang: --enable-sandbox, x86, get it running :(
- I can backport it to -esr60 after a supposedly coming NSS version bump lands.
- Tried some debugging for https://bugzilla.mozilla.org/show_bug.cgi?id=1466192 (jemalloc on Windows in mingw-gcc) but no progress yet - Sent fuzzyfox in for review! https://bugzilla.mozilla.org/show_bug.cgi?id=1432429 (GeKo: Yay!)
mcs and brade: Last week: - Used staged MAR files to test Tor Browser 7.5.6 to 8.0 updates (no issues found). - Helped with bug triage. - Completed month-end administrative tasks. - Was away from keyboard Thursday and Friday. This week: - Review the fix for #26381 (broken about:tor on Windows with sandboxing). - Work on tickets flagged with the tbb-8.0-issues keyword. - Help with triage of new tickets. - Review our notes from #22074 (undocumented bugs since FF52esr) and file additional tickets if necessary.
sysrqb: Last week: Finally released TBA 1.0a1 Moved. Landed patch for #27400 - Target Android API 26 Helped Isa create Google Play Store page for Tor Browser for Android Helped Steph and Isa with blog post This week: Restart Gecko after first-run - #27611 Begin looking at Tor's new embedding API Discussing future plans/roadmap for next alpha release Look at rust code for proxy safety TBA private tabs - #24920
sisbell: Last week: - Completed #27438 - Android Gradle Build Downloads - Source Code: https://github.com/sisbell/artc - Crate: https://crates.io/crates/artc This Week: - Integrate and test rust program output (from #27438) with RBM build for android-toolchain - Respond to comments regarding open issues for android RBM build
igt0: Last Week: - Struggled a bit with the #26690 (padlock for tba), sending a patch today - Started to implement the Tor Circuit Display - Helped out a bit with the TBA release This Week: - Finish the padlock #26690 - Have the Tor Circuit Display UI for Android done - Start to refactor tor button to separate the UI and logic
pospeselr:
Last Week:
- fix for #26381 (broken about:tor on Windows with sandboxing)
- review needed! (mcs/brade: can you take a look?) mcs: Yes, we will take a look.
- cleaned up patch for #26450 (pdfjs range requests on default circuit)
This Week:
- put up patch for #26450 using the 'smuggled' first-party domain technique discussed in ticket
- begin investigation for #3600 (prevent redirects from transmitting cookies)
wayward: User Advocate role - getting started
Last week:
- created new user feedback tracking doc (https://storm.torproject.org/shared/JwsANJ37_QYZnGa9SCTVIGSjCAWm43Tyd_d3cJe5...) https://trac.torproject.org/projects/tor/wiki/UserIssuesResearch
This week:
- establish contact with applications team (would a weekly/monthly email update be too annoying?) (GeKo: We had a weekly mail to tor-project and I think we could keep that format for the time being)
- other places to find feedback, besides reddit, stack exchange, blog posts, and IRC? (twitter? mastodon? any ideas welcome)
- what info to gather for bug investigations and feedback reports
- will set up a monthly mailing list with user feedback
- figure out some place/way to organize user feedback by importance - perhaps on trac, or a wiki page?
arthuredelstein: Last week: - Patch for #27290 (now investigating more for possible revision) - Opened #27476 (Remove gap between Tor Launcher window and main browser window) - Revised #27097 - Looked more at NoScript/torbutton communication (#27413 et al) - #27268 (pref cleanup, will post soon) This week: - tbb-8.0-issues, tbb-fingerprinting - uplifting FPI permissions patch (https://bugzilla.mozilla.org/show_bug.cgi?id=1330467) - look more at optimistic socks
Georg