The Web Incubator Community Group (WICG) provides a lightweight venue for proposing and discussing new web platform features. Each proposal will be discussed in its own repository within the group's Github account. Membership of the group is open to everybody but all participants will have signed the W3C Community Contributor License Agreement.

But then, we should not use "incubation" as a euphemism for "no one is going to implement this and we don't want it" as it demeans the work of groups like the WIGC - that actually do incubation. At least, I will strongly object to the use of that word if your intention is to kill the spec.

So, what then is the real reason for WP terminating work on the spec? Can we see the minutes from the rationale given to the AC?

At the AC meeting in March 2016 the WP co-chairs indicated that the

following two specifications would benefit from further incubation before

continuing along the Recommendation track:

Quota Management API [1]

Input Method Editor API [2]

This is a proposal and may change without any notices. Interested parties should bring discussions to the Web Platform Incubator Community Group.

This is a proposal and may change without any notices. Interested parties should bring discussions to the Web Platform Incubator Community Group.

This is a proposal and may change without any notices. Interested parties should bring discussions to the Web Platform Incubator Community Group.

This document was moved to the Web Platform Incubator Community Group.

This document was moved to the Web Platform Incubator Community Group.

It is being incubated here as part of the CSS Houdini task force, and if successful will be transferred to that task force for full standardization.