W3C home > Mailing lists > Public > public-device-apis@w3.org > December 2011

Re: Draft minutes 14 December 2011

From: Glenn Adams <glenn@skynav.com>
Date: Wed, 14 Dec 2011 22:52:10 -0700
Message-ID: <CACQ=j+cpSF+xSe622QDDfznbHC8dNt-A_PKuvZpVO7xKpcrSNg@mail.gmail.com>
To: Josh Soref <jsoref@rim.com>
Cc: DAP <public-device-apis@w3.org>
you might want to change the instructions at [1] to read something like:

If you do not register via Zakim, then on each call please register
attendance in IRC using

*Present+ firstName_lastName*
[1] http://www.w3.org/2009/dap/

On Wed, Dec 14, 2011 at 10:10 AM, Josh Soref <jsoref@rim.com> wrote:

> Attached are Draft minutes from today's teleconference, 14 December 2011,
> for approval at our next meeting (4 January 2012).
>
> regards, Josh
>
> Josh Soref
> RIM
>
> First, if people haven't managed to teach Zakim about their phone number,
> there's a form [1] to add your number / name mapping (this will save you
> effort later).
>
> As a minor footnote, the scripts are fairly intelligent, so there are some
> things that one doesn't need to do. If you're called into the telcon via
> Zakim (and have at some point done "zakim, aaaa is me" or "zakim, ??p1 is
> Josh_Soref" [2] (or used the form [1]), you don't need to do Present+, as
> Zakim does it for you (according to the name you gave Zakim when you
> introduced yourself) -- generally the present+ requirement is more for F2F
> where you *aren't* calling in (and thus Zakim can't help you out -- unless
> someone has done "Zakim, BallRoom has John, James", "Zakim, Jim entered
> BallRoom", or "Zakim, Jill is with James" [3]). Thus, the following
> additional lines are added by me to the end of my input minutes for
> scribe.pl:
>
> Present- +46.1.08.01.aaaa
> Present- AnssiK
> Present- Cathy
> Present- Claes
> Present- Clarke
> Present- fjh
> Present- glenn
> Present- richt
> Present- darobin
>
> The first one is because Zakim is a bit silly (that's ok), the others are
> because otherwise each of the listed people would otherwise appear twice in
> attendees (once in full form, and once with the short nick which I'm
> removing above). As a note, I now use a script (it isn't perfect, but it's
> fairly clever, I've been trying to send it out but that's been painful)
> which produces the following output:
>
>
> Present:
> Anssi_Kostiainen        Bryan_Sullivan  Cathy_Chan      Claes_Nilsson
> Clarke_Stevens  Deepanshu_Gautam        dom     Dsr
> Dzung_Tran      Ernesto_Jimenez Frederick_Hirsch        Glenn_Adams
> Josh_Soref      Nigil   Pieter  Rich_Tibbett
> Robin_Berjon    Russell_Berkoff(Samsung)
>
> Speakers:
> AnssiK  bryan   Cathy   Claes   Clarke  darobin Deepanshu       dom
> dsr     fjh     Josh_Soref      richt
>
>
> Anssi_Kostiainen:
>        AnssiK
> Bryan_Sullivan:
>        bryan
> Cathy_Chan:
>        Cathy
> Claes_Nilsson:
>        Claes
> Clarke_Stevens:
>        Clarke
> Deepanshu_Gautam:
>        Deepanshu
> dom:
>        dom
> Dsr:
>        dsr
> Frederick_Hirsch:
>        fjh
> Josh_Soref:
>        Josh_Soref
> Rich_Tibbett:
>        richt
> Robin_Berjon:
>        darobin
>
> Not definitively identified as speaking:
> Dzung_Tran      Ernesto_Jimenez Glenn_Adams     Nigil   Pieter
>  Russell_Berkoff(Samsung)
>
> Humans more or less perform the same magic when reading minutes or irc
> logs. It can complain about ambiguity, such as when sicking + timeless are
> both scribed as 'JS' (but only when we're both present+ by our real names)
> or ArtB and AdrianBa are both scribed as 'AB'. When it produces output
> that's confusing, I work to adjust the minutes so that this confusion
> wouldn't arise.
>
> [1] https://www.w3.org/1998/12/bridge/info/name.php3
> [2] http://www.w3.org/2001/12/zakim-irc-bot.html#callers
> [3] http://www.w3.org/2001/12/zakim-irc-bot.html#attendance
>
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-public
> information. Any use of this information by anyone other than the intended
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be unlawful.
>
Received on Thursday, 15 December 2011 14:50:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:27 GMT