Change of release and governance model for Thunderbird

Archaeopteryx archaeopteryx at
Tue Jul 17 10:09:51 UTC 2012

> On 7/10/2012 1:50 PM, Ben Bucksch wrote:
> So what can we do to gel a viable community around Thunderbird?
> rkent


there has been much discussion and it's difficult to choose where to 
post my response to all this.

Getting new contributors, not only now, is key, else the project is dead 
as always some people will leave for various reasons. So Thunderbird 
needs a central, easy to find 'Get Involved' page which ideally is also 
linked in signatures of existing contributors in the usual communication 
channels (newsgroups, forums).

To help existing and new contributors, these points are in my humble 
opinion necessary:
1. (Faster) support by Mozilla for getting Gecko core 
changes/enhancements into trunk, e.g. the auto-height feature for 
2. Sometimes people land something which is very pre-alpha and breaks 
some things, but no tests, and postpone fixing this until short before 
release (or don't fix it because they are too busy). So someone has to 
care about keeping the tree in good shape that people can start to hack.
3. Getting feedback/input before hacking on an issue must be fast. It's 
very disappointing to get rejected or now responses.
4. If something can be used in more than Firefox, it should be written 
as a modulo so it can be easily integrated in Thunderbird and doesn't 
bind too much developers porting it to Thunderbird.
5. Provide documentation: While user-created documented has usually the 
best quality, an easily browsable, complete documentation is a big 
support for development: The only Doxygen generated comm-central 
documentation I know of is 2.5 years old:

Furthermore, it would helpful to know when contracts for currently 
paid-only features like new mail addresses and attachment services end 
so free implementations like (S)FTP can land.


More information about the tb-planning mailing list