W3C home > Mailing lists > Public > public-webcrypto@w3.org > March 2014

[W3C Web Crypto WG] Early alpha announce: PubRules Checker NG

From: GALINDO Virginie <Virginie.GALINDO@gemalto.com>
Date: Tue, 18 Mar 2014 11:16:14 +0100
To: Arun Ranganathan <arun@mozilla.com>, Mark Watson <watsonm@netflix.com>, Ryan Sleevi <sleevi@google.com>
CC: "public-webcrypto@w3.org" <public-webcrypto@w3.org>, Robin Berjon <robin@w3.org>
Message-ID: <239D7A53E5B17B4BB20795A7977613A40207D8ED4CAA@CROEXCFWP04.gemalto.com>
Dear editors,
We have now a new version for pubrules checking, see below.
Hope you will enjoy it.
Robin would be happy to hear your feedback when trying it.
Regards,
Virginie


-----Original Message-----
From: Robin Berjon [mailto:robin@w3.org]
Sent: lundi 17 mars 2014 17:38
To: Chairs
Subject: Early alpha announce: PubRules Checker NG

Dear chairs,

I've just sent the message below to spec-prod[0] which introduces the next-generation pubrules checker that we've been working on.

We invite you to bring this to the attention of your editors, and we'd be very interested in hearing feedback about it.

Thanks!

[0] http://lists.w3.org/Archives/Public/spec-prod/2014JanMar/0035.html


===

Hi,

you are all, of course, familiar with your dear old best frenemy the Pubrules Checker. For a variety of reasons, the W3C team have decided to give it an overhaul in order to make it easier to maintain and to provide it with newer features over time.

The new version is not yet production-ready, but it is starting to take shape and as such we would like to invite you to start using it. We would really like to make it as easy as possible for editors to get their documents published, and as such your feedback in the early stages of this new tool would be very useful.

If you feel daring, you can even try to use it as your primary pubrules checker, just be sure to tell the webmaster that you used the new checker when requesting publication.

You can find the new checker running here:

     http://pubrules.jit.su/


We naturally welcome not only feedback but also patches (well, pull
requests) from the community. You can fork the code from here:

     https://github.com/w3c/specberus


The same repository contains the issues, feel free to report any you find there (be they functional or UI):

     https://github.com/w3c/specberus/issues


Please keep in mind that this is alpha software. Sometimes, it crashes.
When that happens, the page won't disappear on you or show an error: you will just notice that the checking stops progressing (or doesn't even start). In such cases, please don't press the "Run" button twenty times in a row as that will just make things worse (if there are too many crashes in a short period of time, the service is just stopped until I manually restart it — obviously that won't be the case with the final deployment, this is just a temporary measure to avoid it spinning out of control while in development mode).

Also note that the last checks (internal link integrity, HTML validation, CSS validation) can take more time than the other checks, especially on large documents.

We plan to run this experiment for a month, starting now. Based on the number and severity of issues that surface we will formulate a timetable for the final transition from the current pubrules to the new one.

We hope you enjoy the tool and tell us everything that's wrong with it!

PS: For you ReSpec users out there, once this is deployed there will also be a way in ReSpec to run pubrules on your document directly, without having to generate and upload it. Stay tuned!

--
Robin Berjon - http://berjon.com/ - @robinberjon


This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus
Received on Tuesday, 18 March 2014 10:16:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:17:22 UTC