Re: [css-houdini-drafts] One repo per draft?

IIRC the reason for a single repo was that some people on the group 
wanted a single point where they could subscribe to all changes & 
issues. There are advantages and disadvantages (e.g. a number of times
 we've wanted to file an issue on multiple specs at once). I'm not 
opposed to splitting at some point but I think we'd want to get the 
group to agree first.

We've been tagging the outstanding issues by spec to make it easy to 
just focus on one specification at a time - e.g. for typed OM you can 
use 
https://github.com/w3c/css-houdini-drafts/issues?q=is%3Aissue+is%3Aopen+label%3Acss-typed-om-1.



-- 
GitHub Notification of comment by shans
Please view or discuss this issue at 
https://github.com/w3c/css-houdini-drafts/issues/316#issuecomment-250886929
 using your GitHub account

Received on Saturday, 1 October 2016 02:21:47 UTC