<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 2020-05-15 12:42, Kai Engert wrote:<br>
</div>
<blockquote type="cite"
cite="mid:49be18f9-5451-7fbc-24b6-0343f61cdb8c@kuix.de">Hi Magnus,
thanks for the initiative. Here are some thoughts on your
suggestions:
<br>
<br>
With a mailman listed hosted by Mozilla, the project has full
control over the archive.
<br>
<br>
</blockquote>
<p>We'd still have full control over the groups we own on topicbox.</p>
<blockquote type="cite"
cite="mid:49be18f9-5451-7fbc-24b6-0343f61cdb8c@kuix.de">Should
Thunderbird ever decide to stop using the services of the Topicbox
commercial provider, what will happen to the archive of past
discussions on lists that were hosted on Topicbox?
<br>
<br>
</blockquote>
<p>Past archives can be imported <a moz-do-not-send="true"
href="https://www.topicbox.com/pricing">manually per request</a>.</p>
<p>I don't know if there's any export feature, but if we want we
could have a mailbox subscribed for this purpose only. </p>
<blockquote type="cite"
cite="mid:49be18f9-5451-7fbc-24b6-0343f61cdb8c@kuix.de">We might
want to keep tb-planning as a traditional Mailman list, with its
traditional archive. Keeping a permanent archive of the high level
discussions seems more interesting than the archive of short lived
technical discussions.
<br>
<br>
The Maildev list could be removed, and a new list of development
topics created on Topicbox. Given Topicbox already hosts the
"Add-on Developers" list, and the "Thunderbird UX" list, this
seems consistent.
<br>
<br>
The naming should be chosen carefully. Is this list really about
"Mail" development, only? What about discussions on Calendar, Chat
or Feeds?
<br>
</blockquote>
<p>I agree per topic conversations is the way to go. As per my other
mail, circles will often be *very* small though.</p>
-Magnus
</body>
</html>