Improve extension APIs for TB
Wayne Mery (vn)
vseerror at Lehigh.EDU
Wed Oct 26 13:34:13 UTC 2011
Does "no further effort" mean that STEEL is the current state of the
art, but no longer a strategic direction?
Or is stdlib the current state of the art? (If so, it's missing from
Expanding on BenB's initial statement, there has been change over time:
- ("Last time we discussed this")
which is to be expected. But this space seems (from my uninformed
vantage point) to have suffered some churn, and lack of steady attention
But more importantly, if extensions is a strategic part of Thunderbird
ecosystem, perhaps the extensions ecosystem needs to be more "in
your/our face", deserving of a bullet point (along side the features and
experiments bullets) in meetings and such?
On 10/26/2011 4:16 AM, Jonathan Protzenko wrote:
> Last time we discussed this on this list, the bottom line was : no
> further effort will be put into STEEL. I think the proposed way to go is
> https://bugzilla.mozilla.org/show_bug.cgi?id=662367 although I'm really
> too busy to make it happen right now.
> On Wed 26 Oct 2011 08:23:33 AM CEST, Ludovic Hirlimann wrote:
>> On 25/10/11 21:29, Ben Bucksch wrote:
>>> Following a discussion on IRC, maybe I suggest a more planned
>>> approach to improve our extensibility?
>>> So, how about starting it by creating a Wiki page?
>> Would that mean extending steel/fuel ?
>> Thunderbird QAhttps://wiki.mozilla.org/Thunderbird:Testing
>> tb-planning mailing list
>> tb-planning at mozilla.org
> tb-planning mailing list
> tb-planning at mozilla.org
More information about the tb-planning