Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
module ownership of webapprt/ directory
65 views
Skip to first unread message
Myk Melez
May 2, 2012, 3:44:31 AM5/2/12
to mozilla-g...@lists.mozilla.org, Gavin Sharp, Dave Townsend, Benjamin Smedberg
Governors!
I and some other engineers recently landed a desktop webapp runtime to
the webapprt/ top-level directory of mozilla-central. I propose we make
this directory part of the Firefox module, adding the directory to the
module's list of source dirs and giving the module's owner and peers
responsibility for its code.
The runtime currently only builds with Firefox. That isn't essential, as
it could be integrated into another Mozilla product. But we don't have
any concrete plans to do so. Thus making it part of the Firefox module
would align authority over the code with its impact in the codebase.
And its principal developers include Firefox peers and engineers like
Felipe Gomes and Tim Abraldes, while other Firefox peers, such as
Benjamin Smedberg, have taken an active role in its development via
reviews, feedback, and related fixes.
In fact, we've been operating under the informal policy that changes to
the runtime must go through the Firefox review process, and that has
worked well. So the Firefox module seems like a natural home for the code.
I ran this proposal by several Firefox and Toolkit principals (cc:ed),
and they are fine with it. I've considered other options--in particular,
creating a new module for it, or making it a submodule of Toolkit--and
this one seems the best in terms of adding the least additional
structure while aligning code authority with impact.
Thoughts?
-myk
I and some other engineers recently landed a desktop webapp runtime to
the webapprt/ top-level directory of mozilla-central. I propose we make
this directory part of the Firefox module, adding the directory to the
module's list of source dirs and giving the module's owner and peers
responsibility for its code.
The runtime currently only builds with Firefox. That isn't essential, as
it could be integrated into another Mozilla product. But we don't have
any concrete plans to do so. Thus making it part of the Firefox module
would align authority over the code with its impact in the codebase.
And its principal developers include Firefox peers and engineers like
Felipe Gomes and Tim Abraldes, while other Firefox peers, such as
Benjamin Smedberg, have taken an active role in its development via
reviews, feedback, and related fixes.
In fact, we've been operating under the informal policy that changes to
the runtime must go through the Firefox review process, and that has
worked well. So the Firefox module seems like a natural home for the code.
I ran this proposal by several Firefox and Toolkit principals (cc:ed),
and they are fine with it. I've considered other options--in particular,
creating a new module for it, or making it a submodule of Toolkit--and
this one seems the best in terms of adding the least additional
structure while aligning code authority with impact.
Thoughts?
-myk
Mitchell Baker
May 7, 2012, 1:56:59 PM5/7/12
to Myk Melez, Gavin Sharp, mozilla-g...@lists.mozilla.org, Dave Townsend, Benjamin Smedberg
Myk
This seems well thought-out and to cover all aspects. I'd say if you
don't hear anything suggesting otherwise in the next 3 days, go ahead
and make the changes thursday or friday, or any time afterwards
thanks!
mitchell
This seems well thought-out and to cover all aspects. I'd say if you
don't hear anything suggesting otherwise in the next 3 days, go ahead
and make the changes thursday or friday, or any time afterwards
thanks!
mitchell
Mitchell Baker
May 7, 2012, 1:56:59 PM5/7/12
to Myk Melez, Gavin Sharp, mozilla-g...@lists.mozilla.org, Dave Townsend, Benjamin Smedberg
Myk
This seems well thought-out and to cover all aspects. I'd say if you
don't hear anything suggesting otherwise in the next 3 days, go ahead
and make the changes thursday or friday, or any time afterwards
thanks!
mitchell
On 5/2/12 12:44 AM, Myk Melez wrote:
This seems well thought-out and to cover all aspects. I'd say if you
don't hear anything suggesting otherwise in the next 3 days, go ahead
and make the changes thursday or friday, or any time afterwards
thanks!
mitchell
On 5/2/12 12:44 AM, Myk Melez wrote:
Myk Melez
May 14, 2012, 12:28:51 AM5/14/12
to Mitchell Baker, Gavin Sharp, mozilla-g...@lists.mozilla.org, Dave Townsend, Benjamin Smedberg
On 2012-05-07 10:56, Mitchell Baker wrote:
> This seems well thought-out and to cover all aspects. I'd say if you
> don't hear anything suggesting otherwise in the next 3 days, go ahead
> and make the changes thursday or friday, or any time afterwards
Thanks Mitchell. Having heard no additional comments, I just added the
> This seems well thought-out and to cover all aspects. I'd say if you
> don't hear anything suggesting otherwise in the next 3 days, go ahead
> and make the changes thursday or friday, or any time afterwards
webapprt/ directory to Firefox's list of Source Dirs:
https://wiki.mozilla.org/Modules/Firefox
-myk
Mitchell Baker
May 14, 2012, 12:45:34 AM5/14/12
to Myk Melez, Gavin Sharp, mozilla-g...@lists.mozilla.org, Dave Townsend, Benjamin Smedberg
0 new messages