W3C home > Mailing lists > Public > public-cognitive-a11y-tf@w3.org > February 2017

Re: Keeping SC text in the pull request description

From: Gregg C Vanderheiden <greggvan@umd.edu>
Date: Tue, 21 Feb 2017 08:15:33 -0500
Cc: public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
Message-Id: <D0F843E9-F89F-4F88-9B12-1FCC0DC612E2@umd.edu>
To: Alastair Campbell <acampbell@nomensa.com>
Not everyone finds that method very usable.   We use it in our projects all the time — but for many it is not usable .    It may be accessible but not usable.  

Gregg C Vanderheiden

> On Feb 20, 2017, at 6:53 PM, Alastair Campbell <acampbell@nomensa.com> wrote:
> If we stick to pull requests as the place for discussion, then I recommend:
> Keep the up to date SC text & new glossary terms in the description of the pull request.
> That way it is at the top, and (assuming the SC manager does the pull request) it can be kept up to date.
> I had issues on a Resize text where it went through a lot of change, and people were referring to the old version in the issue, which I couldn't update. Frustrating for everyone, so it seems best to keep it up to date at the top of the place it is being discussed.
> Cheers,
> -Alastair
Received on Tuesday, 21 February 2017 13:16:19 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:58 UTC