W3C home > Mailing lists > Public > public-html@w3.org > January 2010

Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)

From: Shelley Powers <shelley.just@gmail.com>
Date: Mon, 18 Jan 2010 19:19:10 -0600
Message-ID: <643cc0271001181719r4e1d3f33ua8043de5362d24d8@mail.gmail.com>
To: Maciej Stachowiak <mjs@apple.com>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Sam Ruby <rubys@intertwingly.net>, HTMLWG WG <public-html@w3.org>, Paul Cotton <Paul.Cotton@microsoft.com>
On Mon, Jan 18, 2010 at 6:49 PM, Maciej Stachowiak <mjs@apple.com> wrote:
> On Jan 18, 2010, at 4:43 PM, Shelley Powers wrote:
> This approach is originally Sam's idea, and I am pleased with the way it's
> been working out. I don't think Sam is saying we're going to change things.
> But he *is* saying that the counter-proposal period is not guaranteed, and
> if a Change Proposal is either a clear winner or a clear loser just from
> mailing list discussion, we may not bother formally calling for
> alternatives.
> That's not a step in the Decision process. The decision process states
> that if the change proposal has general acclaim, it will most likely
> be passed by consensus. If the change proposal has little or no
> support, regardless of how it is written, it probably won't even go to
> the poll.
> The Decision Policy also includes a discussion period with no specific
> bound. A few times now,  we've chosen to request that some of that
> discussion be distilled into additional Change Proposals. That's been our
> best judgment of how to bring discussion to a resolution when there is no
> clear consensus winner. That's seemed more prudent to us than just going to
> a poll - we prefer for that to be the last resort. Other than that, I agree
> with what you said. If a Change Proposal is a clear winner or clear loser,
> it can succeed or fail without the need for any further Change Proposals.

That's not in the Decision Policy. There is nothing about a call for a
formal counter-proposal during the "discussion".

I'm sorry, but "discussion" is not the same as a formal call for a
Counter-Proposal. If people want zero-edit proposals, if they want the
status quo, they should be willing to defend the specification
following the same. If they can't even take the time to do this, then
yes, the change proposal should be the clear winner.

If people can't take the time to actually provide a rationale, aren't
even willing to try until prodded by the co-chairs, then the contested
spec text should not be in the HTML5 spec.

I am disappointed with how uneven and inconsistent the Decision Policy
is being applied. But evidently, there is little I can do.

Received on Tuesday, 19 January 2010 01:19:42 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:57 UTC