Re: The Canvas 2D API split

On Mon, Jan 11, 2010 at 10:28 AM, Maciej Stachowiak <mjs@apple.com> wrote:
>
> On Jan 11, 2010, at 7:56 AM, Shelley Powers wrote:
>
>>
>> Then I will enter an Issue, because I see two proposals, the editor
>> did not take into consideration the original proposed split, and I
>> don't agree with the wording of the editor's proposed change.
>
> I don't think that would be an appropriate use of the issue tracker. If you
> object to the wording, there are ways to do that. You can file a bug against
> the split out draft about the wording, or you can enter a resolvable
> objection when it is proposed for FPWD.
>
> The fact that someone else made another draft is only relevant if someone
> wants to put it forward for FPWD. So far no one has done so.
>
> Please do not enter tracker issues that aren't called for by the process.
>

We have to disagree, then.

Right now, I see two proposals, one that was created before we had a
procedure in place. The whole purpose of the procedure was to manage
disagreement, and allow for multiple proposals or counter-proposals.

If the initial proposal creators drop their proposal, we're still
faced with a new change proposal: one put forth by Ian. He has to go
through this process the same as the rest of the team. He is not above
the procedures of this group, don't you agree?

The Issue Tracker is the only way to track an issue, assign a
responsibility, and ensure something has not fallen through the
cracks, like the initial 2D Canvas split did.

How else are we supposed to track assignments, responsibilities, and
due dates, Maciej?

Shelley

Received on Monday, 11 January 2010 16:34:22 UTC