--===============6814659846865268630==
Content-Type: multipart/alternative; boundary=047d7bfea09a37d02704e4fa86f7

--047d7bfea09a37d02704e4fa86f7
Content-Type: text/plain; charset=ISO-8859-1

Hi folks, I'm replying to this old thread because there has been some work
behind the scenes on this banning discussion. Response below.

On Tue, Aug 6, 2013 at 10:54 AM, Anne Wilson <cannewilson@googlemail.com>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 05/08/13 12:29, Anne Wilson wrote:
> > Some time ago a user started a page on http://community.kde.org on
> > which he detailed things that he considered to be wrong with KDE
> > software.  The comments were largely subjective, and in many cases
> > demonstrated things that were not the general experience.  At that
> > point he was asked to substantiate his complaints by pointing to
> > bug reports.
> >
> > That strategy backfired, as he then began creating a barrage of
> > bug reports, creating a good deal of work for triagers who have to
> > decide whether the report is a duplicate of some other, or invalid
> > for any reason.  Up to now people have been very patient with him,
> > but it has come to our notice that he has crossed a line.
> >
> > He has now begun defacing other pages, adding links to his
> > comments page and/or his bug reports.  This basically results in
> > what should be "official" information, posted by developers of the
> > application in question, being questionable, in that the reader
> > cannot easily differentiate his input.
> >
> > This contributor's input has repeatedly violated the Code of
> > Conduct ( http://www.kde.org/code-of-conduct/). In view of this we
> > have reached the point where we believe that he should be banned
> > from posting on the wikis, and his comments completely removed.
> > This will now take place.
>
> A 2-week ban has been put in place and the contributor has been
> invited to discuss the problem and possible resolution.  If resolution
> is reached the ban will be immediately removed.  If no resolution
> appears to be possible we will go ahead, make the ban permanent and
> remove his content.
>
> I think this is the first time in 5 years that we have had to take
> such a step.  We don't do it lightly, and still hope that the
> contributor will talk to us and enable suitable conclusion to the story.
>
> Anne
>

The CWG was asked to take a look at this banning, because 1. an analysis of
this user's posts did not appear to violate the CoC, and 2. there was no
response to the ban from the banned user.

The analysis was quite complete, and can be found on the KDE-WWW list
archives:

http://kde.6490.n7.nabble.com/Draft-message-to-Community-ML-comments-please-tp1539530p1539662.html

In light of the facts, the web team has been asked by the CWG to look again
at the evidence, and re-think this ban. It does not seem justified to us.

My own personal opinion: I love seeing users with this sort of energy. I
wish he had been recruited into the Quality team, or BugSquad, or both. I
hope that someone from the web team will contact him and suggest that.

Valorie, for the CWG

--047d7bfea09a37d02704e4fa86f7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi folks, I&#39;m replying to this old thread because=
 there has been some work behind the scenes on this banning discussion. Res=
ponse below.</div><div><br></div>On Tue, Aug 6, 2013 at 10:54 AM, Anne Wils=
on <span dir=3D"ltr">&lt;<a href=3D"mailto:cannewilson@googlemail.com" targ=
et=3D"_blank">cannewilson@googlemail.com</a>&gt;</span> wrote:<br>

<div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border=
-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div=
 class=3D"im">

-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
</div><div class=3D"im">On 05/08/13 12:29, Anne Wilson wrote:<br>
&gt; Some time ago a user started a page on <a href=3D"http://community.kde=
.org" target=3D"_blank">http://community.kde.org</a> on<br>
&gt; which he detailed things that he considered to be wrong with KDE<br>
&gt; software. =A0The comments were largely subjective, and in many cases<b=
r>
&gt; demonstrated things that were not the general experience. =A0At that<b=
r>
&gt; point he was asked to substantiate his complaints by pointing to<br>
&gt; bug reports.<br>
&gt;<br>
&gt; That strategy backfired, as he then began creating a barrage of<br>
&gt; bug reports, creating a good deal of work for triagers who have to<br>
&gt; decide whether the report is a duplicate of some other, or invalid<br>
&gt; for any reason. =A0Up to now people have been very patient with him,<b=
r>
&gt; but it has come to our notice that he has crossed a line.<br>
&gt;<br>
&gt; He has now begun defacing other pages, adding links to his<br>
&gt; comments page and/or his bug reports. =A0This basically results in<br>
&gt; what should be &quot;official&quot; information, posted by developers =
of the<br>
&gt; application in question, being questionable, in that the reader<br>
&gt; cannot easily differentiate his input.<br>
&gt;<br>
&gt; This contributor&#39;s input has repeatedly violated the Code of<br>
&gt; Conduct ( <a href=3D"http://www.kde.org/code-of-conduct/" target=3D"_b=
lank">http://www.kde.org/code-of-conduct/</a>). In view of this we<br>
&gt; have reached the point where we believe that he should be banned<br>
&gt; from posting on the wikis, and his comments completely removed.<br>
&gt; This will now take place.<br>
<br>
</div>A 2-week ban has been put in place and the contributor has been<br>
invited to discuss the problem and possible resolution. =A0If resolution<br=
>
is reached the ban will be immediately removed. =A0If no resolution<br>
appears to be possible we will go ahead, make the ban permanent and<br>
remove his content.<br>
<br>
I think this is the first time in 5 years that we have had to take<br>
such a step. =A0We don&#39;t do it lightly, and still hope that the<br>
contributor will talk to us and enable suitable conclusion to the story.<br=
>
<br>
Anne<br>
<div class=3D"im"></div></blockquote></div><div class=3D"gmail_extra"><br><=
/div>The CWG was asked to take a look at this banning, because 1. an analys=
is of this user&#39;s posts did not appear to violate the CoC, and 2. there=
 was no response to the ban from the banned user.</div>

<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">The analysi=
s was quite complete, and can be found on the KDE-WWW list archives:</div><=
div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><a href=3D"h=
ttp://kde.6490.n7.nabble.com/Draft-message-to-Community-ML-comments-please-=
tp1539530p1539662.html">http://kde.6490.n7.nabble.com/Draft-message-to-Comm=
unity-ML-comments-please-tp1539530p1539662.html</a></div>

<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">In light of=
 the facts, the web team has been asked by the CWG to look again at the evi=
dence, and re-think this ban. It does not seem justified to us.</div><div c=
lass=3D"gmail_extra">

<br></div><div class=3D"gmail_extra">My own personal opinion: I love seeing=
 users with this sort of energy. I wish he had been recruited into the Qual=
ity team, or BugSquad, or both. I hope that someone from the web team will =
contact him and suggest that.</div>

<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Valorie, fo=
r the CWG
</div></div>

--047d7bfea09a37d02704e4fa86f7--

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

_______________________________________________
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
--===============6814659846865268630==--