W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 13423] Remove the Editing APIs section. It's extremely incomplete and contradicts my editing spec on a lot of points, so it will confuse implementers.

From: <bugzilla@jessica.w3.org>
Date: Tue, 16 Aug 2011 15:57:38 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QtM1K-0002If-1o@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13423

--- Comment #21 from Aryeh Gregor <ayg@aryeh.name> 2011-08-16 15:57:37 UTC ---
Question for Maciej (and sorry to everyone for abusing this bug for process
discussions): would it be acceptable to Apple if this is published in a W3C
Community Group <http://www.w3.org/community/> for now instead of in an actual
Working Group?  I would find it much more palatable to work in a Community
Group than in a group governed by the full Process.

Community Groups are not governed by the patent policy, so I would expect that
when the draft is more mature I would move it to the WebApps WG.  The patent
policy only applies to Recommendations, so it should make no difference to
patents if it's not REC-track right away.  My understanding is that it's
supposed to be easy to move specs from Community Groups to regular Working
Groups once they mature.

One reason to prefer not putting the spec on REC track right away is that it
can retain its current copyright status without issue.  This means I won't need
to publish a separate specification ( la http://dom.spec.whatwg.org) to make
the copyright status clear: I'll redirect my existing specification URL to the
W3C Community Group one.  Having only one spec URL will reduce confusion for
the time being.

I also would like to test out and support the Community Group mechanism in
general.  I think it's an important step forward for the W3C and could solve a
lot of its institutional problems if it were expanded a bit.  I'm actually not
committed to the downfall of the W3C here, I just think it has a lot of
problems in practice, and Community Groups solve most of them.

So at this point, I would like to submit this for work in a W3C Community
Group, not have any version on the W3C REC track, and submit it to the REC
track when it's more mature and is close to being ready for Last Call.  This
should not materially affect the Patent Policy's applicability, AIUI.  Would
this be okay with Apple, assuming the Community Group proposal is accepted?

-- 
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 Tuesday, 16 August 2011 15:57:39 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:17 UTC