W3C home > Mailing lists > Public > public-w3process@w3.org > November 2014

Re: UI Mockup [Was: CfC: create a public list to announce new publications; deadline Oct 15]

From: <chaals@yandex-team.ru>
Date: Fri, 07 Nov 2014 07:09:38 +0100
To: Wayne Carr <wayne.carr@linux.intel.com>, Ian Jacobs <ij@w3.org>, Arthur Barstow <art.barstow@gmail.com>
Cc: public-w3process <public-w3process@w3.org>, Ted Guild <ted@w3.org>
Message-Id: <42021415340578@webcorp02g.yandex-team.ru>

06.11.2014, 17:13, "Wayne Carr" <wayne.carr@linux.intel.com>:
> On 2014-11-06 03:31, chaals@yandex-team.ru wrote:
>> 04.11.2014, 23:08, "Ian Jacobs" <ij@w3.org>:

>>> Here's a rudimentary UI to make it easier for chairs and team contacts to send these review notices:
>>> http://www.w3.org/2014/11/getreview/
>>> Would something like this be useful?
>> Very, but it *really* needs to cover normal Working Drafts.
> And Editor's drafts too. It could be a WG wants review of a new feature
> in the Editor's draft that they're deciding whether to develop or not.
> For instance, a WG could have sections marked experimental, that they
> don't put into their TRs. They could want feedback on one of those in
> particular and so point to the section of the Editor's draft.
> Also, reviews of proposed charters and other non-spec reviews like
> requests for feedback on what new features a WG should consider would
> need a different form that links to a document that isn't a spec, but is
> the thing to be reviewed.

Actually, you could just put "Other". You get a link to a URI, pointer to where to comment and by when, and a request for what to do.

Although if you want comments in a wiki or on github, an email address isn't going to be appropriate...


Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com
Received on Friday, 7 November 2014 06:10:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:51:23 UTC