<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi all,<div class=""><br class=""></div><div class="">I’ve set up a few things for the Working Group. The first is the holding page for rendered specifications:</div><div class=""><br class=""></div><div class=""><a href="http://openid.bitbucket.org/HEART/" class="">http://openid.bitbucket.org/HEART/</a></div><div class=""><br class=""></div><div class="">This has the three currently-started security specs up there, rendered into HTML format, in their current-as-of-today alpha state. It’s a manual process to render and upload new versions, so this won’t always be in sync with the XML files in the repository. We’ll use this page when we’ve got a substantive “revision” to publish. I’m personally in favor of the IETF model where revision numbers are cheap, so let’s not quarrel about what makes a “revision” or not.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Second, I set up an issue tracker within bitbucket for us to use:</div><div class=""><br class=""></div><div class=""><a href="https://bitbucket.org/openid/heart/issues?status=new&status=open" class="">https://bitbucket.org/openid/heart/issues?status=new&status=open</a></div><div class=""><br class=""></div><div class="">Make sure you tag the appropriate component when reporting an issue. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Third, I’ve deleted the old mercurial-based repository since it looked like everything was up and running just fine in the new git-based one. I don’t think anyone’s going to notice its absence, but if there’s something in the git repo that’s missing (including the wiki), it will have to get re-added.</div><div class=""><br class=""></div><div class=""> — Justin</div></body></html>