RE: mock u[p page for issue tracking

Yes, exactly, and these comments echo my point from earlier this week.

We do need a bug/issue tracking tool, not a document or a wiki page. Gregg Vanderheiden once raised the prospect of 1000 public comments on a WCAG working draft. Unfortunately, this is a very realistic possibility. Whatever their absolute number, we need to be able to track the progress of each issue, comments on it, and resolutions made, all while retaining a complete record. Issues need to be searched and filtered quickly. In short, this problem demands a database and associated software, which is what an issue tracking tool offers.
I strongly support the use of issue tracking tools and strongly oppose resorting to documents, wiki pages or other approaches that do not scale well, open up opportunities for mistakes, or otherwise fail to meet the working group’s needs.

From: Alastair Campbell [mailto:acampbell@nomensa.com]
Sent: Thursday, March 16, 2017 2:06 PM
To: Andrew Kirkpatrick <akirkpat@adobe.com>; lisa.seeman <lisa.seeman@zoho.com>
Cc: Michael Cooper <cooper@w3.org>; W3c-Wai-Gl-Request@W3. Org <w3c-wai-gl@w3.org>
Subject: Re: mock u[p page for issue tracking

I’m struggling to see how this is better than the github issue page?
(Not a rhetorical question, I think I must be missing something?)

As a commenter I’m not clear where / how I should comment, editing the document to add a comment seems strange. (And open to abuse, especially if linked from a public place like the WCAG 2.1 draft).

As an SC manager, the length of document would become totally unmanageable after some public comments, especially if the versions are in the same page. I assume we’ll get more comments from the public than we did from the working group?  Imagine 100 pages of comments…

If we used a google doc as one of the ‘nice reading’ formats (as per my email last night), I think it would need to be locked-down from other people editing it, and link through to github for comments.

As it stands now each reviewer creates one or more new comments (issue) per SC, and that should be much easier to deal with in the github interface because they can be assigned, tagged, replied to and closed.

Cheers,

-Alastair


From: Andrew Kirkpatrick
Date: Thursday, 16 March 2017 at 17:30


Lisa,
This is actually quite similar to the GitHub issue with comments, except I believe:


  1.  The google doc has an index (which needs to be manually created and maintained)
  2.  The google doc has shifted the order of the content so when a new draft version of the SC is available then that version and the comments on it rise to the front of the page rather than being ordered chronologically
Is there more to it than that? I’m asking because I’m trying to understand what makes this better…

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Standards and Accessibility
Adobe

akirkpat@adobe.com<mailto:akirkpat@adobe.com>
http://twitter.com/awkawk


From: "lisa.seeman@zoho.com<mailto:lisa.seeman@zoho.com>" <lisa.seeman@zoho.com<mailto:lisa.seeman@zoho.com>>
Date: Thursday, March 16, 2017 at 10:57
To: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Cc: Michael Cooper <cooper@w3.org<mailto:cooper@w3.org>>
Subject: mock u[p page for issue tracking
Resent-From: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Resent-Date: Thursday, March 16, 2017 at 10:58

I made a mock up page for how we could track success criteria comments

https://docs.google.com/document/d/1WkLTHQ7NKwSM_J9RvsdzkGsQtpnN8A02s72uaiXo8aM/edit?usp=sharing<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1WkLTHQ7NKwSM_J9RvsdzkGsQtpnN8A02s72uaiXo8aM%2Fedit%3Fusp%3Dsharing&data=02%7C01%7C%7Cbbb5efed646047fc6d5e08d46c7cf365%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636252731292960027&sdata=hObjvwkK%2FBqoBbjfA%2FrOKxpo6CJHIzfGkwaI7Pu3WyQ%3D&reserved=0>


All the best

Lisa Seeman

LinkedIn<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fil.linkedin.com%2Fin%2Flisaseeman%2F&data=02%7C01%7C%7Cbbb5efed646047fc6d5e08d46c7cf365%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636252731292960027&sdata=9y1gnhLWqy4vRHhEWpIpC9JNY%2FQAeohp92B70ixPPjU%3D&reserved=0>, Twitter<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2FSeemanLisa&data=02%7C01%7C%7Cbbb5efed646047fc6d5e08d46c7cf365%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636252731292960027&sdata=oCc%2FAPXO85Q57RlkiWZSvqmFd%2FsAqXdOPWHe3JH8hm0%3D&reserved=0>

________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________