<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">First, congratulations on this achievement!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’m writing back with my board secretary hat on and adding the marketing committee. Language matters. I’m going to suggest some alternative language to use
in future communications about this, because some of the language below could be misinterpreted in a way that leads people to reach false conclusions and negatively impacts the OpenID Foundation and its reputation.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">In the future, you should probably replace the sentence “</span><span style="font-size:9.5pt">The Google Identity team has open sourced </span><a href="http://openid.github.io/AppAuth-Android/">AppAuth
for Android</a><span style="font-size:9.5pt"> under the OpenID Foundation</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">” with “</span><span style="font-size:9.5pt">The Google Identity team has contributed the open source </span><a href="http://openid.github.io/AppAuth-Android/">AppAuth
for Android</a><span style="font-size:9.5pt"> code to the OpenID Connect working group</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">”. Why? First, because a contribution is always made to specific working group and
not to the Foundation as a whole. Second, because the current language could be misinterpreted as implying an endorsement of this implementation by the OpenID Foundation. The Foundation has to be extremely careful not to create an impression that it is favoring
implementations by one member over those that are created by others. I’m sure you understand that that is critical to the Foundation’s reputation.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Likewise, you need to replace the sentence “</span><span style="font-size:9.5pt">We contributed the code to the OIDF under the foundation's new contributor
license agreement (CLA)</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">” with “</span><span style="font-size:9.5pt">We contributed the code to the OpenID Connect Working Group under the OpenID Foundation’s new contributor
license agreement (CLA)</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">”.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Language matters. Thanks for listening and trying to be more clear in future communications so that accurate perceptions are formed, particularly those that
might reach a wider audience.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> Best wishes,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> -- Mike<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">P.S. How soon can you run the implementation through the RP certification tests?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Openid-specs-ab [mailto:openid-specs-ab-bounces@lists.openid.net]
<b>On Behalf Of </b>William Denniss<br>
<b>Sent:</b> Friday, February 26, 2016 9:58 AM<br>
<b>To:</b> openid-specs-ab@lists.openid.net; Iain McGinniss<br>
<b>Subject:</b> [Openid-specs-ab] Announcing AppAuth for Android, a client SDK for OAuth 2.0 and OpenID Connect<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt">The Google Identity team has open sourced </span><a href="http://openid.github.io/AppAuth-Android/">AppAuth for Android</a><span style="font-size:9.5pt"> under the OpenID Foundation.</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt">AppAuth is a client SDK for OAuth and OpenID Connect that follows the <a href="https://tools.ietf.org/html/draft-ietf-oauth-native-apps" target="_blank">best practices</a> for doing standards-based auth in
apps, including in-built support for <a href="https://tools.ietf.org/html/rfc7636" target="_blank">PKCE</a> and performing user interaction in
<a href="http://developer.android.com/tools/support-library/features.html#custom-tabs">
custom tabs</a> (a feature of Android supported by <a href="https://developer.chrome.com/multidevice/android/customtabs">
Chrome</a>, and open to other browsers).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt">You can fork the <a href="https://github.com/openid/AppAuth-Android" target="_blank">repository</a> on Github, and reference the
<a href="https://bintray.com/openid/net.openid/appauth/view">Maven dependency</a>. Comprehensive <a href="https://openid.github.io/AppAuth-Android/docs/latest/" target="_blank">API docs</a> are available.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt">I gave a <a href="https://www.youtube.com/watch?v=ppeU8yeI_ks" target="_blank">talk</a> at the OpenID Summit Tokyo last year, which outlines some of the motivations behind this effort.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt">We contributed the code to the OIDF under the foundation's new contributor license agreement (CLA). If you/your company have signed the CLA, feel free to contribute by sending a pull request. Currently myself
and my colleague Iain McGinniss are the maintainers, and will review all incoming pull requests.</span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt">Thanks to the contributors on my team: Iain McGinniss, Steven Wright, Alex Chau, and Benjamin Franz for their hard work building the library. To Don Thibeau, John Bradley, Adam Dawes and Mike Leszcz for their guidance and
help getting the OpenID Foundation setup to accept code contributions, Paul Meyer and John Bradley for interop validation, and Andy Zmolek for advocating this best practice in the Android community.</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt">Special thanks to Adam Dawes and Eric Sachs for backing the AppAuth effort.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt"><o:p> </o:p></span></p>
</div>
</div>
</div>
</body>
</html>