Oustanding issues tracking

Debbie Garside debbie at ictmarketing.co.uk
Fri May 23 20:04:52 CEST 2008

I agree with Mark and Shawn.  We all frequent another IETF group where the
Editor's manage to cut and paste the issues that they have dealt with into
an email briefly stating how they have dealt with it prior to uploading the
next draft.  I am assuming that this is how Editors are working in this
group i.e. they are reading the emails and changing the document
accordingly, so it shouldn't be too onerous.  It becomes very easy to read
through to see if comments have been dealt with and if not to post again.  I
should imagine it helps the Editors and the entire WG to move forward in a
constructive manner.

Best regards


> -----Original Message-----
> From: idna-update-bounces at alvestrand.no
> [mailto:idna-update-bounces at alvestrand.no] On Behalf Of Shawn Steele
> Sent: 23 May 2008 18:27
> To: idna-update at alvestrand.no
> Subject: RE: Oustanding issues tracking
> Obviously Mark feels there isn't enough transparency about
> what issues are considered outstanding by the authors.  Since
> he is a very active participant in other working groups
> without having this concern, it seems likely that there is a
> method of achieving a sufficient level of transparency
> without causing a "denial of service attack.".
> I'd suggest that a list of key changes and outstanding issues
> the authors feel are important be maintained.  For resolved
> issues a quick note should be made.  This would limit the
> noise to the actual items the authors were considering (which
> shouldn't cause a denial of service because they're already
> working on them).  Such a list would also allow transparency
> to the rest of the WG so that interested people could see if
> their item of concern was on the list.
> If someone on the mailing list then felt strongly about an
> item not being on the issues list, they could then ask for it
> to be included.  If the authors felt that it was too much
> noise, they could ignore them.
> I recognize that tracking issues may cost the authors' some
> time, however I'd also like to point out that having a bunch
> of contributors trying to do a diff of a document to discover
> if something was just a grammatical error or a technical
> change also collectively wastes a great deal of everyone's time.
> - Shawn
> _______________________________________________
> Idna-update mailing list
> Idna-update at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/idna-update

More information about the Idna-update mailing list