On Wed, Mar 7, 2018 at 2:27 PM Byron Jones <g...@mozilla.com> wrote: > Dave Camp wrote: > > I've been working with Mitchell and some other folks over the past few > > months to better reflect Firefox technical leadership in the module > > ownership system. I think we're at a point where we're ready to make the > > first proposal: > > [..] > > awesome :) > > > It seems clear that the module system should document ownership for the > > technical side of Firefox code, development practices, and tools. We > > propose to restructure the Firefox-related modules under control of a new > > “Technical Leadership Module Committee” (TLMC), as described below. > > [..] > > is part of this proposal to restructure the existing firefox-related > modules, or will this just to add a new "top-level" module above the > existing modules (thereby making a restructure easier if required)? >
More the latter - no restructure is laid out here, but we propose that this is the group that should be held responsible for the structure of those modules (and so I'd expect restructuring proposals down the line). > what is the proposed process for requesting feedback/decisions from the > TLMC? > For now let's continue to use the governance list. We'll let this list know if that changes. > > Appendix: Proposed List of Applicable Modules > > there's a few modules listed as applicable at first glance appear to be > obsolete: > Yeah - we were assuming responsibility for cleaning those up, but if existing owners there want to disband those modules that's fine too. > > > - Add-On SDK > > - Firefox for Metro > > - BrowserID > > > - SyncLoop > i assume this is "Sync" and "Loop". loop has been shutdown. > > Yeah, that was a formatting error. Thanks, -dave > > -- > glob — engineering productivity — moz://a > > _______________________________________________ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance
