- From: <bugzilla@jessica.w3.org>
- Date: Fri, 19 Aug 2011 18:10:25 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13423 --- Comment #36 from Aryeh Gregor <ayg@aryeh.name> 2011-08-19 18:10:23 UTC --- Community Groups have a patent policy as well. In fact, in this respect it's even stronger than for regular Working Groups: contributors to CG specifications must grant patent licenses *immediately*. I'm currently waiting for TV Raman to agree to the editing CG's terms on behalf of Google. As soon as he does, and I submit my work there, everyone immediately gets a patent license to all of Google's contributions to the editing spec, IIUC. Moreover, the full request for patent commitments from CG members kicks in at Final Specification stage. This doesn't have the requirements of REC, and can be much more frequent. The editing spec could not plausibly get to REC for a few years yet, and implementers would be exposed to patent risk in the interim. In a CG, my current plan is to publish a Final Specification regularly (perhaps annually) as a snapshot, so patent protection is available much more rapidly than under the normal Process. Disclaimer to all of the above: IANAL. It is up to the parties concerned to decide whether they think a CG spec is good enough for them, or if they want a full REC-track spec. I am not ruling out the possibility of eventually publishing a copy of the editing spec on the REC track. I think this bug has been sorely overused at this point, however. I think it would be best resolved. The current text in HTML5 is much too vague to even be testable and would have to be removed for PR anyway, so I suggest it be removed now. If anyone would like to object at that point, the usual channels are available to them. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 19 August 2011 18:10:27 UTC