Philippe Le Hegaret

Note that respec handles subtitles., eg https://w3c.github.io/pointerevents/ Now, compare the data from https://www.specref.org/?q=pointerevents2 and the actual WD at https://www.w3.org/TR/pointerevents2/ (the subtitle got dropped in specref) This is because we don't...

(I think you mean head's h1, not head's h2. I misspoke earlier when I said "instead of h1". You always need the h1 but you can use an additional h2...

@palemieux . it is indeed correct. Since 3rd is a CR, you could make the update in the editor's draft and our system would pick that up at the next...

@tobie, https://github.com/w3c/guide/ would be the place. Version management is documented in https://www.w3.org/2005/05/tr-versions at the moment but could be moved into the Guide repo.

+1 but only if the repo has multiple modules, such as [https://github.com/w3c/csswg-drafts/issues](w3c/csswg-drafts). Otherwise it would simply be a repeat of what the repo is about. I feel that this needs...

@deniak is correct. In fact, the new Process 2021 reemphasizes the need to ensure that W3C maintains [long term control over its content](https://www.w3.org/2021/Process-20211102/#tooling), going way beyond the scope of /TR....

I don't support adding more refined -tracker -needs-resolution labels in all repositories. 1. We already have 10 of them and expecting the community to know what i18n-alreq means seems hard....

Btw, there are 2 versions of the documentation: [1.0](http://karma-runner.github.io/1.0/dev/git-commit-msg.html) and [6.4](http://karma-runner.github.io/6.4/dev/git-commit-msg.html). I chose to stick with 1.0 since it contains 'chore:' while the updated version does not. Happy to debate.

https://github.com/w3c/w3c.github.io/issues/98 is likely related

There is also https://github.com/erlang/otp/wiki/Writing-good-commit-messages