19:00:54 <GeKo> #startmeeting tor browser
19:00:54 <MeetBot> Meeting started Mon Feb 27 19:00:54 2017 UTC.  The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:54 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
19:00:57 <asn> that im gonna think about this tomorrow, and most likely move PROTOID to the beginning
19:01:02 <GeKo> hi all !
19:01:16 <boklm> hi!
19:01:18 <GeKo> so we have another monday with another tor browser meeting
19:01:25 <GeKo> who wants to go first today?
19:01:28 <arthuredelstein> hi!
19:01:42 * mcs will go first
19:01:56 <mcs> Last week, Kathy and I spent a lot of time going through bug lists and developer notes for #19048.
19:02:02 <mcs> We posted our findings in that ticket and we plan to work with GeKo to file bugs for things that need more work.
19:02:07 <mcs> We also spent some time looking at #20761 again.
19:02:15 <mcs> Earlier today we responded to the “design decision for Tor Launcher” thread on tbb-dev (https://lists.torproject.org/pipermail/tbb-dev/2017-February/000484.html)
19:02:21 <mcs> This week we plan to work on a revised fix for #20761.
19:02:28 <mcs> That’s all for us.
19:03:30 <GeKo> i realized to day that you took the hard road and reviewed all the things, not only the dev docs, nice :)
19:03:34 <GeKo> *today
19:04:02 <mcs> Fun stuff.
19:04:05 <mcs> :)
19:04:19 <GeKo> yeah
19:04:24 <GeKo> i can  go i guess
19:04:59 <GeKo> so this week i found an old branch being basically ready for merging: #17034
19:05:09 <GeKo> i worked on #21536
19:05:24 <GeKo> but most of my time i spent on #15988
19:05:36 <GeKo> it's finally ready for review
19:06:08 <GeKo> then i continued my toolchain work and built the sandbox code for windows #16010
19:06:23 <GeKo> now we only need to get it to work :)
19:06:57 <GeKo> and i integrated the latest selfrando changes in #20683
19:07:03 <GeKo> i am currently testing that
19:07:38 <GeKo> i resumed my work on #19048 and started filing tickets and moving things around
19:07:53 <GeKo> this will be my main task for this week apart from release preparations
19:08:24 <GeKo> i hope i have a bug list with high prio bugs for the next 6 weeks ready by next monday
19:08:51 <GeKo> i plan to review #20095
19:08:55 <GeKo> err
19:09:02 <GeKo> #20905
19:09:12 <GeKo> might be alpha territory though
19:09:49 <arthuredelstein> yeah, I think that might be best
19:10:21 <GeKo> i guess i could come up with a quick fix for #21396 for the next stable
19:10:25 <GeKo> we'll see
19:10:33 <GeKo> that's it for me for now
19:10:55 <GeKo> oh, we could need someone looking into #21555
19:11:04 <GeKo> any volunteers?
19:11:11 <tjr> I can go
19:11:16 <GeKo> i have some guesses but no twitter account :)
19:11:40 <arthuredelstein> I volunteer :)
19:11:52 <tjr> (Phew, thanks arthur)
19:12:02 <mcs> yes, thanks!
19:12:16 <GeKo> thanks!
19:12:19 <arthuredelstein> tjr: sorry -- were you volunteering? Didn't mean to step on any toes :)
19:12:33 <tjr> No I was misreading and was hoping I did not accidently volunteer :-p
19:13:12 <GeKo> lol
19:13:26 <tjr> Anyway, tiny update:
19:13:33 <tjr> Mingw is stalled at the moment, but I intend to resume it once I get hardware in, next week or this hopefully.
19:13:37 <tjr> I had some meetings about mozilla onion services and we hope to move that forward once my new hardware comes in also.
19:13:42 <tjr> The Fennec+Tor prototype is moving forward (I am not the developer behind that :) )
19:13:49 <tjr> Participated in discussions about firefox features that may impact Tor. If anyone wants to subscribe to a low-volume place to track this type of data a good choice would be: https://blog.nightly.mozilla.org/author/mconleymozilla-com/
19:14:18 <tjr> And I got three (3!) inquiries about potential GSOC (mozilla GSOC) for the tor add-on prototype. No guarentee Moz is in GSOC or those students will be though.
19:14:23 <tjr> (thats it)
19:15:17 <GeKo> yeah, i saw your project. if that is going to be something. let me know i am interested int it
19:15:40 <GeKo> s/int/in/
19:15:50 <mcs> what is “the tor add-on?”
19:15:51 <GeKo> i might have some cycles to help with things
19:16:16 <tjr> make a test pilot add-on that bundles tor and makes measurements
19:16:21 <tjr> maybe even submit telemetry via tor
19:16:33 <mcs> tjr: thanks
19:16:45 <tjr> Yup. Step 1 in the "Try and get Tor into Firefox proper"
19:16:59 <arthuredelstein> yay
19:17:05 <GeKo> which is why it is so exciting :)
19:17:30 <arthuredelstein> absolutely!
19:18:49 * arthuredelstein can go
19:19:07 <arthuredelstein> This week I posted a patch for #20905.
19:19:32 <arthuredelstein> (resizing bug on Linux)
19:19:34 <arthuredelstein> I also wrote one for #21574
19:19:43 <arthuredelstein> I also wrote one for #21574
19:19:48 <arthuredelstein> And I wrote a patch for #21514 but I am still testing it.
19:20:35 <GeKo> fwiw: #20905 is actually not linux-only
19:20:38 <arthuredelstein> I also started work on #21547.
19:21:10 <GeKo> (but i hope it will fix the issue for windows folks as well)
19:21:11 <arthuredelstein> Geko: Yeah, I could have worded that better. The blocking part was Linux-only
19:21:26 <GeKo> okay, good then :)
19:22:11 <arthuredelstein> Definitely is a cross-platform fix and also a cross-platform liability! :P
19:22:22 <GeKo> yeah
19:22:24 <arthuredelstein> This week I plan to work on anything needed for the next release and try to get a working full bundle for #20680 that can serve as a basis for our new ESR52 patches.
19:22:56 <GeKo> i had a comment for you on #21308
19:23:35 <arthuredelstein> Yeah, I need to go back and test both the old patch and the new. But if I recall correctly, the old patch causes crashes and I didn't immediately figure out why
19:25:00 <GeKo> ok. and there is one comment in #21267 as well you m ight want to think about
19:25:18 <arthuredelstein> For #21308 I also submitted the patch to https://bugzilla.mozilla.org/show_bug.cgi?id=1192643 so we'll see if Mozilla things it is correct.
19:26:06 <arthuredelstein> GeKo: re #21267, I think that isn't a bad suggestion. I guess it depends on how hard the fix is but I also sympathize that you have had to disable that feature in every release.
19:26:48 <GeKo> that's actually the weakest part of the argument :)
19:26:51 <GeKo> but still
19:26:55 <GeKo> ...
19:27:13 <arthuredelstein> I do want to get this feature into tor-browser.git in any case. The nastiest part is mimicking a "resizeend" event, which is why I am afraid it's a deep rabbit hole.
19:27:58 <arthuredelstein> Anyhow, I will also work on #21555 this week
19:28:25 <arthuredelstein> So that's it for me.
19:30:05 * boklm can go next
19:30:20 <boklm> On #17379 I fixed some issues that prevented the Tor Browser built with rbm from working on Windows and OSX
19:30:25 <boklm> I started looking at integrating FPCentral in our test suite
19:30:46 <boklm> On #20426 I looked more at the small diff we have on tor.exe (and tor-gencert.exe in the expert bundle) but did not find yet how to fix it
19:30:54 <boklm> This week I'm planning to integrate FPCentral in our testsuite, work on #21404, #20426 and help building the new releases
19:31:05 <boklm> That's it for me.
19:31:53 <GeKo> boklm: could you put rbm stuff you have in the backlog into the repoand we maybe able to have a test tag?
19:32:14 <GeKo> then i could do a build as well and we could compare whether things look good on different machines
19:32:47 <GeKo> maybe we uncover other issues we'd like to know about early
19:33:12 <boklm> GeKo: ok. I think we can have a test tag on what is in master.
19:34:19 <GeKo> okay, fine. or would just using that commit work as well?
19:34:35 <boklm> yes
19:35:10 <GeKo> ok. then i'll look into building from 38863663120244e4becc66fe7a10cce92d8e639b tomorrow
19:35:45 <boklm> ok
19:35:55 <GeKo> okay. who else is here for a status update?
19:38:39 <GeKo> do we have anything to dicsuss for today then?
19:39:40 <GeKo> alright. thanks for the meeting all *baf*
19:39:44 <GeKo> #endmeeting