- From: Arthur Barstow <art.barstow@gmail.com>
- Date: Tue, 20 Jan 2015 07:50:29 -0500
- To: "Michael Champion (MS OPEN TECH)" <Michael.Champion@microsoft.com>, "public-success-fail@w3.org" <public-success-fail@w3.org>
- CC: Ian Jacobs <IJ@w3.org>
On 1/20/15 12:51 AM, Michael Champion (MS OPEN TECH) wrote: > > Someone suggested that we look at data on *specs* (not just working > groups) as we look for efforts not destined for success. I was hoping > to get data that -- for each spec -- would let us track publication of > working drafts, LC working drafts, CRs, PRs, Recommendations, and > edited Recs. This would let us get an idea of how long it takes -- > minimum, average, maximum -- to get all the way through the process, > and perhaps identify red flags such as "If a spec doesn't get to CR in > x years, it is unlikely to even do so" and generally look for patterns > in the distribution of times it takes specs to move through the process. > > > Unless I'm missing something, that's not easily available from the /TR > page: There's just one entry for each spec indicating the the maximum > level of maturity, not one entry for each time something was published > to /TR. Does anyone know if there is a way to get this more fine > grained data out of /TR , the WG database, etc? Is there a single > mailing list (or public log file of some sort) that gets an entry > every time something is published? > FYI, I created (and still maintain) a document for WebApps that includes that data <https://www.w3.org/wiki/Webapps/TimeToREC>. (Interesting data; lots of variables in `getting to REC`.) [My original use case was "if WebApps had used the TR process in PD-2014 instead of PD-2005, would any of the specs reached REC sooner?" (BTW, the answer was "no").] -AB
Received on Tuesday, 20 January 2015 12:50:57 UTC