Thunderbird Architecture Analysis SOW
ben.bucksch at beonex.com
Thu Mar 17 14:26:54 UTC 2016
I concur with asuth that the language " The existence of half-finished
features such as the global database (gloda)" paints gloda as problem
point, while it's actually one of the best parts of TB that could be
reused. At the same time, it should point out that TB didn't move much
in the last 5 years ,and the world progressed.
* historic growth of features like server-side search, quick-filter and
client-side search based on gloda; and message views based on folders
and messages (old style) vs. conversations (gmail style).
* need of 2010 era features like a new address book, sync address book
and calendar with smartphones, automatic message filtering, and
integration of short messaging like WhatsApp.
* keep and extend the distributed nature of protocols of all sorts
On 03/15/2016 05:28 PM, Gervase Markham wrote:
> On 15/03/16 19:26, Andrew Sutherland wrote:
>> On Tue, Mar 15, 2016, at 02:54 PM, Gervase Markham wrote:
>>> We will certainly provide this person with lots of material once they
>>> start; are you saying that this information would be useful to potential
>>> job applicants?
>> I'm saying that gloda is the least of Thunderbird's problems and
>> anything that places emphasis on it as something that needs to be fixed
>> without context is likely counterproductive.
> I'd happily replace that example or bullet with alternative text, if
> you'd like to suggest something. I have no wish to mislead the person
> into focussing on the non-critical issues.
> tb-planning mailing list
> tb-planning at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tb-planning