<div>>> <span style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif">To meet the above requirement, we are aliasing the bitbucket site (</span><a href="http://bitbucket.org/openid/connect" style="font-family:arial,sans-serif;font-size:13px;color:rgb(17,85,204)" target="_blank">bitbucket.org/openid/connect</a><span style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif">) to </span><a href="http://hg.openid.net/" style="font-family:arial,sans-serif;font-size:13px;color:rgb(17,85,204)" target="_blank">hg.openid.net</a><span style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif"> </span><span style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif">by CNAME, so that everything can be accessed in</span><span style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif"> </span><a href="http://openid.net/" style="font-family:arial,sans-serif;font-size:13px;color:rgb(17,85,204)" target="_blank">openid.net</a><span style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif"> </span><span style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif">domain. </span></div>
<div><span style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif"><br></span></div><div><span style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif">That is a neat trick. I did find <a href="http://support.google.com/sites/bin/answer.py?hl=en&answer=99448" target="_blank">this article</a> describing a way to do that with the tool we are using as well. What led you to choose the "hq" CNAME? Do you have a suggestion of a CNAME for the AC working group? Or should we start a thread on the AC working group to get suggestions?</span></div>
<br><div class="gmail_quote">On Wed, Jul 25, 2012 at 5:53 PM, Nat Sakimura <span dir="ltr"><<a href="mailto:sakimura@gmail.com" target="_blank">sakimura@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Eric and Greg, <div><br></div><div>In the board meeting, the question about the location of the WG procedural rule on the web site requirement was asked. </div><div>Here is the quotation from the OpenID Process Document ver. 1.5 December 2009. </div>
<div><br></div><div><div><b>4.8 Visibility</b>. All WG documents will be located on the WG webpage (“<b>Webpage</b>”), <u>which will be </u></div><div><u>located at a URL within <a href="http://openid.net" target="_blank">openid.net</a></u>, and all work (administrative and technical) of a WG will be conducted via </div>
<div>the applicable Specification Mailing Lists or at meetings that may be called from time to time. The minutes </div><div>of each meeting and a record of all decisions will be published to the Webpage and the applicable </div>
<div>Specification Mailing List. All WG email lists will be archived, and all WG email archives will be publicly </div><div>visible. The Editor(s) should keep the following current on the Webpage: </div><div><b>(a)</b> WG name and Charter; </div>
<div><b>(b)</b> any standing rules and other adopted procedures; </div><div><b>(c)</b> any applicable meeting schedule and attendance method(s); </div><div><b>(d)</b> anticipated deliverables and delivery dates; </div><div>
<b>(e)</b> list of WG Contributors; </div><div><b>(f)</b> the names and email addresses of Editors and any other functionaries (e.g., secretary); </div><div><b>(g)</b> links to draft and completed WG documents (including the latest WG Specifications); and </div>
<div><b>(h)</b> current announcements (including WG formation, any revisions to the Charter, and any call </div><div>to approve a draft as an Implementers Draft or a Final Specification and applicable deadlines).</div><div>
<br></div><div>Like Account Chooser WG, AB/Connect WG is using an external site to manage the working group works. </div><div>In our case, it is <a href="http://bitbucket.org" target="_blank">bitbucket.org</a>. (It is very handy as it has issues tracking with OpenID login.) </div>
<div>To meet the above requirement, we are aliasing the bitbucket site (<a href="http://bitbucket.org/openid/connect" target="_blank">bitbucket.org/openid/connect</a>) to </div><div><a href="http://hg.openid.net" target="_blank">hg.openid.net</a> by CNAME, so that everything can be accessed in <a href="http://openid.net" target="_blank">openid.net</a> domain. </div>
<div>I am pretty sure that you can do the same with the google sites, so you should do that -> Eric. </div><div><br></div><div>As to the mailing list are concerned, we are using <a href="http://openid.net" target="_blank">openid.net</a> mailman. </div>
<div>However, I am pretty sure again here that you can create a google group under <a href="http://openid.net" target="_blank">openid.net</a> domain. </div><div>(I thought David has setup one. AB/Connect WG predated that so we did not bother to migrate.) Either will be fine. </div>
<div><br></div><div>At the end of the day, the requirement from the process point of view is that it will be able to be accessed as a subdomain of <a href="http://openid.net" target="_blank">openid.net</a>. </div><span><font color="#888888"><div>
<br></div>-- <br>Nat Sakimura (=nat)<div>
Chairman, OpenID Foundation<br><a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>@_nat_en</div><br>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div style="line-height:1.5em;padding-top:10px;margin-top:10px;color:rgb(85,85,85);font-family:sans-serif;font-size:small"><span style="border-top-width:2px;border-right-width:0px;border-bottom-width:0px;border-left-width:0px;border-top-style:solid;border-right-style:solid;border-bottom-style:solid;border-left-style:solid;border-top-color:rgb(213,15,37);border-right-color:rgb(213,15,37);border-bottom-color:rgb(213,15,37);border-left-color:rgb(213,15,37);padding-top:2px;margin-top:2px">Eric Sachs |</span><span style="border-top-width:2px;border-right-width:0px;border-bottom-width:0px;border-left-width:0px;border-top-style:solid;border-right-style:solid;border-bottom-style:solid;border-left-style:solid;border-top-color:rgb(51,105,232);border-right-color:rgb(51,105,232);border-bottom-color:rgb(51,105,232);border-left-color:rgb(51,105,232);padding-top:2px;margin-top:2px"> Senior Product Manager |</span><span style="border-top-width:2px;border-right-width:0px;border-bottom-width:0px;border-left-width:0px;border-top-style:solid;border-right-style:solid;border-bottom-style:solid;border-left-style:solid;border-top-color:rgb(0,153,57);border-right-color:rgb(0,153,57);border-bottom-color:rgb(0,153,57);border-left-color:rgb(0,153,57);padding-top:2px;margin-top:2px"> <a href="mailto:esachs@google.com" target="_blank">esachs@google.com</a> </span></div>
<br>