<div dir="ltr"><div>Francesco,<br><br></div>This is a temporary solution while our partner Lithium works on a permanent fix. They will be delivering their plan next week tues/wed.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 30, 2017 at 12:37 AM, Francesco Lodolo <span dir="ltr"><<a href="mailto:flod@lodolo.net" target="_blank">flod@lodolo.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Can someone clarify how this scales for localization, given that it<br>
looks like we're hardcoding URL redirects. What happens when we add a<br>
new locale, or the localized article changes (and the URL changes<br>
accordingly)?<br>
<br>
Is this meant only to be a temporary solution?<br>
<span class="HOEnZb"><font color="#888888"><br>
Francesco<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
2017-03-29 20:16 GMT+02:00 Patrick McClard <<a href="mailto:pmcclard@mozilla.com">pmcclard@mozilla.com</a>>:<br>
> No problem. Thanks for the update Florin.<br>
><br>
> On Wed, Mar 29, 2017 at 4:31 PM, Florin Mezei <<a href="mailto:fmezei@mozilla.com">fmezei@mozilla.com</a>> wrote:<br>
>><br>
>> Hi guys,<br>
>><br>
>> Quick update here: Roxana has been working on the script today, and it<br>
>> seems she got pretty much everything set up, and only needs to fix some<br>
>> certificate issue to have it working. We expect to have the test results for<br>
>> you tomorrow, as Roxana had to leave.<br>
>><br>
>> Regards,<br>
>> Florin.<br>
>><br>
>> On Wed, Mar 29, 2017 at 10:33 AM, Florin Mezei <<a href="mailto:fmezei@mozilla.com">fmezei@mozilla.com</a>> wrote:<br>
>>><br>
>>> Thank you Roland! I've forwarded all the information to Roxana from the<br>
>>> Platform QA team, who will have a look at this today.<br>
>>><br>
>>> Regards,<br>
>>> Florin.<br>
>>><br>
>>> On Wed, Mar 29, 2017 at 10:25 AM, Roland moco Tanglao<br>
>>> <<a href="mailto:rtanglao@mozilla.com">rtanglao@mozilla.com</a>> wrote:<br>
>>>><br>
>>>> HI Florin and QA team<br>
>>>><br>
>>>> The URL being redirect to is on PRODUCUCTION NOT on stage so I've<br>
>>>> revised my testing HOW TO appropriately. Please refer to [1] when testing.<br>
>>>><br>
>>>> Cheers!<br>
>>>><br>
>>>> ...Roland<br>
>>>><br>
>>>> [1]<br>
>>>> <a href="https://github.com/rtanglao/rt-li-sumo-redirects/blob/master/how-to-test-6000-redirects.md" rel="noreferrer" target="_blank">https://github.com/rtanglao/<wbr>rt-li-sumo-redirects/blob/<wbr>master/how-to-test-6000-<wbr>redirects.md</a><br>
>>>><br>
>>>> From Case 00137762<br>
>>>><br>
>>>> Note this is automatable (I am 99% sure) via a script. Here is a proof<br>
>>>> of concept in Ruby.<br>
>>>><br>
>>>> 1. For each of the approximately 6100 rows in the spreadsheet at:<br>
>>>><br>
>>>> <a href="https://docs.google.com/spreadsheets/d/1bqoCUqsCvdrGTXssavzdadTRF38l8JoIjuEJxqc2QiU/edit#gid=277128454" rel="noreferrer" target="_blank">https://docs.google.com/<wbr>spreadsheets/d/<wbr>1bqoCUqsCvdrGTXssavzdadTRF38l8<wbr>JoIjuEJxqc2QiU/edit#gid=<wbr>277128454</a><br>
>>>><br>
>>>> A. Please test the redirection of the links in Column D to the Target<br>
>>>> URL in Column G as follows:<br>
>>>><br>
>>>> i) In the URL from Column D "Redirect this Link" e.g. row 2<br>
>>>> <a href="https://support.mozilla.org/kb/insecure-password-warning-firefox-ach" rel="noreferrer" target="_blank">https://support.mozilla.org/<wbr>kb/insecure-password-warning-<wbr>firefox-ach</a><br>
>>>> replace support.mozilla with support-stage.allizom e.g. row 2, Column D<br>
>>>> -><br>
>>>><br>
>>>> <a href="https://support-stage.allizom.org/kb/insecure-password-warning-firefox-ach" rel="noreferrer" target="_blank">https://support-stage.allizom.<wbr>org/kb/insecure-password-<wbr>warning-firefox-ach</a><br>
>>>> Let's call this URL 1<br>
>>>> ii) Take the URL from Column G "Target URL" e.g. row 2<br>
>>>> <a href="https://support.mozilla.org/t5/Protect-your-privacy/Insecure-password-warning-in-Firefox/ta-p/27861" rel="noreferrer" target="_blank">https://support.mozilla.org/<wbr>t5/Protect-your-privacy/<wbr>Insecure-password-warning-in-<wbr>Firefox/ta-p/27861</a><br>
>>>> Let's call this URL 2<br>
>>>> iii) Load URL 1 in Firefox<br>
>>>> iv) If Firefox redirects to URL 2, THEN test PASS ELSE test FAIL<br>
>>>><br>
>>>><br>
>>>> On 3/28/17 9:53 PM, Mahendranadh Potharaju wrote:<br>
>>>><br>
>>>> Status Update :<br>
>>>><br>
>>>> The interim fix is in place on staging server and available for QA to<br>
>>>> test. After QA validation we will roll out changes to production OR based on<br>
>>>> severity of any issues, switch to Kitsune.<br>
>>>><br>
>>>> For the permanent solution :<br>
>>>> Firefox dev team and Lithium dev team had met yesterday and now have a<br>
>>>> good understanding of the issues in this implementation. Lithium dev team is<br>
>>>> going to present a solution by Tuesday(4/4/17) or Wednesday (4/5/17) and we<br>
>>>> will then plan its implementation.<br>
>>>><br>
>>>> Currently we are on course with intermix fix to have the links fixed in<br>
>>>> this week.<br>
>>>><br>
>>>> Thanks everyone for giving this the right attention and bringing it back<br>
>>>> on track.<br>
>>>><br>
>>>> Regards,<br>
>>>><br>
>>>> Mahe<br>
>>>><br>
>>>><br>
>>>> On Fri, Mar 24, 2017 at 11:27 AM, Mahendranadh Potharaju<br>
>>>> <<a href="mailto:mpotharaju@mozilla.com">mpotharaju@mozilla.com</a>> wrote:<br>
>>>>><br>
>>>>> Here is status update from our call this morning<br>
>>>>><br>
>>>>> Current Action Items :<br>
>>>>><br>
>>>>> Joni is working on the links and will hand over to Lithium for the<br>
>>>>> migration by eod Friday 3/24.<br>
>>>>> Lithium should be able to complete migration on Tuesday 3/28<br>
>>>>> QA team has been reached to plan testing the SUMO links on Wednesday<br>
>>>>> 3/29<br>
>>>>><br>
>>>>> Backup Plan<br>
>>>>><br>
>>>>> Patrick McClard is gauging the work to migrate new content (questions,<br>
>>>>> articles etc) in Lithium since the switch over.<br>
>>>>> Monday, 3/27 -Giorgos will provide a time estimate to stand up Kitsune<br>
>>>>> again and the DNS change<br>
>>>>> If Lithium isn't able to migrate links in time or QA team fails the<br>
>>>>> migration, we will switch over to Kitsune and figure out next course of<br>
>>>>> action with Lithium.<br>
>>>>><br>
>>>>><br>
>>>>> There seems to be few more links from <a href="http://mozilla.org" rel="noreferrer" target="_blank">mozilla.org</a> and other sites which<br>
>>>>> could be broken. Am reaching David Tenser to see who can help here to<br>
>>>>> identify and how we can fix.<br>
>>>>><br>
>>>>> Alex and Jascha are in contact with Lithium folks and are helping<br>
>>>>> getting the necessary attention and resources.<br>
>>>>><br>
>>>>> We will do daily check-ins and intend to have the links all up next<br>
>>>>> week. Feel free to reach back with any questions.<br>
>>>>><br>
>>>>> Thanks,<br>
>>>>><br>
>>>>> Mahe<br>
>>>>><br>
>>>>> On Thu, Mar 23, 2017 at 1:51 PM, Giorgos Logiotatidis<br>
>>>>> <<a href="mailto:giorgos@mozilla.com">giorgos@mozilla.com</a>> wrote:<br>
>>>>>><br>
>>>>>> + Benjamin Sternthal<br>
>>>>>><br>
>>>>>><br>
>>>>>> Madalina Ana writes:<br>
>>>>>><br>
>>>>>> > + Patrick and rest of the SUMO staff<br>
>>>>>> ><br>
>>>>>> > Just to clarify, we're due to finalize the spreadsheets tomorrow and<br>
>>>>>> > send<br>
>>>>>> > for implementation, implementation might take a few days longer.<br>
>>>>>> ><br>
>>>>>> > Let's check-in tomorrow 8:45 Am Pacific, I'll send out an invite.<br>
>>>>>> ><br>
>>>>>> > We're working on getting proper contacts for Lithium dev so that we<br>
>>>>>> > can<br>
>>>>>> > connect you.<br>
>>>>>> ><br>
>>>>>> > I'll be offline for the rest of today as I'm in CET, if you need any<br>
>>>>>> > follow-up today please reach out to Patrick.<br>
>>>>>> ><br>
>>>>>> > Thanks,<br>
>>>>>> ><br>
>>>>>> > Madalina<br>
>>>>>> ><br>
>>>>>> > On Thu, Mar 23, 2017 at 9:06 PM, Mahendranadh Potharaju <<br>
>>>>>> > <a href="mailto:mpotharaju@mozilla.com">mpotharaju@mozilla.com</a>> wrote:<br>
>>>>>> ><br>
>>>>>> >> Thanks for jumping on a quick call Johann, Giorgos and Benjamin.<br>
>>>>>> >><br>
>>>>>> >> Per Madalina's update on the bug<br>
>>>>>> >> <<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1324426" rel="noreferrer" target="_blank">https://bugzilla.mozilla.org/<wbr>show_bug.cgi?id=1324426</a>><wbr>Lithium is<br>
>>>>>> >> working<br>
>>>>>> >> on an interim fix which is due tomorrow. And, we need to test this<br>
>>>>>> >> interim<br>
>>>>>> >> fix to ensure its done right.<br>
>>>>>> >><br>
>>>>>> >><br>
>>>>>> >> The further steps is for us to meet with Lithium engineering team<br>
>>>>>> >> to<br>
>>>>>> >> identify the right permanent fix and find owners to implement it on<br>
>>>>>> >> Firefox<br>
>>>>>> >> and/or Lithium. If its harder with Lithium folks jumping on a call<br>
>>>>>> >> with us,<br>
>>>>>> >> seems like they are based out of SF and we can have an in person<br>
>>>>>> >> meeting at<br>
>>>>>> >> Mozilla or Lithium office.<br>
>>>>>> >><br>
>>>>>> >> We'll meet tomorrow and there after to drive this to finish.<br>
>>>>>> >><br>
>>>>>> >> Madalina - Please propose a check-in meet time for the status.<br>
>>>>>> >><br>
>>>>>> >><br>
>>>>>> >> Thanks,<br>
>>>>>> >><br>
>>>>>> >> Mahe<br>
>>>>>> >><br>
>>>>>> >><br>
>>>>>> >> On Thu, Mar 23, 2017 at 11:55 AM, Erin Lancaster<br>
>>>>>> >> <<a href="mailto:elancaster@mozilla.com">elancaster@mozilla.com</a>><br>
>>>>>> >> wrote:<br>
>>>>>> >><br>
>>>>>> >>> If it's not too late for you, we are in my vidyo room we are on<br>
>>>>>> >>> with some<br>
>>>>>> >>> other folks. Thank you so much.<br>
>>>>>> >>><br>
>>>>>> >>> On Thu, Mar 23, 2017 at 11:54 AM, Johann Hofmann<br>
>>>>>> >>> <<a href="mailto:jhofmann@mozilla.com">jhofmann@mozilla.com</a>><br>
>>>>>> >>> wrote:<br>
>>>>>> >>><br>
>>>>>> >>>> Sure, I can volunteer as a point of contact and would forward any<br>
>>>>>> >>>> bigger<br>
>>>>>> >>>> questions to the Firefox team.<br>
>>>>>> >>>><br>
>>>>>> >>>> Thank you for acting so quickly on this! :)<br>
>>>>>> >>>><br>
>>>>>> >>>> Johann<br>
>>>>>> >>>><br>
>>>>>> >>>><br>
>>>>>> >>>> On 23/03/2017 19:34, Erin Lancaster wrote:<br>
>>>>>> >>>><br>
>>>>>> >>>> Johann, Dão: Mahe is making progress figuring out who is involved<br>
>>>>>> >>>> here<br>
>>>>>> >>>> and what some next steps should be but we need a single point of<br>
>>>>>> >>>> contact on<br>
>>>>>> >>>> the Firefox engineering team. We don’t have any specific requests<br>
>>>>>> >>>> as of yet<br>
>>>>>> >>>> but can Mahe loop one of you in? If not, do you have someone else<br>
>>>>>> >>>> you can<br>
>>>>>> >>>> suggest?<br>
>>>>>> >>>><br>
>>>>>> >>>> Thank you,<br>
>>>>>> >>>> Erin<br>
>>>>>> >>>><br>
>>>>>> >>>> On Mar 23, 2017, at 11:27 AM, Erin Lancaster<br>
>>>>>> >>>> <<a href="mailto:elancaster@mozilla.com">elancaster@mozilla.com</a>><br>
>>>>>> >>>> wrote:<br>
>>>>>> >>>><br>
>>>>>> >>>><br>
>>>>>> >>>><br>
>>>>>> >>>> On Thu, Mar 23, 2017 at 10:14 AM, Peter Dolanjski <<br>
>>>>>> >>>> <a href="mailto:pdolanjski@mozilla.com">pdolanjski@mozilla.com</a>> wrote:<br>
>>>>>> >>>><br>
>>>>>> >>>>> +Joni<br>
>>>>>> >>>>><br>
>>>>>> >>>>> On Mar 23, 2017 12:19 PM, "Liz Henry (:lizzard)"<br>
>>>>>> >>>>> <<a href="mailto:ehenry@mozilla.com">ehenry@mozilla.com</a>><br>
>>>>>> >>>>> wrote:<br>
>>>>>> >>>>><br>
>>>>>> >>>>>> This issue is serious enough that fixing it should be a high<br>
>>>>>> >>>>>> priority<br>
>>>>>> >>>>>> for Firefox 52 as well as a blocking issue for the release of<br>
>>>>>> >>>>>> 53. I see<br>
>>>>>> >>>>>> this as breaking a major user-facing part of our product.<br>
>>>>>> >>>>>><br>
>>>>>> >>>>>> How about this as an option: walking back to Kitsune<br>
>>>>>> >>>>>> immediately,<br>
>>>>>> >>>>>> until the new system is fixed *and tested* by Firefox QE. Is<br>
>>>>>> >>>>>> that<br>
>>>>>> >>>>>> possible and what would it take to switch back to our working<br>
>>>>>> >>>>>> system?<br>
>>>>>> >>>>>><br>
>>>>>> >>>>>> Best<br>
>>>>>> >>>>>><br>
>>>>>> >>>>>> Liz<br>
>>>>>> >>>>>><br>
>>>>>> >>>>>> On Thu, Mar 23, 2017 at 7:06 AM, Johann Hofmann<br>
>>>>>> >>>>>> <<a href="mailto:jhofmann@mozilla.com">jhofmann@mozilla.com</a>><br>
>>>>>> >>>>>> wrote:<br>
>>>>>> >>>>>><br>
>>>>>> >>>>>>> As mentioned in the bug, this also affects most security<br>
>>>>>> >>>>>>> information<br>
>>>>>> >>>>>>> such as cert error pages and the in-content insecure password<br>
>>>>>> >>>>>>> warning.<br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>> The fact that it takes a long time to get this issue fixed<br>
>>>>>> >>>>>>> does not<br>
>>>>>> >>>>>>> speak in favor of the migration. I would really like to see an<br>
>>>>>> >>>>>>> official<br>
>>>>>> >>>>>>> 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<br>
>>>>>> >>>>>>> third-party<br>
>>>>>> >>>>>>> vendor done without feedback or announcement to any other part<br>
>>>>>> >>>>>>> of the<br>
>>>>>> >>>>>>> organization?<br>
>>>>>> >>>>>>> - It seems like there were at not point any Firefox engineers<br>
>>>>>> >>>>>>> involved in this. Why did nobody cross-check with the Firefox<br>
>>>>>> >>>>>>> Owner/Peers?<br>
>>>>>> >>>>>>> - No Mozilla developers were involved in testing the new<br>
>>>>>> >>>>>>> platform<br>
>>>>>> >>>>>>> before it went live. Testing was done by the marketing team. I<br>
>>>>>> >>>>>>> can<br>
>>>>>> >>>>>>> understand that resources may be limited for maintenance, but<br>
>>>>>> >>>>>>> why was it<br>
>>>>>> >>>>>>> decided that no engineers can be spared to integration test<br>
>>>>>> >>>>>>> the new<br>
>>>>>> >>>>>>> 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<br>
>>>>>> >>>>>>> maintainers of Kitsune<br>
>>>>>> >>>>>>> (<a href="https://wiki.mozilla.org/Modules/All#Sumo" rel="noreferrer" target="_blank">https://wiki.mozilla.org/<wbr>Modules/All#Sumo</a>).<br>
>>>>>> >>>>>>> Is this no longer up to date? I'd like to think the lack of<br>
>>>>>> >>>>>>> communication<br>
>>>>>> >>>>>>> around this is in violation of our governance policies.<br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>> Johann<br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>> On 23/03/2017 14:29, Sylvestre Ledru wrote:<br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>> Hello<br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>> FWIW, this has been a very important source of issue and<br>
>>>>>> >>>>>>> frustration<br>
>>>>>> >>>>>>> for the release management team too.<br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>> This added some frictions at the end of the 52 release cycle.<br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>> Sylvestre<br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>> Le 23/03/2017 à 14:26, Dão Gottwald a écrit :<br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>> Apparently in-product links to SUMO have been broken in<br>
>>>>>> >>>>>>> non-en-US<br>
>>>>>> >>>>>>> builds for at least two weeks:<br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>> <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1324426#c6" rel="noreferrer" target="_blank">https://bugzilla.mozilla.org/<wbr>show_bug.cgi?id=1324426#c6</a><br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>> Two weeks passing without a resolution to this seems<br>
>>>>>> >>>>>>> unacceptable.<br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>> Why have we switched SUMO to third-party software and pulled<br>
>>>>>> >>>>>>> our own<br>
>>>>>> >>>>>>> engineers without at least announcing this decision through<br>
>>>>>> >>>>>>> the appropriate<br>
>>>>>> >>>>>>> channels (this includes this mailing list) to allow people to<br>
>>>>>> >>>>>>> voice<br>
>>>>>> >>>>>>> concerns as to what this means for our products?<br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>> Can we switch back from Lithium and resource SUMO<br>
>>>>>> >>>>>>> appropriately again?<br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>> dao<br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>> ______________________________<wbr>_________________<br>
>>>>>> >>>>>>> firefox-dev mailing<br>
>>>>>> >>>>>>> listfirefox-dev@mozilla.<wbr>orghttps://<a href="http://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">mail.mozilla.org/<wbr>listinfo/firefox-dev</a><br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>> WIW<br>
>>>>>> >>>>>>><br>
>>>>>> >>>>>>> ______________________________<wbr>_________________ firefox-dev<br>
>>>>>> >>>>>>> mailing<br>
>>>>>> >>>>>>> list <a href="mailto:firefox-dev@mozilla.org">firefox-dev@mozilla.org</a> <a href="https://mail.mozilla.org/listi" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi</a><br>
>>>>>> >>>>>>> nfo/firefox-dev<br>
>>>>>> >>>>>><br>
>>>>>> >>>>>> --<br>
>>>>>> >>>>>> ----<br>
>>>>>> >>>>>> Liz Henry (:lizzard)<br>
>>>>>> >>>>>> Firefox Release Manager<br>
>>>>>> >>>>>> <a href="mailto:lhenry@mozilla.com">lhenry@mozilla.com</a><br>
>>>>>> >>>>>> ______________________________<wbr>_________________ firefox-dev<br>
>>>>>> >>>>>> mailing<br>
>>>>>> >>>>>> list <a href="mailto:firefox-dev@mozilla.org">firefox-dev@mozilla.org</a> <a href="https://mail.mozilla.org/listi" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi</a><br>
>>>>>> >>>>>> nfo/firefox-dev<br>
>>>>>> >>>>><br>
>>>>>> >>>>> ______________________________<wbr>_________________ firefox-dev<br>
>>>>>> >>>>> mailing<br>
>>>>>> >>>>> list <a href="mailto:firefox-dev@mozilla.org">firefox-dev@mozilla.org</a> <a href="https://mail.mozilla.org/listi" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi</a><br>
>>>>>> >>>>> nfo/firefox-dev<br>
>>>>>> >>>><br>
>>>>>> >>>><br>
>>>>>> >>><br>
>>>>>> >><br>
>>>>>> >><br>
>>>>>> >> --<br>
>>>>>> >> Mahendra Potharaju<br>
>>>>>> >><br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> --<br>
>>>>> Mahendra Potharaju<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> --<br>
>>>> Mahendra Potharaju<br>
>>>><br>
>>>><br>
>>><br>
>><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> firefox-dev mailing list<br>
> <a href="mailto:firefox-dev@mozilla.org">firefox-dev@mozilla.org</a><br>
> <a href="https://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/<wbr>listinfo/firefox-dev</a><br>
><br>
</div></div></blockquote></div><br></div>