0+dev-...@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 locations.
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.
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 a separate thread, Dees posted this recent note from Paul Irish:https://plus.google.com/113127438179392830442/posts/fR3iiuN4kEF > It is a passionate call to action: apps are real and the web is in urgent danger. I could not agree more. When I read it I felt motivated to evangelize but then I read this in one of the top comments and felt even more motivated:
> "There's the Chrome App Store, which is Chrome-specific ... there's Mozilla Marketplace, which is gratuitously Mozilla-specific …"
> I know this person is just misinformed but we absolutely *must* communicate that Mozilla is building an open apps platform. We're not building a Mozilla specific platform.
> The recent press on Firefox OS has been great. The press really seems to understand that we're trying to disrupt the mobile space with a new device. I've seen some passionate blog posts from developers too. However, I do not see people communicating exactly how our apps are fully portable to any HTML5 compliant device. It's simple: some app seller issues a receipt and the receipt is cryptographically verifiable. It's not tied to Mozilla's marketplace. We will be one marketplace out of many and the Firefox OS phone will be one compliant device out of many.
> 0+dev-...@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
> locations.
> 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.
> 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.
> Le 19/09/2012 22:41, Mark Giffin a écrit :
>> 0+dev-...@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
>> locations.
>> 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.
>> 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.
>> Le 19/09/2012 22:41, Mark Giffin a écrit :
>>> 0+dev-...@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
>>> locations.
>>> 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.
>>> 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.
This is great, Marc-Aurèle! Thanks for starting it! I think you have "thrown a net over it" and with some tweaking it should be pretty useful. One thing I am doing is carefully looking over the payments information and trying to make it as accurate as possible. There are a few other things that should probably be done also. I will work on it as I get the time. And of course anyone else is free to work on it also.
>> On 9/28/2012 3:53 AM, Marc-Aurèle DARCHE wrote:
>>> Le 19/09/2012 22:41, Mark Giffin a écrit :
>>>> 0+dev-...@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
>>>> locations.
>>>> 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.
>>>> 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.
> This is great, Marc-Aurèle! Thanks for starting it! I think you have "thrown a net over it" and with some tweaking it should be pretty useful. One thing I am doing is carefully looking over the payments information and trying to make it as accurate as possible. There are a few other things that should probably be done also. I will work on it as I get the time. And of course anyone else is free to work on it also.
Agreed! Thanks Marc A for putting this page together. As any MDN specialist will say, "blogs are not places for documentation" :) so I'm glad that you folded my rant into something more useful and into a more of referential structure. I can go through and also do some tweaks when Mark G is done. For example, I think there are a few items to add to the list of intended eventual standards.
>>> On 9/28/2012 3:53 AM, Marc-Aurèle DARCHE wrote:
>>>> Le 19/09/2012 22:41, Mark Giffin a écrit :
>>>>> 0+dev-...@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
>>>>> locations.
>>>>> 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.
>>>>> 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.
