Any objection to adding other artifacts to the GitHub too (eg. explainer
docs, sample code, use case lists)? Or are those best stored elsewhere?
Can someone add me (@RByers) as a contributor to the repo so I can assign
issues to myself and edit files in the css-scroll-api directory?
Thanks,
Rick
On Fri, Sep 18, 2015 at 1:13 PM, Rossen Atanassov <
Rossen.Atanassov@microsoft.com> wrote:
> > -----Original Message-----
> > From: Greg Whitworth [mailto:gwhit@microsoft.com]
> > Sent: Friday, September 18, 2015 9:22 AM
> >
> > I am really interested in this spec and this one that I would like to
> potentially
> > piggyback parsing off of, and work on at TPAC so can we get this up into
> > CSSHoudini Github (or did it get put somewhere that I missed)?
>
> I would encourage for all specs to be on our github at this point. Layout,
> paint, cssom and everything else that's being worked on is best to be all
> at the same place.
>
> Rossen
>
>