<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I couldn't agree more.</p>
<p>Last week I pledged to lead an effort to set up an "Add-ons
Steering Committee", a group that could get together and talk
through the add-ons situation as it stands and propose some ideas
on how we might best address problems in the Thunderbird add-ons
community.</p>
<p>What does this list think of that idea? I've begun talking about
an effort to update documentation for add-on developers (with new
tutorials and maybe even a pretty, detailed landing page <a
moz-do-not-send="true" href="https://developer.elementary.io/">like
other projects have done</a>).</p>
<p>Since this is an area where there appears to be a lot of passion,
I would hope that we have volunteers who would be willing to
participate.<br>
</p>
<pre class="moz-signature" cols="72">Ryan Sipes
Community Manager
Thunderbird</pre>
<div class="moz-cite-prefix">On 12/2/18 7:29 AM, Ben Bucksch wrote:<br>
</div>
<blockquote type="cite"
cite="mid:49bb0856-7eb0-22ba-b8fc-709be5efab85@beonex.com">Magnus
Melin wrote on 02.12.18 13:12:
<br>
<blockquote type="cite">While I can understand losing add-ons is
not nice, there currently isn't much or any overlap for being on
a supported release. That is, downgrading would just leave you
on an EOL'd release which is not in the users best interest.
<br>
</blockquote>
<br>
I agree. Leaving users with an application that has *known*
security holes is not an option.
<br>
<br>
<br>
Instead, we should make more efforts keeping the addons working.
The TB Council itself obviously can't do this themselves, so this
needs efforts from the community.
<br>
<br>
_______________________________________________
<br>
tb-planning mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:tb-planning@mozilla.org">tb-planning@mozilla.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/tb-planning">https://mail.mozilla.org/listinfo/tb-planning</a>
<br>
</blockquote>
</body>
</html>