- From: Sam Ruby <rubys@intertwingly.net>
- Date: Sun, 23 Nov 2014 09:53:44 -0500
- To: "Michael Champion (MS OPEN TECH)" <Michael.Champion@microsoft.com>, Jeff Jaffe <jeff@w3.org>, Revising W3C Process Community Group <public-w3process@w3.org>
On 11/21/2014 11:59 AM, Michael Champion (MS OPEN TECH) wrote: >>> http://intertwingly.net/blog/2014/11/20/WHATWG-W3C-Collaboration > >> Thanks for asking. I'm just one person in this CG, but my first >> reading agrees that it is not clear that any process change would >> be required. > > That's also my initial read. I think this is consistent with the > letter and spirit of the revised process document: what's important > when finalizing a Recommendation is the extent of consensus, RF > patent commitments, and interoperable implementation experience at > the end of the process, not the mechanisms of how the spec got > written and reviewed. > > I like the idea of using the URL spec as a test case, but I wonder if > we shouldn't use this opportunity to go further and try out some of > Robin Berjon's ideas (if I recall various TPAC conversations > correctly): > > - having a common GitHub repository for WHATWG and W3C versions of a > spec and shipping W3C Recommendations off a "stabilizing" branch > > - Hosting that repo and the discussion forums for a spec in a neutral > venue such as WebPlatform.org to encourage broader participation. Based on a pointer by Anne[1], there may be a problem. Specifically, section 7b of the Member Agreement[2], and section 2.2 of the Invited Expert and Collaborator Agreement[3] seem to prevent this. My original question as to whether or not there would be any process changes required to implement this may have been too limited in scope. What question should I be asking? - Sam Ruby [1] http://lists.w3.org/Archives/Public/www-archive/2014Nov/0029.html [2] http://www.w3.org/2009/12/Member-Agreement#ipr [3] http://www.w3.org/Consortium/Legal/2007/06-invited-expert#L118
Received on Sunday, 23 November 2014 14:54:34 UTC