Hi Justin,
I think you're making two incorrect assumptions:
Although we've seen bad bugs (and bad memory bugs in particular) come from coders of all levels of experience, I personally am not at all comfortable with the idea of inexperienced Firefox front-end coders having review power in a module we intend to ship in Firefox.
That's not the situation we have. Jed Parsons and I have both landed a good bit of code (in BrowserID module) for FX Desktop and FXOS+Gaia. So we have experience. We're not the world's experts, but we also know our limitations and have always consulted with other teams starting with initial designs (e.g. Dolske).
Remember that an equally (if not more) important aspect of this module is the service integration piece, which is where we *are* indeed experts.
Second:
I may be missing something, but I don't think that prior experience with BrowserID -- which is entirely content JS, iiuc -- translates to expertise writing for the Firefox front-end. They are entirely different beasts.
You're right, but that's not the experience we're talking about: there is a native FXOS+Gaia (and a currently-dormant-but-landed native FX Desktop) implementation of Persona, including a whole bunch of service integration.
If one or more existing Firefox peers is willing to personally accept responsibility for this module, I'd be OK with this proposal. Do you think that's a fair burden to meet?
Given the above, and given the module's explicit callout that nay overlap will require full cooperation of other module owners, I don't think that's a fair burden to meet, if only because everyone is already incredibly over-committed.
-Ben _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
