Re: Requirements

For requirements, I think it makes sense to send an email to the  
public list, giving the requirement and associated justification. The  
subject line should indicate "requirements" and which area (api's,  
policy), and a short handle for the requirement. This can start a  
discussion thread.

When there is a related issue, include ISSUE-# (replacing # with the  
issue #) in the body of the message, and the message will  
automatically be linked to the ISSUE in tracker

regards, Frederick

Frederick Hirsch
Nokia



On Sep 22, 2009, at 2:18 PM, ext Tran, Dzung D wrote:

>
> Hello,
>
> On the requirements, do you send it to this group? Or use Tracker?
> Since I am new with this Tracker tool, I can't figure how to edit  
> the issue with a response.
>
> Thanks
> Dzung Tran,
>
>
> -----Original Message-----
> From: public-device-apis-request@w3.org [mailto:public-device-apis-request@w3.org 
> ] On Behalf Of Robin Berjon
> Sent: Tuesday, September 15, 2009 03:57 AM
> To: public-device-apis@w3.org
> Subject: Scribe selection
>
> Hi all,
>
> in order to properly minute calls, we have a rotating system of
> scribes which is described on the following page, along with the
> current list of upcoming scribes:
>
>   http://www.w3.org/2009/dap/victims-list.html
>
> If you have a good reason not to ever scribe, please let it be known
> and I'll take you off the list.
>
> -- 
> Robin Berjon - http://berjon.com/
>
>
>
>
>

Received on Tuesday, 22 September 2009 18:47:48 UTC