Re: [MMUSIC] Issue tracker for 4566bis

[Paul Kyzivat <[e-mail]>]

On 1/14/14 2:49 PM, Ali C. Begen (abegen) wrote:
> Hi everyone
>
> Revising 4566 is underway as you know and there have been some issues with 4566 and some folks want them to be fixed in 4566bis. However, due to convoluted discussions, some of these issues go unfixed. To make the process easier, it was suggested to establish an issue tracker.
>
> I have not done this before, but found the link below:
> http://tools.ietf.org/wg/mmusic/trac/report/1
>
> Is this a good idea to use this or do you have better suggestions?

This is just a link to a report of active tickets.
Are you just asking if doing something analogous for 4566bis would be a 
good thing?

I think the issue tracker is fine if you, as editor, use it to track the 
issues with your document.

But I strongly suggest that you be the only one to open, update, and 
close tickets for 4566bis. Don't leave it for anybody who thinks they 
have an issue to open their own ticket, and don't use updates to the 
tickets as a way to debate an issue. I saw that done once or twice and 
it created a mess - confusing established mechanisms for discussing 
issues via email.

So IMO we should continue to *discuss* proposed changes on the mmusic 
list. Based on those discussions you can make tickets as you see fit to 
track the status of identified issues and their incorporation into the 
draft.

	Thanks,
	Paul