[whatwg] WHATWG on Google+

[Philip Jägenstedt]

On Tue, 22 Nov 2011 01:40:10 +0100, Ian Hickson <ian at hixie.ch> wrote:

> On Mon, 21 Nov 2011, Boris Zbarsky wrote:
>> >
>> > Another option is for someone (possibly me) to create a system whereby
>> > people can subscribe to specific portions of the specification, and
>> > for a tool to detect when a diff affects that portion and e-mail them.
>> > I'm not exactly sure how to make that work, but if it's something
>> > people are interested in, we could figure something out.
>>
>> This could be interesting if new sections are added rarely enough....
>
> I'm poking around at this. I'm not sure sections are the best way to
> organise this, because self-contained features are often in various parts
> of the spec, or end up sprouting new sections unexpectedly. So I'm  
> looking
> at annotating the spec source with specific topics, e.g. "WebSockets" or
> "Navigation" or whatnot.
>
> If people could e-mail me the lists of topics they would be interested in
> being e-mailed diffs for, it would give me a good idea of what coarseness
> would be helpful here, and thus whether this is a realistic idea.

I'd be interested in following any changes to the <video>, <audio>,  
<source> and <track> elements, as well as the WebVTT rendering rules. If  
you want to do it manually, categories "<video>" and "<track>" would  
probably suffice, if we consider WebVTT part of <track>.

As an aside, I once made an attempt at writing tools for tracking changes  
on a per-section basis in and have dumped that in  
<https://gitorious.org/whatwg/diff-sections>. It used the outlining  
algorithm to split things into sections and write each section to a  
separate file. It's rather over-engineered in the use of a complicated git  
history and I never got to the part that would actually create a feed of  
relevant changes, but some of the ideas might be worth keeping.

-- 
Philip Jägenstedt
Core Developer
Opera Software