- From: Cullen Jennings <fluffy@cisco.com>
- Date: Mon, 26 Sep 2005 09:50:18 -0700
- To: Julian Reschke <julian.reschke@gmx.de>, Lisa Dusseault <lisa@osafoundation.org>
- CC: WebDav <w3c-dist-auth@w3.org>
On 9/25/05 1:04 AM, "Julian Reschke" <julian.reschke@gmx.de> wrote: > Actually I was waiting that the WG comes to agreement about how we do > the issue tracking. It's a bit pointless to review drafts if there's no > process how to deal with the comments. You are going to hate my answer on this so I apologize in advance :-) The issues do need to show up in the email lists since that is the archived record of IETF stuff. Clearly they can also be recorded in various other tools - I've seen groups successfully use everything from bugzilla, blogs, source code control systems, word documents with revision control, text files, and just plain old email. The real point of these systems is to help the author of a document track what they need to do. Because of this, I believe that issues fall into two categories. 1) resolved things where the WG group agrees and the author just needs to update the documents 2) complex issues where it is not clear if the WG has reached consensus. For the category 1 stuff, I plan to leave it up to the author of a document to decide how they want to do this and how much they want others members of the group to be able to edit, update, add etc. I'm a big fan of collaborative tools but whatever the author is comfortable with that will get the job done quickest is fine with me. For the category 2 stuff, I as chair need to be able to have clear visibilities into these and so does everyone one else in the WG. Also, there are not many of these sort of issue. Because of this, I plan to track these using the email list as the authoritative copy. I don't care if they are also tracked in the system the author is using but on the key topics we are having a hard time getting consensus on, I'm going to do it on the list. This may seem arcane and prehistoric to do it with ASCII email but there is only a handful of items and it will work out fine and no one can complain about it later. It may not be best, but it will work and I rather focus energy on getting to consensus instead of debating tools. Cullen
Received on Monday, 26 September 2005 16:53:15 UTC