Proposal to start a new implementation of Thunderbird based on web technologies

neandr neandr at
Mon Apr 3 21:23:43 UTC 2017

Following Ben's or Joshua's points about a next-TB it will raise 
questions which technology stack, tools, testing, design rules etc 
should be used, much more should be generalized for it.

With the 'contacts/caldav' project which has been run last year at the 
New Zealand University it was obvious using a technology kit like React 
gives a great boost for productivity and structuring the solution. But 
already that small project -- compared what a next-TB will be -- showed 
also there are many possibilities for "dialects" with the various parts. 
So before starting the next-TB project it would make sense to have a 
common understanding for the technology base.

Paul suggested a few points for the technology stack and more, he 
pointed to an important issues: legal aspects. For React there could be 
a patent problem, see here:

​And also Paul's contribution to a Drupal discussion about React usage 
is worth to read:

React is used with the DevTools and it would be interesting to hear from 
the DevTools how they live with that patent issue. Thunderbird where 
ever it finds it's new home should be save from the start with new 
technologies and 3rd-party contributions.

This is only one example why a serious analysis is necessary and 
stringent standards are an absolute must.

More information about the tb-planning mailing list