19:02:06 <mikeperry> #startmeeting tbb-dev 19:02:06 <MeetBot> Meeting started Mon Feb 9 19:02:06 2015 UTC. The chair is mikeperry. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:02:06 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic. 19:02:18 <arthuredelstein> hi all 19:02:34 <mikeperry> ok, let's get started. I believe we're down a GeKo 19:03:15 <mikeperry> Last week, I filed the remainder of the usability tickets from the uxsprint, and reviewed and tweaked the blog post. I am not sure where David intends to post it. Presumably the Tor Blog? 19:03:18 <MarkSmith> and boklm? 19:03:25 <asn> dgoulet: if you have anything to add, just tell me now and I will insert it before sending to tor-reports. 19:03:31 <mikeperry> I also met with Sid and Steve at Mozilla. As I posed on dev-privacy, we appear to be on the same page that the best path forward to Tor Mode in Firefox is a separate Tor profile and dedicated Firefox process. Sid and Steve are also going to do some work updating our cache isolation to the new Cache2 interface, as well as having a look at updating the DOM storage patch for Firefox 38. 19:04:02 <mikeperry> After that meeting, I went to Wikimedia and discussed working together to enable edits by Tor users on Wikimedia. They seemed excited to fund research and development of cryptographic solutions that we may ultimately bake into Tor Browser to tackle the anonymous authentication in a general way on the Internet. I am trying to put them in contact with some research groups for funding and general hiring co 19:04:08 <mikeperry> nnections. 19:04:13 <mikeperry> I then did some organizational things like helping with the PM hiring process, writing the Tor Browser status report, and organizing tickets for this month. 19:04:24 <mikeperry> This week, I plan to work on as many tickets in https://trac.torproject.org/projects/tor/query?keywords=~MikePerry201502 as I can. I picked a bunch of usability issues, and several tickets to review. 19:04:35 <mikeperry> As a reminder, the next Firefox ESR point release will be tagged on Tuesday, Feb 17 for release on Feb 24th. Due to the dev meeting the week after, we are going to have to be sure we get both the stable and alphas out before everyone disappears for travel, so please have your reviews and patches ready, ideally by the 17th Mozilla tag date. 19:04:48 <mikeperry> That's it for me. 19:05:08 <arthuredelstein> What would a separate Tor profile entail? 19:06:37 <mikeperry> they suggested some kind of launching UI. apparently https://addons.mozilla.org/en-US/firefox/addon/switchy/?src=ss and https://addons.mozilla.org/en-US/firefox/addon/profilist/ are decent. but the idea is to make it easier for all of the prefs we want set for Tor Mode to only apply to Tor Mode, and to avoid state from bleedinging between Tor Mode and non-Tor Mode 19:07:51 <MarkSmith> I made a comment in the ticket: #14713 19:08:13 <arthuredelstein> So that means we would just bind our various features to prefs, and not worry about some kind of PBM-like state? 19:08:25 <MarkSmith> There are definitely some tradeoffs in using a separate profile but that is probably easiest from an implementation point of view 19:08:34 <mikeperry> yes 19:10:05 <mikeperry> the bookmarks import is a good point, but that should be straightforward compared to dealing with all of the other state bleeding issues 19:12:21 <arthuredelstein> It does sound like a good way to keep add-ons out of Tor mode. 19:16:24 <mikeperry> anyway, it's a good target that will also let us not worry so much about retooling all of our patches. the end result may need a bit of UX around the profile management, but the patches and our addons should work without difficulty 19:18:48 <mikeperry> who is next for meeting update? 19:18:57 * MarkSmith can go next 19:19:09 <MarkSmith> This past week, Kathy and I posted patches for #13900 and #13406. 19:19:19 <MarkSmith> We also filed #14716 (found while working on #13900, but it is not a regression). 19:19:28 <MarkSmith> Other than that, we did some bug triage, posted our January status report, and signed a new TPI contract. 19:19:35 <MarkSmith> This week we plan to write some mochitest tests for #13900. 19:19:42 <MarkSmith> We will also work on some these bugs: #13271, #14631. 19:19:49 <MarkSmith> We can also help with #14392 if needed. 19:19:57 <MarkSmith> And we will spend some time on code reviews. 19:20:07 <MarkSmith> That's all for us. 19:22:05 <mikeperry> ok. #14392 might be good to pick up if you have time. I think that #13271 and #14631 are more important though 19:22:22 <MarkSmith> agreed 19:23:10 * arthuredelstein can go next 19:23:19 <mikeperry> I am having second thoughts about #14392. it maybe shouldn't be every tab's homepage due to shoulder surfing concerns, but I think we should fix the url bar and focus behavior perhaps? 19:25:46 <mikeperry> arthuredelstein: go ahead 19:25:49 <arthuredelstein> Last week (and the week before) I posted patches for #14429 and #13670. I also attended the UX sprint and posted some UX-related tickets. This week I plan to write documentation for #14555, finish up a second patch for #13670, and look into #7255. Also, if the profile-switching decision is solid, then this week or next I can start upstreaming patches for https://bugzilla.mozilla.org/show_bug.cgi?id=418986#c39 19:26:34 <arthuredelstein> That's it for me 19:29:42 * sherief is around 19:30:55 <mikeperry> ok, I think perhaps the focus this week should be on code reviews and #13670 and #7255, esp if you want to get them into 4.5a4. perhaps save upstreaming more stuff for next week 19:31:30 <MarkSmith> regarding #14392, we could also set browser.newtab.url to about:blank (if we just want to avoid showing about:newtab) 19:31:37 <arthuredelstein> Yes. 19:32:38 <msvb-lab> ...and leave the new window default url about:tor, just happens once. 19:32:56 <mikeperry> I am not sure about:newtab is bad, per-se. I was just thinking about:tor may be better? 19:34:23 <MarkSmith> I don't know what most people would prefer. 19:34:51 <mikeperry> what is everyone's dev meeting status? arthuredelstein will you be able to make it? 19:35:29 <msvb-lab> I'll attend the last day only. 19:35:30 <MarkSmith> Unfortunately, Kathy and I will not be able to attend 19:37:19 <arthuredelstein> Unfortunately I won't be able to make it either. 19:39:33 <mikeperry> ok. Georg and I will most likely do the roadmapping and try to do some best guesses as to who can do what, when 19:39:59 <mikeperry> oh, we lost sherief already? dag 19:41:03 <mikeperry> ok, well anything else for this week then? 19:41:16 <MarkSmith> it probably makes sense for those of us who will not be at the meeting to set aside some time to review / provide roadmap input immediately after 19:43:48 <mikeperry> yeah 19:44:51 <mikeperry> we will most likely put everything on a new wiki page, and then we can disucss it at the next IRC meeting 19:45:39 <MarkSmith> Also, let us know if it would be helpful for us to be available on irc during specific days / times 19:49:03 <mikeperry> ok. I believe there was some brief discussion of some kind of jitsi conferencing, but we'll see what actually happens 19:51:21 <mikeperry> I think that's it for today then. talk to you later, everyone! 19:51:28 <mikeperry> #endmeeting *baf*