<div dir="ltr"><div><div><div><div>Thanks for jumping on a quick call Johann, Giorgos and Benjamin. <br><br></div>Per Madalina's update on the <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1324426">bug </a>Lithium is working on an interim fix which is due tomorrow. And, we need to test this interim fix to ensure its done right. <br><br></div><div><br></div>The further steps is for us to meet with Lithium engineering team to identify the right permanent fix and find owners to implement it on Firefox and/or Lithium. If its harder with Lithium folks jumping on a call with us, seems like they are based out of SF and we can have an in person meeting at Mozilla or Lithium office. <br><br></div><div>We'll meet tomorrow and there after to drive this to finish. <br><br></div><div>Madalina - Please propose a check-in meet time for the status. <br></div><div><br></div><div><br>Thanks, <br></div><br></div>Mahe<br><div><div><div><br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 23, 2017 at 11:55 AM, Erin Lancaster <span dir="ltr"><<a href="mailto:elancaster@mozilla.com" target="_blank">elancaster@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">If it's not too late for you, we are in my vidyo room we are on with some other folks. Thank you so much. <br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 23, 2017 at 11:54 AM, Johann Hofmann <span dir="ltr"><<a href="mailto:jhofmann@mozilla.com" target="_blank">jhofmann@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
Sure, I can volunteer as a point of contact and would forward any
bigger questions to the Firefox team.<br>
<br>
Thank you for acting so quickly on this! :)<span class="m_4784966760458993068HOEnZb"><font color="#888888"><br>
<br>
Johann</font></span><div><div class="m_4784966760458993068h5"><br>
<br>
<div class="m_4784966760458993068m_-9060406243525138926moz-cite-prefix">On 23/03/2017 19:34, Erin Lancaster
wrote:<br>
</div>
<blockquote type="cite">
Johann, Dão: Mahe is making progress figuring out who is involved
here and what some next steps should be but we need a single point
of contact on the Firefox engineering team. We don’t have any
specific requests as of yet but can Mahe loop one of you in? If
not, do you have someone else you can suggest?
<div><br>
</div>
<div>Thank you,</div>
<div>Erin <br>
<div>
<blockquote type="cite">
<div>On Mar 23, 2017, at 11:27 AM, Erin Lancaster
<<a href="mailto:elancaster@mozilla.com" target="_blank">elancaster@mozilla.com</a>>
wrote:</div>
<br class="m_4784966760458993068m_-9060406243525138926Apple-interchange-newline">
<div>
<div dir="ltr"><br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Mar 23, 2017 at 10:14
AM, Peter Dolanjski <span dir="ltr"><<a href="mailto:pdolanjski@mozilla.com" target="_blank">pdolanjski@mozilla.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">+Joni</div>
<div class="m_4784966760458993068m_-9060406243525138926HOEnZb">
<div class="m_4784966760458993068m_-9060406243525138926h5">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mar 23, 2017 12:19
PM, "Liz Henry (:lizzard)" <<a href="mailto:ehenry@mozilla.com" target="_blank">ehenry@mozilla.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>This issue is serious
enough that fixing it should be a
high priority for Firefox 52 as well
as a blocking issue for the release
of 53. I see this as breaking a
major user-facing part of our
product. <br>
<br>
</div>
<div>How about this as an
option: walking back to Kitsune
immediately, until the new system is
fixed *and tested* by Firefox QE.
Is that possible and what would it
take to switch back to our working
system? <br>
</div>
<div><br>
</div>
Best<br>
<br>
</div>
Liz<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Mar 23,
2017 at 7:06 AM, Johann Hofmann <span dir="ltr"><<a href="mailto:jhofmann@mozilla.com" target="_blank">jhofmann@mozilla.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div> As mentioned in the
bug, this also affects most
security information such as cert
error pages and the in-content
insecure password warning.<br>
<br>
The fact that it takes a long time
to get this issue fixed does not
speak in favor of the migration. I
would really like to see an
official statement explaining the
reasons we are dropping Kitsune.<br>
<br>
What is unclear to me:<br>
<br>
- Why was the decision to make us
depend on a proprietary
third-party vendor done without
feedback or announcement to any
other part of the organization?<br>
- It seems like there were at not
point any Firefox engineers
involved in this. Why did nobody
cross-check with the Firefox
Owner/Peers?<br>
- No Mozilla developers were
involved in testing the new
platform before it went live.
Testing was done by the marketing
team. I can understand that
resources may be limited for
maintenance, but why was it
decided that no engineers can be
spared to integration test the new
platform?<br>
- Is this decision in line with
the module owners of SUMO?<br>
<br>
Absurdly, the modules page lists
the owners of SUMO as the
maintainers of Kitsune (<a class="m_4784966760458993068m_-9060406243525138926m_-7650790122169310044m_-969050471381021253m_2575385075813207388moz-txt-link-freetext" href="https://wiki.mozilla.org/Modules/All#Sumo" target="_blank">https://wiki.mozilla.org/Modu<wbr>les/All#Sumo</a>). Is
this no longer up to date? I'd
like to think the lack of
communication around this is in
violation of our governance
policies.<span class="m_4784966760458993068m_-9060406243525138926m_-7650790122169310044m_-969050471381021253HOEnZb"><font color="#888888"><br>
<br>
Johann</font></span>
<div>
<div class="m_4784966760458993068m_-9060406243525138926m_-7650790122169310044m_-969050471381021253h5"><br>
<br>
<div class="m_4784966760458993068m_-9060406243525138926m_-7650790122169310044m_-969050471381021253m_2575385075813207388moz-cite-prefix">On
23/03/2017 14:29, Sylvestre
Ledru wrote:<br>
</div>
<blockquote type="cite">
<p>Hello</p>
<p>FWIW, this has
been a very important
source of issue and
frustration for the
release management team
too.</p>
<p>This added some
frictions at the end of
the 52 release cycle.<br>
</p>
<p>Sylvestre<br>
</p>
<br>
<div class="m_4784966760458993068m_-9060406243525138926m_-7650790122169310044m_-969050471381021253m_2575385075813207388moz-cite-prefix">Le
23/03/2017 à 14:26, Dão
Gottwald a écrit :<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>Apparently
in-product links
to SUMO have been
broken in
non-en-US builds
for at least two
weeks:<br>
<br>
<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1324426#c6" target="_blank">https://bugzilla.mozilla.org/s<wbr>how_bug.cgi?id=1324426#c6</a><br>
<br>
</div>
Two weeks passing
without a resolution
to this seems
unacceptable.<br>
<br>
</div>
Why have we switched
SUMO to third-party
software and pulled
our own engineers
without at least
announcing this
decision through the
appropriate channels
(this includes this
mailing list) to allow
people to voice
concerns as to what
this means for our
products?<br>
<br>
</div>
<div>Can we
switch back from
Lithium and resource
SUMO appropriately
again?<br>
</div>
<div><br>
</div>
dao<br>
</div>
<br>
<fieldset class="m_4784966760458993068m_-9060406243525138926m_-7650790122169310044m_-969050471381021253m_2575385075813207388mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
firefox-dev mailing list
<a class="m_4784966760458993068m_-9060406243525138926m_-7650790122169310044m_-969050471381021253m_2575385075813207388moz-txt-link-abbreviated" href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a>
<a class="m_4784966760458993068m_-9060406243525138926m_-7650790122169310044m_-969050471381021253m_2575385075813207388moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/firefox-dev" target="_blank">https://mail.mozilla.org/listi<wbr>nfo/firefox-dev</a>
</pre>
</blockquote>
WIW
</blockquote>
</div></div></div>
______________________________<wbr>_________________
firefox-dev mailing list
<a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi<wbr>nfo/firefox-dev</a>
</blockquote></div>
--
<div class="m_4784966760458993068m_-9060406243525138926m_-7650790122169310044m_-969050471381021253gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div>----
</div>Liz Henry (:lizzard)
</div><div>Firefox Release Manager
</div><a href="mailto:lhenry@mozilla.com" target="_blank">lhenry@mozilla.com</a>
</div></div></div></div>
</div>
______________________________<wbr>_________________
firefox-dev mailing list
<a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi<wbr>nfo/firefox-dev</a>
</blockquote></div></div>
</div></div>
______________________________<wbr>_________________
firefox-dev mailing list
<a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi<wbr>nfo/firefox-dev</a>
</blockquote></div>
</div>
</div></blockquote></div>
</div>
</blockquote>
</div></div></div></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Mahendra Potharaju<br></div></div>
</div>