ISSUE-180: "Implementation experience" description should clearly identify likelihood of broad acceptance

implementation experience

"Implementation experience" description should clearly identify likelihood of broad acceptance

State:
RAISED
Product:
Process Document
Raised by:
Erik Anderson
Opened on:
2017-02-22
Description:
"Implementation experience" as currently described should have more emphasis on the requirement that things are likely to get broad adoption.

Essentially this would mean that demonstrating a spec is well-written and implementation is interoperable, but without evidence that the spec will be adopted broadly on the web, would not satisfy the basic requirements to move from CR to PR.
Related Actions Items:
No related actions
Related emails:
No related emails

Related notes:

Transferred to https://github.com/w3c/w3process/issues/32

David Singer, 21 Apr 2017, 18:57:27

Display change log ATOM feed


David Singer <singer@apple.com>, Chair, Dominique Hazaƫl-Massieux <dom@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $