WebPlatform Browser Support phased approach?

Hi, folks:

As you probably know, the CSS properties project is in its last stages. This
means we've edited and added samples & other good stuff to these pages. And
when your WebPlatform Browser Support project is functioning, we'll display
that compatibility information in these properties pages. Without that
information, the pages really aren't ready for primetime. So, the CSS
properties project has a dependency on your project.

At last Friday's general meeting, we discussed the possibility of going out
with "good-enough" data. The idea is: if you divide your WebPlatform Browser
Support project into phases, or sprints, you might be able to do an early
cut of the data from maybe just 1 or 2 sources. If you could do that, then
we could take that drop and format it for inclusion into the css properties
pages compatibility subsection. This would be a 1-time manual or scripted
edit inserting the "pretty-good" data, which would then act as a placeholder
until your project was more mature.

I have to give the larger community a sense of the CSS properties project
timeline, which I can't do until we figure out when we might have
compatibility information. So, while Doug can probably explain more, I
wanted to throw this out to you now for some thinking on a phased approach.

Thanks!

Julee
----------------------------
julee@adobe.com
@adobejulee