<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 3/25/21 4:49 AM, Magnus Melin wrote:<br>
</div>
<blockquote type="cite"
cite="mid:78844839-6329-04be-53ee-86bd318e4ede@iki.fi">On
2021-03-25 08:19, ISHIKAWA,chiaki wrote:
<br>
<blockquote type="cite">So this means we can post technical
question (rather than high-level policy discussions ) to
tb-planning.
<br>
<br>
There will be only one mailing list left for tech discussion of
TB after the transition if I am not mistaken, and so tb-planning
will be the only recourse.
<br>
</blockquote>
<br>
maildev was never a forum for technical *questions*. It was
supposed to be a more moderated tb-planning... but that didn't
quite work out.
<br>
<br>
Where to send a question would depend on what the discussion is
about. If there's a targeted mailing list on our topicbox, post
it there. If it's a bug/action item, send it to bugzilla in an
appropriate component - I'd expect this is the right answer most
of the times. tb-planning would be the catch-all for things that
fall between; use an appropriate subject so uninterested parties
can ignore it.
<br>
<br>
-Magnus
</blockquote>
<p>Right, the original purpose [1] was narrowly scoped to issues
that involved "engineering council". The EC never gained steam,
so the list (d)evolved into a programming QA, which is sort of
what mdat (mozilla.dev.apps.thunderbird) newsgroup and it's
gatewayed email list dev-apps-thunderbird is about. <br>
</p>
<p>If BOTH maildev and dev-apps-thunderbird go away, there needs to
be a corresponding replacement in topicbox that is not
tb-planning.<br>
</p>
<p>[1] maildev's new subscriber message states the purpose as
originally proposed "... this list is intended as the primary
discussion forum for the Thunderbird Engineering Council. Although
the content of these discussions is public, posting to this list
is in most cases restricted to active Thunderbird and Mozilla
developers."</p>
</body>
</html>