Github repo structure/organisation

Wondering if anybody had some thoughts about the (in my view slightly 
unorthodox) way the Github repo for TE is currently structured... with 
the main branch containing TE Extension only and v1 being (i assume?) 
the actual TE spec as it appears on W3C.

https://github.com/w3c/touch-events/issues/9

It's possibly too late already, but to me it doesn't quite gel as a 
structure. Wondering if there's any easy way to untangle/normalise this 
by having master at least contain both TE and TE Extension (in their W3C 
published state). Then the branches would be work in progress on 
errata/next versions, which - once complete - would be merged into master?

If it's not worth the hassle, far enough...just something that slightly 
confused me initially.

Thoughts?

P
-- 
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke

Received on Tuesday, 3 March 2015 09:36:12 UTC