In-product SUMO links broken in non-en-US builds

Erin Lancaster elancaster at mozilla.com
Thu Mar 23 18:34:42 UTC 2017


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? 

Thank you,
Erin 
> On Mar 23, 2017, at 11:27 AM, Erin Lancaster <elancaster at mozilla.com> wrote:
> 
> 
> 
> On Thu, Mar 23, 2017 at 10:14 AM, Peter Dolanjski <pdolanjski at mozilla.com <mailto:pdolanjski at mozilla.com>> wrote:
> +Joni
> 
> On Mar 23, 2017 12:19 PM, "Liz Henry (:lizzard)" <ehenry at mozilla.com <mailto:ehenry at mozilla.com>> wrote:
> 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. 
> 
> 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?   
> 
> Best
> 
> Liz
> 
> On Thu, Mar 23, 2017 at 7:06 AM, Johann Hofmann <jhofmann at mozilla.com <mailto:jhofmann at mozilla.com>> wrote:
> As mentioned in the bug, this also affects most security information such as cert error pages and the in-content insecure password warning.
> 
> 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.
> 
> What is unclear to me:
> 
> - 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?
> - It seems like there were at not point any Firefox engineers involved in this. Why did nobody cross-check with the Firefox Owner/Peers?
> - 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?
> - Is this decision in line with the module owners of SUMO?
> 
> Absurdly, the modules page lists the owners of SUMO as the maintainers of Kitsune (https://wiki.mozilla.org/Modules/All#Sumo <https://wiki.mozilla.org/Modules/All#Sumo>). 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.
> 
> Johann
> 
> 
> On 23/03/2017 14:29, Sylvestre Ledru wrote:
>> Hello
>> 
>> FWIW, this has been a very important source of issue and frustration for the release management team too.
>> 
>> This added some frictions at the end of the 52 release cycle.
>> Sylvestre
>> 
>> Le 23/03/2017 à 14:26, Dão Gottwald a écrit :
>>> Apparently in-product links to SUMO have been broken in non-en-US builds for at least two weeks:
>>> 
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1324426#c6 <https://bugzilla.mozilla.org/show_bug.cgi?id=1324426#c6>
>>> 
>>> Two weeks passing without a resolution to this seems unacceptable.
>>> 
>>> 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?
>>> 
>>> Can we switch back from Lithium and resource SUMO appropriately again?
>>> 
>>> dao
>>> 
>>> 
>>> _______________________________________________
>>> firefox-dev mailing list
>>> firefox-dev at mozilla.org <mailto:firefox-dev at mozilla.org>
>>> https://mail.mozilla.org/listinfo/firefox-dev <https://mail.mozilla.org/listinfo/firefox-dev>
>> WIW
> 
> 
> _______________________________________________
> firefox-dev mailing list
> firefox-dev at mozilla.org <mailto:firefox-dev at mozilla.org>
> https://mail.mozilla.org/listinfo/firefox-dev <https://mail.mozilla.org/listinfo/firefox-dev>
> 
> 
> 
> 
> -- 
> ----
> Liz Henry (:lizzard)
> Firefox Release Manager
> lhenry at mozilla.com <mailto:lhenry at mozilla.com>
> 
> _______________________________________________
> firefox-dev mailing list
> firefox-dev at mozilla.org <mailto:firefox-dev at mozilla.org>
> https://mail.mozilla.org/listinfo/firefox-dev <https://mail.mozilla.org/listinfo/firefox-dev>
> 
> 
> _______________________________________________
> firefox-dev mailing list
> firefox-dev at mozilla.org <mailto:firefox-dev at mozilla.org>
> https://mail.mozilla.org/listinfo/firefox-dev <https://mail.mozilla.org/listinfo/firefox-dev>
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/firefox-dev/attachments/20170323/0c233883/attachment.html>


More information about the firefox-dev mailing list