<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>All,<br></div><div>Per the discussion in the last couple Forum calls, Infrastructure is planning to migrate the Forum website (<a href="http://www.cabforum.org">www.cabforum.org</a>) from Wordpress hosting over to a GitHub-hosted static site. This email is to provide you with some information about this transition and what it will mean for you.<br></div><div><br></div><div><b>When will this change occur?</b><b><br></b></div><div>We will be changing DNS at <b>15:00 Eastern today (7 February)</b>. This is being done quickly in order to allow time to propagate the change before the weekend, and season/test the change well before the face-to-face takes place.<br></div><div><br></div><div><b>What change will we be making?</b><b><br></b></div><div>The Infrastructure team will be changing DNS so that <a href="http://www.cabforum.org">www.cabforum.org</a> becomes a pointer to our GitHub Pages hosted repository (<a href="https://github.com/cabforum/cabforum.org/">https://github.com/cabforum/cabforum.org/</a>). Our DNS configuration is set so that this change will propagate to our AWS DNS service within 60 seconds, and then global DNS has a TTL (time-to-live) of ten minutes on the DNS record — this means that within 20 minutes of making the change, the cutover to the new site should be complete. Local DNS servers may take longer, however.<br></div><div><br></div><div><b>Will that cause issues or outages?</b><b><br></b></div><div>No. We will not be removing our previous website, so during the DNS cutover access will go to the previous site until DNS updates. There may be a brief window where the new website does not yet have a TLS certificate (owing to domain validation rules); however, this period should be smaller than the ten-minute TTL on DNS, meaning most users will not notice it.<br></div><div><br></div><div><b>How do I use the new site?</b><b><br></b></div><div>Instructions for authoring and publishing content are documented both on the new website:<br></div><div> <a href="https://github.com/cabforum/cabforum.org/">https://github.com/cabforum/cabforum.org/</a><br></div><div>And on the wiki:<br></div><div> <a href="https://wiki.cabforum.org/books/infrastructure/page/publishing-to-the-static-cabf-website">https://wiki.cabforum.org/books/infrastructure/page/publishing-to-the-static-cabf-website</a><br></div><div>The short version is that users will now author website pages in Markdown, and then commit them to the website repository in Git. To publish the changes, create a pull request which will then be routed to the appropriate chair or team for review and approval.<br></div><div><br></div><div><b>Who should I contact if I have issues?</b><b><br></b></div><div>You are welcome to contact any member of the Forum Infrastructure Subcommittee, but in particular the following have volunteered as contacts for this change and the publication process afterwards:<br></div><ul><li>Paul van Brouwershaven<br></li><li>Jos Purvis<br></li><li>Ben Wilson<br></li></ul><div>Thanks!</div></body></html>