Hi all!

We had the weekly Tor Browser meeting yesterday in #tor-meeting. Here is the meeting transcript:

http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-01-22-19.00.log....

And the notes from the pad are:

Monday, January 22, 2018 Discussion:

What to do about the Mozilla team meeting Wens nights

Worth making a separate one? Probably can just use this one for now.

GSOC Projects?

tjr intends to keep the Crash Reporter one up; but took down the 'Making Tor Browser faster' one

Will ask Shari for cloud resources if we get anyone

tjr:

Spectre Stuff

I'm working on Timer stuff, taking a lot of my time

Moz intends to pursue Fuzzyfox, might land (off or on) somewhere in the post-60 timeframe.

JIT Mitigations landing in 59: children of https://bugzilla.mozilla.org/show_bug.cgi?id=1430049

MinGW

Going to try and get back in front of this for 60.

Beginning with Sandbox uplift, children of https://bugzilla.mozilla.org/show_bug.cgi?id=1230910 for tracking

Also trying to uplift these all the way to chromium

Besides Sandbox, what is and is not high-priority for me to uplift in 60 for build stuff?

Yes: Get the #&$(@& thing running: https://bugzilla.mozilla.org/show_bug.cgi?id=1411401

Yes but not me: Stylo

Yes: x64 Patches

https://gitweb.torproject.org/tor-browser.git/patch/?id=5aa8644

Any others?

https://gitweb.torproject.org/tor-browser.git/patch/?id=ba9e5d6 <- don't need this

Yes: Fix the TaskCluster integration on not-central-trees

Ideally: jemalloc https://bugzilla.mozilla.org/show_bug.cgi?id=1420350

Ideally: x64 in Task cluster

No: WebRTC

Discussed Rome in the Sandboxing meeting

Related/Unrelated, the timeframe for https://bugzilla.mozilla.org/show_bug.cgi?id=1322426 WAS 'Behind a pref in 61, enable for release in 63' but is now "This will not be happening in the near term, due to staffing changes. It’s not yet clear when or if this will occur."

Will need to re-triage Mozilla bugs and plans =(

Have a lot of 'For 60' things to work on, so if you have some of those yourself, please let me know.

My intention is to search for the whiteboard tags [tor OR fingerprinting which gives this list:

https://bugzilla.mozilla.org/buglist.cgi?quicksearch=sw%3A%5Btor%20OR%20fing...

mcs and brade: Last week: - Reviewed Android Torbutton and Tor Launcher proposals and replied on the tbb-dev "Tor Button Proposal" thread. - Found the root cause and proposed a fix for #24421 (Temporarily allow all this page and New Identity). - Posted patches for #21850 (Update about:tbupdate patch for e10s) Planned for this week: - If there is anything we can do to help, assist Matt with #24432 (meek/Moat tunnel) . - After #24432 is fixed, test and put the Tor Launcher Moat integration code out for review. - Work on #24578 (about:tbupdate popup notification formatting error). - Work on #24159 (The Torbutton version check does not deal properly with platform specific checks). - Triage the Tor Launcher bug list (set priorities, close outdated tickets).

igt0: Last week: - Moved Tor Button to the browser/extension folder (build system, add files to allowed dupe) - Migrated the chrome.manifest to use jar.mn - Added Tor Button in the tor button mobile omni.jar - Updated the Tor Button Proposal This Week: - Verify why torbutton-logger is not printing debug messages in the console (mobile) - Update the overlay components to work in the mobile browser when needed. (about:addons, extensions, about:tbupdate[maybe not needed, Android has its own thing about updates]) (the work is being made here: https://github.com/igortoliveira/tor-browser)

boklm: Last week: - helped with building the new releases - made some patches for #24924, #24931 - opened #24921 to create https://nightlies.tbb.torproject.org/ This week: - publish the new releases - finish fpcentral setup/integration in testsuite to be able to close all fpcentral tickets - enable testsuite on nightly builds and fix any issue in the tests

sysrqb: Last Week: - Opened some tickets for Tor Browser for Android (TBA), based on Orfox bugs - Re-wrote some Orfox commits - Wrote a revised TorLauncher proposal - Started looking at Moat - Ran into some problems during Orfox rebase - Investigated Firefox preferences parsing This week: - Finishing Orfox/TBA branch with squashed/rebase/rewritten patches - Investigating why a couple firefox prefs are not overwritten: - On desktop, app.update.staging.enabled is not set correctly - On mobile, browser.casting.enabled is not set correct - Probably look more at Moat server-side

pospeselr:

Last Week:

- Posted a 'fix' for #15599 (by fix I mean it just disables the broken feature)

- Started work on #22794, synced with Yawning

- made travel plans for Rome

- got setup with mozilla testing TryServer

This Week:

- Get ae patch up for #22794

- JURY DUTY Wednesday -> Friday

arthuredelstein:

Last Week:

- Worked on rebasing to mozilla-central and nightly rebase. Getting closer!

- Worked https://trac.torproject.org/projects/tor/ticket/22343 (Save As)

- Here's my proposed list of bugs to work on for uplift: https://mzl.la/2E1eVn2 (Deadline, roughly March 12)

This Week:

- Continue on rebasing

- Try to rebase #22343

- Work on uplifting patches

- Look at https://trac.torproject.org/projects/tor/ticket/24918

GeKo: Last Week - release preparations and working on the Tor Browser design doc update This Week - finish the design doc update and work on the toolbar and security indicator improvements proposal

isabela: 2 months extension for sponsor4 sponsor8 Q4 report - I will probably ping some mobile folks and geko to make sure I collected all the tickets etc antonela did user testing in India! o/ Tor Launcher new UI (tested text interpretation of our new copy) and .onion http/https states icons comprehension - will share more soon also want to check if arthur/geko can meet about tor circuit (probably next week) ux team will help with the blog post for the release - add stuff about the Tor Launcher new UI

Georg