- From: Marcos Caceres <w3c@marcosc.com>
- Date: Fri, 23 Mar 2012 15:58:08 +0000
- To: Carr, Wayne <wayne.carr@intel.com>
- Cc: Anne van Kesteren <annevk@opera.com>, Jeff Jaffe <jeff@w3.org>, Dominique Hazael-Massieux <dom@w3.org>, public-w3process <public-w3process@w3.org>, Daniel Glazman <daniel.glazman@disruptive-innovations.com>
On Friday, March 23, 2012 at 3:36 PM, Carr, Wayne wrote: > This whole thing about not kicking in until Recommendation seems irrelevant. What we should be doing is figuring out how to divide up problems so specs don't take 10 years to complete. I suggest: hire a rockstar spec editor (or two, or three! depending on project scope), a good team of devs to prototype, some QA folks to generate tests and get a vibrant community (who provide use cases and sanity check things) and you are rocking… oh, maybe a product manager, to go around promoting the spec, showing off the prototypes, making sure it gets in front of the right people (Chairs are usually pretty good at this role). But these people have to be dedicated to getting the job done more or less full time (though not at the same time, of course). My experience is that there are few full time spec editors at the W3C: everyone has their day job too… and that's why things take ages. Also, you need strong backing from key W3C members from the get-go (if not, it's dead from the start… DAP uses this rule, which can be paraphrased as: "No browser maker interest? No spec!" ). Otherwise, let the innovation happen elsewhere (as is happening with Webkit and CSS regions) and then try to standardize from that. At least most of the hard work is done quickly with all the aspects above already covered. Kind regards, Marcos -- Marcos Caceres
Received on Friday, 23 March 2012 15:58:47 UTC