On Tuesday 2013-09-17 16:42 -0400, Andrew Overholt wrote: > When we expose new things to web developers, I'd like us to consider > some suggestions. Due to a number of factors, I've made them > suggestions and not a set of pan-module hard rules. > > https://wiki.mozilla.org/User:Overholt/APIExposurePolicy > > I've incorporated lots of feedback given on previous revisions > (thanks!) and feel like this is ready to go.
One comment on this draft: # Once we have agreement in the Web community about the stability # of an API and we feel it is ready, we will make it generally # available to the platform (more details below on this process). I think I'd drop the "have agreement in the Web community about the stability of an API and" in favor of leaving that bit to the later prose, which describes the intent in more detail. (This is at least partly because I think "have agreement in the Web community" is probably too strong a term; I'm not sure such agreement ever exists.) Otherwise I think it looks good. (Though, also, I wonder if the "When is an API ready to be shipped by Gecko?" section should distinguish the "indications" it uses more clearly from "requirements".) -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla https://www.mozilla.org/ 𝄂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
signature.asc
Description: Digital signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
