<div dir="ltr"><div><font size="2">Hello humans (not ghosts -- definitely not ghosts!),</font></div><div><font size="2"><br></font></div><div><font size="2">I hope you are all preparing your Hallowe'en costumes.  We held a Mobile Tech Leads meeting on 
Wednesday (NA/AU timezones).</font><font size="2"><span style="color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">  As mentioned in </span><a href="https://lists.mozilla.org/pipermail/android-components/2018-September/000038.html" style="text-decoration:none" target="_blank"><span style="color:rgb(17,85,204);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap">last week’s summary email</span></a><span style="color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">, there has been a very involved discussion about the architecture of Android Components, browser data, and the Sync 1.5 stack being developed by the Application Services team.</span></font></div><div><div id="gmail-:2cb" class="gmail-ii gmail-gt"><div id="gmail-:2cc" class="gmail-a3s gmail-aXjCH"><div dir="ltr"><font size="2"><br></font><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size="2"><span style="color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">I interpret this as a classic “where to set the slider?” question where there are multiple reasonable positions on the continuum between “flexible to solve future problems” and “efficient to solve immediate problems”.  On one side of the slider there is a </span><a href="https://docs.google.com/document/d/1I417io4B5CNwcHFAqlDUu0PDjd1VXXN8nv3Qw1k8Sws/edit" style="text-decoration:none" target="_blank"><span style="color:rgb(17,85,204);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap">document</span></a><span style="color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"> positing that flexibility can be achieved by separating the implementation of storage from the implementation of Sync 1.5.  On the other side of the slider there is a </span><a href="https://docs.google.com/document/d/1jXu0Wd3QciblBUrkBlVMDfDldXp07fGvXygGtf7yUwI/edit" style="text-decoration:none" target="_blank"><span style="color:rgb(17,85,204);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap">document</span></a><span style="color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"> arguing that history shows that storage and Sync 1.5 are best tightly coupled.</span></font></p><font size="2"><br></font><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size="2"><span style="color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Much discussion ensued, and we conclude that the most fruitful way to achieve “rough consensus” is explore the solution space through some “running code” (an </span><a href="https://tools.ietf.org/html/rfc7282" style="text-decoration:none" target="_blank"><span style="color:rgb(17,85,204);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap">aphorism from the IETF</span></a><span style="color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">).  To that end</span></font></p><ul style="margin-top:0pt;margin-bottom:0pt"><li dir="ltr" style="list-style-type:disc;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size="2"><span style="color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Grisha Kruglov is prototyping some “future-oriented” Android Components that want to manage their own storage but still (potentially) be synced across products and devices;</span></font></p></li><li dir="ltr" style="list-style-type:disc;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"><font size="2"><span style="color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"></span><span style="color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Mark Hammond et al are gluing the </span><a href="https://github.com/mozilla/application-services/commit/d754917ca94a2902e7358e0ed21c5094e6aa8f96" style="text-decoration:none" target="_blank"><span style="color:rgb(17,85,204);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap">in-progress application-services Sync 1.5 + history + awesomebar stack</span></a><span style="color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"> into the </span><span style="color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">newly minted <a href="https://github.com/mozilla-mobile/reference-browser">Reference Browser</a></span></font><font size="2"><span style="color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">.<br></span></font></li></ul></div><div class="gmail-adL">
</div></div></div></div><div><font size="2"><br></font></div><div><font size="2">What is the Reference Browser, I hear you say?  "</font><span class="gmail-text-gray-dark gmail-mr-2">A full-featured browser reference implementation using Mozilla Android Component" -- basically, the kitchen sink of example and sample applications, and the place where we'll work through tricky aspects of integrating all of these components.<br></span></div><div><span class="gmail-text-gray-dark gmail-mr-2"><br></span></div><div><span class="gmail-text-gray-dark gmail-mr-2">Until next week,</span></div><div><span class="gmail-text-gray-dark gmail-mr-2">Nick</span></div></div>