Hey all,
For the past year or so Chris Wilson, Yoav Weiss, and Marcos Caceres have been chairing a new Community Group at the W3C called the "Web Incubation Community Group" [1] (WICG for short).
The goal of this group is to provide a clearinghouse for new APIs proposals so that they can get broad review and community engagement before they land at a chartered working group. The lightweight design of this process is inspired by how we have developed some recent features (e.g. Service Workers and <picture>) with heavy community involvement. More recently, some of us in the Web Platform team at Google have been using the new WICG incubation process to iterate quickly on features like Intersection Observer [2].
From my perspective this has been going very well. Well enough, in fact, that we're now going to require Googlers to use this process for all new web platform features regardless of their eventual destination in the formal process. The intent is for new designs to iterate inside the WICG process, perhaps to the point of shipping, and then graduate to a more formal venue. This process preserves the ability to get broad participation from other browser engine teams while lowering the social and process hurdles for web developers and community members to participate in the design phase.
You should expect Googlers to ask to move new design discussions to repos hosted at WICG, and we hope other groups will also start choosing to incubate their designs before pursuing formal standardization.
We've found WICG to be hugely productive but are continuing to look for ways to improve how we do this sort of work, so if you have ideas or concerns, please let me know.
Regards