tripu

@r12a, w3c/specberus#143 is pending clarification from @plehegar. There are doubts about what is possible/advisable to do with non-normative docs according to the current rules. I need someone with a better...

@r12a, I talked about this today with @deniak too. We believe the exact same rules we are applying when we check WDs should work for _WDs-that-are-intended-to-become-notes_ too. (With the probable...

Hello, @aphillips. I'm now coming back to this issue, and to w3c/specberus#143, and will answer you soon, either here or in the _spec-prod_ mailing list.

Coming back to this one after a *long* time, I'm a bit confused by some nuances in the status of documents, and overlapping ways to classify them and their intended...

@jyasskin, the URL that is passed to Echidna should be either the spec to publish, or a manifest. The way Echidna discerns which one it is is [by checking whether...

> *“Please say that in the error message.”* @jyasskin, I'm not sure that checking for this specific type of mistake makes sense in Echidna. The URL posted to Echidna must...

Okay, @jyasskin. I'll try to work on better errors for this specific issue (a manifest containing an absolute URI).

@marcoscaceres: yes, definitely it's bad UI now… We shall make it more legible very soon. Thank you for keeping track here. In the meantime, when you see error _keys_ specifically...

@marcoscaceres, we have work to do to improve documentation about the project, and explain things more clearly. That being said, the token that you obtain from W3C will be used...

Good idea, @marcoscaceres. [Done](https://github.com/w3c/echidna/wiki/Token-creation) :)