@lists.mozilla.org because MDN writers are on that list.
Great point Kumar. I agree that it should be made more clear that Open
Web Apps are intended to be standardized and to become part of "the web."
I can't speak for marketing-type writing but I work on the Open Web Apps
developer docs and I have noticed that it is not really clear in much of
the docs where Mozilla ends and standards begin. Like which parts of the
nuts and bolts of OWA are intended to eventually be standardized, where
Firefox comes in and so on. I have been thinking about how to make this
clear throughout the developer docs, or at least in a couple visible
I want to at least identify the parts of OWA that are intended to be
standardized at some point. I'm interested in feedback on my attempt below.
Intended eventual standards:
- OWA manifest https://developer.mozilla.org/en-US/docs/Apps/Manifest
- OWA API (mozApps API)
- Web APIs to access things like phone, geolocation, etc. These are
numerous and messy to explain the status of.
- Mozilla Marketplace, I have heard that the idea is to export this
also, if not standardize it.
- identity? (Persona/BrowserID)
- what else?
And then maybe a list of related standards or proposed or eventual
standards that are related to OWA but Mozilla is not driving them.
I'm thinking that an MDN article is needed with a title like "Open Web
Apps and Web standards". I could probably steal a lot from your nice
blog post Kumar. And maybe some indication on Apps doc pages that they
are "non-standard" or "intended standard" or whatever.
On 9/14/2012 9:34 AM, Kumar McMillan wrote: