The message you quote has a specific example - "Mozillians who have experience designing JS APIs and will have at least one representative from the JS team at all times" is probably not the best group to determine whether we should implement support for/ship SPDY, for example. I think it's clear the document was written with a focus on Web APIs, applying it more broadly to things like network protocols is (I think) a laudable goal, but might require some tweaks.
Gavin On Wed, Jun 26, 2013 at 1:17 PM, Ehsan Akhgari <ehsan.akhg...@gmail.com> wrote: > On 2013-06-26 12:28 PM, Brian Smith wrote: >> >> I understand that Brendan would like to have more/all web-facing >> functionality covered by some kind of guidelines similar to what you >> propose. I am not against that idea. However, I don't think the rules you >> write work very well for the modules I work in. For example, I don't think >> this part makes sense for networking or PKI: "The Mozilla API review team >> will consist of Mozillians who have experience designing JS APIs and will >> have at least one representative from the JS team at all times." After the >> quarter is over, I am willing to spend time working with you to try to >> define a policy that might work better for modules that aren't >> DOM/JS-related. > > > I'm still not sure why it won't work well for the modules that you work on. > Can you please clarify, perhaps with an example? Are there parts of your > work which involves things that web developers can detect which doesn't fit > with what's being proposed here? > > Cheers, > Ehsan > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
