RFC: rationalisation of Stow mailing lists

--===============1277233277537172809==
Content-Type: multipart/alternative; boundary=f46d041825f00f845104b34f653a

--f46d041825f00f845104b34f653a
Content-Type: text/plain; charset=UTF-8

Good idea. (Based on the traffic, maybe even two lists are sufficient? 1.
info 2. devel&users)

On Sunday, December 4, 2011, Adam Spiers wrote:

> [This has been deliberately cross-posted to 3 lists; please reply to all.]
>
> Hi all,
>
> We currently have four mailing lists for stow.  Given the extremely
> low traffic, I think that's at least one too many.  Here are the
> subscription statistics:
>
>  info-stow:  26 (of which 7 appear to be list archivers)
>  help-stow:  21 (of which 6 appear to be list archivers)
>  bug-stow:   19 (of which 5 appear to be list archivers)
>  stow-devel: 21 (of which 6 appear to be list archivers)
>
> There is a large amount of overlap in subscribers between the lists,
> and I suspect that most of the discrepancies are due to spreading
> ourselves too thinly and not making it clear what belongs where.  For
> example, if you want to discuss an idea about a new way of using Stow
> (and this has happened to me and one other person in the last few
> days), it's not really a plea for help, or a bug report, or a
> development topic, or an announcement, so not of those four lists are
> named in a way which suggests that your post belongs in that list.
>
> Therefore I propose the following:
>
>  - Keep info-stow as an announcements-only list (this seems to be
>    the GNU convention for info-*).
>
>  - Keep stow-devel as a developers-only list.
>
>  - Merge help-stow and bug-stow into a new `stow-users' list.
>    Technically speaking, this would involve closing the two old
>    lists, creating the new one, automatically signing up all human
>    subscribers of the old lists to the new one, and informing the
>    mail archivers of the change.
>
> Thoughts?
>
> Thanks,
> Adam
>
> _______________________________________________
> Help-stow mailing list
> [email protected]
> https://lists.gnu.org/mailman/listinfo/help-stow
>

--f46d041825f00f845104b34f653a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Good idea. (Based on the traffic, maybe even two lists are sufficient? 1. i=
nfo 2. devel&amp;users)<br><br>On Sunday, December 4, 2011, Adam Spiers  wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">
[This has been deliberately cross-posted to 3 lists; please reply to all.]<=
br>

<br>
Hi all,<br>
<br>
We currently have four mailing lists for stow. =C2=A0Given the extremely<br=
>
low traffic, I think that&#39;s at least one too many. =C2=A0Here are the<b=
r>
subscription statistics:<br>
<br>
 =C2=A0info-stow: =C2=A026 (of which 7 appear to be list archivers)<br>
 =C2=A0help-stow: =C2=A021 (of which 6 appear to be list archivers)<br>
 =C2=A0bug-stow: =C2=A0 19 (of which 5 appear to be list archivers)<br>
 =C2=A0stow-devel: 21 (of which 6 appear to be list archivers)<br>
<br>
There is a large amount of overlap in subscribers between the lists,<br>
and I suspect that most of the discrepancies are due to spreading<br>
ourselves too thinly and not making it clear what belongs where. =C2=A0For<=
br>
example, if you want to discuss an idea about a new way of using Stow<br>
(and this has happened to me and one other person in the last few<br>
days), it&#39;s not really a plea for help, or a bug report, or a<br>
development topic, or an announcement, so not of those four lists are<br>
named in a way which suggests that your post belongs in that list.<br>
<br>
Therefore I propose the following:<br>
<br>
 =C2=A0- Keep info-stow as an announcements-only list (this seems to be<br>
 =C2=A0 =C2=A0the GNU convention for info-*).<br>
<br>
 =C2=A0- Keep stow-devel as a developers-only list.<br>
<br>
 =C2=A0- Merge help-stow and bug-stow into a new `stow-users&#39; list.<br>
 =C2=A0 =C2=A0Technically speaking, this would involve closing the two old<=
br>
 =C2=A0 =C2=A0lists, creating the new one, automatically signing up all hum=
an<br>
 =C2=A0 =C2=A0subscribers of the old lists to the new one, and informing th=
e<br>
 =C2=A0 =C2=A0mail archivers of the change.<br>
<br>
Thoughts?<br>
<br>
Thanks,<br>
Adam<br>
<br>
_______________________________________________<br>
Help-stow mailing list<br>
<a>[email protected]</a><br>
<a href=3D"https://lists.gnu.org/mailman/listinfo/help-stow" target=3D"_bla=
nk">https://lists.gnu.org/mailman/listinfo/help-stow</a><br>
</blockquote>

--f46d041825f00f845104b34f653a--


--===============1277233277537172809==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Help-stow mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/help-stow

--===============1277233277537172809==--