Re: Pubrules: Use https for /TR documents

Mike West <[email protected]> Mon, 1 Aug 2016 11:20:49 +0200
Newsgroups gmane.org.w3c.specifications
Message-ID <CAKXHy=f5FTiOQ2Ofhy8xWOuPhhbCAGZvXSroribd9285kzaU+g@mail.gmail.com>
--001a114024bcf240680538ff1ef0
Content-Type: text/plain; charset=UTF-8

On Mon, Aug 1, 2016 at 9:14 AM, Denis Ah-Kang <[email protected]> wrote:

> The day has finally come. With the official release of the new
> pubrules [1], we now require people to switch the TR links to https.
> The spec generators like Bikeshed and Respec have been updated to handle
> that switch so if you are using these tools, you probably have nothing
> to do.
> As usual, if you want to make sure your documents are ready to be
> published, you should check them with pubrules [2].
>
> Feel free to report issues on irc (#pub) or github [3].


Thanks for getting this done!

I filed https://github.com/tabatkins/bikeshed/issues/767 against Bikeshed
to correct one error I found (and update WebAppSec's templates), but was
otherwise able to publish an update to https://www.w3.org/TR/CSP3/ this
morning without issue.

As an aside, the only link in the boilerplate that can't currently be
converted to HTTPS is http://ev.buaa.edu.cn/; perhaps y'all could chat with
the folks at Beihang?

Thanks again!

-mike

--001a114024bcf240680538ff1ef0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>On Mon, Aug 1, 2016 at 9:14 AM, Denis Ah-Kang <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]=
rg</a>&gt;</span> wrote:<br></div><div class=3D"gmail_extra"><div class=3D"=
gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The day has =
finally come. With the official release of the new<br>
pubrules [1], we now require people to switch the TR links to https.<br>
The spec generators like Bikeshed and Respec have been updated to handle<br=
>
that switch so if you are using these tools, you probably have nothing<br>
to do.<br>
As usual, if you want to make sure your documents are ready to be<br>
published, you should check them with pubrules [2].<br>
<br>
Feel free to report issues on irc (#pub) or github [3].</blockquote><div><b=
r></div><div>Thanks for getting this done!</div><div><br></div><div>I filed=
 <a href=3D"https://github.com/tabatkins/bikeshed/issues/767">https://githu=
b.com/tabatkins/bikeshed/issues/767</a> against Bikeshed to correct one err=
or I found (and update WebAppSec&#39;s templates), but was otherwise able t=
o publish an update to=C2=A0<a href=3D"https://www.w3.org/TR/CSP3/">https:/=
/www.w3.org/TR/CSP3/</a> this morning without issue.</div><div><br></div><d=
iv>As an aside, the only link in the boilerplate that can&#39;t currently b=
e converted to HTTPS is=C2=A0<a href=3D"http://ev.buaa.edu.cn/">http://ev.b=
uaa.edu.cn/</a>; perhaps y&#39;all could chat with the folks at Beihang?</d=
iv><div><br></div><div>Thanks again!</div><div><br></div><div>-mike</div></=
div></div></div>

--001a114024bcf240680538ff1ef0--