Fwd: Unintended changes at community.kde.org?

Anne Wilson annew at kde.org
Mon Aug 5 09:01:42 UTC 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/08/13 09:19, Ben Cooksley wrote:
> ---------- Forwarded message ---------- From: Frank Reininghaus
> <frank78ac at googlemail.com> Date: Sat, Aug 3, 2013 at 3:45 AM 
> Subject: Unintended changes at community.kde.org? To:
> plasma-devel at kde.org
> 
> 
> Hi everyone,
> 
> (please CC me in any replies, I'm not subscribed)
> 
> I recently had a look at the Dolphin pages at community.kde.org.
> We don't actually use them much - Peter and I mostly used 
> http://community.kde.org/Dolphin/Dolphin-2.0-Status to list the
> things that still needed to be done for the new view engine before
> the KDE 4.8 release (the page is mostly empty now because the vast
> majority of these issues had been resolved a long time ago).
> 
> I found out that a certain user 'Cyberhacker' has recently started 
> adding links to bug reports to the page:
> 
> http://community.kde.org/index.php?title=Dolphin/Dolphin-2.0-Status&action=history
>
>  It's not hard to guess which bugs.kde.org user 'Cyberhacker' is.
> 
> The reason why I'm telling you about this is that he did the same 
> thing with the "Plasma/Tasks" page:
> 
> http://community.kde.org/index.php?title=Plasma/Tasks&action=history
>
>  I don't know how much you use that page, but if you do, be aware
> that not all content on the page is made by the Plasma team.
> 
> Moreover, 'Cyberhacker' has set up this page:
> 
> http://community.kde.org/Back_to_basics
> 
> which is linked to from the community.kde.org start page with the 
> comment "Let's make KDE better!" - I'm not sure if we want that.
> 
I'm very aware of cyperhacker's "back to basics" page, and feel at
least in part responsible for his activity in linking from other
pages.  That was never my intention.

When he first started creating the page he was making strong comments
about things supposedly wrong, when they were obviously not the
experience of most people.  At that point I told him that he could not
continue accusing in this way without evidence, and his statements
should point to relevant bug reports (not that I expected him to
create an avalanche of his own reports).

In view of the escalation of the problem, I'm wondering if it would be
sensible to discuss this (without naming him or the pages, at least at
first) on the new community ML.  If he's damaging "official" pages he
needs to be stopped, but I don't want to give him fuel to say that he
was blocked from making legitimate complaint.

Comments?

Anne
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlH/afMACgkQj93fyh4cnBduOACfbazNc9Wx2ZaNdgYkNmr+nv0s
cZMAmwVQ0o51+LYZ/JvcIwmX+eeQ9xpw
=REeE
-----END PGP SIGNATURE-----


More information about the kde-www mailing list