[Maildev] Engineering Council or Engineering Steering Committee (ESC) - where art thou?

Jörg Knobloch jorgk at jorgk.com
Fri Aug 31 02:55:11 EDT 2018


On 31/08/2018 01:30, Ben Bucksch wrote:
> The ESC is *not* in charge of the UI, only of technical aspects.

The larger technical aspect is: How much of an HTML editor do we want 
Thunderbird to be.

There appear to be tendencies to deconstruct HTML capabilities for no 
apparent reason, or perhaps with the argument, that you can do stupid 
things with it. Some recent quotes:

https://bugzilla.mozilla.org/show_bug.cgi?id=690644#c44:
Yack (sic) - too many things inherited from Editor :(

https://bugzilla.mozilla.org/show_bug.cgi?id=1486051#c3
Falls into the category we-have-it-because-we-inherited-editor - there's 
fairly little reason to have something like this in an email client.

So I just wanted to present the (perceived) tendency of the module owner 
to a wider audience. However, since we follow the Mozilla module owner 
system, the module owner makes the final call and all discussion is more 
or less futile.

I reiterate that the so-called ESC as a larger group of developers, see 
http://lists.thunderbird.net/pipermail/maildev_lists.thunderbird.net/2018-August/001254.html 
for a proposed list of members, has not been established and even the 
group of "technical directors" of Magnus, BenB, Kent and myself as per 
Thunderbird Council decision of 2017-06-23 as decision makers is under 
discussion of being abolished again. Certainly not all people in the 
group are still available or their membership has been questioned 
otherwise, see 
https://mail.mozilla.org/pipermail/tb-planning/2018-August/006142.html.

So as I see it: During the course of the year we have achieved nothing 
except the creation of the Maildev mailing list, and steps of getting 
more people involved in the decision making, not only the discussion, 
are even being wound back. So much for governance changes :-(

Jörg.




More information about the Maildev mailing list