On 2013-06-26 11:50 AM, Kyle Huey wrote:
On Wed, Jun 26, 2013 at 8:48 AM, Ehsan Akhgari <ehsan.akhg...@gmail.com <mailto:ehsan.akhg...@gmail.com>> wrote:The other question is, what we're going to do about negative feedback from the API review phase but where the feedback cannot be incorporated because of other concerns? I was thinking the module owner (or I guess the DOM module owner in certain cases) would make the call. But maybe I'm misunderstanding what sort of feedback you're thinking of; can you give an example? Certainly. In our efforts to support Web Audio, we've considered implementing some parts of the API which are not exactly webby after extensive discussions in the working group in the interest of having an interoperable implementation with other engines at some point. We've done so as a compromise. I'm certain that such an API, if it went through the proposed API review process, would get a negative feedback on the API design itself. Assuming that the DOM module owner upholds the opinion of the API review team, it would mean an impasse at the implementation since the feedback of the API review team would not necessarily affect the decision of the Audio Working Group. In this hypothetical scenario, following the process would probably mean that we would be unsable to ever ship Web Audio support. Any API review that doesn't take into account the need for interoperable implementations and the existence of legacy content is a waste of time. Most of the web would fail an API review then ...
Absolutely, but different people reviewing the APIs can have different priorities, which is why I raised the question on what exactly needs to be done upon receiving negative feedback from the API review.
Cheers, Ehsan _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
