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

List:       kde-community
Subject:    Re: Proposal: Mailing List owner policy
From:       Valorie Zimmerman <valorie.zimmerman () gmail ! com>
Date:       2020-08-26 1:16:13
Message-ID: CACpu026PVqq7L1AS+4Zhs5OT2kpJz3i-R4vnzRBmhXUN8VxU-w () mail ! gmail ! com
[Download RAW message or body]

Unfortunately 9 UTC = 2 am here. But I will submit some notes about it. -v

On Tue, Aug 25, 2020 at 2:28 PM Albert Astals Cid <aacid@kde.org> wrote:

> El dijous, 23 de juliol de 2020, a les 0:31:29 CEST, Albert Astals Cid va
> escriure:
> > 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 healthy
> 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 working
> condition we don't see it as a problem, but if that person goes on holiday,
> 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 are
> 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 find a new
> person.
> >
> > Does that sound something like we could agree on?
> >
> > 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 if the CWG doesn't
> feel this is a task they want to take on.
> >
> > Things I'm missing?
> >
> > Improvement suggestions?
>
> So it seems there was some agreement that is something that could improve
> but we didn't 100% agree on what to do. I've scheduled an Akademy BoF,
> hopefully we can reach to a conclusion there.
>
> https://community.kde.org/Akademy/2020/Tuesday#Room_02_-_8th_September
>
> Cheers,
>   Albert
>
> >
> > Cheers,
> >   Albert
> >
> > [1] yes, i know they are not the same, but since one is a subset of the
> other, let's pretend they are.
> >
> >
> >
>
>
>
>
>

-- 
http://about.me/valoriez - pronouns: she/her

[Attachment #3 (text/html)]

<div dir="ltr">Unfortunately 9 UTC = 2 am here. But I will submit some notes about \
it. -v</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, \
Aug 25, 2020 at 2:28 PM Albert Astals Cid &lt;<a \
href="mailto:aacid@kde.org">aacid@kde.org</a>&gt; wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">El dijous, 23 de juliol de 2020, a les 0:31:29 \
CEST, Albert Astals Cid va escriure:<br> &gt; Dear Community,<br>
&gt; <br>
&gt; One important part of mailing lists being healthy is owners/moderators[1].<br>
&gt; <br>
&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; <br>
&gt; So to keep our mailing lists healthy we need to be sure to have healthy list \
owners.<br> &gt; <br>
&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; <br>
&gt; For that I&#39;d like to enact this policy:<br>
&gt;           <br>
&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; <br>
&gt; One keyword in that sentence is &quot;active&quot;.<br>
&gt; <br>
&gt; Mailing list ownership/moderation un-activity is hard to detect.<br>
&gt; <br>
&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; <br>
&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; <br>
&gt; For that I&#39;d like to enact this policy sub-point:<br>
&gt; <br>
&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; <br>
&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; <br>
&gt; Does that sound something like we could agree on?<br>
&gt; <br>
&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; Things I&#39;m missing?<br>
&gt; <br>
&gt; Improvement suggestions?<br>
<br>
So it seems there was some agreement that is something that could improve but we \
didn&#39;t 100% agree on what to do. I&#39;ve scheduled an Akademy BoF, hopefully we \
can reach to a conclusion there.<br> <br>
<a href="https://community.kde.org/Akademy/2020/Tuesday#Room_02_-_8th_September" \
rel="noreferrer" target="_blank">https://community.kde.org/Akademy/2020/Tuesday#Room_02_-_8th_September</a><br>
 <br>
Cheers,<br>
   Albert<br>
<br>
&gt; <br>
&gt; Cheers,<br>
&gt;     Albert<br>
&gt; <br>
&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; <br>
<br>
<br>
<br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" \
class="gmail_signature"><div dir="ltr"><div><a href="http://about.me/valoriez" \
target="_blank">http://about.me/valoriez</a>  - pronouns: \
she/her<br><br><br></div></div></div>



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

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