On Jun 26, 2013 7:33 PM, "Ehsan Akhgari" <ehsan.akhg...@gmail.com> wrote: > > On 2013-06-25 9:02 PM, Jonas Sicking wrote: >> >> "For new products, APIs that have not yet been embraced by other >> vendors or thoroughly discussed by standards bodies may be shipped >> only as a part of this product. Standardization must however start >> within X months after shipping initial version of the product". > > > Hmm, is there any reason why we're not explicitly making this about Firefox OS? Talking about a new product means that for example Firefox for Metro can also do this when it's shipped. So far we've been able to avoid a lot of this problem on our more traditional products, so maybe it's not a great idea to open a wildcard for all future products. If, in the future, another product proves to be as different in its requirements and challenges as Firefox OS is, we can always amend the policy to include that as well.
I don't think this is for FirefoxOS only. For example WenRT also seems like it could have fallen under this policy. I guess I don't see Firefox for Metro as a new product but rather simply adding support for another platform for the existing Firefox product (not saying that there hasn't been a huge amount of work going into that obviously). But I agree the line is fuzzy. / Jonas _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
