18:01:06 <GeKo> #startmeeting application-team
18:01:06 <MeetBot> Meeting started Mon Oct  5 18:01:06 2015 UTC.  The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:01:06 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
18:01:12 <GeKo> hi folks
18:01:15 <boklm> hi
18:01:17 <GeKo> let's get started
18:01:37 <GeKo> last week a lot of people have been at the dev meeting
18:02:02 <GeKo> we had good discussions about the structure of the furture application team meetings
18:02:15 <sukhe> hi
18:02:25 <GeKo> I've transcribed the most important points here: https://trac.torproject.org/projects/tor/wiki/org/meetings/2015SummerDevMeeting/ApplicationsTeam
18:02:43 <GeKo> if there is something missing in your opinion, please edit the wiki page
18:03:50 <GeKo> i guess i plan to write an email tomorrow to tor-dev explaining the changes for everyone and starting to collect things for the first non Tor Browser application team meeting
18:03:58 <GeKo> we'll see how it goes
18:04:40 <sukhe> sounds good
18:04:56 <GeKo> then i spent some time organizing the workload for Tor Browser in October 2015
18:05:04 <mcs> Are we going to get rid of tbb-dev ?
18:05:14 <GeKo> the most important things can be found on https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&keywords=~TorBrowserTeam201510&sponsor=~SponsorU&col=id&col=summary&col=keywords&col=status&col=owner&col=type&col=priority&order=priority
18:05:42 <GeKo> mcs: no, it is getting back to its original purpose of being a tbb only mailing list
18:05:50 <mcs> OK; makes sense.
18:06:26 <GeKo> only one item for SponsorU is missing (testing related things) which I'll add tomorrow
18:06:35 <GeKo> then I worked on #10599 a bit.
18:07:35 <GeKo> next week I'll try to get our nightly builds going again (fixing #16909) and hope to have some hardened builds by next Monday for testing
18:07:50 <GeKo> there is a bunch of stuff in the review queue, i lan to look at that as well
18:07:56 <GeKo> *plan
18:08:03 <GeKo> that's it for me
18:08:48 * mcs will go next
18:08:54 <mcs> Since our last IRC meeting, I traveled to Berlin, met a lot of great people, and participated in some good face-to-face discussions.
18:08:59 <mcs> Kathy and I also did some bug triage (e.g., #17140) and reviewed #16665.
18:09:08 <mcs> We spent a little time on #16753; for now, we can probably leave that ticket alone.
18:09:13 <mcs> On our plate for the coming weeks:
18:09:18 <mcs> - Help triage new tickets.
18:09:23 <mcs> - Create a fix for #12967.
18:09:29 <mcs> - Create a fix for #16620.
18:09:34 <mcs> - Create a design (and soon a fix) for #16940.
18:09:38 <mcs> That’s all for us.
18:12:07 * arthuredelstein ca go
18:12:10 <arthuredelstein> *can
18:12:25 <arthuredelstein> Since the last IRC meeting, I worked primarily on #17009, #16665, and #17164.
18:12:44 <arthuredelstein> Then I went to the excellent dev meeting.
18:13:07 <arthuredelstein> Over the weekend I worked on https://bugzilla.mozilla.org/show_bug.cgi?id=902580 (a patch for Thunderbird, not related to Tor Browser).
18:13:33 <arthuredelstein> This week I hope to work more on font fingerprinting and window resizing patches.
18:13:48 <arthuredelstein> That's it for me.
18:14:21 * sukhe can go next
18:15:11 <sukhe> at the dev meeting, arlo, boklm and I fixed our build issues for Tor Messenger and were ready to release. there were some last minute branding issues related to the name, so we are rebranding the product as "Unnamed Messenger" (for the lack of a better name)
18:15:20 <sukhe> and we will be making a release at the end of this week
18:15:50 <sukhe> we are not using Tor Messenger as the name because it would imply that this is *the* Tor Messenger, when there are other products out there
18:15:51 <GeKo> why not "Tor Messenger"?
18:16:02 <GeKo> aha
18:16:14 <mcs> ugh (on naming problems)
18:16:40 <sukhe> yeah, we had published the blog post also, had to unpublish it :)
18:16:59 <sukhe> in any case, we are rebranding currently and the release should go out this week.
18:17:21 <GeKo> what are the plans after that?
18:17:48 <sukhe> depends on the feedback we get... we had a long discussion at the meeting and we will update the wiki with the session notes
18:17:58 <sukhe> mostly things like sandboxing, translations, reproducible builds ...
18:18:50 <sukhe> from TorBirdy land: arthuredelstein submitted a patch for a known leak that prevents TorBirdy from shedding the beta tag (thanks arthur!). hoping this gets merged
18:19:18 <sukhe> that's it for Messenger and TorBirdy
18:20:37 * boklm can go next
18:20:43 <arthuredelstein> I think if you capitalize Tor Messenger it is clear that is a name and not claiming to be the only Tor messenger.
18:21:10 <boklm> Last week I went to the tor-dev meeting and was happy to meet many tor people.
18:21:18 <boklm> I helped arlo and sukhe finish an unnamed-messenger beta release (which is now delayed due to last minute name change)
18:21:20 <sukhe> arthuredelstein: I was not at the meeting when this discussion took place but I think the consensus was having "tor" in the name and "Tor Messenger" is a big no
18:21:29 <boklm> Today I started looking at marionette for ticket #16009
18:21:39 <boklm> This week I'm planning to try converting some of our mozmill tests to marionette
18:21:46 <boklm> That's all for me.
18:23:19 <mcs> maybe "A Tor Messenger" :)
18:24:02 <GeKo> ha. who else wants to give a status update?
18:24:35 <GeKo> otherwise, what things should we discuss in the more unstructed part of the meeting?
18:24:40 <tjr> GeKo: I am here actually.
18:24:45 <GeKo> *unstructured
18:24:49 <GeKo> tjr: hi!
18:24:57 <tjr> I'm going to write up the status of #10281 and make sure the code I had is accessible
18:25:10 <GeKo> thanks, this is very helpful
18:25:14 <tjr> but the main takeaway is "Sync with Mozilla about jemalloc3 and their plans"
18:25:28 <GeKo> ok
18:25:34 <tjr> I don't know what the deliverable is for Sponsor U is, or it's timeline though.  Is there a succinct summary of that?
18:27:08 <GeKo> "Deploy builds of Tor Browser using the
18:27:10 <GeKo> PartitionAlloc memory allocator"
18:27:39 <GeKo> but we settled at giving good documentation where we are right now
18:27:46 <huseby> anybody know if there is a trac ticket for making TBB use a domain socket when connecting to a proxy?
18:27:55 <GeKo> and maybe pointing to a test build
18:28:01 <huseby> I just created http://bgz.la/1211567
18:28:08 <GeKo> huseby: there is, let me look
18:28:08 <huseby> and I'm adding to the spreadsheet
18:28:13 <huseby> GeKo: awesome, thanks
18:28:40 <GeKo> #14270
18:28:42 <GeKo> #14271
18:28:45 <tjr> Ah okay.  I think it will be relatively easy to get a build out that randomizes partitions for allocations, but more difficult to have it put specific allocations (like javascript arrays) into specific partitions.
18:28:48 <GeKo> #14272
18:29:28 <GeKo> tjr: for the deliverable the first thing is totally enough
18:29:32 <huseby> GeKo: why are there three?
18:29:45 <GeKo> because we have to adapt these three components
18:30:00 <huseby> and what about #13028 ?
18:30:31 <huseby> i have 13028 on my spreadsheet as "prevent potential proxy bypass cases"
18:31:09 <GeKo> that is unrelated to domain sockets
18:31:12 <huseby> k
18:31:22 <GeKo> i mean we want to be sure there are no leaks on windows as well, right ;)
18:31:29 <GeKo> ?
18:31:46 <huseby> GeKo: so since, I'll be doing just the gecko/necko/proxy stuff, it looks like 14270 is the matching tor trac for bz 1211567 ?
18:31:57 <huseby> GeKo: re: leaks, of course
18:33:47 <GeKo> huseby: maybe. what about https://bugzilla.mozilla.org/show_bug.cgi?id=892114 ?
18:34:12 <GeKo> i think #14273 is more what you want
18:37:30 <huseby> GeKo: so 892114 makes me think that finishing 1211567 might be somewhat trivial
18:37:46 <huseby> just changing the code paths that validate the proxy settings input
18:38:00 <huseby> and adding a case for "if it is a file://" use the domain socket support
18:38:07 <huseby> but of course
18:38:08 <huseby> it's gecko
18:38:10 <huseby> :)
18:38:15 <huseby> so it is *never* that easy
18:38:50 <GeKo> yeah, i had the same hope actually :)
18:40:22 <GeKo> what else do we have?
18:44:12 <GeKo> alright. thanks for attending this meeting *baf*
18:44:17 <GeKo> #endmeeting