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

Fwd: [DRAFT] Media Capture Task Force Charter

From: Robin Berjon <robin@berjon.com>
Date: Tue, 22 Nov 2011 13:18:43 +0100
To: DAP <public-device-apis@w3.org>
Message-Id: <09D77D66-A919-4526-A225-677D843354C6@berjon.com>
Any feedback on this before it becomes solid and we get started?

Begin forwarded message:
> Resent-From: public-device-apis@w3.org
> From: Robin Berjon <robin@berjon.com>
> Date: November 16, 2011 15:42:59 GMT+01:00
> To: "public-device-apis@w3.org public-device-apis@w3.org" <public-device-apis@w3.org>, public-webrtc@w3.org
> Subject: [DRAFT] Media Capture Task Force Charter
> archived-at: <http://www.w3.org/mid/22C84B78-685C-4B6F-85E4-A12BC073D075@berjon.com>
> 
> Dear WebRTC and Device APIs Working Groups,
> 
> As discussed during our joint and respective meetings, here is a draft proposal for a TF charter on media capture. As indicated, it is only a draft and is very much open to feedback, concerns, etc.
> 
> As per process, a TF charter is a rather informal document that only needs to document the TF's existence. It can just live in an email that is linked to from our groups' pages — so we don't need to do anything complicated and only need to write down what we think is important to capture (i.e. no boilerplate required).
> 
> """
> The Media Capture Task Force is a joint task force of the Web Real-Time Communications and Device APIs WGs that aims to produce APIs to capture media from cameras and microphones in a manner that is both simple for local-only use cases and amenable to real-time streaming. This work will be produced by iterating over the existing "getUserMedia()" API.
> 
> The mailing list on which the TF's discussions take is public-media-capture@w3.org. The chairs are Stefan Håkansson and Harald Alvestrand. Since any participant in either group can join the TF, decisions are made by consensus inside of the task force and do not require separate ratification by the wider groups.
> 
> Operational modalities such as whether or not to have phone and/or face to face meetings, as well as where to store the draft document are left to the TF to decide by consensus.
> 
> Given that this deliverable is covered by both groups' charters, the resulting specification will be covered by the union of RF commitments for both groups.
> """
> 
> Ideally, we should be able to garner sufficient feedback inside of a week to tweak this charter and just get to work, which my understanding is what everyone wants to do!
> 
> -- 
> Robin Berjon - http://berjon.com/ - @robinberjon
> 
> 

-- 
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Tuesday, 22 November 2011 12:19:21 GMT

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