What happened to hiring an architect?

Ben Bucksch ben.bucksch at beonex.com
Wed Dec 21 00:05:31 UTC 2016


Great! 

Where is the glodastrophe work organized? source code, plans for architecture and UI, bug tracker, mailing list to announce progress and discuss work organization etc.?

Ben


Am 20. Dezember 2016 20:22:20 MEZ, schrieb Jim <squibblyflabbetydoo at gmail.com>:
>On Tue, Dec 20, 2016 at 12:48 PM, Ben Bucksch <ben.bucksch at beonex.com>
>wrote:
>
>> I'm saying: we need to accept that fact that foregoing gecko is not
>an
>> option. Unmarrying thunderbird doesn't work either. So, that leaves
>only
>> one choice: Write a new client. Yes, that will take 1-3 years. That's
>why
>> we need to start now. Once gecko is not usable by thunderbird
>anymore, it
>> will be to late to start. It will be game over. Accept that, and act
>> accordingly. That's my point.
>>
>
>This is pretty much where I'm at. There are surely a few things we can
>salvage from Thunderbird, but even if we somehow magically fixed the
>Gecko
>issue, Thunderbird's codebase itself is showing its age. There are
>major
>architectural issues (Mork, broken mail tab multiplexing, 3+ different
>ways
>to listen for folder events, etc) with it that we've never had the
>resources to fix, not even when Thunderbird had paid staff.
>
>All things considered, I'd rather spend time helping out on
>Glodastrophe,
>since I think it'd be easier to add features to that than to fix
>Thunderbird.
>
>- Jim
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>tb-planning mailing list
>tb-planning at mozilla.org
>https://mail.mozilla.org/listinfo/tb-planning

-- 
Sent from my mobile phone. Please excuse the brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/tb-planning/attachments/20161221/77c57b85/attachment.html>


More information about the tb-planning mailing list