<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<p>Why reduce the traffic of an already quiet list?</p>
<p>I doubt making a separate list for technical discussion(s) will
increase the traffic <i>but</i> it could splinter the community.</p>
<p>To be honest, unless this list got sunk so much in a flurry of
technical questions appropriate for a Linux/Open Source related
mailing list ... the absolute horror ... I'd be inclined to leave
it as it is.</p>
<p><br>
</p>
<p>...unless someone knows of a contingent who want to activate such
a list that I/we(?) don't know about :)</p>
<p><br>
</p>
<p>DSL<br>
</p>
<div class="moz-cite-prefix">On 31/08/2021 1:46 am, Russell Coker
via linux-aus wrote:<br>
</div>
<blockquote type="cite" cite="mid:2548892.hIFruQV7Wq@xev">
<pre class="moz-quote-pre" wrap="">Past discussions here have had a conclusion that using this list for general
Linux support is OK. But the majority of traffic here isn't about that which
will be a disincentive to people asking such questions.
Should we have a separate list for Linux support in Australia to be welcoming
to such queries?
I received more replies to my message about hands-on training from the luv-
main list than this list in spite of this list having more than twice as many
subscribers. Does that mean this list isn't reaching the sort of people who
want to learn about how to configure Postfix etc and is mostly about the sort
of people who are interested in LCA CFPs? That isn't a bad thing, but if so
then we probably need a separate list for the people who aren't planning to
present at LCA.
<a class="moz-txt-link-freetext" href="http://lists.linux.org.au/pipermail/lugcomms/">http://lists.linux.org.au/pipermail/lugcomms/</a>
Finally we have the lugcomms list which we tried to resurrect months ago. One
possibility would be to repurpose that list for announcements to general LUG
members which members of each of the LUGs could forward to their groups by
whatever method is most appropriate.
What do you think?
</pre>
</blockquote>
</body>
</html>