Re: [sipcore] Tracker Etiquette

[as chair]

I've been ignoring the tracker till now, but it seems impossible to 
continue doing so.

ISTM we do need some group norms on this.
Especially given my lack of experience with the tool, I'm reluctant to 
impose them, at least *yet*. Instead, I'd like to see some discussion on 
how people think this should be used.

Here are a few questions that come to mind:

- can anybody create a new topic? Or should the topics be controlled
   in some way? (e.g. consensus)

- can anybody create a new ticket? Or should ticket issuance be
   controlled in some way? (e.g. consensus)

- is creating a ticket done after discussion, or in lieu of discussion?

- who is responsible for assigning ownership of a ticket?
   can the author pick anybody he wants? Or should people only be
   allowed to assign ownership to themself?  Or should there be
   ownership of topics?

- who can close a ticket? The reporter? The owner? Anybody?

I'd like to hear what people in this WG think about this. (My own first 
reaction is that it would be helpful for wg doc editors to use tracker 
for those things that need to be addressed in a document, based on 
emails from others. I'm not so sure about use beyond that, but have an 
open mind.)

Should I have created a tracker topic "Tracker Etiquette" and submitted 
tickets for each of these questions, rather than sending this mail?

	Thanks,
	Paul

James M. Polk wrote:
> At 02:57 PM 8/31/2010, Adam Roach wrote:
> 
>> [as chair]
>>
>> Finally, it would be helpful to document authors if you included 
>> something in the ticket name that indicated which document the tracker 
>> issue is on. It doesn't have to be a whole document name; something 
>> like "4244bis" for the history-info draft would be sufficient.
> 
> Amen
> 
> tracking which issues pertain to which docs is a fundamental flaw in 
> this whole process regardless of the WG or doc involved.
> 
> James
> 
> 
>> Thank you.
>>
>> /a
>> _______________________________________________
>> sipcore mailing list
>> sipcore@ietf.org
>> https://www.ietf.org/mailman/listinfo/sipcore
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
> 