- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Fri, 24 Mar 2017 20:05:07 -0700
- To: "public-tracking@w3.org (public-tracking@w3.org) (public-tracking@w3.org)" <public-tracking@w3.org>
> On Mar 13, 2017, at 9:01 AM, Roy T. Fielding <fielding@gbiv.com> wrote: > > I have moved the TPE editors' draft to > > https://w3c.github.io/dnt/drafts/tracking-dnt.html > > and will eventually figure our how to tie it into the github issues. > There are no significant changes from the last CR, yet, but some of the > WebIDL sections look different due to a variety of non-compatible > changes in the current version of Respec. I am still working around > a way to fix those. After that, I can incorporate the changes already > waiting in the issues. I figured this out on Tuesday and finished issue #12. I also created a word diff so that folks can see how little has been changed since the CR. https://w3c.github.io/dnt/diffs/diff_tpe_CR_to_ED_20170321.html Note that almost all of these changes are just rearranging things so that the tool (ReSpec) can understand the interfaces and stop complaining. The history of specific commits is visible at https://github.com/w3c/dnt/commits/master/drafts/tracking-dnt.html which is more extensive because most of the changes were in HTML mark-up. Doing this also forced me to read the API sections carefully, which I hadn't done for a long time because I was expecting to delete them instead (a far easier task ;-). I'll send my comments on the API later. In the future, if you have a github account and know how to use it, PLEASE use the common GitHub mechanisms for requesting changes to the specification (even if you have write access to the repo). I will try to do the same for my changes to any content. This will allow github to produce nice looking (and issue-specific) diffs that everyone can review before they are committed by one of the editors. In other words, fork the upstream source repo https://github.com/w3c/dnt make changes in your local copy, and then submit them as a pull request with reference to an appropriate issue on the issues list at https://github.com/w3c/dnt/issues Alternatively, just open an issue with the suggested text change and one of the github-savvy folks can create a pull request based on that. Cheers, Roy T. Fielding <http://roy.gbiv.com/> Senior Principal Scientist, Adobe <https://www.adobe.com/>
Received on Saturday, 25 March 2017 03:05:36 UTC