My belief is that this is not a submodule for Fennec. Much of this is standalone Java code that isn't inherently app specific, and could be used to support multiple/different applications. To me, the closest equivalent for this module would be Toolkit, which is generally where this type of code lives for desktop apps.
That said, I don't think it's necessary to pre-constrain scope here. If we get to a future where it doesn't make sense to depend on this module for a new app, I would expect that we'd have a discussion about the best path forward regardless of how the lines are drawn on paper. -- Mike On 2013-03-05, at 1:14 PM, David Ascher wrote: > This is a nit, but the name and/or placement in the module tree could > (should?) specify that this is a submodule of the Firefox-on-android product? > I can imagine a future where we have other things on android which have > background services, and I would expect if such a future were to occur we'd > have a reasonable discussion about whether the same codebase should be used > or not. > > --da >
_______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
