[Council Meeting] Minutes from 2019-10-24
kewisch at thunderbird.net
Tue Nov 12 07:49:48 UTC 2019
I am glad you ask, it is actually fairly easy to get started on this. The quickest way would be to start this out as a web extension experiment. You can just write your API together with some code that is using it and if you make a mistake you can quickly reload to using about:debugging.
Once you are happy it just takes a little bit of changing the boiler plate to make it ready for comm-central. Writing tests depends on the API but there are some good test examples in our code. They can be xpcshell if possible (preferred) or mochtests if necessary.
I think everything aside from the tests is documented, maybe you can check out developer.thunderbird.net and share your experience.
> On 11. Nov 2019, at 11:23 PM, Patrick Cloke <patrick at cloke.us> wrote:
> Hey Geoff,
> That’s definitely in the works too. We should also make sure that it isn’t just one person working on this! Is it documented how to add a new API? E.g. I’ve considered if there are reasonable ones to add for chat, but have no idea where to even start!
>> On Mon, Nov 11, 2019, at 4:40 PM, Geoff Lankow wrote:
>> On 12/11/2019 03:40, Patrick Cloke wrote:
>> > * Ryan brought up the topic of publishing an add-ons roadmap, in
>> > response to community feedback.
>> > * Wayne brought up that there isn't agreement in philosophy on the
>> > amount of resources to use on supporting add-ons. The amount of
>> > support necessary is likely disproportionate to the number of add-ons
>> > and add-on users. Some amount of commitment should be made.
>> > * Jörg identified that many power users (the biggest advocates for
>> > Thunderbird) likely use add-ons.
>> > * Patrick and Ryan discussed what the root cause might be: do we
>> > need more documentation? Guidance?
>> More personnel? There's much more we could/should be doing but I'm
>> swamped with a number of big projects on the go. The current rate of
>> about one meaningful API addition per release cycle is nowhere near enough.
>> tb-planning mailing list
>> tb-planning at mozilla.org
> tb-planning mailing list
> tb-planning at mozilla.org
More information about the tb-planning