Re: System Level API spec editors

This list is too long.  Even if we find a dozen qualified editors to
work on these drafts, the working group won't have the bandwidth to
review that many specs at the start, and the result will be
low-quality specs.

Do you have one or two of these that are most important to work on first?

Adam


On Fri, Jun 1, 2012 at 12:16 PM, Carr, Wayne <wayne.carr@intel.com> wrote:
> We will need to go through our usual (very long) approval process to
> participate in the WG, but we can make a provisional offer to edit the
> following specs.  This is an offer for after we get our internal (Legal)
> approval and the WG is approved and starts.
>
> Mozilla indicted they may offer editors for some, so we would be offering to
> join them on any that overlap – and we hope others offer editors for these
> or the other specs too.  We assume the WG will choose editors and that specs
> will have multiple editors.
>
> Specs we would offer editors for (we’re also still looking at another):
>
> Sensors API. Examples: No sample draft, but previous work was done in DAP,
> likely Web Intents based and including sensors in local network.
>
> Network Interface API. Examples: B2G Mobile Connection, B2G WiFi
> Information.
>
> Secure Elements API. Examples: none
>
> Alarm API. Examples: Tizen Alarm
>
> Calendar API. Examples: B2G Calendar, Tizen Calendar
>
> Contacts API. Examples: Tizen Contacts, B2G Contacts
>
> NFC API. B2G Web NFC, Tizen NFC
>
> Accounts API. Examples: none
>
> Bluetooth API. Examples: Tizen Bluetooth, B2G Web Bluetooth
>
> Media Storage API. Example: Tizen Media Content.
>
> Power Management API. Example: B2G Power Management
>
> Resource Lock API. Example: B2G Resource Lock
>
> Telephony API. Examples: B2G Web Telephony, Tizen Call
>

Received on Friday, 1 June 2012 20:35:01 UTC