On 2013-06-26 11:21 AM, Andrew Overholt wrote:
On 24/06/13 05:52 PM, Ehsan Akhgari wrote:
There are two things that I think can use clarification.  One is what
we're going to do about "trivial changes"?  Do all web facing features
ned to go through this process?

I was going to put a blurb about "trivial changes" but thought it would
be too hard to define.  Would you be okay with it being in there with
something like "definition of triviality is left up to the module owner"?

Do we really need to precisely define it? I mean, at some point we should rely on people to use their best judgement. Of course, needless to say, the module owner will still have the power to act at the final arbiter on these matters.

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.

Cheers,
Ehsan

_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to