- From: Michael Champion (MS OPEN TECH) <Michael.Champion@microsoft.com>
- Date: Thu, 7 Nov 2013 18:17:05 +0000
- To: Arthur Barstow <art.barstow@nokia.com>
- CC: Advisory Board <ab@w3.org>, W3C Process Community Group <public-w3process@w3.org>
Hi Art, "freedom" was not the right choice of words. Experienced chairs do know how to make the process work by initiating reviews by key outside stakeholders and getting critical decisions made early enough to be effective. But they are working AROUND the process, following the letter but not the spirit of it. Or maybe they follow the more "agile" spirit of the process as it really is, but that is quite different from the "waterfall" spirit of the process as it was conceived and written down. I think much of the motivation for process reform comes from people who are frustrated with the creative fictions that it requires (e.g. "call for implementation" of a spec that ships in all browsers) and the gyrations needed to remove bits of a spec that seemed like a good idea at FPWD time but never got implemented (or never achieved interoperability). Both this and the Chair Training initiatives being driven through the AB aspire to a revise the process to match reality and provide proven best practice guidelines so more people can be effective chairs without having to understand all the folklore chairs need to have internalized to be effective today. Does that make sense? ________________________________________ From: Arthur Barstow <art.barstow@nokia.com> Sent: Thursday, November 07, 2013 5:22 AM To: Michael Champion (MS OPEN TECH) Cc: Advisory Board; W3C Process Community Group Subject: Re: Transition to a revised Technical Report Development Process [W3Process-ISSUE-39, W3Process-ACTION-10, proposal] On 11/7/13 1:48 AM, ext Michael Champion (MS OPEN TECH) wrote: > I think we understand that this does put more of a responsibility on chairs, but hopefully more freedom for them to customize and optimize the workings of a group to meet its real constraints Sorry for being so dense here, but would you please elaborate a bit on how you see the current ProcDoc somehow prevents or precludes this from happening (now)? -Thanks, AB
Received on Thursday, 7 November 2013 18:17:50 UTC