"The plan" - working with the spec, timelines…

Hi all,

==Working with the spec:

We've now got the HTML spec in a state where we can edit it with  
relatively straightforward Pull Requests, although you may need to  
understand Bikeshed if you want to keep linking robust.

So please feel free to submit Pull Requests.

Editorial clarifications, especially for saying what algorithms are meant  
to do if they are moderately complex and it isn't yet explained, typo  
fixes and the like are vary welcome.

If you find something that doesn't work in at least two shipping browsers,  
please mark it. We generally want to remove it, even if we think it is a  
nice feature and hope that it gets enough implementation in future to  
justify including it.

If you want to add a feature, we generally prefer:
1. An extension specification instead of adding to different places in the  
current spec
2. Tests showing that it has implementation support.

If you don't know how to make a Pull Request, and you're a member of the  
Working Group, please feel free to file an issue instead.

==Timelines

This Working Group will need to be rechartered by 30 September.

Our plan is to ship and HTML 5.1 Recommendation, that is better than HTML5  
- more interoperable, better reflects reality, and easier to read.

The goal is not perfect, just better. We expect further improvements and  
changes to be made under the next charter.

To do this, we need to have the specification into Candidate  
Recommendation by mid-June, so expect a Call for Consensus at the  
beginning of June based on a Public Working Draft published then.

We expect to produce a Public Working draft in about the next week, and  
another in about a month, as interim milestones.

As always, we look forward to your collaboration and input.

cheers

Chaals, Ade and Léonie (your friendly chairs)

-- 
Charles McCathie Nevile - web standards - CTO Office, Yandex
  chaals@yandex-team.ru - - - Find more at http://yandex.com

Received on Tuesday, 29 March 2016 18:59:29 UTC