<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 2020-02-02 01:09, Óvári wrote:<br>
</div>
<blockquote type="cite"
cite="mid:ea9c6e2e-bffb-75e0-c540-9314fe2ebff0@zoho.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">On 2/2/20 8:46 am, Magnus Melin
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:d5ada5b0-824e-3507-518f-c87d2a466cdf@iki.fi">
<blockquote type="cite" style="color: #000000;">> <br>
> ... Integrating some of the best parts of the more
popular add-ons into core. <br>
<br>
Has the council taken a decision on this matter? It has been
quite contentious. <br>
</blockquote>
<br>
The council has approved the job reqs. In particular the main
parts of Import/Export tools we want to integrate, or well,
rather the corresponding functionality. </blockquote>
<p>Would the council please advise the council's position on:</p>
<p>1. integrating CardBook; and<br>
<a class="moz-txt-link-freetext"
href="https://gitlab.com/CardBook/CardBook#features"
moz-do-not-send="true">https://gitlab.com/CardBook/CardBook#features</a><br>
</p>
<p>2. enabling the add-on infrastructure to enable CardBook to be
rewritten to be functional with the next Thunderbird ESR
version.<br>
<a class="moz-txt-link-freetext"
href="https://addons.thunderbird.net/addon/cardbook/"
moz-do-not-send="true">https://addons.thunderbird.net/addon/cardbook/</a><br>
</p>
<br>
</blockquote>
<p>There are plans to integrate it as such, but some of its
functionality we'd like to achieve. </p>
<p>For #2, the only route for that is through an experiment - which
is already possible. In general, Thunderbird can't expose APIs to
do things it can't do internally.</p>
<p> -Magnus<br>
</p>
<p><br>
</p>
</body>
</html>