Michele, I agree and I think the concern with developer response is appropriate, but we really have to be authentic with ourselves as to why that is. It is reciprocal to that with ICANN gives. My experience with developers/developer communities, is that it is necessary to engage appropriately in their world for results to happen. While it is improving, we still don't have ICANN presence at developer conferences like OSCON, WWDC, Etc from ICANN, or if we do, it is a 'meh' participation, and thus a reciprocal and diminished relevance and ability to inspire response and action to things ICANN publishes. I noticed a lot of traction with Mozilla when I put in time with that community and take the time to inspire, educate, and evangelize the added value of action. Otherwise, there are a number of things like security patches and keeping up with critical standards or other resource spends take priority. As the comms and resourcing improves, I hope also that the participation of ICANN in developer events increases, which will have higher potential for impact. -Jothan Jothan Frakes Tel: +1.206-355-0230 On Fri, Sep 1, 2017 at 4:29 AM, Michele Neylon - Blacknight < michele@blacknight.com> wrote:
Don et al
Some really interesting data in these docs.
The lack of engagement / response from developers with respect to issues raised with them is concerning.
Regards
Michele
--
Mr Michele Neylon
Blacknight Solutions
Hosting, Colocation & Domains
Intl. +353 (0) 59 9183072 <+353%2059%20918%203072>
Direct Dial: +353 (0)59 9183090 <+353%2059%20918%203090>
Personal blog: https://michele.blog/
Some thoughts: https://ceo.hosting/
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845
*From: *<ua-discuss-bounces@icann.org> on behalf of Don Hollander < don.hollander@icann.org> *Date: *Thursday 31 August 2017 at 01:19 *To: *"ua-discuss@icann.org" <ua-discuss@icann.org> *Subject: *[UA-discuss] Pending Documents for Publication
Please find attached documents for final comments before we publish:
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.
04c – a look at the issues that have been raised through our UA Complaints process and their resolution. Short answer, not too many raised and even fewer resolved by the website developer
04d – A look at Websites and how UA Ready they are. Good news – 7% accepted all names and just 7% accepted none of our sample set. Bad news, just 7% accepted all names.
04g – UASG Programming Language Evaluation Criteria
06a – Revised UASG010 – Quick Guide to Linkification
06b – Revised UASG014 – Quick Guide to EAI
Don