- From: Travis Leithead <travis.leithead@microsoft.com>
- Date: Tue, 19 Jan 2016 21:07:53 +0000
- To: "tink@tink.uk" <tink@tink.uk>, "public-html@w3.org" <public-html@w3.org>
Last year in Sapporo, we had an interesting conversation about the future of HTML5 [1]. I was asked, from my implementer perspective, what I would like to see happen with HTML. As a former editor, I understand how bad the build and publishing process had become, and despite all the complexity (or perhaps because of it) the W3C HTML spec was less usable for me and many of those I work with: it was periodically out-of-date due to build process failures, and many of the cross-links in the document itself were broken. I'm very excited to see this new draft, and to have had some insight into the preparation of the new Bikeshed source. Bikeshed has been instrumental in bringing a high degree of internal consistency to the source, making it possible to find and fix the cross-linking bugs that plagued the former HTML spec. (Bikeshed itself has likewise benefitted from numerous fixes and improvements.) The build process is now far less complicated. To me, what remains to be seen is whether we will leverage this new source, the Github process, and our consensus-driven ideology to rapidly fix existing and yet-to-be-found bugs, primarily in the space of interoperability. I'm excited to get started. Thanks Léonie and those responsible for this huge effort. > Finally, we also welcome expressions of interest from anybody who would like to join > the editing team - for which the reward is hard work and the satisfaction of a job well > done. While anybody can submit a pull request proposing a change to the specification, > the editors will work together to review pull requests and integrate them when they are > ready. Count me in. [1] https://www.w3.org/2015/10/28-html-minutes.html
Received on Tuesday, 19 January 2016 21:08:24 UTC