18:02:27 <mikeperry> #startmeeting app-dev
18:02:27 <MeetBot> Meeting started Tue Sep  8 18:02:27 2015 UTC.  The chair is mikeperry. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:02:27 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
18:04:23 <mikeperry> ok, let's get started
18:04:47 <mikeperry> I suppose I can go first
18:04:50 <mikeperry> Last week, I wrote our status report and organized our tickets for September.  We have quite a pile, including the finishing touches on some SponsorU items.  I think we have until the end of October for those, but I added them anyway (#10599, #16620, and #6540). I also started writing some Tor proposals that I want to have ready by the meeting.
18:05:53 <mikeperry> This week, I might pick off a few regressions from our September list, but I really want to finish up my Tor proposals. We also have only two weeks until the next Firefox release, so things might be a little tight.
18:07:15 <mikeperry> I probably will take #16783 and #16837 in specific
18:07:30 <mikeperry> but otherwise I'll be working on tor proposals and meetings
18:07:38 <mikeperry> that's it for me for now
18:09:51 <GeKo> here is what i did
18:10:45 <GeKo> I finished up #15538 and #16444 + wrote a patch for #16909 which is missing the updater relevant parts
18:10:58 <GeKo> i plan to look at the latter tomorrow
18:11:46 <GeKo> then i reviewed and merged a bunch of things like #16887, #16937 and #16551
18:13:14 <GeKo> i tried hard to contact yahoo for #16874 and got something back
18:13:32 <GeKo> i am not convinced that i get the chance to talk to a technician but we'll see
18:13:55 <GeKo> the cross-compiling might be "more" promising :)
18:14:37 <GeKo> next week i plan to get more reviews done as we are approaching our next release
18:14:59 <GeKo> apart from that tickets i intend to work on this month are tagged with GeorgKoppen201509
18:15:33 <GeKo> so i probably start with #15578 and maybe #10599 again giving our timeframe
18:15:40 <GeKo> that's it for now
18:16:52 * mcs can go next
18:17:00 <mcs> Last week, Kathy and I did some research for #16778.  It would be helpful if someone else chimed in there.
18:17:06 <mcs> We also spent some time on #16937; I think Kathy, GeKo, and I are getting close to agreeing on a plan.
18:17:14 <GeKo> :)
18:17:21 <mcs> And we came up with a fix for #16910.
18:17:25 <mcs> Finally, we spent some time on #16735 but do not have a fix ready yet.
18:17:34 <mcs> This week we will continue working on #16937 and #16735.
18:17:40 <mcs> We may also look at #16753, at least to see if it is less of an issue now that we are planning to whitelist more fonts in TB 5.5.
18:18:06 <mcs> And, based on Mike's comments above, if no one else wants it we could take #16620 (move window.name to FF patch)
18:18:14 <mcs> That's all.
18:23:03 * arthuredelstein can go
18:23:09 <arthuredelstein> Last week I developed a patch for Windows and Mac font whitelisting for #16707.
18:23:16 <arthuredelstein> And I worked on furthering our KeyboardEvent fingerprinting defense with #17009.
18:23:27 <arthuredelstein> I also spent a day on #16936, but it turned out to ridiculously complex. I need think about possible other approaches.
18:23:35 <arthuredelstein> Apart that, this week I want to look at #14429 again, and work on more Mozilla upstreaming and any tbb-5.0-regression I can help with.
18:23:45 <arthuredelstein> That's all for me
18:25:35 * boklm can go next
18:25:55 <boklm> Last week I fixed #16956, #16963, #16973, I help sukhe on tor-messenger build
18:26:04 <boklm> I rebased the split branch repo on 38.2.1esr, added branches for 5.5 patches and pushed everything to Try: https://lists.torproject.org/pipermail/tbb-dev/2015-September/000305.html
18:26:12 <boklm> This week I will try to fix / disable more unit tests.
18:26:17 <boklm> That's all for me
18:28:27 <GeKo> what do you mean with "disable"?
18:29:14 <GeKo> just to test what the issue is?
18:29:57 <boklm> for example, disabling plugin tests on the branch that disable plugins
18:30:26 <GeKo> ah, i see
18:30:53 <boklm> disabling tests where it is expected that our patches make them fail
18:31:29 <boklm> to make it easier to see real test failures
18:32:16 <mikeperry> makes sense
18:32:35 <GeKo> yeah
18:33:54 <arthuredelstein> boklm: Some of the broken patches are fixed for ESR45, so you may want to avoid working on those. See the "FIXED" section here: https://docs.google.com/spreadsheets/d/1rF4Gah_OEequYDfPedoQu3oETM5Gj4NagxDuKQG-IOk/edit?usp=sharing
18:36:08 <boklm> arthuredelstein: oh ok, I will check with this list. Thanks.
18:37:59 <GeKo> arthuredelstein: didn't you have a fancier one somewhere? I can't find it anymore...
18:39:32 <arthuredelstein> GeKo: I did, but I haven't updated it in a while. I've requested edit access for this one...
18:41:38 <GeKo> ok
18:42:52 <arthuredelstein> boklm: #13025, #16315 are also tickets already upstreamed but missing from that spreadsheet right now
18:43:33 <GeKo> and the JAR patch IIRC
18:43:38 <boklm> arthuredelstein: ok
18:44:51 <arthuredelstein> GeKo: Yes, although that isn't causing any failures in boklm's tests
18:46:03 <GeKo> yeah, i was just looking at the spreadsheet
18:46:46 <isis> arthuredelstein: also (re: #17009) i've been suspecting that, because i'm constantly pressing the windows/super key, i'm giving away that i'm actually a linux user using a tiling window manager
18:46:58 <isis> not sure if that is within the scope of your ticket
18:47:49 <arthuredelstein> isis: Aha, interesting. I wonder if we should suppress that key as well.
18:49:12 <isis> would that supress windows users pressing it in order to get to the FF menu (the one that linux users press L-Alt to see)?
18:49:46 <isis> or just supress content windows from watching for it with some JS?
18:49:56 <GeKo> the latter
18:50:13 <GeKo> (ideally :) )
18:50:30 <arthuredelstein> Yeah, ideally!
18:50:35 <isis> oh okay, that would probably be good then
18:51:11 <arthuredelstein> isis: If you visit https://arthuredelstein.github.io/tordemos/keyboard.html, click in the text field, and then try a twm key command, does it register the super-key event?
18:51:32 <arthuredelstein> Hmm, now that I ask the question, I'm pretty sure it will.
18:51:33 <isis> wow fancy demos :)
18:52:05 <isis> yeah, it does. the keycode is OSLeft
18:53:31 <isis> oh man, it's totally obvious that i use Firemacs too. :(
18:54:13 <arthuredelstein> Do you also see a modified key event? Such as key = "N" and metaKey = true? Or does the twm prevent that from reaching FF?
18:55:05 <isis> ModifierState: OS
18:55:07 <arthuredelstein> IIRC, OSLeft === metaKey
18:55:33 * boklm has "metaKey = false" with OSLeft
18:55:53 <isis> yeah, "metaKey = false" here too
18:56:28 <isis> i have "ModifierState: OS" on keydown and just "ModifierState: " on keyup, for some reason
18:57:46 <isis> okay, sorry, i didn't mean to derail your meeting talking about a specific ticket.  carry on, and feel free to ask me about #17009 stuff whenever is appropriate.
18:58:13 <arthuredelstein> OK, thanks. Looks like I need to do a lot of experimenting in a twm.
18:59:54 <mikeperry> ok, any other updates or questions/comments?
19:00:36 <mikeperry> we will probably see tags for the next firefox release on next Tuesday, so we should consider that the soft freeze for 5.0.3
19:01:24 <mikeperry> and probably we won't be able to take anything past next Thursday the 17th, or so
19:02:20 <GeKo> mikeperry: if you could comment on the spellchecker issue on #16937 that would be neat
19:02:22 <mikeperry> I will also be traveeling prior to the dev meeting, which may complicate the actual release process
19:06:31 <GeKo> (does not need to be now fwiw)
19:07:12 <mikeperry> ok, yeah I missed the spellchecker bits
19:09:16 <mikeperry> ok, anything else then?
19:11:01 <mikeperry> alrighty! time to call it
19:11:06 <mikeperry> #endmeeting *baf*