<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Ryan Sipes wrote on 03.12.18 22:58:<br>
</div>
<blockquote type="cite"
cite="mid:a66291aa-e675-c313-9b02-f4d0fe465404@thunderbird.net">
<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 href="https://developer.elementary.io/"
moz-do-not-send="true">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>
</blockquote>
<p><br>
</p>
<p>Yes. that would be nice. Condition for joining should be that
you're not only addon developer, but willing to actively
participate in the implementation of new APIs.</p>
<p><br>
</p>
<p>I think WebExperiments are a also great opportunity for
grass-roots action.</p>
<ol>
<li>Individual addon developers can implement an API that they are
lacking, and use it immediately in their addon, without waiting
for Thunderbird.</li>
<li>Then, they can generalize the API, make it generic for other
addons to use</li>
<li>They can propose the API for inclusion, and seasoned
developers can look over the API, improve it. (This step is
important to keep the public APIs consistent, generic, stable,
and of high quality.)<br>
</li>
<li>It's included in Thunderbird<br>
</li>
</ol>
<p><br>
</p>
</body>
</html>