Per previous discussion[1], I am happy to announce that we have now
created the new Firefox Technical Leadership Module[2], governed
by the Technical Leadership Module Committee. One
of the committee’s first steps will be to clean up the existing list
of modules, removing now obsolete modules and t
Hello,
Thanks everyone for comments on the first version of this proposal both on
and off list. Below is our second attempt. The changes revolve around two
points:
* First, only two of the positions are explicitly tied to the Mozilla
Corporation, the rest are left unspecified. This felt like a
On Fri, 2 Mar 2018 at 16:29 Justin Dolske via governance <
governance@lists.mozilla.org> wrote:
> Overall, +1 on filling this gap in the module system.
>
> One comment/question...
>
> IME a significant number of possible-escalation grumbles have been less
> about the _technical_ aspects, and more
On 2018-03-07 2:16 PM, Dave Camp wrote:
Would EKR and my commitment (representing moco leadership) and
Mitchell's commitment (representing project leadership) that we'll
revisit and revise the description if the org structure changes be
sufficient to address your concerns?
Yes, definitely.
On Wed, Mar 7, 2018 at 2:27 PM Byron Jones 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
> >
Would EKR and my commitment (representing moco leadership) and Mitchell's
commitment (representing project leadership) that we'll revisit and revise
the description if the org structure changes be sufficient to address your
concerns?
On Fri, Mar 2, 2018 at 10:32 PM mhoye via governance <
governanc
On 8 March 2018 at 01:27, Byron Jones via governance <
governance@lists.mozilla.org> wrote:
> there's a few modules listed as applicable at first glance appear to be
> obsolete:
>
>- BrowserID
>>
>
I can confirm that this module is 100% obsolete. The few remaining places
where we use BrowserI
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 modul
On Fri, Mar 2, 2018 at 1:43 PM Ben Kelly wrote:
> On Fri, Mar 2, 2018 at 2:49 PM, Dave Camp via governance <
> governance@lists.mozilla.org> wrote:
>
>> FTLM Proposed Structure
>>
>>
>> Instead of a single owner, the Technical Leadership would be governed by a
>> Technical Le
On 2018-03-02 4:43 PM, Ben Kelly via governance wrote:
Why is this tied to the Mozilla Corporation org chart?
I have a similar concern; this proposal seems to imply long-term
commitment to on the part of the Mozilla Corporation to a specific
organizational structure supporting it.
I can se
On Fri, Mar 2, 2018 at 2:49 PM, Dave Camp via governance <
governance@lists.mozilla.org> wrote:
> FTLM Proposed Structure
>
>
> Instead of a single owner, the Technical Leadership would be governed by a
> Technical Leadership Module Committee (TLMC) consisting of the
> DE/Fell
Overall, +1 on filling this gap in the module system.
One comment/question...
IME a significant number of possible-escalation grumbles have been less
about the _technical_ aspects, and more about general disagreements around
outcomes or direction. Things like random objections to feature removals
12 matches
Mail list logo
