W3C home > Mailing lists > Public > public-html@w3.org > September 2012

Info from HTML5 editors: merging WHATWG patches

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Sun, 9 Sep 2012 18:49:08 +1000
Message-ID: <CAHp8n2no80bV2WbcS_0_YNZH2zSU2SGmEXPMJ2Goqb0Ng4K5pQ@mail.gmail.com>
To: public-html <public-html@w3.org>
Hi all,

Our Working Group is chartered to actively pursue convergence with the
WHATWG specification [1].

As such, one of the tasks that the new editors of the W3C HTML
specification have taken upon themselves is to work through the
patches that Ian has been making to the WHATWG specification and
successively merging them into the W3C specification where

Since we have moved to using GitHub [2] to manage the development of
the specification, we are using a development model that is
extensively based on branches [3], [4].

Over the last weeks, I have experimented with this approach and found
it works well to help others review patches before landing them.

Today I want to take this to the WG, so you can all get involved in
helping review changes before they get in - and help me from merging
features that we really want in HTML.next or that are not ok to be
merged for any other reason.

Every week, I will put together a set of new feature branches with
commits from the WHATWG spec for review.

These fall generally in these three classes:
(B1) branches with fixes for typos or that resolve bugs in our bug
tracker (i.e. we likely all appreciate that these should be applied).
(B2) branches with features that are either new, or for which I don't
know if we should merge them.
(B3) branches/patches with features that we decided to hold back from
HTML5 (also listed in [5]).

Every Friday (Australian time) I will apply the feature branches from
the previous week that I have announced will be applied the week
before, or for which we have resolved through discussion during the
week that we should apply them.

At any time, you can find the list of current branches at [6].

Here is the list of branches that we have this week for your review:

Today, I have managed to get to WHATWG patch 7256 (inc) [7].
So, please do not complain about any patches that were made afterwards
- I'll get to them eventually.
I have only this far caught up with the WHATWG work before the 23rd August.

B1 branches (i.e. branches/patches I will commit next week unless I
hear otherwise):

*  feature/whatwg_patches
  This is the branch with the largest number of patches.
  These patches are all small-ish, mostly typo fixes or replies to
small bug reports.
  You can reeview the patches here:
  Click on "Files Changed" tab to see the change to the files themselves.
  You can even leave comments right there.

*  feature/whatwg_i18n
  This is a branch with changes to internationalization issues.
  Review here:
  Try clicking on the "..." in the commits to get more info.

*  feature/whatwg_ruby
  This is a branch with <ruby> examples.
  Review here:

*  feature/whatwg_tables
  This is a patch that deals with table borders.
  Review here:

*  feature/whatwg_websockets
  This is a branch that relates to websockets.
  Review here:

*  feature/whatwg_window_find
  This is a patch that drops the window.find() legacy API.
  Review here:

*  feature/whatwg_fingerprinting
  This patch discusses user privacy vs user convenience & implications
on fingerprinting.
  Review here:

B2 branches (i.e. branches I don't know if we should commit them):
If you feel strongly about one of these branches either way
(pro/contra commit), please speak up.

*  feature/whatwg_inert
  This patch clarifies 'inert' wrt focusability.
  Review here:

*  feature/whatwg_inputmode
  This branch introduces several changes to form elements, including
inputmode and autocomplete attributes.
  Review here:

*  feature/whatwg_srcset
  This patch introduces the @srcset attribute on images.
  Review here:

B3 branches (i.e. branches that we decided to keep back for HTML.next):

*  feature/whatwg_canvas
  This branch has several patches for new Canvas features, in
particular HD versions for the ImageData API.
  Review here:

Feedback will be welcome on list or directly in the feature branches.
You will need a GitHub account to leave comments there.
Please make statements for which you expect a discussion here on the
mailing list, and only report trivial mistakes in GitHub, since only
the editors will see the feedback on GitHub.

Thanks for your patience and support in helping us get our extensive
editing tasks done!

Best Regards,

[1] http://www.w3.org/2007/03/HTML-WG-charter.html
[2] https://github.com/w3c/html
[3] https://github.com/nvie/gitflow
[4] http://www.w3.org/QA/2012/09/the_flowing_standard.html (Robin's
blog post on the issue)
[5] https://github.com/w3c/html/blob/master/unmergedFromWHATWG
[6] https://github.com/w3c/html/branches
[7] http://html5.org/tools/web-apps-tracker?from=7255&to=7256
Received on Sunday, 9 September 2012 08:49:56 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:27 UTC