On Tue, Nov 27, 2012 at 10:49 AM, Henri Sivonen <hsivo...@iki.fi> wrote: > Therefore, I propose that we adopt the following policy: > 1) APIs that are shipped on the release channel shall be shipped > without a prefix. > 2) If we ship APIs that don't have specs already, we'll write specs.
In yesterday’s platform meeting, it turned out that I had misunderstood Randell’s position on prefixing WebRTC. Even though in general, it might be bad for a policy to have seemingly ad hoc exceptions, I think making an exception for WebRTC is reasonable, because: * WebRTC is already in the implementation pipeline and the policy was meant for new features and not for abruptly removing existing prefixes, so it seems reasonable to stretch the notion of “existing feature” to an in-the-pipeline feature in the case of a huge feature like WebRTC where making changes right now might be too disruptive. * It appears that there’s some kind of commitment made in the WG involved as in the case of WebGL. * WebRTC is a uniquely huge feature (or set of features) and it needs special rollout (unusual iteration after release). * Even if WebRTC and WebGL were excluded, I think it would be a big win to stop prefixing other APIs that are introduced. Also, a clarification was asked about whether the policy was proposed to apply to new features only or also to existing features. (I intended it to apply to new features.) Therefore, I propose that we adopt the following policy: 1) Excluding WebGL and WebRTC APIs, new APIs that are shipped on the release channel shall be shipped without a prefix. 2) If APIs that don’t already have specs are shipped, we’ll get specs written. (For clarity, the above formulation does not require WebGL or WebRTC to have prefixes.) -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
