Dominique Hazael-Massieux

random remark: Octokit's throttling plugin was broken for some weeks due to a change in the error message sent upon hitting the abuse rate - see https://github.com/octokit/plugin-throttling.js/issues/437

For reference, `[[Stopping]]` was introduced in 40719f46665005ae5b819110ff1731492bca6f6f (June 2019), where as that piece of the algorithm was introduced in 85284b76baebf9e149d194e692be16a21768a91a (August 2018)

The process to add a candidate change with this approach is to add a description of the change based on the following template: ```html is a candidate correction - see...

Reporting from my discussion with @plehegar : * having a document which integrates seamlessly the candidate (or in the future, proposed) amendments in the normative text is not a priori...

@alvestrand @caribouW3 @plehegar I have now taken another stab at this that fulfills the process requirements as I understand them from @plehegar while still reducing the editing burden substantially (although...

For illustration purposes, I've gone through the exercise of what it would take to import transferable data channels from WebRTC extensions to the main spec as a candidate addition: https://github.com/dontcallmedom/webrtc-pc/pull/2...

@plehegar have you had a chance to check if the results match what you expect would be acceptable for an updated Rec?

@plehegar indicated offline that this approach should pass muster, so I'm now marking it as ready for review & merging, which will help completing upcoming pull requests with additional substantive...

I've rebased to main and updated the sample, which removes the said respec errors (the ones that remain are "expected").

the first step is to document it in our [errata page](https://github.com/w3c/webrtc-pc/blob/master/errata.html). We can also fix the editors draft maintained in this repo without further ado. Assuming we don't think the...