<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 12/11/2016 11:51 PM, R Kent James wrote:<br>
<blockquote
cite="mid:0bad7a47-85e6-d207-4d5d-97a8bb695ef5@caspia.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
On 12/9/2016 12:25 PM, Ben Bucksch wrote:<br>
<blockquote
cite="mid:6535d802-ca7d-794c-1b93-9ac5281f10c4@beonex.com"
type="cite">R Kent James wrote on 29.09.2016 19:13: <br>
<blockquote type="cite" style="color: #000000;"> <br>
I made an argument to Mozilla, that I believe was largely
accepted, that said that consulting on a future platform for
Thunderbird is not really what we need. <br>
<br>
</blockquote>
<br>
I'm sorry to object here, but that statement couldn't be more
off. </blockquote>
<br>
You didn't copy the rest of my statement, and you did not consider
that.<br>
</blockquote>
<br>
Sorry, that got sent before I was finished.<br>
<br>
I was going to say that the main issue is not whether some sort of
rewrite is needed, the main issue is how to gather the resources to
do the rewrite. And in case it is not clear to all, that is where I
put the majority of my personal efforts.<br>
<br>
Show me your path to gather the 30 person-years of effort needed for
a rewrite, then we can talk about architecture. Otherwise, someone
will write a report, and nothing will happen. In the meantime, the
more pressing issues are associated with infrastructure changes and
build engineering, which is the major pain point with Mozilla at the
moment.<br>
<br>
:rkent<br>
<br>
</body>
</html>