<div dir="ltr"><div>Please don't take the following as a response from Mozilla, as I do not represent them or speak on their behalf, but I can 99% forecast next steps here and make some suggestions based upon the time I have invested in being a volunteer with them...</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px">The reference for Mozilla seems to have been unch</span><span class="gmail-aBn" tabindex="0" style="font-size:12.8px"><span class="gmail-aQJ">anged in 8</span></span><span style="font-size:12.8px"> years, which is a long time. Do you know if anyone at Mozilla has actually looked at the issue since then? In particular, I tried changing the settings as described there, to allow the open dot, and it didn't.</span></blockquote><div>@Chaals as a member of the community, would you update that stale wiki to align it with how it currently works? Clearly, it is likely the wiki has not been updated in a while due to resourcing or prioritization, and it obviously has older information that has become incorrect with the evolution of the actual function/behaviour.<br><br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px">I'm on Mozilla's Policy Advisory Board, </span></blockquote><div>@Christian I am impressed with how many hats you wear. What do you NOT do in this industry, man? Thank you for all you do. We're all better off for it.<br><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px">if you want me to try to escalate it. We just need to narrow things down to a simple, discrete ask.</span></blockquote>I agree that narrowing things down to simple discrete ask can help -<b> I think resourcing Mozilla would be even more effective towards goal.<br></b><br><b>The best path forward would most likely be ICANN-employed UA developers participating by supplying developers to projects as members of mozilla community and tackling these issues from within. </b><br>(Perhaps coordination with Gerv Markham, who I connected Don with, and your PAB affiliations would allow that to evolve?)<div><br></div><div>Next best (current suggested) is conforming our 'ask' process using their ticketing system to submit issues into the appropriate conduits for attention from the community volunteers and developers - this is how they do business and manage these tens of thousands of development volunteers globally.<br><br>if you could work your politically-smooth mojo in a way that brings the ask in a different conduit than I have been using... I suspect it will still flow into the same ultimate constraint point and system that currently have any tickets that have been submitted - or will be directed to do so..<br><br>I would just recommend to be cognizant of coming across as over-assertive in our asks if we're flowing it through >1 management chain into the same (current) constrained resource(s). <br><br>I don't think the effect would be a punitive reaction, but it could be counterproductive if the matter moves from its current state of 'we know this is important to do and have an eye to do it when possible' over to a 'into the bucket with everything else'. <br>It is a common theme within the development community at large - certainly irritating to volunteers to have yet more pressure/work while under-resourced to be reminded of it again by yet another "manager" - help them help you (hence the resourcing suggestion).<br><br>Their ticketing system takes time to understand and work with, and you do not always get what you asked for, but it is the mechanism in place to flow the myriad of requests for a myriad of bugfix/feature requests to be submitted to a myriad of geometrically distributed volunteer developers. <br><br>Just like humans have to work the paid workers at the DMV for their process for their drivers license or have to follow ICANN's mixture of paid staff/volunteer resourced flow and process for new TLDs or other needs, so unto us is the Mozilla ticket system for having their majority-volunteer-resources address things. <br><br></div></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><br>Jothan Frakes<br>Tel: +1.206-355-0230<br><br></div></div></div>
<br><div class="gmail_quote">On Thu, Aug 31, 2017 at 1:22 PM, Christian Dawson <span dir="ltr"><<a href="mailto:dawson@i2coalition.com" target="_blank">dawson@i2coalition.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"><div>I'm on Mozilla's Policy Advisory Board, if you want me to try to escalate it. We just need to narrow things down to a simple, discrete ask.<br><br><div><span style="background-color:rgba(255,255,255,0)">Christian Dawson</span></div><div style="margin:0cm 0cm 0.0001pt"><i><span style="background-color:rgba(255,255,255,0)">Executive Director<u></u><u></u></span></i></div><div style="margin:0cm 0cm 0.0001pt"><span style="background-color:rgba(255,255,255,0)">Internet Infrastructure Coalition (i2C)<u></u><u></u></span></div><div style="margin:0cm 0cm 0.0001pt"><span style="background-color:rgba(255,255,255,0)">c: <a href="tel:703%20623%202612" target="_blank">703 623 2612</a></span></div><div style="margin:0cm 0cm 0.0001pt"><span><span style="background-color:rgba(255,255,255,0)"><a href="http://i2coalition.com/" target="_blank">http://i2coalition.com</a></span></span></div><div style="margin:0cm 0cm 0.0001pt"><span style="background-color:rgba(255,255,255,0)"><br></span></div><div style="margin:0cm 0cm 0.0001pt"><span style="background-color:rgba(255,255,255,0)"><span>PGP: </span><font><span>22DF5493</span></font></span></div><div style="margin:0cm 0cm 0.0001pt"><span style="background-color:rgba(255,255,255,0)"><span>Fingerprint: </span><font><span>7C95 A3BE 1E10 <a href="tel:4864%208417" target="_blank">4864 8417</a> DCED B9E1 C8FD 22DF 5493</span></font></span></div></div><div><div class="h5"><div><br>On Aug 31, 2017, at 3:50 PM, Don Hollander <<a href="mailto:don.hollander@icann.org" target="_blank">don.hollander@icann.org</a>> wrote:<br><br></div><blockquote type="cite"><div><span>We did have some engagement with Mozilla facilitated by Jothan. But their response was for us to file a bug report. </span><br><span></span><br><span>Don</span><br><span></span><br><span></span><br><blockquote type="cite"><span>On 1/09/2017, at 12:27 AM, chaals is Chaals McCathie Nevile <<a href="mailto:chaals@yandex.ru" target="_blank">chaals@yandex.ru</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>On Thu, 31 Aug 2017 02:18:54 +0200, Don Hollander <<a href="mailto:don.hollander@icann.org" target="_blank">don.hollander@icann.org</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>04a – A review of popular browsers for UA Readiness – Spoiler alert – most are OK, but few >handle the open dot or IDNs as we expect them to. Some browser developers may see this >as a feature and not a bug.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>The document says there is no W3C document talking about open dot. I am pretty sure you are right about that - in general W3C defers to IETF RFCs for URL definitions, having abandoned its own work on them a few years ago.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>The reference for Mozilla seems to have been unchanged in 8 years, which is a long time. Do you know if anyone at Mozilla has actually looked at the issue since then? In particular, I tried changing the settings as described there, to allow the open dot, and it didn't.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>cheers</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>-- </span><br></blockquote><blockquote type="cite"><span>Chaals is Charles McCathie Nevile</span><br></blockquote><blockquote type="cite"><span>find more at <a href="http://yandex.com" target="_blank">http://yandex.com</a></span><br></blockquote><span></span><br><span>Don Hollander</span><br><span>Universal Acceptance Steering Group</span><br><span>Skype: don_hollander</span><br><span></span><br><span></span><br><span></span><br></div></blockquote></div></div></div></blockquote></div><br></div>