Is there any kind of policy about when we land code in the main Gaia repo vs a separate repository?
I've been told by participants that it seems arbitrary, which makes them feel like the core team can land whatever they decide to in the core, but others cannot. If there's a rule about what goes in the core vs what doesn't, expectations will be easier to manage, and decisions like this can be clear and consistent. On Wed, Oct 28, 2015 at 6:47 AM Tim Guan-tin Chien <[email protected]> wrote: > Hi all, > > Yesterday, managers was informed by Sandip that DT would like to > contribute to Gaia with an app called "Wallet", powered by NFC-related > technology and APIs already implemented and landed in Gecko. > > I've talk with Yoshi on this and we agreed Mozilla can make use of this > app, as a source of implementation reference and a manual testing tool. > > Product management have confirmed that there is no plan currently to brand > and further develop the app as a Firefox OS app. Yoshi also stated that the > current Gecko APIs only works with QC RIL so the app and the APIs will > likely not useful to anyone other than partners with QC and w/ a special > SIM. > > If this is the level of support we are happy with, I will rubber stamp the > code dump in to ./dev_apps/ and any lint error etc. will be xfailed. > > Thanks, > > > Tim > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
