> If you think a new module is really warranted here, you should probably get > dcamp's green light since this is really breaking an existing part of a > module into a new module. Also as I mentioned before, as a pure matter of > technicality, if you want to create a new module you should figure out how > you'd do that with Firefox not having submodules. The new module would need > a home. :-)
Thanks for the feedback. I didn't know Firefox didn't have submodules anymore. For now, we're pretty much tethered to Firefox and as such, perhaps no new module is warranted yet. I'll chat with dcamp. - Olivier +1 (647) 299-6074 > On Oct 28, 2015, at 9:05 PM, Ehsan Akhgari <[email protected]> wrote: > > On 2015-10-28 4:26 PM, Olivier Yiptong wrote: >> The non-Firefox part of this module proposal lives outside of Firefox and >> would be updated out-of-band from Firefox. > > The location of the source code is not the important issue, IMO. So far at > least the Firefox module has covered all user-facing aspects of the browser, > and the new tab page is no different. Where it is hosted and how it's > implemented should not affect what module governs it. > > You can document the knowledge of the proposed owners and peers by adding > them as Firefox peers focusing on specific parts of the browser code. I > think for all intents and purposes the end result is the same for you. For > example, I'm a Firefox peer, but I usually only review private browsing > specific code. > > If you think a new module is really warranted here, you should probably get > dcamp's green light since this is really breaking an existing part of a > module into a new module. Also as I mentioned before, as a pure matter of > technicality, if you want to create a new module you should figure out how > you'd do that with Firefox not having submodules. The new module would need > a home. :-) > >> Basically, except for the parts where we are tethered to Firefox to, this >> web application is independent of Firefox. >> This opens up possibilities... who knows, we may make a Firefox newtab for >> Chrome. > > The awesome upcoming development will hopefully happen no matter what module > governs the code. In the current Firefox module, individual peers make > decisions governing their own areas and I trust that the same system can give > you enough altitude to explore the future of the module as you'd like. :-) > > Cheers, > Ehsan
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
