July OSCon in Portland - Getting UA in front of developers
One of the larger Open Source developer conferences is called OSCon in Portland, operated by O'Reilly (those books with the various black and white animal pictures on them). The event is July 20-24 in Portland Oregon. Here is the URL: http://www.oscon.com/open-source-2015/public/schedule/grid/public There are quite a number of infosec sessions if you need 'security and stability' justification for budget, but the focus of UA advancement might be helped by being in front of the people who are actually writing the code on the majority of the websites that Internet users are interacting with. In skimming the sessions, this one stood out to me: You type "google.com" into your browser bar and press enter: what happens next? http://www.oscon.com/open-source-2015/public/schedule/detail/41094 Seems to me like participation in events like this would have a large impact. The bad news about UA in the developer community is that there is very little awareness of new TLDs and IDN - the majority of the developers I speak with have little or no awareness of the new TLDs, IDN, or EAI issues. The silver lining to that, which I think is the good news, is that there's really not much that could be done to set UA backwards by participating and elevating awareness of new TLDs. Are there any UA participants that are attending this event to help grow awareness of the IDN TLDs, new TLDs and UA? -Jothan Jothan Frakes Tel: +1.206-355-0230
On 4/15/15, 10:32, "Jothan Frakes" <jothan@jothan.com> wrote:
The bad news about UA in the developer community is that there is very little awareness of new TLDs and IDN - the majority of the developers I speak with have little or no awareness of the new TLDs, IDN, or EAI issues.
To address this, I gave this in early February. That was a shortened version of what I wanted, shortened to fit in to a 15 mins time slot. https://www.nanog.org/sites/default/files/nanog63-dnstrack-lewis-newgtlds.pd f The focus of that (NANOG) was to alert ISPs that they may receive customer tickets related to what amounts to be UA issues. The same base awareness needs to be set for developers (who are not ISP/operators). Should this be added to the ICANN "universalacceptance" page?
Developers are going to need an entirely different resource and dialog... I mean this with kind, loving respect - Most of the audience at Nanog (I am one of them) are essentially the "Security, DNS or router jedi" - the equivalence of characters that the great Harvey Kitel plays in films, like Mr. Wolfe or "The Cleaner" ... They push the broom behind the parade cleaning up what the marketing folk and developers do and stabilize things for secure operational resilience and what not. Totally different message to them about UA. The message to the developer community would be more one of awareness of nTLDs, resources like the IANA PSL (or even the Mozilla one), and "here's how you can best interact with a User Interface and not present errors for valid domains", TLD handling, IDNA, and other things that they'll care about. Separately, on the topic of including that presentation on the universalacceptance page - I think that presentation probably helped the audience at nanog (I'm a member, I liked it). The presentation gained the benefit of your narrative, and it was designed to support the narrative rather than be a stand alone document, so someone reading that deck without the benefit of your dialog may get lost in a sea of insider acronyms or terminology. I would defer to others at ICANN on the choice to use it, though it certainly could not hurt to have more. I'd have it be a video with your narrative running through the deck to make things more clear if I ran the world. Jothan Frakes Tel: +1.206-355-0230 On Wed, Apr 15, 2015 at 8:07 AM, Edward Lewis <edward.lewis@icann.org> wrote:
On 4/15/15, 10:32, "Jothan Frakes" <jothan@jothan.com> wrote:
The bad news about UA in the developer community is that there is very little awareness of new TLDs and IDN - the majority of the developers I speak with have little or no awareness of the new TLDs, IDN, or EAI issues.
To address this, I gave this in early February. That was a shortened version of what I wanted, shortened to fit in to a 15 mins time slot.
https://www.nanog.org/sites/default/files/nanog63-dnstrack-lewis-newgtlds.pd...
The focus of that (NANOG) was to alert ISPs that they may receive customer tickets related to what amounts to be UA issues. The same base awareness needs to be set for developers (who are not ISP/operators).
Should this be added to the ICANN "universalacceptance" page?
On 4/15/15, 13:21, "Jothan Frakes" <jothan@jothan.com> wrote:
Developers are going to need an entirely different resource and dialog...
Good and relevant feedback follows - yes, we have to consider the audience. Saying that while myself not intending to attend OScon.
The message to the developer community would be more one of awareness of nTLDs, resources like the IANA PSL (or even the Mozilla one), and "here's how you can best interact with a User Interface and not present errors for valid domains", TLD handling, IDNA, and other things that they'll care about.
You're right that my slides played (pandered) to the NANOG and specifically the DNS sub-culture and is tuned to knowing what I'd be saying on stage. But I'll point out that it seems like the links to the resources later in the slide deck would be a key ingredient in presenting to the developer community, i.e., the "CSV" of the class-of-2012 TLDs. E.g., I think slide 12 (not sure if I'm referring to my as-used deck or a draft): ¤ Want to know what TLD is coming? https://newgtlds.icann.org/newgtlds.csv Looking at the other URLs, they are focused on what operators would need to use in NOC operations. Perhaps there is not a lot of reusable portions - other than the idea that developers need to get some "plain facts" about the roll out (the chart showing the years) so they know this is an on-going process, etc. Beyond that, the needs of developers and code distributors/software engineers differs from the operators. (If you've ever come across "devops" you'd find that unsurprising.)
The presentation gained the benefit of your narrative, and it was designed to support the narrative rather than be a stand alone document, so someone reading that deck without the benefit of your dialog may get lost in a sea of insider acronyms or terminology. I would defer to others at ICANN on the choice to use it, though it certainly could not hurt to have more. I'd have it be a video with your narrative running through the deck to make things more clear if I ran the world.
Good suggestion. Especially here when I had to cut the deck down to fit the time allotted, so it isn't stand-alone capable.
participants (2)
-
Edward Lewis -
Jothan Frakes