[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-community
Subject:    Re: Proposal: Mailing List owner policy
From:       Johnny Jazeix <jazeix () gmail ! com>
Date:       2020-07-23 13:12:20
Message-ID: CAEtcAPEed0=EJ5wLk=tLL87SZMo9hfoePKZ4Ecz9r8aiATpaSQ () mail ! gmail ! com
[Download RAW message or body]

Hi,

should I open a sysadmin ticket to add owners/moderators or can I do it
directly for the list I moderate?

Johnny

Le jeu. 23 juil. 2020 =C3=A0 10:38, Ben Cooksley <bcooksley@kde.org> a =C3=
=A9crit :

> On Thu, Jul 23, 2020 at 4:55 PM Valorie Zimmerman
> <valorie.zimmerman@gmail.com> wrote:
> >
> > On Wed, Jul 22, 2020 at 3:31 PM Albert Astals Cid <aacid@kde.org> wrote=
:
> >>
> >> Dear Community,
> >>
> >> One important part of mailing lists being healthy is
> owners/moderators[1].
> >>
> >> They moderate the lists, they help users that want to
> subscribe/unsubscribe but don't know how to, they enact emergency
> moderation in the very very seldom case that it is needed, etc.
> >>
> >> So to keep our mailing lists healthy we need to be sure to have health=
y
> list owners.
> >>
> >> In plural, more than one, because from time to time, we go on vacation
> and the list duties still need taking care of.
> >>
> >> For that I'd like to enact this policy:
> >>
> >>     Mailing lists should have at least 2 active owners, ideally 3
> [Obviously exceptions apply, like if we just started a mailing list to
> coordinate translators for a language that has no translation in KDE yet,
> we'd probably have no way to get 2 list owners]
> >>
> >> One keyword in that sentence is "active".
> >>
> >> Mailing list ownership/moderation un-activity is hard to detect.
> >>
> >> One way to potentially detect it, is by those summaries that sysadmin
> sends periodically for lists with lots of mails to moderate, but that
> doesn't cover all the cases.
> >>
> >> For example, it's possible that a mailing list has 2 owners and only
> one of them is inactive, since the other one is keeping the list in worki=
ng
> condition we don't see it as a problem, but if that person goes on holida=
y,
> then it suddenly is.
> >>
> >> For that I'd like to enact this policy sub-point:
> >>
> >>     Mailing list owners will be contacted every year asking if they ar=
e
> still active and if they want to continue being list owner or if they'd
> prefer we find a substitute.
> >>
> >> If they say "please find a substitute" or fail to answer in a given
> time frame (I'd say a month is fair), they will be removed as owners and =
in
> case the "at least 2 active owners, ideally 3" policy is broken we'll fin=
d
> a new person.
> >>
> >> Does that sound something like we could agree on?
> >
> >
> > I think this is a good idea.
> >
> >> Then the big question is "who will do this work?" Because it seems
> quite a bit of work (albeit only once a year). I would suggest the
> Community Working Group does this, as it's a way to keep our community
> healthy, but i understand it's quite some work, so i volunteer to do it i=
f
> the CWG doesn't feel this is a task they want to take on.
> >
> >
> > As a member of CWG, I think that this is a suitable task for us, and I'=
m
> willing to do it. However, surely there is a master list of all the lists
> and who the stated owners and mods are. If so, can't the sending be done
> somewhat automatically? With the answers going to the CWG or whoever, to
> find replacement people.
> >
>
> You'd need a way of catching the exceptions - the people who don't reply
> though.
> Not sure how easy that would be to automate, but it's probably possible.
>
> In terms of getting a list of all lists, we can provide one of those
> (it's attached). I'm not sure if Mailman provides anything out of the
> box that lists who the owners of a list are though.
>
> >> Things I'm missing?
> >
> >
> > Healthy lists are somewhat active. While a major protective duty of
> owners and mods is to keep spam out and keep conversations moving in a
> positive way, another is to keep the list active by bringing to it
> appropriate topics of discussion. I don't want that forgotten. Too often
> issues are discussed in IRC and never brought to the list where they ough=
t
> to be.
> >
> >> Improvement suggestions?
> >>
> >> Cheers,
> >>   Albert
> >>
> >> [1] yes, i know they are not the same, but since one is a subset of th=
e
> other, let's pretend they are.
> >
> >
> > I would like to hear from Sysadmin how many lists we have and how many
> owners and if there is a way to automatically send an email to all owners
> along with the names of the lists they administer.
> >
> > Valorie
>
> Cheers,
> Ben
>
> >
> > --
> > http://about.me/valoriez - pronouns: she/her
> >
> >
>

[Attachment #3 (text/html)]

<div dir="ltr"><div>Hi,</div><div><br></div><div>should I open a sysadmin ticket to \
add owners/moderators or can I do it directly for the list I \
moderate?</div><div><br></div><div>Johnny<br></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">Le  jeu. 23 juil. 2020 Ã   \
10:38, Ben Cooksley &lt;<a href="mailto:bcooksley@kde.org">bcooksley@kde.org</a>&gt; \
a écrit  :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, Jul 23, 2020 \
at 4:55 PM Valorie Zimmerman<br> &lt;<a href="mailto:valorie.zimmerman@gmail.com" \
target="_blank">valorie.zimmerman@gmail.com</a>&gt; wrote:<br> &gt;<br>
&gt; On Wed, Jul 22, 2020 at 3:31 PM Albert Astals Cid &lt;<a \
href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>&gt; wrote:<br> \
&gt;&gt;<br> &gt;&gt; Dear Community,<br>
&gt;&gt;<br>
&gt;&gt; One important part of mailing lists being healthy is \
owners/moderators[1].<br> &gt;&gt;<br>
&gt;&gt; They moderate the lists, they help users that want to subscribe/unsubscribe \
but don&#39;t know how to, they enact emergency moderation in the very very seldom \
case that it is needed, etc.<br> &gt;&gt;<br>
&gt;&gt; So to keep our mailing lists healthy we need to be sure to have healthy list \
owners.<br> &gt;&gt;<br>
&gt;&gt; In plural, more than one, because from time to time, we go on vacation and \
the list duties still need taking care of.<br> &gt;&gt;<br>
&gt;&gt; For that I&#39;d like to enact this policy:<br>
&gt;&gt;<br>
&gt;&gt;        Mailing lists should have at least 2 active owners, ideally 3 \
[Obviously exceptions apply, like if we just started a mailing list to coordinate \
translators for a language that has no translation in KDE yet, we&#39;d probably have \
no way to get 2 list owners]<br> &gt;&gt;<br>
&gt;&gt; One keyword in that sentence is &quot;active&quot;.<br>
&gt;&gt;<br>
&gt;&gt; Mailing list ownership/moderation un-activity is hard to detect.<br>
&gt;&gt;<br>
&gt;&gt; One way to potentially detect it, is by those summaries that sysadmin sends \
periodically for lists with lots of mails to moderate, but that doesn&#39;t cover all \
the cases.<br> &gt;&gt;<br>
&gt;&gt; For example, it&#39;s possible that a mailing list has 2 owners and only one \
of them is inactive, since the other one is keeping the list in working condition we \
don&#39;t see it as a problem, but if that person goes on holiday, then it suddenly \
is.<br> &gt;&gt;<br>
&gt;&gt; For that I&#39;d like to enact this policy sub-point:<br>
&gt;&gt;<br>
&gt;&gt;        Mailing list owners will be contacted every year asking if they are \
still active and if they want to continue being list owner or if they&#39;d prefer we \
find a substitute.<br> &gt;&gt;<br>
&gt;&gt; If they say &quot;please find a substitute&quot; or fail to answer in a \
given time frame (I&#39;d say a month is fair), they will be removed as owners and in \
case the &quot;at least 2 active owners, ideally 3&quot; policy is broken we&#39;ll \
find a new person.<br> &gt;&gt;<br>
&gt;&gt; Does that sound something like we could agree on?<br>
&gt;<br>
&gt;<br>
&gt; I think this is a good idea.<br>
&gt;<br>
&gt;&gt; Then the big question is &quot;who will do this work?&quot; Because it seems \
quite a bit of work (albeit only once a year). I would suggest the Community Working \
Group does this, as it&#39;s a way to keep our community healthy, but i understand \
it&#39;s quite some work, so i volunteer to do it if the CWG doesn&#39;t feel this is \
a task they want to take on.<br> &gt;<br>
&gt;<br>
&gt; As a member of CWG, I think that this is a suitable task for us, and I&#39;m \
willing to do it. However, surely there is a master list of all the lists and who the \
stated owners and mods are. If so, can&#39;t the sending be done somewhat \
automatically? With the answers going to the CWG or whoever, to find replacement \
people.<br> &gt;<br>
<br>
You&#39;d need a way of catching the exceptions - the people who don&#39;t reply \
though.<br> Not sure how easy that would be to automate, but it&#39;s probably \
possible.<br> <br>
In terms of getting a list of all lists, we can provide one of those<br>
(it&#39;s attached). I&#39;m not sure if Mailman provides anything out of the<br>
box that lists who the owners of a list are though.<br>
<br>
&gt;&gt; Things I&#39;m missing?<br>
&gt;<br>
&gt;<br>
&gt; Healthy lists are somewhat active. While a major protective duty of owners and \
mods is to keep spam out and keep conversations moving in a positive way, another is \
to keep the list active by bringing to it appropriate topics of discussion. I \
don&#39;t want that forgotten. Too often issues are discussed in IRC and never \
brought to the list where they ought to be.<br> &gt;<br>
&gt;&gt; Improvement suggestions?<br>
&gt;&gt;<br>
&gt;&gt; Cheers,<br>
&gt;&gt;     Albert<br>
&gt;&gt;<br>
&gt;&gt; [1] yes, i know they are not the same, but since one is a subset of the \
other, let&#39;s pretend they are.<br> &gt;<br>
&gt;<br>
&gt; I would like to hear from Sysadmin how many lists we have and how many owners \
and if there is a way to automatically send an email to all owners along with the \
names of the lists they administer.<br> &gt;<br>
&gt; Valorie<br>
<br>
Cheers,<br>
Ben<br>
<br>
&gt;<br>
&gt; --<br>
&gt; <a href="http://about.me/valoriez" rel="noreferrer" \
target="_blank">http://about.me/valoriez</a> - pronouns: she/her<br> &gt;<br>
&gt;<br>
</blockquote></div>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic