Axel Grude axel.grude at
Fri Dec 7 10:06:52 UTC 2018

Why not - it's a start.

I don't expect everything to surface free of charge, but I am currently incorporating 
a business. That means within the next few months I want to start an indigogo 
fundraiser campaign to *pay* developers to write the necessary APIs *and landthem in 
TB Core*. I think landing them (having them approved for general use) should almost be 
a requirement for payment, because it is no good to fund something that is potentially 
only temporary.

Once this has been approved, the next important question is, will there be free 
mentoring from the Thunderbird team to get people started? I would suspect people who 
already work at core Tb patches are too busy to write APIs, so this may attract some 
fresh commercial developers instead.


*Axel Grude <mailto:axel.grude at>*
Music Production and Composition
Thunderbird Add-ons Developer (QuickFolders 
quickFilters <>, 
QuickPasswords <>, Zombie Keys 
<>, SmartTemplate⁴ 
Visit my YouTube Channel <> for email 
productivity tips Get Thunderbird!
> *Subject:*MailExtensions
> *From:*Ben Bucksch <ben.bucksch at>
> *To:*<tb-planning at>
> *Sent: *Friday, 12/7/2018 04:52 GMT ST +0000 [Week 49]
> Let's rename "WebExtensions" to "MailExtensions" and "WebExperiments" to "Addon API 
> Experiments".
> See below:
>> I think WebExperiments are a also great opportunity for grass-roots action.
>>  1. Individual addon developers can implement an API that they are lacking, and use
>>     it immediately in their addon, without waiting for Thunderbird.
>>  2. Then, they can generalize the API, make it generic for other addons to use
>>  3. They can propose the API for inclusion, and seasoned developers can look over
>>     the API, improve it. (This step is important to keep the public APIs
>>     consistent, generic, stable, and of high quality.)
>>  4. It's included in Thunderbird
> All addon authors: This is your call to action!
> Go and try to implement your addon as MailExtension. You will miss APIs left and 
> right, everywhere. But with "Addon API Experiments", you have all the access that 
> you have from a normal restartless XPCOM addon (without XUL), and you can implement 
> the APIs you need. Then, proceed with the steps outlined above, and other addon 
> developers can benefit from it, and Thunderbird will start to develop a stable (!) 
> API surface for addons.
> With stable addon APIs, the "my addon stopped working after upgrade" should 
> gradually stop as well.
> Please don't expect somebody else to do it for you. The TB Council or Core devs are 
> too busy keeping Thunderbird running. This is now up for the addon developers to do, 
> bottom up, grass roots fashion. Get your hands dirty and help!
> FWIW, that's what we did with Owl 
> <>, too.
> Ben
> _______________________________________________
> tb-planning mailing list
> tb-planning at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: thunderbird_blog2.png
Type: image/png
Size: 846 bytes
Desc: not available
URL: <>

More information about the tb-planning mailing list